Hi

 

I try to update my array from 4.6 to 4.7. I do the steps like documented in http://lime-technology.com/forum/index.php?topic=10483 (BTW: Download link does not work). I replace bzimage and bzroot at the stick an reboot the machine. After reboot the I get an error:

 

Replacement disk is to small.

 

But I have not replaced any disk!

After I go back to 4.6 the array works fine.

The "error" disk is a Seagate Barracuda 7200.8 300 GB. At 4.6 I see a disk size of 293 035 096 after the update the disk "shrinks" to 293 035 092 and the array report the error.

 

Robert

 

 

 

 

Do you have a Gigabyte motherboard?    If so, this is a well-known issue whereby the BIOS has created an HPA (Host Protected Area) on the parity drive, so it's now not quite as large as it once was.

 

The simplest "fix" is to replace the drive with a larger drive 

 

... but there are other ways to resolve this.

 

Post the specifics of your system ... motherboard;  how many disks; the size of those disks.

 

Hardware:

Mainboard: ASUS M4A78LT-M LE

CPU: AMD Sempron 140

RAM: 2 GB

Second SATA Controler: Adaptec 1430 AS

Disks:

 

parity ST31500341AS_9VS14L29 * 1,465,138,552 - 51 39 0

disk1 ST500DM002-1BD14_Z2AJLP9P * 488,386,552 331,639,124 50 5 0

disk2 ST31500341AS_9VS4TCX0 * 1,465,138,552 298,587,004 47 9 0

disk3 ST31500341AS_9VS14FVV * 1,465,138,552 280,850,788 42 5 0

disk4 ST3300831AS_3NF0ACM4 * 293,036,152 281,642,720 45 6 0

disk5 ST3300831AS_3NF0B5YS * 293,035,096 281,675,984 42 5 0

disk6 ST31500341AS_9VS14L2Q * 1,465,138,552 273,820,416 50 5 0

disk7 SAMSUNG_HD103SJ_S246J9BB312141 * 976,762,552 282,993,096 48 5 0

 

I know that the simplest fix is to replace the disk, but i haven't an other disk yet. I only what to go to 4.7 to be ready to use AF-Disks.

Array is running fine with 4.6.

 

Robert

=>  Go back to v4.6

 

=>  Copy all of the data off of the troublesome drive [To another PC, or to another disk on the array]

 

=>  Do  parity check to be SURE all is okay ... you're going to "run at risk" for a few hours after this (without parity protection) ... so you want to be sure your array is all good.

 

=>  Now Stop the array and reset the configuration to include all disks EXCEPT the troublesome drive.  Be CERTAIN you assign the correct drive to the parity position (Serial #9VS14L29).  Start the array and wait for it to compute parity.    Then, just to be paranoid, do a parity check to be sure all was okay.

 

=>  Upgrade to v4.7  ... this should work fine now.

 

=>  Stop the array and add the troublesome drive to the config.    Start the array -- and when it finishes clearing the drive you're done.

 

Okay I try, thx.

 

Need I to reset the configuration, or can I un-assign the disk an than make initconfig?

Okay I try, thx.

 

Need I to reset the configuration, or can I un-assign the disk an than make initconfig?

 

initconfig is how to reset the config.

reset configuration == initconfig 

Works fine! Thx.