[Solved] Filesystem is read-only before mounting /run

[drhouse123]

Hi, everydody!

After upgrading openrc to 0.11.8 I got strange message 'rm: can not remove «/run/openrc»: The file system is read-only' anytime at startup. How i can fix it ?
But system startup anyway is OK.

Code: Select all

  OpenRC 0.11.8 is starting up Gentoo Linux (x86_64)

 * /proc is already mounted
rm: can not remove «/run/openrc»: The file system is read-only
 * Mounting /run ...
 * /run/openrc: creating directory
 * /run/lock: creating directory
 * /run/lock: correcting owner
 * /dev is already mounted
 * Mounting /dev/shm ...
 [ ok ]
 * Mounting security filesystem ...
 [ ok ]
 * Mounting debug filesystem ...
 [ ok ]
 * Mounting cgroup filesystem ...
 [ ok ]
 * Starting udev ...
 [ ok ]
 * Populating /dev with existing devices through uevents ...
 [ ok ]
 * Waiting for uevents to be processed ...
 [ ok ]

I hope for your help.

[NeddySeagoon]

drhouse123,

Heres what happens.

/run is a mount point on the / filesystem. Before a tmfs is mounted at /run, it should be empty.
For some reason, yours isn't. So the message

Code: Select all

 rm: can not remove «/run/openrc»: The file system is read-only 

is correct. root is still mounted read only.

Next

Code: Select all

 * Mounting /run ... 

mounts /run as tmpfs over the top of whatever you have in /run, so it can't be seen any more.
You may not umount /run as it will be in use on your live system.

If you want to clear it out, you can boot with a liveCD, mount your / at /mnt/gentoo and look in /mnt/gentoo/run
There should be nothing there. Thats your real /run mount point without tmpfs mounted on top.

On a live system you can look with

Code: Select all

mount -o bind / /mnt/gentoo

and you see the underlying run in the same place.
I have never felt comfortable with using a bind mount to manipulate the hidden filesytsem but it should work.

[drhouse123]

NeddySeagoon

Thank you very much for explaining

I just cleaned /run using live-cd,

[rootor]

Very nice explication

[Mgiese]

very good indeed.

could that be the solution to my problem described here :

http://forums.gentoo.org/viewtopic-t-97 ... ight-.html??

thanks in advance