root device is not configured to be mounted read-write? [SOLVED]

anonymous_user · 2013-08-02 04:12:37

During boot I see the following message:

WARNING

The root device is not configured to be mounted
read-write! It may be fsck'd again later.

My computer boots fine otherwise and I can login and run apps. I run the linux-ck kernel and here is my fstab:

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sda5
UUID=4d1cf3fb-87ba-4059-997a-407af2e06ccc	/         	ext4      	defaults,relatime	0 	1

# /dev/sda6
UUID=a334a939-e4eb-4388-9fa1-39cf858cbf10	/home     	ext4      	defaults,relatime	0 	2
/swapfile									none		swap		defaults			0	0

https://www.box.com/dav /mnt/box.com    davfs   rw,user,noauto     0 0

I only recently started recieving this message so I am wondering if it is "normal" or if theres something I should change.

Last edited by anonymous_user (2013-08-02 04:56:59)

Scimmia · 2013-08-02 04:19:11

It's not about fstab, it's about your bootloader config.

Do a search, there was a thread about this earlier. Testing forum, maybe?

jasonwryan · 2013-08-02 04:33:42

Yes, long thread in [testing] explaining the change...

anonymous_user · 2013-08-02 04:56:44

Somehow I missed that thread when searching. Anyways thanks for the hint.

ntbc · 2013-08-02 15:43:07

Hi Guys,

i did an update to kernel 3.10.... this day. After that my laptop starts with the same error message. I removed the "ro" in grub.cfg but that didn't help. Can someone tell me what happens.?

Maybe you could post a link to the mentioned thread

Last edited by ntbc (2013-08-02 15:43:55)

Trilby · 2013-08-02 15:54:43

ntbc, here is that thread. See posts 6 + 15, you need to *add* rw, not just remove ro.

I don't know about grub, but syslinux was recently updated and came with a pacnew config with the appropriate change.

Last edited by Trilby (2013-08-02 15:55:17)

ntbc · 2013-08-02 16:03:48

Perfect. That solved the issue. Thanks Trilby.

But i'm still confused. I did the same update on my desktop pc which works fine. No need to change anything in grub.cfg. Does someone know what happens here?

techge · 2013-08-02 16:13:04

Trilby wrote:

I don't know about grub, but syslinux was recently updated and came with a pacnew config with the appropriate change.

grub was fixed in 2.00.5043-3 by tpowa https://projects.archlinux.org/svntogit … 5d7edda21a

(as mentioned in the thread)

Until now it is in testing.

EDIT: fixed link

Last edited by techge (2013-08-02 16:15:18)

wucherpfennig · 2013-08-04 14:27:50

ntbc wrote:

Perfect. That solved the issue. Thanks Trilby.
But i'm still confused. I did the same update on my desktop pc which works fine. No need to change anything in grub.cfg. Does someone know what happens here?

well I'm stuck at the same problem. changing kernel hooks gives me kernel panics... what exactly did you do to solve the error?

Trilby · 2013-08-04 14:38:41

wucherpfennig, you'll need to be much more clear about what you have done. None of the changes discussed in this thread could lead to a kernel panic.

Your problem seems to be something different. And as this is a [SOLVED] thread you will not likely get much attention here. Start a new thread detailing what you have done and a description of when in the boot process you get the kernel panic, and link back to this thread if you think it is relevant.

wucherpfennig · 2013-08-04 21:21:58

Trilby wrote:

wucherpfennig, you'll need to be much more clear about what you have done. None of the changes discussed in this thread could lead to a kernel panic.
Your problem seems to be something different. And as this is a [SOLVED] thread you will not likely get much attention here. Start a new thread detailing what you have done and a description of when in the boot process you get the kernel panic, and link back to this thread if you think it is relevant.

Sorry my bad. I should know that I should not post anymore to [SOLVED] posts. Anyway my error was that I missunderstood the above stated post from you which is about kernel building and kernel hooks. I finally understood that I only had to edit the grub.cfg. Sorry again...

WonderWoofy · 2013-08-04 21:44:40

@wucherpfennig, posting in a thread marked as [solved] is okay. It is just that the issue you are posting about seems to be something totally different than the one described in the thread. So Trilby is just pointing this out. You'd likely be better off trying to address your problem in either a new thead, or one that directly relates to the problem that you are having (without hijacking the thread of course).

If you have more to add about the discussion of this particular topic, then continuing the conversation is fine.

silent · 2013-08-13 09:34:42

.

Last edited by silent (2013-08-21 08:02:30)

falconindy · 2013-08-13 11:21:45

