I was able to set up a script to mount the drives as I needed by turning off the automount option and setting up separate mount commands during startup. However, I am seeing the following errors in dmesg during start up around recognizing the usb devices. Does this mean any issues with router flash memory since it is referencing "mtdblock0"?
Quote:
[ 40.238980] sd 2:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[ 40.405070] blk_update_request: I/O error, dev mtdblock0, sector 0
[ 40.405624] blk_update_request: I/O error, dev mtdblock0, sector 8
[ 40.410728] blk_update_request: I/O error, dev mtdblock0, sector 16
[ 40.416812] blk_update_request: I/O error, dev mtdblock0, sector 24
[ 40.423106] blk_update_request: I/O error, dev mtdblock0, sector 32
[ 40.429363] blk_update_request: I/O error, dev mtdblock0, sector 40
[ 40.435570] blk_update_request: I/O error, dev mtdblock0, sector 48
[ 40.441885] blk_update_request: I/O error, dev mtdblock0, sector 56
[ 40.448110] blk_update_request: I/O error, dev mtdblock0, sector 64
[ 40.454232] blk_update_request: I/O error, dev mtdblock0, sector 72
[ 40.472447] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[ 40.508854] Buffer I/O error on dev mtdblock1, logical block 0, async page read
[ 40.518025] Buffer I/O error on dev mtdblock1, logical block 32, async page read
[ 40.518663] Buffer I/O error on dev mtdblock1, logical block 32, async page read
[ 40.525041] Buffer I/O error on dev mtdblock1, logical block 33, async page read
[ 40.532510] Buffer I/O error on dev mtdblock1, logical block 33, async page read
[ 40.539882] Buffer I/O error on dev mtdblock1, logical block 34, async page read
[ 40.547216] Buffer I/O error on dev mtdblock1, logical block 34, async page read
[ 40.576543] Buffer I/O error on dev mtdblock2, logical block 0, async page read
[ 40.619886] Buffer I/O error on dev mtdblock3, logical block 0, async page read
I was able to turnoff automount and use findfs to mount my drives using drive-label last year. It worked well.
However, it looks like that has stopped working with the recent versions I can't find "findfs" command any longer on this router. Are there any other alternatives? Will that be added back?
I am on 52485 using EA8500. 5/11 build
Code:
root@EA8500:~# which which
/usr/bin/which
root@EA8500:~# which findfs
root@EA8500:~#
In the Services->USB, fill in the UUID to mount as "jffs" and "opt" and use them in the NAS setup.
And use automount and your mount point information for scripts. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
In the Services->USB, fill in the UUID to mount as "jffs" and "opt" and use them in the NAS setup.
And use automount and your mount point information for scripts.
If I use both usb ports, same drive is assigned sda1 or sdb1 during reboot. So my mountpoints become invalid which was the reason for using findfs. While one of my mountpoint is optware, the other one is not jffs.
Joined: 18 Mar 2014 Posts: 12882 Location: Netherlands
Posted: Sun May 21, 2023 16:40 Post subject:
There a scripts available to do that (which use blkid, I think).
From my notes:
Quote:
Script to create fixed mountpoints
Can be handy if you have more than one drive as the drives might swap mount points on reboot:
https://pastebin.com/VDZ32r2D
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Sun May 21, 2023 16:50 Post subject:
mark74 wrote:
dale_gribble39 wrote:
Per Yngve Berg wrote:
In the Services->USB, fill in the UUID to mount as "jffs" and "opt" and use them in the NAS setup.
And use automount and your mount point information for scripts.
If I use both usb ports, same drive is assigned sda1 or sdb1 during reboot. So my mountpoints become invalid which was the reason for using findfs. While one of my mountpoint is optware, the other one is not jffs.
In the Services->USB, fill in the UUID to mount as "jffs" and "opt" and use them in the NAS setup.
And use automount and your mount point information for scripts.
If I use both usb ports, same drive is assigned sda1 or sdb1 during reboot. So my mountpoints become invalid which was the reason for using findfs. While one of my mountpoint is optware, the other one is not jffs.
Are you saying that the UUID of your drive volumes change? Interesting. I don't think sir PYB would suggest something so trivial if that were the case.
No, UUID is the same. The device name(sd1, sdb1 etc.) associated with physical device will keep changing on reboot.
I think if I provide UUID and mount it as jffs (i.e. not my own mount point name), it may work through auto mount GUI. I was trying to keep it mounted to a different mount point that I reference elsewhere in the network.
There a scripts available to do that (which use blkid, I think).
From my notes:
Quote:
Script to create fixed mountpoints
Can be handy if you have more than one drive as the drives might swap mount points on reboot:
https://pastebin.com/VDZ32r2D
There are others too
Just added the 1 line for findfs() function and executed it followed by mount commands. Everything worked as it used to.
