[SOLVED] Debian 9 Taking A Long Time To Boot Lots Of Errors

Ztcoracat · 02-15-2019, 07:30 PM

I'm running Debian 9 stable on an AMD 64-bit desktop.

All was fine until I installed Linux Mint and MX-18 on their own hard drives.
Since installing those 2 distributions Debian takes a long time to boot with error messages.

There are 3 error messages at start up.

Code:

devsda1:clean
A start job is running for dev-disk byxxxx2cuuid-7ceo685e\x2de820\xx8905.device (28s / 1min 30s

Where the x's are I couldn't make out the numbers.
When the start job times out I'm greeted with the sign in screen and can sign in thus taking me to the Mate DE.

Code:

ACPI Error: Method parse/exec
mdadm: No arrays found in config file or auto

Code:

ACPI Error: Method parse/exec (Node ffff 92584e169bo)
AE_NOT_FOUND [1.208602} ACPI Error:[DSSP] Namespace 31/psargs-359)

I looked up the first error and I found something about a swap partition being an issue. I'm not sure if that's what is wrong or not and or if deleting the swap and creating another one is a good idea.

https://askubuntu.com/questions/7110...or-dev-disk-by

I have no idea if this is a grub, systemd or pc hardware issue.

What do these errors mean and how do I fix them?

Any help is appreciated:-

Ztcoracat · 02-15-2019, 09:14 PM

Code:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=ff6a9927-e1b5-4177-8957-2cc2598ec91e /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda2 during installation
UUID=d8f6b93e-dbaf-4ac3-b02a-f1fc70d558bf none            swap    sw              0       0
# swap was on /dev/sdb2 during installation
UUID=7ce0685e-e8a0-40c4-9197-317ad97f0905 none            swap    sw              0       0
# swap was on /dev/sdc2 during installation
UUID=dd5c1461-6503-48e9-af54-e4e7aa5734a1 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0

Code:

sifu@sifu-MS-7845:~$ sudo blkid
[sudo] password
/dev/sda1: UUID="ff6a9927-e1b5-4177-8957-2cc2598ec91e" TYPE="ext4" PARTUUID="000688b0-01"
/dev/sda2: UUID="d8f6b93e-dbaf-4ac3-b02a-f1fc70d558bf" TYPE="swap" PARTUUID="000688b0-02"
/dev/sdb1: LABEL="rootMX18" UUID="8d9aa50a-f6d2-47d3-9f60-13ec85b3672b" TYPE="ext4" PARTUUID="c2d23fcd-01"
/dev/sdb2: UUID="22b34198-7f33-4b7e-9ffd-77d6f96744ca" TYPE="swap" PARTUUID="c2d23fcd-02"
/dev/sdc1: UUID="0ac4246d-399a-447d-b33b-ca5b09f6f079" TYPE="ext4" PARTUUID="000ce4f3-01"
/dev/sdc2: UUID="df960

hydrurga · 02-15-2019, 09:40 PM

Does your Debian system need to access all three swap partitions?

If not, comment out the entries in fstab for the swap partitions on the other two disks.

Ztcoracat · 02-15-2019, 11:33 PM

The output of blkid for the swap partitions and the output of the fstab file for the swap partitions don't jive.

Here's blkid from the Debian 9 Mate system:

Code:

/dev/sda1: UUID="ff6a9927-e1b5-4177-8957-2cc2598ec91e" TYPE="ext4" PARTUUID="000688b0-01"
/dev/sda2: UUID="d8f6b93e-dbaf-4ac3-b02a-f1fc70d558bf" TYPE="swap" PARTUUID="000688b0-02"
/dev/sdb1: LABEL="rootMX18" UUID="8d9aa50a-f6d2-47d3-9f60-13ec85b3672b" TYPE="ext4" PARTUUID="c2d23fcd-01"
/dev/sdb2: UUID="22b34198-7f33-4b7e-9ffd-77d6f96744ca" TYPE="swap" PARTUUID="c2d23fcd-02"
/dev/sdc1: UUID="0ac4246d-399a-447d-b33b-ca5b09f6f079" TYPE="ext4" PARTUUID="000ce4f3-01"
/dev/sdc2: UUID="df96003d-7675-42ee-a14f-d9b3fd023a4c" TYPE="swap" PARTUUID="000ce4f3-02"

THIS IS THE OUTPUT THAT THE /etc/fstab FILE GAVE (after opening fstab on the distro that is booting real slow)

Code:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=ff6a9927-e1b5-4177-8957-2cc2598ec91e /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda2 during installation
UUID=d8f6b93e-dbaf-4ac3-b02a-f1fc70d558bf none            swap    sw              0       0
# swap was on /dev/sdb2 during installation
UUID=7ce0685e-e8a0-40c4-9197-317ad97f0905 none            swap    sw              0       0
# swap was on /dev/sdc2 during installation
UUID=dd5c1461-6503-48e9-af54-e4e7aa5734a1 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0

Since the UUID's are not the same when compared what is the correct way of fixing this?

I need to know how to fix this for all 3 distributions:-

Brains · 02-16-2019, 01:08 AM

