Red Hat Bugzilla – Bug 59934
changing label of root prevents boot
Last modified: 2007-04-18 12:40:26 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204 Description of problem: I like to have the label of each root filesystem indicate the OS that's installed in there. So, for enigma, after installation, I run tune2fs -L enigma/ /dev/hda6, adjusted /etc/fstab and the system would just work next time. Now, it appears that mkinitrd uses a disk label to mount /sysroot in linuxrc, so adjusting /etc/fstab is no longer enough. initrd.img must be rebuilt. I see the value in this change, and I approve of it, but it would be nice to have this more clearly stated in the release notes, and perhaps it would be appropriate to print an error message suggesting that initrd may have to be rebuilt in case mount /sysroot fails in linuxrc? Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.install hampton-beta1 2.tune2fs -L hampton/ /dev/<rootdevice> 3.modify /etc/fstab accordingly 4.reboot Actual Results: can't mount /sysroot, so pivot_rool fails Expected Results: it used to just work, but at least some warning pointing at the need for rebuilding initrd after modifying the label would have saved me 4 installs in a row and a lot of grief, head scratching and hair pulling :-) Additional info:
This is confirmed with Beta 3 as well. Too late to do something about this?
Rerun mkinitrd if you do this. Previous behavior was that if drive order changed for whatever reason, you broke your system. I think that label changing is a far less common case.
Isn't it even worth printing a more clear message explaining what the problem was, when we fail to remount root?