Ext USB disk plugged out/in repeadtely

[mdi]

It finally seems a disk issue. I attached the docking station to a Raspberry Pi and run a bad block scan with fsck. Then i run a backup of the largest dataset i have. The backup have been running for 3 days uninterrupted now, from the NAS to the RPi via samba.

I'll scan also the other disk then I'll try again attaching the docking station to the NAS.

I'll feedback with more details if I'm successful.

[Jocko]

:thumbup
Indeed these hardware problems always take a lot of time ...

[mdi]

The docking station on the RPi worked perfectly and backupped my data in 3-4 days without issues, continuously.

Then it stayed calm (i performed no more data transfers), but still connected, for other 3-4 days.

But as soon as i moved it back to the NAS it started disconnecting and reconnecting again.

I'm going to backup data via network, even if it is slower, as i cannot find a stable and safe solution when any disk is connected directly to the NAS USB port.

Am I the only one having this issue? :dontknow
No one has a disk attached to the nas on the front USB port (NSP2)?

[Jocko]

Hi mdi,

I have two nwsp2 and when I plug a disk or a docking station my USB drives are not disconnected.
So your issue is not usual.

If you have another usb interface or an usb hub you can test if you have the same behaviour

[mdi]

But why is the USB disk reconnecting after a safe-removal? :fists
Isn't it supposed to stay disconnected until I physically disconnect and reconnect it?

[Jocko]

Hi mdi,

It is a significant information.

What you must know:
a safe remove action allows to undo how the device is used by the firmware on the user side: mount point, nas database and servers configuration updating (ftp, smba,...). So for example allows to unmount the partition without corrupting its file system.
This action does nothing on the kernel side : hardware side.
When the kernel detects a new device or a device is dettached, kernel performs an udev event to run the expected actions by the firmware on the user side.

What your last feedback means:
The kernel fails to manage rightly your device as the one is regulary brought down and up. Then after a remove safe action, an udev action is performed by the kernel which mounts again your disk.

Now we go back at the original question: why your disk is regulary brought down and up.
It seems it is not a power supply as it works nicely on your rspb.
So it may be an hardware issue on nswp2 side (it is why I asked you for testing with another usb interface), an usb driver issue : it does not support rightly your device (it is why I asked you previously for updating the usb id database) and ???

[fvdw]

But why is the USB disk reconnecting after a safe-removal? :fists
Isn't it supposed to stay disconnected until I physically disconnect and reconnect it?

In addition to Jocko's comment
This can only happen if it is reconnected again, so unplug and plug in again or if your usb-disk hub has a problem with its power supply. Power on / off will have same effect as unplu/plug. So besides a unstable power supply of your usb-disk hub It might be that you are suffering from a bad connector or cable. Did you try to use other cables or clean the connectors?

[mdi]

Thank you both, guys.

I exclude to be a cable issue as the docking station works great on a RPi and i tried also another USB to SATA set of cables in place of the docking station. Exactly same issue.

The docking station is brand new.

Everything is attached to a small UPS, while the RPi is not.
But on the RPi everything is stable and on the NAS is not.

Jocko, with "another USB interface" you mean another cable, as fvdw suggested, or a different usb port? I think i can just use the front usb port on the NSP2.

I also updated the usb ids and the codes seems to be recognized:

Code: Select all

T:  Bus=01 Lev=02 Prnt=26 Port=00 Cnt=01 Dev#= 27
 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=6
4 #Cfgs=  1
P:  Vendor=048d ProdID=1336 Rev=01.00
S:  Manufacturer=Generic
S:  Product=Mass Storage Device
S:  SerialNumber=00000000000006
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Pr
ot=50 Driver=usb-storage

T:  Bus=01 Lev=02 Prnt=26 Port=03 Cnt=02 Dev#= 28
 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=6
4 #Cfgs=  1
P:  Vendor=152d ProdID=2352 Rev=01.00
S:  Manufacturer=JMicron
S:  Product=USB to ATA/ATAPI Bridge
S:  SerialNumber=DC42893059FF
C:  #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=2mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Pr
ot=50 Driver=usb-storage
root@nas:/usr/share # grep -i 152d usb.ids
        02b6  DCP-8152DN
152d  JMicron Technology Corp. / JMicron USA Tech
nology Corp.
root@nas:/usr/share # grep -i 2352 usb.ids
        2352  ATA/ATAPI Bridge


I suspect that the USB port of the nas doesn't work well, apart from the disks (WD Red 2Gb, 3.5"). I tried 2 different docking stations plus the usb-sata cable on the nas and i always had this issue.

At least one of the 2 disks was performing great on the RPi, but not when i attached it to the NAS. That's why now i sudpect more the usb port of the nas or the nas driver.

What do you think?

I can manage to attach the docking to the RPi since it works. I won't go gigabit fast, as the RPi is 10/100ethernet, but i prefere to have slow regular backups than not having at all.

[Jocko]

Jocko, with "another USB interface" you mean another cable, as fvdw suggested, or a different usb port? I think i can just use the front usb port on the NSP2.

Hi mdi,

My suggestion is to use another usb hard disk interface instead of your docking station. (=> if you have the same behaviour that would mean it is an hardware issue on the NAS side)

[mdi]

Yes, i used a different usb-sata adapter too, instead of the docking station, but the issue is the same.