October 14, 201411 yr So I had a 4TB drive which I wanted to install in my unraid server to upgrade a smaller drive. Can't do that as it tells me that parity is smaller (also a 4TB drive) so I have to use it to replace parity instead. Calculated parity on the new drive, showing up fine in the system. Moved parity to a different slot, as I am trying to rearrange the drives to reduce extreme temperatures of my 500GB drives (55C during parity calculation). BOOOOOOM now I have wrong disk messages for parity. It says that the drive in the system is "xxxxxxx (sda)" instead of "xxxxxxx". And it also says it is 3TB instead of 4TB. Tried swapping it back to the previous slot. No change, same message. AAAAARGH! Any suggestions to make it see that it is a 4TB drive, and restart parity calculations?
October 14, 201411 yr I think your motherboard just messed you up pretty good. It has a "feature" that writes a backup copy of the BIOS to your hard drive(s) which causes them to be just a little smaller than normal. Here is a little light reading for your edification. http://lime-technology.com/wiki/index.php/UnRAID_Topical_Index#HPA
October 14, 201411 yr Author Put back the old parity, which it sees as 4TB, thankfully, recalculating parity now. Interestingly this 1TB loss happened before to the old parity too. Can't remember how I fixed it though.
October 15, 201411 yr Clearly this is not due to a HPA ... that would be a very small loss -- not a terabyte !! What's the model # of the drive that's now shown as 3TB?
October 15, 201411 yr ... Moved parity to a different slot, as I am trying to rearrange the drives to reduce extreme temperatures of my 500GB drives (55C during parity calculation). ... What is this different slot? It sounds as though the controller you moved it to may have an incompatibility with that drive.
October 15, 201411 yr Author Clearly this is not due to a HPA ... that would be a very small loss -- not a terabyte !! What's the model # of the drive that's now shown as 3TB? Back home, the drive is not in the server anymore, I replaced it with the old drive a Seagate ST4000DM000-1F2168_Z3008G1J. The drive that was reported as 3TB was a Western Digital WD40EZRX-WCC4EKLRLUUK. I will now try to use the WD drive to replace a 320GB disk, and will send you a screenshot of the WebGui showing the drive reported size shortly.
October 15, 201411 yr Author ... Moved parity to a different slot, as I am trying to rearrange the drives to reduce extreme temperatures of my 500GB drives (55C during parity calculation). ... What is this different slot? It sounds as though the controller you moved it to may have an incompatibility with that drive. I thought that, but when I moved it back to the slot where parity was created on that 4TB WD drive, it still said it was the wrong drive. Why wrong? It does not tell you why, but it showed a different name for the drive WD40EZRX-WCC4EKLRLUUK which was missing (the available drive was "WD40EZRX-WCC4EKLRLUUK (sda)") and the size reported was 3TB vs 4TB for WD40EZRX-WCC4EKLRLUUK (which is the same god forsaken drive!). , cause it was smaller and
October 15, 201411 yr Author Attached the screenshot of my attempt to swap the 320GB drive, showing the 4TB replacement identified by webgui as a 3TB...
October 20, 201411 yr Author No ideas anyone on how to resolve this? Well, I am going to try a nuke approach. I believe this to be a software issue. So I will wipe the key and start from scratch. What I want to do is to remove any memory of what drives I had in the configuration. Any other way to do that other than wiping the key?
October 20, 201411 yr Author It was showing correctly in Unraid. I used it to replace the old parity, it calculated parity fine. Then I moved it to a different sata connector (slot) and there my troubles began. It is like UNRAID has rewritten the description of the drive when I moved it and it is now seeing it as a 3TB drive no matter which slot I place it in. I had the same issue with the current parity drive (the old one). Wiping the key seems to be connected with the fix, although I will only know for sure if it fixes it this time too.
October 20, 201411 yr Understand. The issue, however, is whether or not the drive's internal parameters have been modified, or if this is just some strange behavior on the part of UnRAID. If you simply connect the drive to a different system, and then see what size Disk Management shows for the drive, that would answer that question. If the drive's internal parameters have been modified, it's easy to set them back to the correct value.
October 22, 201411 yr Author So I plugged it in another PC, and it showed to be of size over 3TB. I deleted the only partition on it, and now it says size is 2794.54 GB. I will try to put it back in the unraid server and see if deleting the partition has made any difference.
October 23, 201411 yr Author No change, unraid still thinks the drive is a 3TB drive. So does Windows now for that matter. Stumped.
October 23, 201411 yr So I plugged it in another PC, and it showed to be of size over 3TB. I deleted the only partition on it, and now it says size is 2794.54 GB. I will try to put it back in the unraid server and see if deleting the partition has made any difference. 2794.54 is correct for a 3TB drive => remember that disk drive makers use decimal values; while in "computerese" a KB is 2^10 = 1024. So a GB in "computerese" is 1024 x 1024 x 1024 bytes. If you multiple 2794.54 by (1024 x 1024 x 1024) you get over 3,000,000,000,000 bytes, or 3TB in "disk drive maker - ese") However, the issue still remains that your 4TB drive now "looks" like a 3TB drive => but since it's consistent on different platforms, that simply means it's set incorrectly in the drive's internal memory. You can change that with the free HDat2 utility. Just download the bootable ISO; boot to it; and use the "SetMax" function to change the drive to its native size. ... I'd do this on a system where it was the only drive installed, just to be CERTAIN you don't change the wrong drive http://www.hdat2.com/
October 23, 201411 yr Author I'm not familiar at all with this program. Seems to be command line operated. Any ideas what the command line should be?
October 24, 201411 yr You just need to select the Set Max function ... by default it will reset the drive to its native size.
November 4, 201411 yr Author You just need to select the Set Max function ... by default it will reset the drive to its native size. Well, you were so right garycase, HPA of 1TB, for some reason. Strange but true. Removed it using the utility you linked, now it is seen again as a 4TB drive. Thanks for that, appreciated!
Archived
This topic is now archived and is closed to further replies.