linux - Motherboard/PSU crippling USB and Sata
2013-12
celebdor
I very recently bought a new desktop computer. The motherboard is: Z77MX-D3H and the power supply is ocz zs series 550w.
The issue I have is that once I boot to the operating system (I have tried with fedora and Ubuntu with kernels 2.6.38 - 3.4.0), my hard drive (2.5" Magnetic) occasionally makes a power switch noise and it resets. Needless to say, when this drive is the OS drive, the OS crashes. I also have a SSD that works fine with the same OS configurations, but if I have the magnetic hard drive attached as second drive, it works erratically and the reconnects result in corrupted data.
I also noticed that whenever I plug an external hard drive USB2.0 or USB3.0 to the computer the issue with the reconnects is even worse:
[ 52.198441] sd 7:0:0:0: [sdc] Spinning up disk...
[ 57.955811] usb 4-3: USB disconnect, device number 3
[ 58.023687] .ready
[ 58.023914] sd 7:0:0:0: [sdc] READ CAPACITY(16) failed
[ 58.023919] sd 7:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 58.023932] sd 7:0:0:0: [sdc] Sense not available.
[ 58.024061] sd 7:0:0:0: [sdc] READ CAPACITY failed
[ 58.024063] sd 7:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 58.024064] sd 7:0:0:0: [sdc] Sense not available.
[ 58.024099] sd 7:0:0:0: [sdc] Write Protect is off
[ 58.024101] sd 7:0:0:0: [sdc] Mode Sense: 00 00 00 00
[ 58.024135] sd 7:0:0:0: [sdc] Asking for cache data failed
[ 58.024137] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 58.024400] sd 7:0:0:0: [sdc] READ CAPACITY(16) failed
[ 58.024402] sd 7:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 58.024405] sd 7:0:0:0: [sdc] Sense not available.
[ 58.024448] sd 7:0:0:0: [sdc] READ CAPACITY failed
[ 58.024450] sd 7:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 58.024451] sd 7:0:0:0: [sdc] Sense not available.
[ 58.024469] sd 7:0:0:0: [sdc] Asking for cache data failed
[ 58.024471] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 58.024472] sd 7:0:0:0: [sdc] Attached SCSI disk
[ 58.407725] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
[ 58.424921] scsi8 : usb-storage 4-3:1.0
[ 59.424185] scsi 8:0:0:0: Direct-Access WD My Passport 0740 1003 PQ: 0 ANSI: 6
[ 59.424406] scsi 8:0:0:1: Enclosure WD SES Device 1003 PQ: 0 ANSI: 6
[ 59.425098] sd 8:0:0:0: Attached scsi generic sg2 type 0
[ 59.425176] ses 8:0:0:1: Attached Enclosure device
[ 59.425248] ses 8:0:0:1: Attached scsi generic sg3 type 13
[ 61.845836] sd 8:0:0:0: [sdc] 976707584 512-byte logical blocks: (500 GB/465 GiB)
[ 61.845838] sd 8:0:0:0: [sdc] 4096-byte physical blocks
[ 61.846336] sd 8:0:0:0: [sdc] Write Protect is off
[ 61.846338] sd 8:0:0:0: [sdc] Mode Sense: 47 00 10 08
[ 61.846718] sd 8:0:0:0: [sdc] No Caching mode page present
[ 61.846720] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 61.848105] sd 8:0:0:0: [sdc] No Caching mode page present
[ 61.848106] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 61.857147] sdc: sdc1
[ 61.858915] sd 8:0:0:0: [sdc] No Caching mode page present
[ 61.858916] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 61.858918] sd 8:0:0:0: [sdc] Attached SCSI disk
[ 69.875809] usb 4-3: USB disconnect, device number 4
[ 70.275816] usb 4-3: new SuperSpeed USB device number 5 using xhci_hcd
[ 70.293063] scsi9 : usb-storage 4-3:1.0
[ 71.292257] scsi 9:0:0:0: Direct-Access WD My Passport 0740 1003 PQ: 0 ANSI: 6
[ 71.292505] scsi 9:0:0:1: Enclosure WD SES Device 1003 PQ: 0 ANSI: 6
[ 71.293527] sd 9:0:0:0: Attached scsi generic sg2 type 0
[ 71.293668] ses 9:0:0:1: Attached Enclosure device
[ 71.293758] ses 9:0:0:1: Attached scsi generic sg3 type 13
[ 73.323804] usb 4-3: USB disconnect, device number 5
[ 101.868078] ses 9:0:0:1: Device offlined - not ready after error recovery
[ 101.868124] ses 9:0:0:1: Failed to get diagnostic page 0x50000
[ 101.868131] ses 9:0:0:1: Failed to bind enclosure -19
[ 101.868288] sd 9:0:0:0: [sdc] READ CAPACITY(16) failed
[ 101.868292] sd 9:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 101.868296] sd 9:0:0:0: [sdc] Sense not available.
[ 101.868428] sd 9:0:0:0: [sdc] READ CAPACITY failed
[ 101.868434] sd 9:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 101.868439] sd 9:0:0:0: [sdc] Sense not available.
[ 101.868468] sd 9:0:0:0: [sdc] Write Protect is off
[ 101.868473] sd 9:0:0:0: [sdc] Mode Sense: 00 00 00 00
[ 101.868580] sd 9:0:0:0: [sdc] Asking for cache data failed
[ 101.868584] sd 9:0:0:0: [sdc] Assuming drive cache: write through
[ 101.868845] sd 9:0:0:0: [sdc] READ CAPACITY(16) failed
[ 101.868849] sd 9:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 101.868854] sd 9:0:0:0: [sdc] Sense not available.
[ 101.868894] sd 9:0:0:0: [sdc] READ CAPACITY failed
[ 101.868898] sd 9:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 101.868903] sd 9:0:0:0: [sdc] Sense not available.
[ 101.868961] sd 9:0:0:0: [sdc] Asking for cache data failed
[ 101.868966] sd 9:0:0:0: [sdc] Assuming drive cache: write through
[ 101.868969] sd 9:0:0:0: [sdc] Attached SCSI disk
Now, if I plug the same drive to the powered usb 2.0 hub of my monitor, the issue is not reproduced (at least on a 20h long operation). Also the issue of the usb reconnects is less frequent if the hard drive is plugged before I switch on the computer.
Does anybody have some advice as to what I could do? Which is the faulty part/s that I should replace? As for me, I really don't know if to point my finger to the PSU or the Motherboard (I have updated to the latest firmware and checked the BIOS settings several times).
EDIT: The reconnects are happening both in the Sata connected drives and the USBX connected drives.
Magicianeer
I had a similar issue with an old Dell. One of the Harddisk power line bundles from its powersupply was "weak".
A device (DVDROM, CDRW or HD) drawing current on that weak line would (occasionally) fail its operation and reset itself. If any other part of the machine was drawing substantial power when the device on the weak line is used, then a system-reset would occur.
For troubleshooting, try putting all internal devices on one power string, then another string. stress the system with each configuration.
Seems you can run with only SSD internal and all other devices as external powered USB.
celebdor
After giving it more thought I took my chances and replaced the PSU. It is early to say, but for the moment the system is stable.
What gave it away was the fact that not only the USB devices (where the power goes through the mainboard were malfunctioning, but also the directly powered Sata drives.
bmdhacks
I recently purchased a 64gb usb thumb drive, but for some reason it appears as two disks on every system I've insert it in. I've tried to repartition it in Linux, Windows, and MacOS to no avail. Here's the dmesg when I insert it in a linux box:
usb 1-6: USB disconnect, address 4 usb 1-5: new high speed USB device using ehci_hcd and address 5 usb 1-5: New USB device found, idVendor=1307, idProduct=0165 usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-5: Product: USB Mass Storage Device usb 1-5: Manufacturer: USBest Technology usb 1-5: SerialNumber: 09090388b7b0a7 usb 1-5: configuration #1 chosen from 1 choice scsi5 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 5:0:0:0: Direct-Access 0.00 PQ: 0 ANSI: 2 scsi 5:0:0:1: Direct-Access 0.00 PQ: 0 ANSI: 2 sd 5:0:0:0: Attached scsi generic sg4 type 0 sd 5:0:0:1: Attached scsi generic sg5 type 0 sd 5:0:0:0: [sdc] 61440000 512-byte hardware sectors: (31.4 GB/29.2 GiB) sd 5:0:0:0: [sdc] Write Protect is off sd 5:0:0:0: [sdc] Mode Sense: 00 00 00 00 sd 5:0:0:0: [sdc] Assuming drive cache: write through sd 5:0:0:1: [sdd] 63995904 512-byte hardware sectors: (32.7 GB/30.5 GiB) sd 5:0:0:1: [sdd] Write Protect is off sd 5:0:0:1: [sdd] Mode Sense: 00 00 00 00 sd 5:0:0:1: [sdd] Assuming drive cache: write through sd 5:0:0:0: [sdc] Assuming drive cache: write through sdc: sd 5:0:0:0: [sdc] Attached SCSI removable disk sd 5:0:0:1: [sdd] Assuming drive cache: write through sdd: sd 5:0:0:1: [sdd] Attached SCSI removable disk
Can somebody tell me how I can re-partition this thing to appear as a single drive? I've had no luck with any of the partition utilities on any OS because this drive doesn't appear as one disk with two partitions, but two physical disks.
UPDATE
The drive is a Centon ElitePlus.
I'm beginning to think that something is physically wrong with this drive. Can anyone confirm?
Marcin
Here is the explanation directly from Centon:
Question: I recently purchased one of your 64GB DataStick flash drives, and I was surprised to find that the 64GB device was formatted with two partitions. Why is this? Can it be re-configured?
Answer: Due to a limitation in Windows 2000/XP/2003 computers, drive volumes cannot be formatted in capacities larger than 32GB using the FAT32 file system. As a result, to ensure the drive can be recognized by the most number of computer systems, our 64GB drive is partitioned into two 32GB volumes. The Windows formatted capacity is roughly around 30GB.
When the 64GB drive is connected to your Windows computer, it will be assigned two drive letters.
The drive cannot be reconfigured into a single 64GB partion. The partition on these drives is hardcoded into the USB-to-flash controller chip.
So no, your drive is not faulty. They decided that the best thing for you, the consumer, is to actually use two seperate drives. I would be pissed if I ordered a USB drive and realized that the manufacturer created this restriction without any mention on the product description page.
quack quixote
It doesn't appear to be two partitions, it appears as two separate drives. If it were two partitions on a single drive, you'd see device names like sdc1 and sdc2.
It's likely the drive is implemented as two physical drives at the hardware layer, and depends on a special driver to allow the OS to see it as a single drive. It may also be a chipset limitation (in whatever chipset is used in the thumbdrive hardware).
Either way, it doesn't seem likely that you'll be able to force it to be seen as a single drive. If you require this functionality, return the device for a refund and buy a different device.