- After creating a new file system, migrating all the contents from the
/usrdirectory to that new file system and adding the corresponding new entry in the
/etc/fstabfile, the system is unable to boot up.
- The system could either enter in a loop trying to mount the newly entry added in
/etc/fstabfor the new
/usrfile system or, either, the system could time out waiting for the device that contains the new
/usrfile system and then rollback the booting process:
[ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Found device /dev/mapper/vg_root-lv_root. Starting File System Check on /dev/mapper/vg_root-lv_root... [ OK ] Started File System Check on /dev/mapper/vg_root-lv_root. [ OK ] Started dracut initqueue hook. Mounting /sysroot... [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Mounted /sysroot. [ OK ] Reached target Initrd Root File System. Starting Reload Configuration from the Real Root... [ OK ] Started Reload Configuration from the Real Root. [ TIME ] Timed out waiting for device dev-di...2d3jv7\x2dGvZ7\x2dzd1CYX.device. [DEPEND] Dependency failed for /sysroot/usr. [DEPEND] Dependency failed for Initrd File Systems. [ OK ] Stopped target Basic System. [ OK ] Stopped dracut initqueue hook. Stopping dracut initqueue hook... Starting Cleaning Up and Shutting Down Daemons... [ OK ] Stopped dracut pre-udev hook. Stopping dracut pre-udev hook... [ OK ] Stopped dracut cmdline hook. Stopping dracut cmdline hook... [ OK ] Stopped target System Initialization. ...
- The system has other system's directories on separate file systems that are only specified in
/etc/fstaband the problem has never existed before, why does
/usrbehave in a different way?
Red Hat Enterprise Linux 7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.