[SOLVED] systemd can't 'find' local drives

grail · 03-16-2014, 01:29 AM

So I recently upgraded a CLFS based system to include systemd 211. The previous version of 208 ran just fine but for some reason I am being thrown to the rescue console after 1 minute
and 30 seconds of checking (trying to perform fsck) for 3 partitions (sda5 (/home), sda6 (/var), sdb1 (/usr/src/build)).
Once dropped to the rescue console I can login as root and the manually mount all of the above and after pressing Ctrl-d I am placed at the login prompt and the system behaves as if booted normally.

I have attached a screenshot of just prior to logging into the rescue console.
Also, I have attached output from journalctl -xb and the offending errored lines.
Errors for drives start at 14:09:22

If anyone would advise on what I might check it would be much appreciated

Please let me know if there is any other information you may require to help me?

As will be evident from the screenshot, I am running this on virtualbox (in case that matters)

unSpawn · 03-16-2014, 04:14 AM

Your systemd_output.log shows it's trying to determine what kind of file system /dev/sda2 contains:

Code:

Mar 16 14:07:52 theGrail kernel: EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240)
Mar 16 14:07:52 theGrail kernel: EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240)
Mar 16 14:07:52 theGrail kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Mar 16 14:07:52 theGrail kernel: VFS: Mounted root (ext4 filesystem) readonly on device 8:2.

and eventually it settles for Ext4:

Code:

Mar 16 14:07:52 theGrail kernel: EXT4-fs (sda2): re-mounted. Opts: acl,user_xattr

so best check 'blkid' output against your /etc/fstab contents.

grail · 03-16-2014, 05:30 AM

fstab:

Code:

UUID=825fe35e-970d-4f9c-85c9-b0cbfefddc27     /               ext4    defaults,acl,user_xattr 1   1
UUID=c9984bd4-3651-4609-a265-6d497b4fbd07     /var            ext4    defaults,acl,user_xattr 0   2
UUID=a9183fae-5911-4bbd-98d4-e045b5dbb13a     /home           ext4    defaults,acl,user_xattr 0   2
UUID=b9891768-1302-4ff5-9f27-92d61615be5c     /usr/src/build  ext4    defaults,acl,user_xattr 0   2

UUID=5fee09f8-5c9c-4e5c-bfee-ee251b3f3e48     swap    swap    sw          0   0

blkid output:

Code:

device                         fs_type     label        mount point                        UUID
-------------------------------------------------------------------------------------------------------------------------------
/dev/sda1                      swap                     <swap>                             5fee09f8-5c9c-4e5c-bfee-ee251b3f3e48
/dev/sda2                      ext4        /            /                                  825fe35e-970d-4f9c-85c9-b0cbfefddc27
/dev/sda5                      ext4        /home        /home                              a9183fae-5911-4bbd-98d4-e045b5dbb13a
/dev/sda6                      ext4        /var         /var                               c9984bd4-3651-4609-a265-6d497b4fbd07
/dev/sdb1                      ext4                     /usr/src/build                     b9891768-1302-4ff5-9f27-92d61615be5c

Data looks ok from what I can see

unSpawn · 03-16-2014, 03:40 PM

Try adding "rootfstype=ext4" to your GRUB command line?

grail · 03-16-2014, 08:14 PM

Yes I did find that option, however the 'error' is more of a warning and does not affect the boot process.

The offending lines in the log would be:

Code:

Mar 16 14:09:22 theGrail systemd[1]: Job dev-disk-by\x2duuid-b9891768\x2d1302\x2d4ff5\x2d9f27\x2d92d61615be5c.device/start timed out.
Mar 16 14:09:22 theGrail systemd-journal[948]: Forwarding to syslog missed 1 messages.
Mar 16 14:09:22 theGrail systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-b9891768\x2d1302\x2d4ff5\x2d9f27\x2d92d61615be5c.device.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for /usr/src/build.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for Local File Systems.
Mar 16 14:09:22 theGrail systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/b9891768-1302-4ff5-9f27-92d61615be5c.
Mar 16 14:09:22 theGrail systemd[1]: Job dev-disk-by\x2duuid-a9183fae\x2d5911\x2d4bbd\x2d98d4\x2de045b5dbb13a.device/start timed out.
Mar 16 14:09:22 theGrail systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-a9183fae\x2d5911\x2d4bbd\x2d98d4\x2de045b5dbb13a.device.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for /home.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/a9183fae-5911-4bbd-98d4-e045b5dbb13a.
Mar 16 14:09:22 theGrail systemd[1]: Job dev-disk-by\x2duuid-c9984bd4\x2d3651\x2d4609\x2da265\x2d6d497b4fbd07.device/start timed out.
Mar 16 14:09:22 theGrail systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-c9984bd4\x2d3651\x2d4609\x2da265\x2d6d497b4fbd07.device.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for /var.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for Load/Save Random Seed.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for Update UTMP about System Boot/Shutdown.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/c9984bd4-3651-4609-a265-6d497b4fbd07.
Mar 16 14:09:22 theGrail systemd[1]: Job dev-disk-by\x2duuid-5fee09f8\x2d5c9c\x2d4e5c\x2dbfee\x2dee251b3f3e48.device/start timed out.
Mar 16 14:09:22 theGrail systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-5fee09f8\x2d5c9c\x2d4e5c\x2dbfee\x2dee251b3f3e48.device.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for /dev/disk/by-uuid/5fee09f8-5c9c-4e5c-bfee-ee251b3f3e48.
Mar 16 14:09:22 theGrail systemd[1]: Dependency failed for Swap.

I believe it is these errors that are halting the boot process and stopping it from mounting the required partitions.

unSpawn · 03-17-2014, 02:04 AM

"Dependency failed for File System Check"? Maybe run a fsck manually, see if that fixes things?

grail · 03-17-2014, 03:00 AM

Nope

I think the reason for the failures is due to the system not being able to recognise the partitons for some reason.

I have also tried changing all the UUID values to device names (such as /dev/sda2) but this did not seem to change anything except the following:

Code:

systemd[1]: Job dev-disk-by\x2duuid-b9891768\x2d1302\x2d4ff5\x2d9f27\x2d92d61615be5c.device/start timed out.

# became

systemd[1]: Job dev-sdb1.device/start timed out.

grail · 03-17-2014, 04:57 AM

okee dokee ... turns out it is a missing kernel option.

tested with a number of reboots to confirm, but the following is required to be set in the kernel:

Code:

CONFIG_FHANDLE=y

After that, all is well again

Thanks for your time unSpawn

unSpawn · 03-17-2014, 05:06 PM

Sorry I couldn't be of more help & thanks for posting your solution.

faical · 02-12-2020, 08:12 AM

Quote:

Originally Posted by grail

okee dokee ... turns out it is a missing kernel option.

tested with a number of reboots to confirm, but the following is required to be set in the kernel:

Code:

CONFIG_FHANDLE=y

After that, all is well again

Thanks for your time unSpawn

Hello,
Please, I had same problem
Can you tell me where did you exactly add the option :

Code:

CONFIG_FHANDLE=y