Hi there,

I have a strange problem.. that requires some manual updating of the unraid disk config to stop it from wiping out my data I think......

 

I upgraded a disk in my array - stopped, upgraded, and restarted the array, prompting a rebuild and all was well.

 

Then, when I went to pre clear the next disk (replacing two drives) I got an error saying that it couldn't write the preclear report. That's when I realized that my boot drive was mounted read only, so I shut down, pulled the USB drive and did a Windows repair on it and put it back in - I then replaced the second drive to reboot and rebuild the second disk.

 

That's when things went south...  the next day when I rebooted, Unraid is complaining that both disks are wrong - the first disk that I already rebuilt, and the new one that I want to rebuild now. It's asking for both original drives. I kinda figure this must be because it couldn't write the new disk info from the first rebuild to the config file on the USB drive, so unRaid doesn't know that my first disk has been rebuilt already.

 

Now I have the issue that both the old drives have gone to my brother for his unraid box, so just putting the last drive back and rebuilding is a pain.

 

Can I make a change to a config file somewhere to get unraid to trust the first disk, so I can rebuild the second and get my array back? Or do I have to go across town tomorrow and get the old drives from my brother's.

 

Cheers,

 

whiteatom

The safest (and maybe only) course is to retrieve the original disks. I'm a little confused on the timeline. One disk was rebuilt and then both old disks were given away before the second rebuild was attempted?  The old disks need to be kept at least until a parity check has completed after replacing the last disk. The procedure is parity check, rebuild 1, parity check, rebuild 2, parity check. Keep the old disks until your comfortable with the operation of the new ones. Some keep the old disks for 90 days.

 

The latest RCs have a "parity is valid" checkbox that appears after a new config is set. I don't know if b14 has this feature.

I can get the old disks, and they haven't been reformatted.. my brother was just here, so it was a convenient time to give them to him. I didn't for see a problem, until I thought through the impact of the "read-only" mount of the boot drive. It might be a nice feature to flag this on the GUI - it took me a while to find out that unRaid had decided to make my boot partition read-only.

 

I guess I'll have to rebuild again tomorrow.

Ok, I got the disks back. I put the 2nd one back in and now it boots properly and it identifies the one "Wrong" disk. So I started the array and it started the rebuilding the first new disk again - every thing was perfect until about 12% then the web gui stopped responding. I can see the unraidd and mdrecoveryd processes working, and the drives lights are still showing activity, so I'm guessing it's still rebuilding.

 

Is there any other way to see the status of the rebuild? Where is the gui reading the rebuild percentage from?

 

Cheers,

 

whiteatom

Well no replies, but I'll update for completeness.

 

1) if you boot drive is read only and you make changes to the array (new disk) you'll have to do it all again after you fix the read only boot drive problem

 

2) the rebuild process doesn't seem to be tied to the GUI... I killed emhttpd a few times to try and get it back, but eventually the disk activity stopped and I just rebooted.

 

Whiteatom