December 21, 201312 yr I just purchased a 3TB WD red drive to expand my array. I have a 3TB 7200rpm Toshiba drive as my parity drive. This system was previously on a Gigabyte motherboard, so it may be HPA. Ideally, I would like to keep the 7200rpm drive as my parity. How can I determine whether this is a manufacturer difference or HPA? What is the best way to make the 7200rpm drive look bigger?
December 22, 201312 yr Author hdparm says HPA is enabled. Is there a safe way to remove it from an active parity drive?
December 22, 201312 yr hdparm says HPA is enabled. Is there a safe way to remove it from an active parity drive? I don't have a direct answer to your question but the following thread is devoted to this problem: http://lime-technology.com/forum/index.php?topic=10866.0
December 22, 201312 yr Clearly this is an HPA issue. Just follow the removal procedures outlined in the thread Frank1940 linked to. Either method works fine -- I've used HDAT2 several times and it's very simple; but the HDParm method is just as easy as long as you're VERY careful that you input the correct value for resetting the block count. In either case, be CERTAIN that you're referring to the correct disk when you make the change !!
December 22, 201312 yr Author Ok, I'll use hdparm to reset the size (no cd drive). What line should I look at in the syslog to find the correct size? Do I need to rebuild the parity disk after doing this?
December 22, 201312 yr Just log in and do this: hdparm -N /dev/sdx ... where the x is the correct drive designation for your parity drive You'll get a response something like this: /dev/sdx: max sectors = 586070255/586072368, HPA is enabled The second number is the native # of sectors on the disk (the first is the current setting) Then just do this: hdparm -N pnnnnnnnnnn /dev/sdx where the "nnnnnnnnnn" is the correct number of sectors (Leave the "p" in place -- that makes the change permanent, which is what you want); and, again, the "x" is the correct letter for your disk. After that command, do another "hdparm -N /dev/sdx" to confirm that it was effective. ... and yes, you'll need to rebuild parity after doing this.
December 22, 201312 yr Author I'm getting this error when running the hdparm command: SG_IO: bad/missing sense data, sb[] Followed by a bunch of numbers. How should I fix this??
December 22, 201312 yr I'm getting this error when running the hdparm command: SG_IO: bad/missing sense data, sb[] Followed by a bunch of numbers. How should I fix this?? I'm not a "Linux guy", so I really don't know. But from what you listed above, did you by any chance type "sb" instead of "sd" when typing the disk designation? If so, that would likely be why the command isn't working
December 22, 201312 yr Author All the other threads I can find on this issue seem to involve virtual machines and/or usb hard drives. I'm using neither of those, so I'm stumped.
December 22, 201312 yr All the other threads I can find on this issue seem to involve virtual machines and/or usb hard drives. I'm using neither of those, so I'm stumped. Show the EXACT command you typed, and the full error output. As described earlier, you likely did not type the command properly. Also, show the output of ls -l /dev/disk/by-id
December 22, 201312 yr Author root@server:~# hdparm -N /dev/sda /dev/sda: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 15 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70 00 00 00 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 15 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70 00 00 00 max sectors = 0/1, HPA is enabled root@server:~# ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 ata-ST3320620AS_6QF2QSJW -> ../../sde lrwxrwxrwx 1 root root 10 2013-12-21 11:33 ata-ST3320620AS_6QF2QSJW-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 ata-TOSHIBA_DT01ACA300_43NNMU8XS -> ../../sdb lrwxrwxrwx 1 root root 10 2013-12-21 11:33 ata-TOSHIBA_DT01ACA300_43NNMU8XS-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 ata-WDC_WD10EADS-00L5B1_WD-WCAU4C531119 -> ../../sdd lrwxrwxrwx 1 root root 10 2013-12-21 11:33 ata-WDC_WD10EADS-00L5B1_WD-WCAU4C531119-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 ata-WDC_WD10EADS-00L5B1_WD-WCAU4C533945 -> ../../sdc lrwxrwxrwx 1 root root 10 2013-12-21 11:33 ata-WDC_WD10EADS-00L5B1_WD-WCAU4C533945-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N0374539 -> ../../hde lrwxrwxrwx 1 root root 9 2013-12-21 11:33 scsi-SATA_ST3320620AS_6QF2QSJW -> ../../sde lrwxrwxrwx 1 root root 10 2013-12-21 11:33 scsi-SATA_ST3320620AS_6QF2QSJW-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 scsi-SATA_TOSHIBA_DT01ACA_43NNMU8XS -> ../../sdb lrwxrwxrwx 1 root root 10 2013-12-21 11:33 scsi-SATA_TOSHIBA_DT01ACA_43NNMU8XS-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C531119 -> ../../sdd lrwxrwxrwx 1 root root 10 2013-12-21 11:33 scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C531119-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C533945 -> ../../sdc lrwxrwxrwx 1 root root 10 2013-12-21 11:33 scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C533945-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 usb-SanDisk_U3_Cruzer_Micro_0000169BA77049B7-0:0 -> ../../sda lrwxrwxrwx 1 root root 10 2013-12-21 11:33 usb-SanDisk_U3_Cruzer_Micro_0000169BA77049B7-0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 wwn-0x5000039ff4c961ce -> ../../sdb lrwxrwxrwx 1 root root 10 2013-12-21 11:33 wwn-0x5000039ff4c961ce-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 wwn-0x50014ee25870a7d0 -> ../../sdd lrwxrwxrwx 1 root root 10 2013-12-21 11:33 wwn-0x50014ee25870a7d0-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 wwn-0x50014ee2adc62bae -> ../../sdc lrwxrwxrwx 1 root root 10 2013-12-21 11:33 wwn-0x50014ee2adc62bae-part1 -> ../../sdc1
December 22, 201312 yr root@server:~# hdparm -N /dev/sda /dev/sda: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 15 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70 00 00 00 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 15 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70 00 00 00 max sectors = 0/1, HPA is enabled root@server:~# ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 ata-ST3320620AS_6QF2QSJW -> ../../sde lrwxrwxrwx 1 root root 10 2013-12-21 11:33 ata-ST3320620AS_6QF2QSJW-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 ata-TOSHIBA_DT01ACA300_43NNMU8XS -> ../../sdb lrwxrwxrwx 1 root root 10 2013-12-21 11:33 ata-TOSHIBA_DT01ACA300_43NNMU8XS-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 ata-WDC_WD10EADS-00L5B1_WD-WCAU4C531119 -> ../../sdd lrwxrwxrwx 1 root root 10 2013-12-21 11:33 ata-WDC_WD10EADS-00L5B1_WD-WCAU4C531119-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 ata-WDC_WD10EADS-00L5B1_WD-WCAU4C533945 -> ../../sdc lrwxrwxrwx 1 root root 10 2013-12-21 11:33 ata-WDC_WD10EADS-00L5B1_WD-WCAU4C533945-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N0374539 -> ../../hde lrwxrwxrwx 1 root root 9 2013-12-21 11:33 scsi-SATA_ST3320620AS_6QF2QSJW -> ../../sde lrwxrwxrwx 1 root root 10 2013-12-21 11:33 scsi-SATA_ST3320620AS_6QF2QSJW-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 scsi-SATA_TOSHIBA_DT01ACA_43NNMU8XS -> ../../sdb lrwxrwxrwx 1 root root 10 2013-12-21 11:33 scsi-SATA_TOSHIBA_DT01ACA_43NNMU8XS-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C531119 -> ../../sdd lrwxrwxrwx 1 root root 10 2013-12-21 11:33 scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C531119-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C533945 -> ../../sdc lrwxrwxrwx 1 root root 10 2013-12-21 11:33 scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C533945-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 usb-SanDisk_U3_Cruzer_Micro_0000169BA77049B7-0:0 -> ../../sda lrwxrwxrwx 1 root root 10 2013-12-21 11:33 usb-SanDisk_U3_Cruzer_Micro_0000169BA77049B7-0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 wwn-0x5000039ff4c961ce -> ../../sdb lrwxrwxrwx 1 root root 10 2013-12-21 11:33 wwn-0x5000039ff4c961ce-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 wwn-0x50014ee25870a7d0 -> ../../sdd lrwxrwxrwx 1 root root 10 2013-12-21 11:33 wwn-0x50014ee25870a7d0-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2013-12-21 11:33 wwn-0x50014ee2adc62bae -> ../../sdc lrwxrwxrwx 1 root root 10 2013-12-21 11:33 wwn-0x50014ee2adc62bae-part1 -> ../../sdc1 Looks like sda is your flash drive. The Toshiba is sdb.
December 22, 201312 yr Wow, I'm a bonehead. Thank you! I wouldn't quite say that ... but you DO need to do as I noted earlier ... In either case, be CERTAIN that you're referring to the correct disk when you make the change !!
December 22, 201312 yr Author Thanks all for your help. HDA has been removed and parity is rebuilding. The WD drive is still just slightly larger than the Toshiba. Can I use the same hdparm command to make the WD drive appear the same size?
December 23, 201312 yr I'm surprised there's a difference ... but yes, you can set the WD drive so it's the same size as the Toshiba.
December 23, 201312 yr you should also check your BIOS for settings related to creating the HPA in the first place and make sure those are disabled.
December 23, 201312 yr Just out of curiosity, what are the exact sizes shown for the WD and Toshiba disks? As I noted, I'm surprised there's a difference.
December 23, 201312 yr Just out of curiosity, what are the exact sizes shown for the WD and Toshiba disks? As I noted, I'm surprised there's a difference. what is the output from hdparm -N /dev/sdx for each of the two drives showing slightly different sizes. ( where "sdx" is the proper three letter drive designation for your two drives)
December 24, 201312 yr Author The toshiba is 2930266532. The WD is 2930266584. Luckily, the system let me keep the Toshiba as the parity disk without resizing it.
December 24, 201312 yr VERY interesting. I have a dozen 3TB WD Reds, and they ALL show 2930266532 ... same as your Toshiba. I'm very surprised that yours has a different count !!
December 24, 201312 yr Author That is strange! The WD is preclearing now, hopefully there won't be any issues.
Archived
This topic is now archived and is closed to further replies.