Again, should be no difference in the spinup. The only thing I can think of, is that I have linux caching on by default, while Merlin's default is to periodically flush all the internal linux caches. So, I may be caching the drive directory structure while Merlin isn't. But it shouldn't cause a problem as long as the drive has a reasonable spoinup time. If you want to try to emulate the default Merlin behavior, log into the router and enter
nvram set drop_caches=1
nvram commit
and reboot. The trade-off is the drive will need to spin-up more frequently.
This is working fine .. also vice versa on Merlin release.
On my 68P (media-bridge mode) I have used "drop_caches=0" to "activate cashing" on merlin release.
The connected drive will spin-up less frequently now.
One other issue ..
I do have a 4TB WD MyBook USB-disk connected to my 68U (router mode) running on 22E4.
If the USB-disk is connected via the USB3 port all is working fine - for some hours only
At some point the USB-disk will be reconnected as SDB (not as SDA anymore)
This happens within the first 24 hours and after serveral successful disk spin-ups.
But the actual reconnect as SDB happens always on disk spin-up.
The same USB-disk is working fine for months, connected to the USB2 port on the same 68U.
And the same USB-disk is working fine connected to the USB3 port on the 68P, but on Merlin release.
The media-bridge mode should not be related here.
There are some comments and reports about USB3 performance and problems on 68U ..
Yes, the 68P has much better USB3 performance as the 68U.
But these reconnect issues ..
I did not test Merlin release on 68U to verify if the firmware is related to the USB3 problem ..
Do you think this problem is "software-related" ?
Is this USB3 reconnect problem known on 68U ?