March 26, 200719 yr I have just upgraded from 3.1b2 to 4.0b4 and am having a drive problem. Before the upgrade my drives were all in working order and showed up as usable. (see below) Now after my update I have a drive that needs to be rebuilt for me to start my array. (see below) I have not done anything yet, please let me know what my next step should be.
March 26, 200719 yr I have just upgraded from 3.1b2 to 4.0b4 and am having a drive problem. Before the upgrade my drives were all in working order and showed up as usable. (see below) Now after my update I have a drive that needs to be rebuilt for me to start my array. (see below) Your disk is now being detected as 1056 bytes bigger. This was an obscure bug Tom never did figure out and apparently is fixed with the 2.6 kernel. Looking at the size mismatch (1056 bytes), it appears you were a victim of the "mysterious shrinking disks" problem in 3.x release. We never figured out the cause of this problem, but suspect an obscure bug in linux 2.4 kernel. It seems like the 2.6 kernel has corrected this! You can Restore the array config (check "I'm sure" checkbox) which will correct the size mismatch (will also start a parity sync). Let the sync finish. He advised somebody else with the same issue in this thread; http://lime-technology.com/forum/index.php?topic=563.0
March 26, 200719 yr I can also confirm that all my "shrinking" HDDs got their 1056 bytes back under v4 too. Mark.
Archived
This topic is now archived and is closed to further replies.