Ok, more info. I've just looked at the rdsosreport from a 327 kernel, and the one from this morning, from the 229-20 kernel, and I see where they croak: [ 3.045600] lym.cit.nih.gov systemd[1]: Found device ST500NM0003-9ZM172 /. [ 3.045950] lym.cit.nih.gov systemd[1]: Starting File System Check on /dev/disk/by-label/\x2f... [ 3.047209] lym.cit.nih.gov systemd-fsck[575]: Failed to detect device /dev/disk/by-label// [ 3.047337] lym.cit.nih.gov systemd[1]: systemd-fsck-root.service: main process exited, code=exited, status=1/FAILURE [ 3.047449] lym.cit.nih.gov systemd[1]: Failed to start File System Check on /dev/disk/by-label/\x2f. [ 3.047559] lym.cit.nih.gov systemd[1]: Dependency failed for /sysroot.
and yet. starting at line 75 of 1281, I see + ls -l /dev/disk/by-id /dev/disk/by-label /dev/disk/by-path /dev/disk/by-uuid <...> /dev/disk/by-label: total 0 lrwxrwxrwx 1 root 0 10 Jan 29 14:27 SWAP-sda2 -> ../../sda2 lrwxrwxrwx 1 root 0 10 Jan 29 14:27 \x2f -> ../../sda3 lrwxrwxrwx 1 root 0 10 Jan 29 14:27 \x2fboot -> ../../sda1
So, at some point, it seems to have lost the visibility to /dev/disk/by-label.
Any thoughts, here?
mark