October 25, 201015 yr hallo everyone i have recently ordered a WD EARS 2T HD. I know i have to put a jumper on pins 7-8 . But i remember the old days (when we had to define master and slave drives using jumpers) that once i had a problem with a configuration and finally found out that it was due to a faulty jumper. I know that this is very far-fetched but better be safe than sorry. So, my question is: is there a command that can help me verify that a hdd is jumpered?
October 25, 201015 yr I don't know of one. Can't you just look at the drive to see if it has a jumper or not? Also, in the case of the WD EARS, the jumper has nothing to do with master/slave settings. Instead it sets the drive in compatibility mode, which means that it shifts the drive's alignment (so that it starts at sector 63 instead of 64).
October 25, 201015 yr Can't you just look at the drive to see if it has a jumper or not? I think he meant via software, such as with hdparm.
October 25, 201015 yr Does anyone have an EARS drive, that is not jumpered? If so, please post the results from hdparm -i -I Compare to this (EARS with 7-8 jumper): Model=WDC WD20EARS-00MVWB0 , FwRev=50.0AB50 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50 BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16? CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=18446744073321613488 Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 3907029168 device size with M = 1024*1024: 1907729 MBytes device size with M = 1000*1000: 2000398 MBytes (2000 GB) cache/buffer size = unknown
October 25, 201015 yr Author Also, in the case of the WD EARS, the jumper has nothing to do with master/slave settings. Instead it sets the drive in compatibility mode, which means that it shifts the drive's alignment (so that it starts at sector 63 instead of 64). I know that. I was just explaining why I am being so paranoid Does anyone have an EARS drive, that is not jumpered? If so, please post the results from hdparm -i -I Compare to this (EARS with 7-8 jumper): Model=WDC WD20EARS-00MVWB0 , FwRev=50.0AB50 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50 BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16? CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=18446744073321613488 Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 3907029168 device size with M = 1024*1024: 1907729 MBytes device size with M = 1000*1000: 2000398 MBytes (2000 GB) cache/buffer size = unknown Unless someone posts before i receive my new WD EARS, I will post the results of hdparm -i -I before i use the jumper myself
October 25, 201015 yr Non jumpered EARS drive in Unraid system: Model=WDC WD20EARS-00S8B1 , FwRev=80.00A80, SerialNo= W D-WCAVY1922315 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50 BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?0? CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=18446744073321613488 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 udma6 AdvancedPM=no WriteCache=enabled Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7 * signifies the current active mode ATA device, with non-removable media Model Number: WDC WD20EARS-00S8B1 Serial Number: WD-WCAVY1922315 Firmware Revision: 80.00A80 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5 Standards: Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 3907029168 device size with M = 1024*1024: 1907729 MBytes device size with M = 1000*1000: 2000398 MBytes (2000 GB) Cheers, -jj-
October 25, 201015 yr Author thanx jj666 Well, no differences in the hdparm -i -I output. Any other suggestions? well, if i'm right, i see a difference but only in this line: jumpered: BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16? non-jumpered: BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?0? and i dont know if it has to do with jumpering or something else
October 25, 201015 yr For what it's worth, both of my jumpered WD20EARS drives have this: MultSect=?16?
October 25, 201015 yr That is the MultSect setting... it can be changed with the hdparm -m setting. It is a tunable performance parameter. But the test would be to install the jumper, and see if it changes.
October 26, 201015 yr My two EARS with jumper (firmware 80.00A80): BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?0? Looks like the MultSect indicates that it has nothing to do with if the jumper is installed? I also recently just received an EARS with firmware 51.0AB51. The first preclear completed in 27 hours where as all my EARS took 30 hours. It is still going through a second round of preclear so I am heistant to issue any commands to the drive.
November 3, 201015 yr Author Does anyone have an EARS drive, that is not jumpered? If so, please post the results from hdparm -i -I Compare to this (EARS with 7-8 jumper): Model=WDC WD20EARS-00MVWB0 , FwRev=50.0AB50 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50 BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16? CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=18446744073321613488 Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 3907029168 device size with M = 1024*1024: 1907729 MBytes device size with M = 1000*1000: 2000398 MBytes (2000 GB) cache/buffer size = unknown Just FYI i just got my EARS drive and tried hdparm -i -I with and without the jumper. The results are identical.. That either means that this command cannot provide info about jumpering or that the jumper i used does not work. i think the former is more possible than the latter
Archived
This topic is now archived and is closed to further replies.