[opensuse] New WD Drives only initialize at 1.5Gbps on boot? (old drives are 3.0Gbps)
Guys, Here is a new one on me. I had a failure of a drive in a dmraid array, so I have replaced the array with a new pair of Carvair Black 1T drives. (WD1002FAEX-00Z3A0) The problem I see is that the drives only appear to come up at 1.5Gbps (SATA-1) instead of 3.0Gbps (SATA-II). My old drive that was the survivor from the failed array initializes just fine at 3.0Gbps. Here is the relevant boot info (new drives are ata1, ata2, old is ata3): [ 0.895439] sata_nv 0000:00:08.0: PCI INT A -> Link[APSJ] -> GSI 22 (level, low) -> IRQ 22 [ 0.897884] sata_nv 0000:00:08.0: setting latency timer to 64 [ 0.898152] scsi2 : sata_nv [ 0.900609] scsi3 : sata_nv [ 0.903086] ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xc000 irq 22 [ 0.905490] ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xc008 irq 22 [ 0.980910] pata_amd 0000:00:06.0: version 0.4.1 [ 0.980946] pata_amd 0000:00:06.0: setting latency timer to 64 [ 0.981318] scsi4 : pata_amd [ 0.983763] scsi5 : pata_amd [ 0.986587] ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xe800 irq 14 [ 0.988943] ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xe808 irq 15 [ 0.991351] ata5: port disabled. ignoring. [ 1.353358] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1.373351] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.380285] ata3.00: ATA-8: ST3750528AS, CC35, max UDMA/133 [ 1.382539] ata3.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 1.386569] ata1.00: ATA-8: WDC WD1002FAEX-00Z3A0, 05.01D05, max UDMA/133 [ 1.388856] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 1.396954] ata3.00: configured for UDMA/133 [ 1.404399] ata1.00: configured for UDMA/133 [ 1.406814] scsi 0:0:0:0: Direct-Access ATA WDC WD1002FAEX-0 05.0 PQ: 0 ANSI: 5 [ 1.873353] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1.880837] ata2.00: ATA-8: WDC WD1002FAEX-00Z3A0, 05.01D05, max UDMA/133 [ 1.883126] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 1.897864] ata2.00: configured for UDMA/133 [ 1.900254] scsi 1:0:0:0: Direct-Access ATA WDC WD1002FAEX-0 05.0 PQ: 0 ANSI: 5 [ 1.902806] scsi 2:0:0:0: Direct-Access ATA ST3750528AS CC35 PQ: 0 ANSI: 5 [ 2.370021] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.376766] ata4.00: ATAPI: TSSTcorp DVD+/-RW TS-H653A, D400, max UDMA/33 [ 2.379072] ata4.00: applying bridge limits [ 2.393432] ata4.00: configured for UDMA/33 [ 2.397364] scsi 3:0:0:0: CD-ROM TSSTcorp DVD+-RW TS-H653A D400 PQ: 0 ANSI: 5 [ 2.399844] ata6: port disabled. ignoring. [ 2.412331] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 2.414736] sd 0:0:0:0: [sda] Write Protect is off [ 2.417016] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 2.417039] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.419481] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 2.421858] sd 1:0:0:0: [sdb] Write Protect is off [ 2.424172] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 2.424194] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.424621] sd 2:0:0:0: [sdc] 1465149168 512-byte logical blocks: (750 GB/698 GiB) [ 2.424677] sd 2:0:0:0: [sdc] Write Protect is off [ 2.424680] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [ 2.424703] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA The new drives are capable of 6.0Gbps. Do I need to set a jumper to limit them to 3.0Gbps in order for the system to initialize them at 3.0Gbps? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/07/23 09:44 (GMT-0500) David C. Rankin composed:
Guys,
Here is a new one on me. I had a failure of a drive in a dmraid array, so I have replaced the array with a new pair of Carvair Black 1T drives. (WD1002FAEX-00Z3A0) The problem I see is that the drives only appear to come up at 1.5Gbps (SATA-1) instead of 3.0Gbps (SATA-II). My old drive that was the survivor from the failed array initializes just fine at 3.0Gbps. ... The new drives are capable of 6.0Gbps. Do I need to set a jumper to limit them to 3.0Gbps in order for the system to initialize them at 3.0Gbps?
Maybe WD preconfigures them as SATA1 via jumper or software? People who replace SATA drives on controllers only supporting SATA1 sometimes find drives not so configured won't be recognized at all. Maybe you need to remove an existing jumper, or run WD's setup utility, to free it from a safety valve. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/23/2011 09:52 AM, Felix Miata wrote:
Guys,
Here is a new one on me. I had a failure of a drive in a dmraid array, so I have replaced the array with a new pair of Carvair Black 1T drives. (WD1002FAEX-00Z3A0) The problem I see is that the drives only appear to come up at 1.5Gbps (SATA-1) instead of 3.0Gbps (SATA-II). My old drive that was the survivor from the failed array initializes just fine at 3.0Gbps. ... The new drives are capable of 6.0Gbps. Do I need to set a jumper to limit them to 3.0Gbps in order for the system to initialize them at 3.0Gbps?
Maybe WD preconfigures them as SATA1 via jumper or software? People who replace SATA drives on controllers only supporting SATA1 sometimes find drives not so configured won't be recognized at all. Maybe you need to remove an existing jumper, or run WD's setup utility, to free it from a safety valve.
Thanks Felix, I'll check the setup utility. There are no jumpers at all on the drives. The jumper settings for the drive are here: http://wdc.custhelp.com/app/answers/detail/search/1/a_id/5387#jumper What I don't know is if I need to set the PHY jumper on pins 5-6 to get it recognized as a 3.0 Gbps drive. It seems that since it is a 6.0Gbps drive, it should fall back to 3.0, but conceivably, it could default from 6.0->1.5 unless pins 5-6 are set?? I'll give that a go. Advise: Warning: NEVER delete a partition in cfdisk to create 2 partitions with dmraid after Manually configure block devices, filesystems and mountpoints have been set. (really screws with dmraid metadata and existing partitions are worthless) Solution: delete the array from the bios and re-create to force creation under a new /dev/mapper ID, reinstall/repartition :p -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/23/2011 01:02 PM, David C. Rankin wrote:
Thanks Felix, I'll check the setup utility. There are no jumpers at all on the drives. The jumper settings for the drive are here:
http://wdc.custhelp.com/app/answers/detail/search/1/a_id/5387#jumper
What I don't know is if I need to set the PHY jumper on pins 5-6 to get it recognized as a 3.0 Gbps drive. It seems that since it is a 6.0Gbps drive, it should fall back to 3.0, but conceivably, it could default from 6.0->1.5 unless pins 5-6 are set?? I'll give that a go.
It was the jumpers! With the new 6.0Gbps WDC drives, you have to limit the drives to 3.0Gbps in order for some sata controllers to recognize the drives as SATA-II drives instead of SATA-I drives. This is on a older Tyan Tomcat 8KE board (S2865) with the following nvidia SATA controllers: 13:23 nirvana:~> lspci <snip> 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) After setting pins 5-6 on each of the WD1002FAEX-00Z3A0 drives, the drives came right up at 3.0Gbps: 13:23 nirvana:~> sudo dmesg | grep ata <snip> [ 1.363358] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.370543] ata1.00: ATA-8: WDC WD1002FAEX-00Z3A0, 05.01D05, max UDMA/133 [ 1.372815] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 1.380018] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.386960] ata3.00: ATA-8: ST3750528AS, CC35, max UDMA/133 [ 1.389290] ata3.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 1.389303] ata1.00: configured for UDMA/133 [ 1.406937] ata3.00: configured for UDMA/133 [ 1.853354] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1.860937] ata2.00: ATA-8: WDC WD1002FAEX-00Z3A0, 05.01D05, max UDMA/133 [ 1.863299] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 1.877002] ata2.00: configured for UDMA/133 [ 2.350019] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.356766] ata4.00: ATAPI: TSSTcorp DVD+/-RW TS-H653A, D400, max UDMA/33 [ 2.359131] ata4.00: applying bridge limits [ 2.373431] ata4.00: configured for UDMA/33 Thanks Istvan, Felix for your thoughts! -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2011. július 23. 16:44 napon "David C. Rankin" <drankinatty@suddenlinkmail.com> írta:
Guys,
Here is a new one on me. I had a failure of a drive in a dmraid array, so I have replaced the array with a new pair of Carvair Black 1T drives. (WD1002FAEX-00Z3A0) The problem I see is that the drives only appear to come up at 1.5Gbps (SATA-1) instead of 3.0Gbps (SATA-II). My old drive that was the survivor from the failed array initializes just fine at 3.0Gbps. Here is the relevant boot info (new drives are ata1, ata2, old is ata3):
[snip] David, Can't it be that your fakeraid controller has only SATA1 interface? When you connected your old drives and got the 3 Gbps speed, did yout connect them to the very same controller? Or, maybe, to another one that has SATA2 interface? Just a guess. Cheers, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
David C. Rankin -
Felix Miata -
Istvan Gabor