lixuewei / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

Random USB HDD "disconnects" #1139

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
RT-N65U,

since around after I upgraded from 071 to 072 and 075 I have noticed that my 
USB HDD randomly gets disconnected:

dmesg log:
System boots and detects HDD:
Jan  1 00:00:06 kernel: usb 1-1: new high speed USB device number 2 using 
xhci_hcd
Jan  1 00:00:06 kernel: usb 1-1: New USB device found, idVendor=04fc, 
idProduct=0c25
Jan  1 00:00:06 kernel: usb 1-1: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
Jan  1 00:00:06 kernel: usb 1-1: Product: USB to Serial-ATA bridge
Jan  1 00:00:06 kernel: usb 1-1: Manufacturer: Sunplus Technology Co.,Ltd.
...
Jan  1 00:00:08 kernel: sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: 
(500 GB/465 GiB)
..

Then randomly:
Jan 26 20:57:21 kernel: usb 1-1: USB disconnect, device number 2
Jan 26 20:57:32 kernel: usb 1-1: new high speed USB device number 4 using 
xhci_hcd
Jan 26 20:57:32 kernel: usb 1-1: New USB device found, idVendor=04fc, 
idProduct=0c25
Jan 26 20:57:32 kernel: usb 1-1: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
Jan 26 20:57:32 kernel: usb 1-1: Product: USB to Serial-ATA bridge
Jan 26 20:57:32 kernel: usb 1-1: Manufacturer: Sunplus Technology Co.,Ltd.
...
Jan 26 20:57:35 kernel: sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: 
(500 GB/465 GiB)
...

The problem is that now the name of my network share changes, sda doesn't get 
replaced but still exists but is invalid, instead I get sdb. Additionally, /opt 
doesn't get remounted but stays mounted on the now invalid sda.
This causes additional errors:

Jan 26 23:38:14 kernel: Buffer I/O error on device sda1, logical block 0
Jan 26 23:38:14 kernel: lost page write due to I/O error on sda1
Jan 26 23:38:14 kernel: EXT4-fs error (device sda1): ext4_find_entry:931: inode 
#16908289: comm minidlnad: reading directory lblock 0
Jan 26 23:38:14 kernel: EXT4-fs (sda1): previous I/O error to superblock 
detected
Jan 26 23:38:14 kernel: Buffer I/O error on device sda1, logical block 0
Jan 26 23:38:14 kernel: lost page write due to I/O error on sda1
Jan 26 23:38:14 kernel: EXT4-fs error (device sda1): ext4_find_entry:931: inode 
#16908289: comm minidlnad: reading directory lblock 0

I am using hd-idle to spin-down the disk after a couple of minutes of 
inactivity, but I have not noticed this random disconnect problem before.

Original issue reported on code.google.com by xno...@gmail.com on 27 Jan 2014 at 1:44

GoogleCodeExporter commented 9 years ago
You need check the filesystem on your HDD

Original comment by Dr.Sydorenko.O on 27 Jan 2014 at 8:43

GoogleCodeExporter commented 9 years ago
Hi,

I have exactly the same problem. I also have the spin-down configured, but I 
don't think is related.
My guess is that it is related to "heavy" use and to the I/O buffer.
I recreated my partition, and reformatted to ext4.
Started to copy big files back and forth and the problem appeared again.

Please let me know if you manage to work around.

Thanks.

Original comment by barnitar...@gmail.com on 29 Jan 2014 at 3:40

GoogleCodeExporter commented 9 years ago
Look at issue 220, comment #49

Original comment by barnitar...@gmail.com on 30 Jan 2014 at 5:12

GoogleCodeExporter commented 9 years ago
My disconnects happened far less often. Maybe once or twice every week.

I updated USB3 AsMedia ASM1042 firmware a few days ago, replugged the external 
HDD (still in the first USB port) and so far no disconnects.

I will report back when the disconnects start again.

Original comment by xno...@gmail.com on 3 Feb 2014 at 3:46

GoogleCodeExporter commented 9 years ago
As stated above this is definitely a hardware issue which plagues us all. It 
can happen on any flash drive or HDD. 

The only known workaround is to use the port closest to the back of the machine.

Original comment by c_u_late...@hotmail.com on 5 Feb 2014 at 1:34