The above post is bad advice. The point of the fsck hook was never about what pid 1 might or might not do (hint, init has always fsck'd devices going back to sysvinit) but that fsck can be performed in early userspace before the filesystem is even mounted. This lets you fix more errors without rebooting, as fsck'ing later on necessitates that the disk is mounted (and read-only).

Trilby · 2013-08-13 12:05:03

silent wrote:

It may be a cleaner solution than changing "ro" to "rw" in the generated bootloader configuration at the Arch kernel line each time, as the bootloader is not necessarily installed form Arch.

This also doesn't make any sense. You don't need to add it "each time", only once then leave it there.

And it doesn't matter which OS the bootloader is installed from. If the bootloader is capable of booting archlinux then it is capable of having kernel line options added.

silent · 2013-08-13 14:23:15

.

Last edited by silent (2013-08-21 08:02:53)

WonderWoofy · 2013-08-13 14:44:16

@silent, Considering that Fedora uses systemd and is likely going to have this same requirement for rw to skip the fsck, I expect that the issue should be easily resolvable. But also, the Arch kernel name and initramfs file name do not change. They stay persistent and the old kernel gets removed. We do not end up with countless kernel version like some other distributions. So I am not sure how it would be an excessive amount of work to make a persistent grub addition for Arch Linux. Apparently grub2 has a hell of a time recognizing Arch Linux anyway, so making something in the custom configuration grub script would probably be easiest, and not require the user to change anything "each time".

Also, the wiki is not always right, but someone once said, that falconindy is. That being the case, I would listen to falconindy. But in this particular case, you are advising that people use one fsck facility over the other, which is fine. But the fsck in the intiramfs has advantages, none of which were addressed in your post of (what falconindy called) bad advice. So you are giving up the advantages of having an initramfs fsck simply so you don't have to possibly change the 'ro' to 'rw'?!

(Not everyone uses grub BTW)

falconindy · 2013-08-13 15:49:03

silent wrote:

This advice was directly taken form Arch Wiki

Sure, and you're advising against what you yourself point out to be the recommended default. Specifically, your quote:

silent wrote:

typically the fsck hook is no longer needed, except for some special setups

This simply isn't true, and it's no wonder you weren't able to clarify this.

JTjohnston · 2013-08-19 14:37:42

Thank you falconindy! I've been trying to understand how to fix this for a few days. Finally after carefully reading enough I figured out where the change needed to be made (in my grub.cfg file). I found that file early on, but it said not to change it (because it was automatically generated...). Just wanted to say I appreciate your efforts (and can feel your frustration from reading all your posts on this topic).

fry · 2013-08-27 09:17:55

For me this problems was resolved by the re-installation of the grub2, I used this command:

$ sudo grub-install --recheck /dev/sda
$ sudo grub-mkconfig -o /boot/grub/grub.cfg

And problem was solved.

jb.1234abcd · 2014-09-10 16:45:34

I hope this will answer your question.
https://bugs.archlinux.org/task/41915
jb

teateawhy · 2014-09-10 17:28:03

fry wrote:

For me this problems was resolved by the re-installation of the grub2, I used this command:
$ sudo grub-install --recheck /dev/sda
$ sudo grub-mkconfig -o /boot/grub/grub.cfg
And problem was solved.

I understand why that solved the problem, but as a clarification, it is *not* necessary to reinstall grub. See previous posts for what to do.

ewaller · 2014-09-10 17:30:59

Careful of old threads
Closing.

Arch Linux

#1 2013-08-02 04:12:37

root device is not configured to be mounted read-write? [SOLVED]

#2 2013-08-02 04:19:11

Re: root device is not configured to be mounted read-write? [SOLVED]

#3 2013-08-02 04:33:42

Re: root device is not configured to be mounted read-write? [SOLVED]

#4 2013-08-02 04:56:44

Re: root device is not configured to be mounted read-write? [SOLVED]

#5 2013-08-02 15:43:07

Re: root device is not configured to be mounted read-write? [SOLVED]

#6 2013-08-02 15:54:43

Re: root device is not configured to be mounted read-write? [SOLVED]

#7 2013-08-02 16:03:48

Re: root device is not configured to be mounted read-write? [SOLVED]

#8 2013-08-02 16:13:04

Re: root device is not configured to be mounted read-write? [SOLVED]

#9 2013-08-04 14:27:50

Re: root device is not configured to be mounted read-write? [SOLVED]

#10 2013-08-04 14:38:41

Re: root device is not configured to be mounted read-write? [SOLVED]

#11 2013-08-04 21:21:58

Re: root device is not configured to be mounted read-write? [SOLVED]

#12 2013-08-04 21:44:40

Re: root device is not configured to be mounted read-write? [SOLVED]

#13 2013-08-13 09:34:42

Re: root device is not configured to be mounted read-write? [SOLVED]

#14 2013-08-13 11:21:45

Re: root device is not configured to be mounted read-write? [SOLVED]

#15 2013-08-13 12:05:03

Re: root device is not configured to be mounted read-write? [SOLVED]

#16 2013-08-13 14:23:15

Re: root device is not configured to be mounted read-write? [SOLVED]

#17 2013-08-13 14:44:16

Re: root device is not configured to be mounted read-write? [SOLVED]

#18 2013-08-13 15:49:03

Re: root device is not configured to be mounted read-write? [SOLVED]

#19 2013-08-19 14:37:42

Re: root device is not configured to be mounted read-write? [SOLVED]

#20 2013-08-27 09:17:55

Re: root device is not configured to be mounted read-write? [SOLVED]

#21 2014-09-10 16:45:34

Re: root device is not configured to be mounted read-write? [SOLVED]

#22 2014-09-10 17:28:03

Re: root device is not configured to be mounted read-write? [SOLVED]

#23 2014-09-10 17:30:59

Re: root device is not configured to be mounted read-write? [SOLVED]

Board footer