Jump to content
We're Hiring! Full Stack Developer ×

[SOLVED] Upgraded from 4.5.6 to 4.7; array won't start


Recommended Posts

Likely HPA...

 

What is HPA? http://lime-technology.com/forum/index.php?topic=10866.0

 

 

more info

http://lime-technology.com/forum/index.php?topic=13793.msg130566#msg130566

 

Downloads:

http://206.217.193.39/download/

 

Edit:

HPA Detected -

Aug 15 10:07:38 Tower kernel: ata6.00: HPA detected: current 2930275055, native 2930277168

Aug 15 10:07:38 Tower kernel: ata6.00: ATA-7: SAMSUNG HD154UI, 1AG01118, max UDMA7

Link to comment

Grrr! Argh!  I eradicated HPA off the drives before, and disabled in the BIOS of my motherboard... how does that sucker keep coming back?

 

If I run the hpparm command to remove it off the drive, is it going to hurt the data on the drive, or invalidate the parity?

 

Thanks for the download link, at least I'll be able to get access my shares now :

Link to comment

Don't panic, you should be fine. If there is a delay in mounting the drives, version 4.5.6 had a bug that caused the drive to show as unformatted. Just stop and restart the array or reboot. Run a parity check for a few minutes to verify that parity was not changed.

 

Fix your HPA issues in 4.5.6 and then move to 4.7. You can also move from 4.5.6 to 4.6 without this size problem.

Link to comment

Grrr! Argh!  I eradicated HPA off the drives before, and disabled in the BIOS of my motherboard... how does that sucker keep coming back?

 

If I run the hpparm command to remove it off the drive, is it going to hurt the data on the drive, or invalidate the parity?

 

Thanks for the download link, at least I'll be able to get access my shares now :

You removed the HPA, but probably did not re-size the partition.   

 

Joe L.

Link to comment

Okay, think hdparm got rid of it; on reboot the syslog don't mention HPA on it.

 

Now I'm looking at this:

HU6Sc.png

 

Should I just let the array rebuild the drive?  Or would it be better to unassign both, just copy the data for disk4 over from my cache drive (make a backup before hdparm to be safe) where I made the copy, then rebuild the parity?

Link to comment

Okay, think hdparm got rid of it; on reboot the syslog don't mention HPA on it.

 

Now I'm looking at this:

HU6Sc.png

 

Should I just let the array rebuild the drive?  Or would it be better to unassign both, just copy the data for disk4 over from my cache drive (make a backup before hdparm to be safe) where I made the copy, then rebuild the parity?

I would let it upgrade the drive.  (basically, it will expand the file-system and then re-construct the exact same data as on it now back into place in the expanded file-system)  Letting it do it will preserve parity (and, in fact will use parity and the other data disks to perform the re-construction)
Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...