HDD gets not detected after reboot

[pascal51882]

Hi. 
I use Linux xenial minimal from the rock64 site. 
The version is the latest. 
The HDD is plugged in via the USB 3.0 Port. 
I tried different adapters.  it s always the same.
When I reboot my rock64 the HDD gets not detected. 
If i unplug it and plug it back in it gets detected. 
It s every time the same. 

Is this a siftware based problem?  
i think so. 
Is there a solution?

[dkryder]

this can also happen if the hdd is not externally powered. if powered through usb the hdd might start spin down when the board loses power and then as the board powers again the boot up sequence may not detect the drive since it had begun power down and the boot up process happens faster than the time it takes the drive to spin up and report ready. this may be more of an issue with boot on sd card & filesystem on hdd. if the hdd is externally powered most of the time the drive does not begin spin down immediately. if externally powered and not recognized it could be software as you mention or a sync issue between usb port and drive interface.

[pascal51882]

if externally powered and not recognized it could be software as you mention or a sync issue between usb port and drive interface.

Yes exactly. The drive is externally powered. Is there a way to resolve the issue? 
My Drive: WD Blue 2TB Interne Festplatte (8,9 cm (3,5 Zoll)), SATA 6 Gb/s BULK WD20EZRZ

[dkryder]

can you mention the usb to sata interface chip you have? also, have you or could you try as a test if the issue exists on the usb-2.0 ?

[pascal51882]

can  you mention the usb to sata interface chip you have? also, have you or could you try as a test if the issue exists on the usb-2.0 ?

I tried two different usb to sata interfaces from Inateck. Is it ok to post a link?
https://www.amazon.de/gp/product/B00N4JL...UTF8&psc=1
this one and an older one.

I have not the option to use USB 2.0
I need USB 3.0, but I will try it later.
If it would work with USB 2.0 would it change something?

Edit:
Wit USB 2.0 it gets detected fine...

[dkryder]

can  you mention the usb to sata interface chip you have? also, have you or could you try as a test if the issue exists on the usb-2.0 ?

I tried two different usb to sata interfaces from Inateck. Is it ok to post a link?
https://www.amazon.de/gp/product/B00N4JL...UTF8&psc=1
this one and an older one.

I have not the option to use USB 2.0
I need USB 3.0, but I will try it later.
If it would work with USB 2.0 would it change something?

Edit:
Wit USB 2.0 it gets detected fine...

that is why i asked you to test, to get better idea of issue. so we know that the hardware[hdd] is fine, at least the usb 2.0 interface. but now issue is with the usb3.0 circuit. i know of earlier issues with some of latest images.  you mention latest builds of xenial, some of the latest did have problems reported before. if you could locate the last  RELEASE version of xenial and try that. i do not have a link but search for  rock64 ayufan xenial RELEASE  or similar either on google or here, to locate the last release, the latest builds are more like alpha/beta builds and are not official releases, was built late last year i think but it has the fewest bugs. so try to find that and check if it will work with usb3.0. if not then log into the chat rock64 channel [the link is at top of page] and ask for ayufan or one of the other devs to help you out. i've not the additional knowledge to take the process to solution. if anyone asks tell them it has ASM1153 chipset.

[pascal51882]

can  you mention the usb to sata interface chip you have? also, have you or could you try as a test if the issue exists on the usb-2.0 ?

I tried two different usb to sata interfaces from Inateck. Is it ok to post a link?
https://www.amazon.de/gp/product/B00N4JL...UTF8&psc=1
this one and an older one.

I have not the option to use USB 2.0
I need USB 3.0, but I will try it later.
If it would work with USB 2.0 would it change something?

Edit:
Wit USB 2.0 it gets detected fine...

