Hi there, if you have a "/usr" partition and uses sysvinit to boot then you end up with a system having /usr mounted read-only. Looking to the logs, it looks like dracut mount anc check first the partitions "/" and "/usr" partitions. Then, sysvinit try to check them, but fails because they are already mounted by dracut. I don't know why "/" ends up being mounted rw wheares /usr remains ro. The mounting goes fine if I use systemd; so it looks like an interaction pb in between dracut and sysvinit. My fstab looks like this: # Entry for /dev/sda1 : UUID=5243cfa3-260f-4ebc-ae89-e4f1a4713f5d / ext4 acl,relatime 1 1 # Entry for /dev/sda7 : UUID=06a67d1a-8d4d-4127-b775-a648873d57ec /usr ext4 acl,relatime 1 2 Cheers, chris.
Blocks: (none) => 2120
Are you using dracut or mkinitrd?
Keywords: (none) => NEEDINFOQA Contact: (none) => mageia
dracut, it logs some message at boot claiming to check/mount / and /usr.
Yeah dracut mounts it readonly... I'm not sure if it's dracuts job to mount it rw initially, or systemd's job to remount it rw.... will ask upstream.
Status: NEW => ASSIGNED
what about this bug with systemd 40 ?
CC: (none) => dmorganec
Still there for the time being, but as Colin say, comes from dracut. So, it is also there with both systemd-sysvinit and sysvinit. Cheers, Chris.
I know this is actually fixed in latest dracut upstream, so it will be fixed when I get round to updating it (should be this week now I'm back from hols)
Cool, thanks!
Just to say that that works now, thanks guys, as far as I am concerned you can close the bug. Cheers.
Oh yeah, forgot to close this off. Thanks :)
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED