So I decided to upgrade the parity disk with a new 6 TB harddrive from Western Digital. I precleared it by doing 2 cycles (94h) and when it was done I removed the old 4TB and replaced it with the new one and started the array. I did a Parity-Check and all was good. Then I stopped the array and shut down the server to add the previous parity disk to add more disk to the array. I booted up and started the array and began a preclear on the old disk. I browsed to "myMain" to check all disks. Then I noticed on the default view that the newley added parity disk had a HPA? How can that be? I don't have an old Gigabyte motherboard, I have a pretty new Supermicro X9SRL-F motherboard.

 

Why does it say that my parity disk is HPA?

Did I do something wrong when I did the preclear?

Do I have some problems now if I want to add a 6TB disk to my storage?

 

Please help me sort this out!!

 

I'm running unRAID 5.05 with a pro key

 

//Christer

 

myMain uses standard disk sizes to see if a disk has HPA. 6TB standard size has not been entered yet, so your drive doesn't match any of the known sizes, and says it might have a HPA. Google the reported size in k and see if it matches the common 6TB size.

If you go to the "Detail" view in myMain, and look in the column called "Size (k)", you will see the size of your 6T drive.

 

For a 4T drive you'll see the number 3,907,018,532. Tell me the size of the 6T drive. With that I can update myMain to recognize them as a valid size.

 

If you set the "hpa_ok" attribute to 1 on the drive settings page, you can turn off that HPA warning.  Just click on the drive's ID (last few digits of the SN).  The drive settings dialog will open.  Under the bottom setting (Other Notes) enter hpa_ok, and to the right enter 1.  Click save.  Go back and refresh and you'll see that the warning is gone.

If you go to the "Detail" view in myMain, and look in the column called "Size (k)", you will see the size of your 6T drive.

 

For a 4T drive you'll see the number 3,907,018,532. Tell me the size of the 6T drive. With that I can update myMain to recognize them as a valid size.

 

If you set the "hpa_ok" attribute to 1 on the drive settings page, you can turn off that HPA warning.  Just click on the drive's ID (last few digits of the SN).  The drive settings dialog will open.  Under the bottom setting (Other Notes) enter hpa_ok, and to the right enter 1.  Click save.  Go back and refresh and you'll see that the warning is gone.

 

Thanks! jonathanm, never thought that was the case :-)

 

@bjp999, The drive reports it self to be 5,860,522,532 (k).

Brian,

If you are going to make an update to MyMain, then you could also add the size of a 2.5TB drive: 2,441,890,532

If you go to the "Detail" view in myMain, and look in the column called "Size (k)", you will see the size of your 6T drive.

 

For a 4T drive you'll see the number 3,907,018,532. Tell me the size of the 6T drive. With that I can update myMain to recognize them as a valid size.

 

If you set the "hpa_ok" attribute to 1 on the drive settings page, you can turn off that HPA warning.  Just click on the drive's ID (last few digits of the SN).  The drive settings dialog will open.  Under the bottom setting (Other Notes) enter hpa_ok, and to the right enter 1.  Click save.  Go back and refresh and you'll see that the warning is gone.

 

Thanks! jonathanm, never thought that was the case :-)

 

@bjp999, The drive reports it self to be 5,860,522,532 (k).

 

I am having the same problem with the 3 HGST 6tb drives I recently installed.

1 parity and 2 data drives. They all have 6,001,175,072 (k) as the size.

I entered hpa_ok 1 in the window under Other Notes as you suggested,saved and reloaded the page  and nothing happens.

I also have HPA ? appearing on my cache drive which has a size of 512,110,158 (k) entering hpa_ok 1 does not eliminate the message here either.

Appreciate any help you can give.

See THIS POST. Pay particular attention to the screenshot attached to that post.

 

Let me know if this fixes your problem.

See THIS POST. Pay particular attention to the screenshot attached to that post.

 

Let me know if this fixes your problem.

 

Fixed. Thank you. My stupidity. I was putting the 1 value just to the right of hpa_ok and not into the correct location which was the value column.