On Sun, Sep 13, 2015 at 4:07 PM, Scott M. Jones <scott@xxxxxxxx> wrote: > Boot is failing on Fedora 22, kernel 4.1.6-201, on a Beagleboard XM rev > B, at this step. > > [ OK ] Found device /dev/disk/by-label/_\x2f. > Starting File System Check on /dev/disk/by-label/_\x2f... > [FAILED] Failed to start File System Check on /dev/disk/by-label/_\x2f. > See "systemctl status systemd-fsck-root.service" for details. > [DEPEND] Dependency failed for /sysroot. > [DEPEND] Dependency failed for Initrd Root File System. > [ 11.360931] audit: type=1130 audit(1442156101.392:12): pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-fsck-root > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > terminal=? res=failed' > ;33mDEPEND] Dependency failed for Reload Configuration from the Real Root. > [ OK ] Stopped dracut pre-pivot and cleanup hook. > [ OK ] Stopped target Initrd Default Target. > [ OK ] Reached target Initrd File Systems. > [ OK ] Stopped dracut mount hook. > [ OK ] Stopped target Basic System. > [ OK ] Stopped target System Initialization. > Starting Emergency Shell... > > > Checking rdsosreport.txt in the emergency shell I see: > > [ 11.206220] localhost systemd[1]: Starting Basic System. > [ 11.208143] localhost systemd[1]: Found device /dev/disk/by-label/_\x2f. > [ 11.226453] localhost systemd[1]: Starting File System Check on > /dev/disk/by-label/_\x2f... > [ 11.261671] localhost systemd-fsck[237]: Failed to stat > '/dev/disk/by-label/_/': No such file or directory > [ 11.272718] localhost systemd[1]: systemd-fsck-root.service: main > process exited, code=exited, status=1/FAILURE > [ 11.282880] localhost systemd[1]: Failed to start File System Check > on /dev/disk/by-label/_\x2f. > > Notice especially at 11.261671. by-label is this: > > :/# ls -l /dev/disk/by-label > total 0 > lrwxrwxrwx 1 root 0 15 Sep 13 15:03 UBOOT -> ../../mmcblk0p1 > lrwxrwxrwx 1 root 0 15 Sep 13 15:03 _\x2f -> ../../mmcblk0p4 > lrwxrwxrwx 1 root 0 15 Sep 13 15:03 _\x2fboot -> ../../mmcblk0p2 > lrwxrwxrwx 1 root 0 15 Sep 13 15:03 _swap -> ../../mmcblk0p3 > :/# > > This failure does NOT occur using un-upgraded kernel 4.0.4-301. > > Any ideas? Not really, on Fedora we usually use UUID, although in some cases I do use labels when dealing manually. First up I'd check a 4.2 kernel from F-23 [1[ and see if it's OK with that. Then I'd reboot to the 4.0.4 kernel and use lsinitd and friends to ensure the modules in the initrd look OK. If the 4.0.4 kernel is the original GA kernel it'll be a generic initrd vs a host specific one. The later is smaller as it only contains the modules required for the specific device. You could try the generic initrd with the 4.1.x kernel too (details in /etc/dracut.conf) Peter [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=682842 _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