Code:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=ff6a9927-e1b5-4177-8957-2cc2598ec91e /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda2 during installation
UUID=d8f6b93e-dbaf-4ac3-b02a-f1fc70d558bf none            swap    sw              0       0
# swap was on /dev/sdb2 during installation
UUID=22b34198-7f33-4b7e-9ffd-77d6f96744ca none            swap    sw              0       0
# swap was on /dev/sdc2 during installation
UUID=df96003d-7675-42ee-a14f-d9b3fd023a4c none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0

Just change the UUID entry in /etc/fstab to what is displayed by blkid. If I assume correct, Debian is on /dev/sda, thus this is what it's /etc/fstab file should look like.
EDIT: For me, the ACPI errors came in December, forgot which kernel, I think it was kernel 4.19.0.1, they still exist with 4.19.0.2, aparently according to a Ubuntu bug report, problem exist in 4.20 kernel also. Did you upgrade to backports kernel?

Ztcoracat · 02-16-2019, 03:09 AM

Quote:

Just change the UUID entry in /etc/fstab to what is displayed by blkid.

That worked. Thank You-

I no longer have the 1 min and 30 second start job running.
However, I still have this error:

Code:

mdadm:No arrays found in config file or automatically

Is this the right fix for that?

https://lists.debian.org/debian-user.../msg00845.html

Ztcoracat · 02-16-2019, 03:11 AM

Quote:

Did you upgrade to backports kernel?

No, should I?

I'm running kernel:
4.9.0-8

hemlocktree · 02-16-2019, 05:43 AM

brains - is the kernel situation due to the fact that debian is running a bit older things /kernels/etc and that it finally comes around a bit later than when it hit ubuntu earlier? seems like the delay in issues would be expected. i have been interested in debian for a long time and am curious about trying it so i am asking. thanks.

ztor - glad you got it fixed....

Brains · 02-16-2019, 11:36 AM

Quote:

Originally Posted by Ztcoracat

Code:

mdadm:No arrays found in config file or automatically

Is this the right fix for that?

https://lists.debian.org/debian-user.../msg00845.html

I don't have raid setups, I get the impression neither is yours a raid array. If I had that message I would do a backup image of the root partition, then try the recommendations in that link. As for upgrading to the backports kernel, you likely wouldn't gain anything, and if you were to need build kernel modules, you would get version conflicts with gcc and possibly libraries.

Brains · 02-16-2019, 11:46 AM

Quote:

Originally Posted by hemlocktree

brains - is the kernel situation due to the fact that debian is running a bit older things /kernels/etc and that it finally comes around a bit later than when it hit ubuntu earlier? seems like the delay in issues would be expected. i have been interested in debian for a long time and am curious about trying it so i am asking. thanks.

ztor - glad you got it fixed....

I'm not sure what's the scoop with these ACPI messages, the bug report I read was back in December when not even Ubuntu was using the 4.20 kernel by default. And does it affect other distributions? I don't know as I have not installed any other to my drive, only in VMware which uses different virtual hardware than the actual hardware. And Debian is kind of verbose when booting up, you see a lot, many other distributions are better at being quiet and not displaying anything.

hemlocktree · 02-16-2019, 12:09 PM

Thank You! Just wondering.

Ztcoracat · 02-16-2019, 02:39 PM

Quote:

Originally Posted by Brains

I don't have raid setups, I get the impression neither is yours a raid array. If I had that message I would do a backup image of the root partition, then try the recommendations in that link. As for upgrading to the backports kernel, you likely wouldn't gain anything, and if you were to need build kernel modules, you would get version conflicts with gcc and possibly libraries.

You're correct-
I don't have a raid array set up:-

To backup the /root partition I can use rsync for that right?

Brains · 02-16-2019, 02:51 PM

Quote:

Originally Posted by Ztcoracat

You're correct-
I don't have a raid array set up:-

To backup the /root partition I can use rsync for that right?

That's what I hear.
I have never used it, I use BootitBM which comes with image for DOS, personal data and Debian's package cache and lists directories are in a separate data drive. BootitBM, like Clonezilla (apparently, have not used it either), makes compressed images of used space only.
Takes 3 minutes to create a backup of my Debian, image file size is 3.34GB. Then it's easy to take risks, if there's a problem, rather than spend hours or days trying to revert the damage, I just take 3 minutes to restore from the image and I'm back to square one looking for other risky manuevers.

Ztcoracat · 02-16-2019, 02:57 PM

Quote:

Originally Posted by Brains

That's what I hear.
I have never used it, I use BootitBM which comes with image for DOS, personal data and Debian's package cache and lists directories are in a separate data drive. BootitBM, like Clonezilla (apparently, have not used it either), makes compressed images of used space only.
Takes 3 minutes to create a backup of my Debian, image file size is 3.34GB. Then it's easy to take risks, if there's a problem, rather than spend hours or days trying to revert the damage, I just take 3 minutes to restore from the image and I'm back to square one looking for other risky manuevers.

Ok, I'll go with using rsync. It should already be installed but I'll find out:-
Seems pretty straight forward to use. The basic syntax of rsync is:

Code:

rsync option source-directory destination-directory

https://www.linux.com/learn/how-back...c-command-line

hemlocktree · 02-16-2019, 07:18 PM

ztor - took me a while but i found these 2 old threads from last year re: kernel issues that your roblem reminded me of

https://ubuntuforums.org/showthread.php?t=2395529

https://ubuntuforums.org/showthread....0#post13781140

i realize this is ot your problem but it did ring a bell.