February 25, 201115 yr I'm unable to upgrade to 4.7 due to the HPA issue on one of my data drives (thankfully not my parity drive!) My board is a GB EP43 DS3L and has the current bios. The only option in the bios is to set where the bios recovery comes from, either the dual bios or hdd hpa. Its currently set to the dual bios. My sys log reports Feb 24 14:46:52 Tower kernel: ata1.00: HPA detected: current 3907027055, native 3907029168 Would the hdparm method work here? i.e hdparm -N p3907029168 /dev/sda Thanks in advance.
February 25, 201115 yr Before you correct this issue, would you do me a favor? Run the command fdisk -lu /dev/sdX (the parameter is dash, lower case "L", lower case "U") and sdX is the device (looks like it might be sda based on your example) I am working on a tool to help users know when they have an HPA, and an actual example of the results of this command on a disk that actually has HPA would be very helpful. This is a non-destructure command that will just display some data about your disks size and partitioning. Thanks for your help!
February 25, 201115 yr Author here you go... Disk /dev/sda: 2000.3 GB, 2000397852160 bytes 1 heads, 63 sectors/track, 62016302 cylinders, total 3907027055 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 63 3907027054 1953513496 83 Linux Partition 1 does not end on cylinder boundary. so is the hdparm the way to go?
February 25, 201115 yr i'm in the same boat as your mazma, was discussing it last night, if you want to check my thread labeled "few questions" yes that hdparm will get rid of it.. the problem is, if the hpa isn't disabled, it will just be re created. weather your option of setting it to dual bios has indeed disabled it.. well i don't know. i'll do that fdisk for you as well bjp edit: here ya go Disk /dev/sdg: 1500.3 GB, 1500300828160 bytes 1 heads, 63 sectors/track, 46512302 cylinders, total 2930275055 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdg1 63 2930275054 1465137496 83 Linux Partition 1 does not end on cylinder boundary.[\code]
February 25, 201115 yr Make sure that you resolve this. If your board does not turn off HPA by default then the problem will reoccur when CMOS is reset for any reason, e.g., the CMOS battery dies. Having the option to disable it is not good enough; the board must default to the off setting. Sometimes a BIOS update will fix the problem. Although, others have replaced their MB due to this problem. Motherboards the have HPA enabled by default are not suitable for unRAID.
February 25, 201115 yr Author I hear ya, just trying to avoid opening a can of worms by buying new stuff, but I do understand the grander implications. Any suggestions at a board that will accept a core 2 duo and ddr2 memory? seems like slim pickings on newegg!
February 25, 201115 yr Author going on the presumption I replace the MB, how do I then fix that error?
February 25, 201115 yr here you go... Disk /dev/sda: 2000.3 GB, 2000397852160 bytes 1 heads, 63 sectors/track, 62016302 cylinders, total 3907027055 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 63 3907027054 1953513496 83 Linux Partition 1 does not end on cylinder boundary. so is the hdparm the way to go? Thanks! hdparm is the tool that is recommended for removing the HPA. You'll have to search the forums for specific instructions. Joe L. is probably the best source on this topic.
February 26, 201115 yr Author so in the end I upgraded again to 4.7 (I had downgraded to 4.56 so the array worked,) and ran hdparm -N p3907029168 /dev/xxx where xxx is the drive I confirmed this number (3907029168) by checking what all the other drives were listed at (they are the same drives). After rebooting unRaid is rebuilt that drive at the correct size and no new HPA listed in the log.
Archived
This topic is now archived and is closed to further replies.