FS#36251 - root device not read-write warning

Attached to Project: Arch Linux
Opened by c (c) - Tuesday, 23 July 2013, 07:15 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 29 July 2013, 09:20 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
A new warning popped up today during bootup.

WARNING:
The root device is not configured read-write! It may be
fscked again later!

Additional info:
* linux 3.10.2-1
* systemd 204-3
* mkinitcpio 0.15.0-1


Steps to reproduce:
Reboot and look for the warning.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 29 July 2013, 09:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  grub-2.00.5xxx-4
syslinux-4.07-1
syslinux-6.01-4
Comment by Dave Reisner (falconindy) - Tuesday, 23 July 2013, 12:26 GMT
So.... fix it? The warning is there to annoy you -- your config is wrong.
Comment by Pierre Schmitz (Pierre) - Friday, 26 July 2013, 12:46 GMT
Sorry, but we should be clearer about how to fix it and what the issue here is. It affects our default config,right?
Comment by Dave Reisner (falconindy) - Friday, 26 July 2013, 13:55 GMT
Yes, it affects default configurations in syslinux and grub. I added this warning because the double fsck would have gone otherwise unnoticed -- mkinitcpio isn't the cause of this, it's simply the messenger. If you'd like to change the warning printed on bootup, I'll happily accept patches on arch-projects@.
Comment by c (c) - Friday, 26 July 2013, 14:07 GMT
Shouldn't grub-mkconfig also stop adding 'ro'? Someone else pointed out in https://bbs.archlinux.org/viewtopic.php?pid=1303696 that it's added by /etc/grub.d/10_linux and it looks like 20_linux_xen also adds it. I manually edited /boot/grub/grub.cfg and in addition removed the 'fsck' hook.
Comment by c (c) - Sunday, 28 July 2013, 12:05 GMT

Loading...