Hi,
I`m using OMV 4 on Rock64 with HDD WD RED for NAS solutions, disk is brand new, work only for few days.
I observe that from time to time disk stop working, is not visible in Windows (mapped) and on OMV interface. When I restart OMV it start working for next few days, and than again is stop in random time.
Any solution?
Disk turn off automatically in random time
-
- OMV 4.x
- maciekelga
-
-
Is this an USB3 disk from WD or another USB disk enclosure with a WD RED inside? Host powered or with a separate power brick?
Please prepare SSH login to your board. When this happens the next time you login via SSH and then please provide the output of
Only then reboot and when the system is up again run the aforementioned commands one more time but also lsusb | curl -s -F 'f:1=<-' ix.io. Provide all the generated support URLs in the forum.
-
Is a disk as below
Power supply (5V 11A) is connected to Rock, then via USB-SATA disk is connected (signal and power supply).
https://www.komputronik.pl/product/164920/wd-red-1tb.html -
I think is a UAS problem.
root@NAS:~# lsusb
Bus 005 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0bc2:5030 Seagate RSS LLC FreeAgent GoFlex Upgrade Cable STAE104
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@NAS:~# lsusb -t
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480MI`m starting with OMV, and don`t know how to edit it.
-
Bus 005 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge
...
Bus 002 Device 002: ID 0bc2:5030 Seagate RSS LLC FreeAgent GoFlex Upgrade Cable STAE104Which of these two is the disk you mention?
-
Bus 005 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge
Is a 2,5" WD disk conected via SATA->USB
-
-
is it solution to turn off UAS?
If it's an underpowering problem then not.
-
Now I set command to reset every night OMV, and I will be observe. But I found similar problem and solution was disable UAS.
I think power supply should be enough. -
-
outputs:
ix.io/1JAa
ix.io/1JAbThe output only shows the Seagate Disk being attached (no trace of the WD at all) so no idea what the problem is...
If you think 'the issue' is related to UAS then blacklist it. In the past I contributed code to parse /etc/modprobe.d/rk3328-usb-storage-quirks.conf so in case this file is still there you could adjust contents like this and reboot: options usb-storage quirks=0x2537:0x1066:u,0x2537:0x1068:u,0x174c:0x55aa:u
(disclaimer: I don't use ayufan's image on the Rock64 but my own so no idea how UAS blacklisting might work with his image)
-
I edit /boot/ArmbianEnv.txt same like in last post
https://forum.pine64.org/showthread.php?tid=5137&page=3
Now disk is in usb-storage mode instead uas. I will observe.
-
I edit /boot/ArmbianEnv.txt
Ok, for others who might stumble across this thread: this only works with the Armbian based OMV images available from here: https://sourceforge.net/projec…ngle%20Board%20Computers/
With ayufan images users are on their own. The mechanism to UAS blacklist disks seems to be removed for reasons unknown to me.
Now disk is in usb-storage mode instead uas. I will observe.
Please report back whether this has helped or not.
-
Yes, right, I`m using ayufan version with Armbian.
I will let You know.
-
So, OMV is running since tuesday without restart (almost one week) and disk WD still running, looks that disabled UAS solve a problem. Usually after 2- 3-4 days disk was off.
Today I will connect my second SSD disk to and will observe again.
-
OMV is running more than 2 weeks without issue, so now I`m 100% sure that disable UAS solved a problem.
-
delete
-
delete
-
For the past three years I have had occasional spontaneous unmounts of the second, back-up drive on my NAS. The unmounts seem to occur when my rsync job backs-up the master drive (Boss) to the back-up (Slave). NB, to re-mount the disc I just click on Mount, I do not have to then click on Apply and Agree.
When I ran a test of rsync today both the master and the back-up unmounted.
The ROCK 64 and the two discs get power from a regulated Power Supply, where each drive is powered using a ROCK64 USB 3.0 to SATA III hard drive adapter cable/converter with UASP. The power supply delivers more than enough power for the set-up, and for additional devices, e.g. additional back-up discs - none was attached at the time of the unmount.
Are you able to suggest a reason for the unmount and whether there might be a fix? In case it helps I have attached an edited syslog from the time of the unmount.
-
Further to the message above, my NAS' internal back-up was unmounted as the back-up cron job started. Has anyone any thoughts on why this might be happening (syslog attached for 02:30, the time of the cron job).
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!