I want to upgrade to 5.0 and read the recommendation to get to 4.7 first.  I was using 4.4.2 for Bubbaraid and it just worked.  I want some 5.0 features and so am now willing to put in the effort to upgrade.  I can succesfully boot after removing bubbaraid (complete overwrite of usb with config files copied back into config folder) and am now getting this error:

 

Replacment disk is too small.

 

Initial forum search indicates that it's a HDPARM error but I'm on a supermicro board and a search of the syslog does not indicate that this drive contains HDPARM data.  After further searches I can't seem to find the solution and would appreciate some help.  Here is my info:

 

Version 4.7

Syslog attached.

 

Thanks in advance for the help.

2013-09-14-1742Syslog.txt

Were you previously using a Gigabyte board for this system?    Or a disk that had been in a Gigabyte-based system?

 

seems to be the case, gary 

 

Sep 14 17:42:01 Tower kernel: ata26.00: HPA detected: current 1953523055, native 1953525168

Yes, it's clear this is an HPA issue (as I suspected).

 

There are two ways to resolve it ...

 

(1)  Remove the HPA from the troublesome drive.    You can search this forum for fixes -- I'd outline one but we're on our way out for the evening, so I don't have time right now.    The best fix is to download a bootable ISO of HDAT2 and use it, but there are other ways outlined in the forum.  http://www.hdat2.com/

 

(2)  Simply not worry about the small space loss on the drive; and start from scratch with your v5.0 build.    To do this, first be SURE you know the serial number of your parity drive and all of the data drives;  then rebuild your flash drive with v5.0;  boot to v5.0; and simply assign all your data drives (the order doesn't matter).    Start the array and confirm all is okay;  then Stop it; assign the parity drive; and Start it back up and let it do the initial parity sync.

 

When done, you're ready to start installing your add-ins/plug-ins and set up your shares.

 

Hmm, I searched hpa on the syslog and found it but it didn't seem that the drive with the error is the drive that was failing.  I found the help page for the HPA issue here: http://lime-technology.com/forum/index.php?topic=10866.0 and will follow those steps to remove from impacted drives.  I have had gigabyte motherboards and these drives are all pulled from various systems so likely this came from one of the pulls.  I still am confused by which drive is impacted but will follow the instructions and post back.  Thanks for the quick responses.

I figured out why I didn't think it was that issue, I was looking at the size and expecting it to be around the 1tb mark.  Anyway, I tried the command line fix which didn't work and decided to try 5.0 which did so this issue is solved.

 

Thanks again for the help.

Glad you've got it working.    Did you actually remove the HPA's ... or simply install v5.0 from scratch and use the drives as they are?  [Not a bad thing to do ... it's VERY little space that's lost to an HPA ... EXCEPT you do NOT want to use a drive with an HPA as parity !!]