View Single Post
Old 06-21-2016, 11:13 AM   #14
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by encol View Post
Here it is:
Code:
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,noatime,nodiratime,barrier=0,data=writeback)
...
The "mount" command on my PW3 gives this:
Code:
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (ro,noatime,nodiratime,barrier=0,data=writeback)
...
Notice that rootfs is 'rw' like yours, but '/dev/root' is different.

Because TWO things are mounted on '/', try remounting '/dev/root' instead. That may also explain why the mntroot script fails -- it only tries to remount the FIRST '/', which is always busy. It should probably remount the device instead of the shared mountpoint.

But the real question is WHY rebooting continues to mount it 'rw'. The answer probably hides in an upstart script, perhaps triggered by some persistent residue from the first time you remounted it.

Last edited by geekmaster; 06-21-2016 at 05:06 PM.
geekmaster is offline   Reply With Quote