MV1000W along with Other OpenWRT Routers: Difference between revisions

Line 119:

**rsync -av /rom/overlay/upper/ /mnt/mmcblk0p2/ (this will overwrite all the 'stock' files with duplicate or upgraded files)

*Reboot

=== Watch Out! ===

There is one insidious thing that will occur during boot and even after booting is complete (at around 5 minutes after booting)

During the boot process, when the Image file (which contains the kernel and mounts the root file system among other things) is loaded and run, it mounts /dev/mmcblk0p2 as /rom and /data. /data isn't a bit issue (but it is puzzling, will explain shortly). /rom is a concern, because it gets mounted as Read Only. Here's why it is a concern: /dev/mmcblk0p2 is the Root (IE / ) Partition and needs to be Read / Write. Now as originally configured it was a SquashFS File system, but now converted to EXT4.

By definition SquashFS is read only (unless one is building it, IE 'squashing' it), so why explicitly mount it as /rom Read Only? Why not just mount it, as it will be Read Only? Who knows, but that's how it is.

Solution?

in /etc/rc.local (or LuCI GUI);<syntaxhighlight lang="text">

sleep 11

umount /rom

umount /data

mount -o remount,rw /dev/mmcblk0p2

</syntaxhighlight>This solves the Read Only issue, but as mentioned, for some reason, /data remounts (but in Read / Write mode). Thankfully /rom does not. And since the /data remounting thing doesn't affect anything, it doesn't matter. It is frustrating, but what's even more frustrating is there is no logging evidence whatsoever that /data got remounted. Woof!

Check it with this command (before applying the fix): <code>mount | grep /dev/mmcblk0p2</code>

...and you'll get this;<syntaxhighlight lang="text">

/dev/mmcblk0p2 on /rom type ext4 (ro,noatime,data=ordered)

/dev/mmcblk0p2 on / type ext4 (ro,relatime,data=ordered)

/dev/mmcblk0p2 on /data type ext4 (ro,relatime,data=ordered)

</syntaxhighlight>Assuming the order displayed is also the order of how things were mounted, it appears that whoever mounts first trumps everything else in terms of Read / Only or Read / Write. Once /rom is unmounted, as noted above, / can be remounted as Read / Write with: <code>mount -o remount,rw /dev/mmcblk0p2</code>

*

=== Marvell U-Boot and PRINTENV ===

===Marvell U-Boot and PRINTENV===

Below are the default values displayed by the printenv command from within the Marvell U-Boot Command Prompt;<syntaxhighlight lang="text">

args_mmc=setenv bootargs "${console} root=/dev/mmcblk0p2 rw rootwait"

@@ Line 119: / Line 119: @@
 **rsync -av /rom/overlay/upper/ /mnt/mmcblk0p2/ (this will overwrite all the 'stock' files with duplicate or upgraded files)
 *Reboot
+=== Watch Out! ===
+There is one insidious thing that will occur during boot and even after booting is complete (at around 5 minutes after booting)
+During the boot process, when the Image file (which contains the kernel and mounts the root file system among other things) is loaded and run, it mounts /dev/mmcblk0p2 as /rom and /data.  /data isn't a bit issue (but it is puzzling, will explain shortly).  /rom is a concern, because it gets mounted as Read Only.  Here's why it is a concern: /dev/mmcblk0p2 is the Root (IE / ) Partition and needs to be Read / Write.  Now as originally configured it was a SquashFS File system, but now converted to EXT4.
+By definition SquashFS is read only (unless one is building it, IE 'squashing' it), so why explicitly mount it as /rom Read Only?  Why not just mount it, as it will be Read Only?  Who knows, but that's how it is.
+Solution?
+in /etc/rc.local (or LuCI GUI);<syntaxhighlight lang="text">
+sleep 11
+umount /rom
+umount /data
+mount -o remount,rw /dev/mmcblk0p2
+</syntaxhighlight>This solves the Read Only issue, but as mentioned, for some reason, /data remounts (but in Read / Write mode).  Thankfully /rom does not.  And since the /data remounting thing doesn't affect anything, it doesn't matter.  It is frustrating, but what's even more frustrating is there is no logging evidence whatsoever that /data got remounted.  Woof!
+Check it with this command (before applying the fix): <code>mount | grep /dev/mmcblk0p2</code>
+...and you'll get this;<syntaxhighlight lang="text">
+/dev/mmcblk0p2 on /rom type ext4 (ro,noatime,data=ordered)
+/dev/mmcblk0p2 on / type ext4 (ro,relatime,data=ordered)
+/dev/mmcblk0p2 on /data type ext4 (ro,relatime,data=ordered)
+</syntaxhighlight>Assuming the order displayed is also the order of how things were mounted, it appears that whoever mounts first trumps everything else in terms of Read / Only or Read / Write.  Once /rom is unmounted, as noted above, / can be remounted as Read / Write with: <code>mount -o remount,rw /dev/mmcblk0p2</code>
 *
-=== Marvell U-Boot and PRINTENV ===
+===Marvell U-Boot and PRINTENV===
 Below are the default values displayed by the printenv command from within the Marvell U-Boot Command Prompt;<syntaxhighlight lang="text">
 args_mmc=setenv bootargs "${console} root=/dev/mmcblk0p2 rw rootwait"