A couple of days ago, after updating to Kernel 3.10, when I started my brand new ArchLinux after the GRUB, I got a warning that said:
The root device is not configured to be mounted read-write! It may be fsck'd again later
But since everything started normally, I didn't pay attention to it. But today I decided that I did not want to see that warning any more and I began to look for the possible causes.
Checking my file / etc / fstab I notice that the discs are mounted with the option rw (read-write), therefore the above warning was meaningless.
Without internet in the house I couldn't search Google nor in the Forums or the Arch Wiki, so I kept "touching" the files, checking where the problem might be.
So I thought: Who is the one that tells my distribution to raise the kernel on a given partition? And it turns out that the first one that appears when you turn on the computer is none other than GRUB.
Checking in the file /etc/grub/grub.cfg I noticed the problem on the line:
linux /vmlinuz-linux root=UUID=722dbb91-9299-44e9-9032-d9fd812152e7 ro quiet
Which if you look at it has the option ro (Read only) and it should be rw (reading writing).
To solve this I did not touch the file manually, but first I ran the command:
sudo grub-mkconfig -o /boot/grub/grub.cfg
Then when accessing the GRUB configuration again, the line already appeared correctly:
linux /vmlinuz-linux root=UUID=722dbb91-9299-44e9-9032-d9fd812152e7 rw quiet
I restarted the computer and voila, the warning disappeared 🙂
Hello,
It is the first time that I comment, although I follow you regularly.
I have been using Arch for a short time and also since I updated to kernel 3.10 I get that error, although as you say, everything seems to continue working correctly. I have proceeded as indicated in the post and "rw" already appears in grub.cfg, but when I reboot the error continues to appear.
I take this opportunity to congratulate you on the blog.
Hello:
Did you notice if the /etc/grub/grub.cfg file also changed the ro to rw? I started looking in the Arch forum and maybe your case is not like mine and you have to do what they indicate in this post, although I suggest you read the entire thread. In that same thread one of the users solves his problem exactly like me.
I have installed on another Ubuntu partition and there is the "master" grub, I updated the latter and the error no longer appears.
Thank you very much
as they say in the Arch-Spanish forum reinstall grub2 and run
# grub-mkconfig -o /boot/grub/grub.cfg
I did not have to reinstall Grub2. Just run the command you mention.
It may not be the right place, but taking advantage of the fact that the post is about Arch, does anyone know why libreoffice 4.1 is still not in the Arch repo?
Hmm, no idea, you would have to search and read about it.
Normally, in Arch Linux we have the latest versions of the software shortly after release, but LibreOffice is an exception, it always takes a long time to reach stable repos. Last time I checked it took about a month, if I'm not mistaken.
What you can do while is compile or install it from Testing.
Thanks elav, I spent weeks looking for this solution and it was something so simple, the warning had become common xD.
Hahaha the same thing happened to me until I got tired of seeing it .. to hell with Warning
Hahahaha, another like it, the first time the message came out I did what it said, I fsck the root partition, and since it didn't help I just ignored it, at the end it didn't seem to affect at all. 😀
It seems that all Arch users are somewhat lazy. 😀
I also get that little message and come pass fsck xd ... but the point is that I don't have / etc / grub, I'm going to try to modify /boot/grub/grub.cfg.
Solution for those like me who use Syslinux instead of Grub2.
Do:
sudo hand /boot/syslinux/syslinux.cfg
On the kernel line, change the ro to rw.
Save and
Save and restart.
Problem solved.
When I used archlinux, it appeared to me too but since I didn't notice anything strange, I never thought of fixing it.
Thanks, the truth is that I was stressed out seeing that warning, even though it did not influence anything in the system.
Greetings.
I did something similar to what they suggested with GRUB2 in the thread, but in BURG. For those of you using BURG like me, edit the file:
/etc/burg.d/proxifiedScripts/linux
Find line 92, and where it says "ro" change it to "rw". Then run as root:
burg-mkconfig -o /boot/burg/burg.cfg
And with that you should be ready.
It seems that the problem is already fixed as standard. I did a clean install and now that message no longer appears.
In manjaro it is in:
/boot/grub/grub.cfg
Another thing, the file is supposed to /boot/grub/grub.cfg It should not be edited, preferably you should work with / Etc / default / grub. There you have to add rw:
...
GRUB_DISTRIBUTOR = »Arch»
GRUB_CMDLINE_LINUX_DEFAULT = »rw ipv6.disable = 1 ″
GRUB_CMDLINE_LINUX = »»
...
The point is that it may happen to you like me, that I did it as you say and when generating the configuration I put "rw ro quiet splash". I mean, it didn't fix anything.
It would be preferable to fix line 138 of /etc/grub.d/10_linux or line 92 of /etc/burg.d/10_linux_proxy. That way when updating the configuration it will be perfectly fixed.
To me it put something like "ro rw nosequemás" but anyway the problem the warning stopped appearing.
"Strange" things tend to happen in Arch. For example, before reinstalling Arch, with the LTS ALSA kernel it recognized everything, after reinstalling I had to install PulseAudio to make it work with my headphones; and not everyone.
thanks!
It did not work for me, that message keeps appearing when booting.
I ran the command: sudo grub-mkconfig -o /boot/grub/grub.cfg, no problem, but when booting I still get the message.
Thanks, I'll try. I had noticed the error, but when I saw that everything worked correctly I did not start looking for a solution.
Thank you…..
When it was installed (it happened to me as in some other occasions) I got the message that it was installed as grub.cfg.pacnew and when I restart pain to the eye the error message…. So before making the respective change of the files I started to compare the two files (grub.cfg and grub.cfg.pacnew) and it turns out that there were some differences:
first the one you mentioned del ro and rw
then the UUID of the / dev / sda2 that you can check in the fstab, it was changed in the grub.cfg.pacnew,
as well as in the grub.cfg it appears look at the 2 at the end
if [x $ feature_platform_search_hint = xy]; then
search –no-floppy –fs-uuid –set = root –hint-bios = hd0, msdos2
and in grub.cfg.pacnew it is changed to 5
if [x $ feature_platform_search_hint = xy]; then
search –no-floppy –fs-uuid –set = root –hint-bios = hd0, msdos5
I had come up with this solution before and it worked on my desktop computer (bios) but not on my laptop (uefi). In my laptop to boot it uses efistub alone, neither grub, nor syslinux, nor gumiboot. Surely if I install grub it would solve the problem, but I would like to find the solution before going off on a tangent.
Thanks for the post, a few days ago I was also looking at that warning but as everything was still fine, and I did not want to repair it, do not look for anything hoy but today I got tired of seeing it.
Greetings, thanks for the post.
Thank you very much, I had checked many settings and could not find what the problem was. It was starting to scare me. : p
It helped me.
But I use syslinux, and I went to the / boot / syslinux folder and edited the syslinux.cfg file and changed everything that said ro to rw.
Thank you very much.
Thanks, if it works!
Cheers!!!! 🙂
I just updated everything, I was scared when I saw that message, I thought my installation would be lost, thanks for the information, everything is fine now.
Thanks elav, it worked perfectly
It not only fixed the mentioned error, but also an error that it had previously. There was a line that was out of date from a previous update, and I was modifying it by hand every time I booted!
Many thanks! 🙂
Thanks it worked perfectly. Now keep throwing a message, but I think it's normal
Your contribution was very helpful to me, thank you!
I just have one question, in the line you wrote:
Checking the file /etc/grub/grub.cfg I noticed the problem in the line:
It wouldn't be in the / boot / grub / address instead of / etc ??.
Does this work for Kademar who is based on Arch?