Background

I upgraded from 4.7 to 5rc3.

I had some problems with being able to access the user shares, had to keep remapping them to drives etc.

I decided to go back to 4.7 while trying to get answers here on what I may have done wrong.

I copied over bzimage and bzroot.

 

Restarted and suddenly all disks were redballed. Under devices, the disks are all in the correct places and are assigned the right slots. See attachment in next message.

I deleted the shadow, password and smbpassword files from the flash/config folder, suspecting that these files from 5rc3 may be interfering with the ability of 4.7 to see the disks properly.

No go.

I tried copying the 5rc3 bzroot and bzimage files back, hoping to get a clean start again. That too showed all disks as missing.

Finally, I went back to 4.7.

I'm assuming that I just need to run an "initconfig - trust my parity" to get back to normal. However, I don't want to do it without getting the experts to give em the go-ahead.

 

Thanks for any comments/suggestions.

 

 

syslog.txt

Update: I am back to 5rc3, and disks are showing again. Still wondering what's up, though.

I had the same thing happen this week-end when I upgraded to 5RC3, then reverted to 4.7 (because of some additional scripts that v5 didn't like).  Array wouldn't start, "too many wrong disks", although the were assigned to the correct slots.

 

Upgraded back to 5RC3 and all was ok.

 

Then, I copied my original 4.7 files over to my flash and the array started normally. Must have something to do with the new disk.cfg

 

 

 

 

Looks like this is the answer:

http://lime-technology.com/forum/index.php?topic=12403.msg117922#msg117922

 

If you read the release notes and announcements of the various 5.0 beta series you will notice an explicit mention of the file "config/super.dat" as being incompatible between the 4.x series and the 5.x series. It also mentions backing up your previous config/ directory should you desire to revert back to previous versions.