I’m having some grief. I’ve posted elsewhere about a disk that is going faulty on my system, which is based on an MSI K8M Neo-V m/b. My current strategy is to try to add a new disk by adding a new controller. There’s good news and bad news. The good news is that everything’s detected and sometimes works. The bad news is that it doesn’t work all the time
I’ve borrowed a Sweex PU102 - SATA Card PCI - PU102 - which uses the Sil 3512 chip and I’ve bought a Samsung HD103SJ 1 TB SATA disk - Samsung SpinPoint F3 Desktop Class 1 TB Internal hard drive - 300 MBps - 7200 rpm
I’ve partitioned the disk and installed Ubuntu 10.04 (I run both opensuse 11.2 and Ubuntu 10.04 on the machine and I had to pick one!). It boots and kind of runs but with lots of flakiness and lockups. There’s lots of lines like this in /var/log/messages:
Jan 5 22:53:27 piglet kernel: 157.390039] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 5 22:53:32 piglet kernel: 162.390035] ata5: hard resetting link
Jan 5 22:53:33 piglet kernel: 162.740037] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 5 22:53:33 piglet kernel: 162.780287] ata5.00: configured for UDMA/100
Jan 5 22:53:33 piglet kernel: 162.780294] ata5.00: device reported invalid CHS sector 0
Jan 5 22:53:33 piglet kernel: 162.780302] ata5: EH complete
Jan 5 22:54:03 piglet kernel: 193.040089] ata5: hard resetting link
Jan 5 22:54:03 piglet kernel: 193.390060] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 5 22:54:03 piglet kernel: 193.430287] ata5.00: configured for UDMA/100
Jan 5 22:54:03 piglet kernel: 193.430295] ata5.00: device reported invalid CHS sector 0
Jan 5 22:54:03 piglet kernel: 193.430308] ata5: EH complete
Jan 5 22:54:07 piglet kernel: 197.042033] ata5.00: limiting speed to UDMA/66:PIO4
Jan 5 22:54:07 piglet kernel: 197.042070] ata5: hard resetting link
Jan 5 22:54:07 piglet kernel: 197.390059] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 5 22:54:07 piglet kernel: 197.430288] ata5.00: configured for UDMA/66
Jan 5 22:54:07 piglet kernel: 197.430305] ata5: EH complete
Jan 5 22:54:08 piglet kernel: 197.821413] ata5.00: configured for UDMA/66
Jan 5 22:54:08 piglet kernel: 197.821437] ata5: EH complete
Jan 5 22:54:38 piglet kernel: 228.040099] ata5: hard resetting link
Jan 5 22:54:38 piglet kernel: 228.390046] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 5 22:54:38 piglet kernel: 228.430286] ata5.00: configured for UDMA/66
Jan 5 22:54:38 piglet kernel: 228.430309] ata5: EH complete
I can find lots of threads here and elsewhere about people with problems where some of these lines occur, but none that I’ve been able to use to clarify my own troubles.
I rebooted into the existing suse 11.2 installation (which is on the disk that is slowly failing with increasing bad sectors) and looked at the disk with smart:
[smartctl 5.39 2009-08-08 r2872~ x86_64-unknown-li - Smartctl-a-hd103sj#1
I then ran a long test (smartctl -t long - took 157 minutes) and had another look:
[smartctl 5.39 2009-08-08 r2872~ x86_64-unknown-li - Smartctl-a-hd103sj#2 which as far as I can tell says there were no problems. I used dd to copy 5 GB from /dev/zero to the disk a few times; it completed without errors and nothing in the log.
I also ran hdparm -tT
Timing cached reads: 1044 MB in 2.00 seconds = 521.51 MB/sec
Timing buffered disk reads: 244 MB in 3.01 seconds = 81.07 MB/sec
and this is what lspci shows:
00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:0b.0 Mass storage controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
00:0c.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link)
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200] (rev a1)
Does this give enough information for anybody to offer an opinion on whether this is a disk problem or a controller problem or something else? What other information would be useful to track down the problem?
Over the next few days I’m hoping to be able to test with another new disk and another new controller, but it would be useful to have some clue what to do in the meantime