that is why i asked you to test, to get better idea of issue. so we know that the hardware[hdd] is fine, at least the usb 2.0 interface. but now issue is with the usb3.0 circuit. i know of earlier issues with some of latest images.  you mention latest builds of xenial, some of the latest did have problems reported before. if you could locate the last  RELEASE version of xenial and try that. i do not have a link but search for  rock64 ayufan xenial RELEASE  or similar  either on google or here, to locate the last release, the latest builds are more like alpha/beta builds and are not official releases,  was built late last year i think but it has the fewest bugs. so try to find that and check if it will work with usb3.0. if not then log into the chat rock64 channel [the link is at top of page] and ask for ayufan or one of the other devs to help you out. i've not the additional knowledge to take the process to solution. if anyone asks tell them it has ASM1153 chipset.

The problem is I have not the option reinstall my rock64.
I use storj and if i have a long off time this is really bad for storj.
An unstable beta/alpha is also a thing...
Will it get fixed in future with normal updates?
If this is possible i just wait for the update.

[Jame3243324]

I have same issue. Every reboot fails. I wonder if there are any official support for the board.

[k8Va]

I have the same problem: https://forum.pine64.org/showthread.php?tid=5875

What do you get when you enter: dmesg -wH?

Turning on and off the hard drives a few times make it work. But it doesnt work by default on USB3.0 on boot.



[Mar27 20:41] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.001330] usb usb5-port1: cannot disable (err = -32)
[ +19.989129] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.001335] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:42] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.001341] usb usb5-port1: cannot disable (err = -32)
[ +1.202664] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.018718] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:44] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.019053] usb usb5-port1: cannot disable (err = -32)
[ +40.660799] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.018685] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:46] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.019019] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:47] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.006564] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:48] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.018923] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:49] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.019101] usb usb5-port1: cannot disable (err = -32)
[ +16.277967] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.006342] usb usb5-port1: cannot disable (err = -32)
[Mar27 21:30] xhci-hcd xhci-hcd.8.auto: port 0 resume PLC timeout
[ +5.742867] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +5.232322] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +0.218864] usb 5-1: device not accepting address 2, error -62
[Mar27 21:31] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +5.232182] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +0.207003] usb 5-1: device not accepting address 3, error -62
[ +5.409325] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +0.207016] usb 5-1: Device not responding to setup address.
[ +0.206919] usb 5-1: device not accepting address 4, error -71
[ +0.006232] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.006210] usb usb5-port1: cannot disable (err = -32)
[ +5.365865] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +5.216288] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +0.207000] usb 5-1: device not accepting address 5, error -62
[ +0.027109] usb usb5-port1: unable to enumerate USB device
[ +18.534735] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +5.216250] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +0.206943] usb 5-1: device not accepting address 6, error -62
[ +5.395727] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +5.229836] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[ +0.218966] usb 5-1: device not accepting address 7, error -62
[ +0.018411] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ +0.018858] usb usb5-port1: cannot disable (err = -32)
[Mar27 21:32] usb 5-1: new SuperSpeed USB device number 8 using xhci-hcd
[ +0.029930] usb 5-1: New USB device found, idVendor=174c, idProduct=55aa
[ +0.018513] usb 5-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ +0.013358] usb 5-1: Product: External HDD
[ +0.006015] usb 5-1: Manufacturer: 01234567890123456789012345678901234567890123
[ +0.006308] usb 5-1: SerialNumber: 201308070213
[ +0.059266] usb-storage 5-1:1.0: USB Mass Storage device detected
[ +0.007795] usb-storage 5-1:1.0: Quirks match for vid 174c pid 55aa: 400000
[ +0.006389] scsi host0: usb-storage 5-1:1.0
[ +0.006746] usbcore: registered new interface driver usb-storage
[ +0.010794] usbcore: registered new interface driver uas
[ +6.364552] scsi 0:0:0:0: Direct-Access WDC WD32 01ABYS-01B9A0 13.0 PQ: 0 ANSI: 5
[ +0.007974] sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ +0.007000] sd 0:0:0:0: [sda] Write Protect is off
[ +0.006170] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[ +0.000435] sd 0:0:0:0: [sda] No Caching mode page found
[ +0.006158] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ +0.080574] sda: sda1
[ +0.007636] sd 0:0:0:0: [sda] Attached SCSI disk
[ +1.791350] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl