CHL-v2/XHL 1.24/1.26/1.31 Big USB Firmware Bug

[Shonk]

I have to move 2tb of data and have been using my drivestations to do it

there seems to be a usb drive problem with the 1.24 firmware

 

I have tried 3 different drivestations

and an iomega drive

all result in the same problems

 

the drives work just fine on DHGL v1 and v2's

but fail with 2 different CHL v2's

 

Im not looking for support

im wanting this to be passed on to be fixed

 

please dont offer me advise on how to fix it as i cant see 4 usb drives all being faulty

i have also used the usb cables that came with them and belkin cables to rule that out

 

I will post the log to aid in fixing it

 

Please can you confirm escalation

 

 

 

 

[Shonk]

   

EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
USB Universal Host Controller Interface driver v3.0
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
eth1: link down
eth1: started
eth1: link up, full duplex, speed 1 Gbps
usb 1-1: new high speed USB device using ehci_marvell and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
XFS mounting filesystem sda6
Ending clean XFS mount for filesystem: sda6
scsi 2:0:0:0: Direct-Access     HDS72505 0KLA360               PQ: 0 ANSI: 2
sd 2:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 38 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 38 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI disk
sd 2:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
XFS mounting filesystem sdb1
Ending clean XFS mount for filesystem: sdb1
bfSetMagicKey > Changed to 0x71 from 0x5c
hub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
usb 1-1: USB disconnect, address 2
sd 2:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdb, sector 737050319
sd 2:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdb, sector 737050559
sd 2:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdb, sector 737050799
I/O error in filesystem ("sdb1") meta-data dev sdb1 block 0x1d009f07       ("xlog_iodone") error 5 buf count 14336
xfs_force_shutdown(sdb1,0x2) called from line 960 of file fs/xfs/xfs_log.c.  Return address = 0xc0276fcc
Filesystem "sdb1": Log I/O Error Detected.  Shutting down filesystem: sdb1
Please umount the filesystem, and rectify the problem(s)
I/O error in filesystem ("sdb1") meta-data dev sdb1 block 0x24fffdb0       ("xfs_trans_read_buf") error 5 buf count 4096
xfs_force_shutdown(sdb1,0x1) called from line 423 of file fs/xfs/xfs_rw.c.  Return address = 0xc0276fcc
xfs_force_shutdown(sdb1,0x1) called from line 423 of file fs/xfs/xfs_rw.c.  Return address = 0xc0276fcc
Buffer I/O error on device sdb1, logical block 92131569
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 92131570
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 92131571
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 92131572
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 92131573
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 92131574
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 92131575
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 92131576
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 92131577
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 92131578
lost page write due to I/O error on sdb1
usb 1-1: new high speed USB device using ehci_marvell and address 3
usb 1-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi 3:0:0:0: Direct-Access     HDS72505 0KLA360               PQ: 0 ANSI: 2
sd 3:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 38 00 00 00
sd 3:0:0:0: [sdc] Assuming drive cache: write through
sd 3:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 38 00 00 00
sd 3:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 3:0:0:0: [sdc] Attached SCSI disk
sd 3:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
xfs_force_shutdown(sdb1,0x1) called from line 423 of file fs/xfs/xfs_rw.c.  Return address = 0xc0276fcc
xfs_force_shutdown(sdb1,0x1) called from line 423 of file fs/xfs/xfs_rw.c.  Return address = 0xc0276fcc
XFS mounting filesystem sdc1
Starting XFS recovery on filesystem: sdc1 (logdev: internal)
Ending XFS recovery on filesystem: sdc1 (logdev: internal)

[Shonk]

   

hub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
usb 1-1: reset high speed USB device using ehci_marvell and address 3
usb 1-1: device not accepting address 3, error -22
usb 1-1: reset high speed USB device using ehci_marvell and address 3
usb 1-1: device not accepting address 3, error -22
usb 1-1: USB disconnect, address 3
sd 3:0:0:0: scsi: Device offlined - not ready after error recovery
sd 3:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 739983871
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
printk: 982 messages suppressed.
Buffer I/O error on device sdc1, logical block 92498752
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 92498753
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 92498754
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 92498755
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 92498756
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 92498757
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 92498758
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 92498759
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 92498760
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 92498761
lost page write due to I/O error on sdc1
sd 3:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 739984111
sd 3:0:0:0: rejecting I/O to offline device
I/O error in filesystem ("sdc1") meta-data dev sdc1 block 0x1d00a51c       ("xlog_iodone") error 5 buf count 28160
xfs_force_shutdown(sdc1,0x2) called from line 960 of file fs/xfs/xfs_log.c.  Return address = 0xc0276fcc
Filesystem "sdc1": Log I/O Error Detected.  Shutting down filesystem: sdc1
Please umount the filesystem, and rectify the problem(s)
xfs_force_shutdown(sdc1,0x1) called from line 423 of file fs/xfs/xfs_rw.c.  Return address = 0xc0276fcc
xfs_force_shutdown(sdc1,0x1) called from line 423 of file fs/xfs/xfs_rw.c.  Return address = 0xc0276fcc
usb 1-1: new high speed USB device using ehci_marvell and address 4
usb 1-1: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
scsi 4:0:0:0: Direct-Access     HDS72505 0KLA360               PQ: 0 ANSI: 2
sd 4:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 38 00 00 00
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 38 00 00 00
sd 4:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 4:0:0:0: [sdb] Attached SCSI disk
sd 4:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
xfs_force_shutdown(sdc1,0x1) called from line 423 of file fs/xfs/xfs_rw.c.  Return address = 0xc0276fcc
xfs_force_shutdown(sdc1,0x1) called from line 423 of file fs/xfs/xfs_rw.c.  Return address = 0xc0276fcc
XFS mounting filesystem sdb1
Starting XFS recovery on filesystem: sdb1 (logdev: internal)
Ending XFS recovery on filesystem: sdb1 (logdev: internal)

[Shonk]

   

Thats a Freecom 100gig mobile drive bus powered just used to for test reasons

it got 25gig into the file copy and the whole nas hard locked up

 

The nas replied to pings but thats it

gave it 20 mins to recover and nothing

wouldnt shut down via the soft off switch on the back

and ended up having to pull the plug

 

nothing showed in the log

 

Feb 28 01:59:04 Nas5 login[4799]: ROOT LOGIN  on 'pts/0'
Feb 28 02:43:17 Nas5 syslogd 1.5.0: restart.

 

Feb 28 01:55:58 Nas5 kernel: scsi 2:0:0:0: Direct-Access     HTS54101 0G9SA00               PQ: 0 ANSI: 2 CCS
Feb 28 01:55:58 Nas5 kernel: sd 2:0:0:0: [sdb] 195371568 512-byte hardware sectors (100030 MB)
Feb 28 01:55:58 Nas5 kernel: sd 2:0:0:0: [sdb] Write Protect is off
Feb 28 01:55:58 Nas5 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
Feb 28 01:55:58 Nas5 kernel: sd 2:0:0:0: [sdb] 195371568 512-byte hardware sectors (100030 MB)
Feb 28 01:55:58 Nas5 kernel: sd 2:0:0:0: [sdb] Write Protect is off
Feb 28 01:55:58 Nas5 kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
Feb 28 01:55:58 Nas5 kernel:  sdb: sdb1
Feb 28 01:55:58 Nas5 kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
Feb 28 01:55:58 Nas5 kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0
Feb 28 01:55:58 Nas5 kernel: XFS mounting filesystem sdb1
Feb 28 01:55:58 Nas5 kernel: eth1: link up, full duplex, speed 1 Gbps

[Shonk]

   

Has this been passed on?

Has buffalo verify'd this?

[Methanoid]

   

This is a big concern and I am surprised that a company seeking to keep a good rep in the marketplace is just choosing to IGNORE A MAJOR BUG.

 

FFS Buffalo sort this out.... or at least try and prove/disprove this bug, because word will spread that your product is broken!

[Shonk]

   

Glad to see you guys got straight on this

and kept us informed

[Methanoid]

   

I guess that was sarcasm? It's not like Buffalo seem to care about a FATAL bug. If buyers find out then this will cost them sales, as well as reputation.

 

This is reported on Nas-central.org yes?

[Shonk]

Bump for a good cause:smileymad:

[davo]

Works fine for me on 1.31 (LS-CHL => Drivestation)

[Dustrega]

For future reference Shonk we report the bugs to the UK support team who escalates the firmware issue to be debugged and rewritten.  We're just being nice enough to support the rest of the world at the same time.  Your issue has been noted and will be sent up the proper chain to have the issue looked into.  Thank you for the detailed logs, they will be helpful in spotting the problem.