Arch Linux

CyberShadow

Member

Registered: 2016-03-03

Posts: 9

Website

systemd can't find disk during boot

systemd fails to find one of my volumes during boot and throws me into emergency mode:

systemd-fsck[823]: Failed to stat /dev/disk/by-uuid/f4162b8e-930d-49fa-bbea-56ea3bb544fa: No such file or directory

But if I exit emergency mode (i.e. simply hit Ctrl+D), it continues to boot just fine, and the volume is mounted once booted.

I'm guessing I need to add a delay or make the mount depend on the disk device somehow?

Not sure if it matters, but the volume in question is a btrfs volume spanning four drives (in raid10). In my fstab I have:

UUID=f4162b8e-930d-49fa-bbea-56ea3bb544fa	/mnt/data2016			btrfs	rw,relatime,space_cache,subvol=@data2016	0 5
UUID=f4162b8e-930d-49fa-bbea-56ea3bb544fa	/mnt/2012-hdd-3t-raid		btrfs	rw,relatime,space_cache				0 5

Later in the boot I see:

Apr 07 20:58:57 home.thecybershadow.net systemd[1]: dev-disk-by\x2duuid-2b738eaf\x2d519c\x2d47bc\x2d9981\x2de76fd644423f.device: Dev dev-disk-by\x2duuid-2b738eaf\x2d519c\x2d47bc\x2d9981\x2de76fd644423f.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata5/host6/target6:0:0/6:0:0:0/block/sdg/sdg2 and /sys/devices/pci0000:00/0000:00:1f.2/ata3/host4/target4:0:0/4:0:0:0/block/sdb/sdb2

but this does not seem to get in the way of booting successfully.

Last edited by CyberShadow (2016-04-07 23:52:22)