First off thank you for the info that I have already found here. Its been a time saver getting up to speed.
I am new here and recently picked up a DS6100 unit for my wife’s small home business. I know it was over kill but I am an IT guy and like toys plus the prices was good. I got the unit all configured and it was working great but we had a storm roll in and the power went out. needless to say when the DS6100 came back up the boot raid was not happy. Turns out one of the 320GB drives got wacked and needed replaced. However before replacing it I tried a raid rebuild on it and had my fingers crossed. The rebuild went to 99% and hung there for days, then finally I had some errors get reported in the monitor logs. Yep bad sectors found so the drive is shot. I even put the drive in another computer to scan and mess with and it all pointed to a bad drive. I ordered a new one same make and model. It arrived and of course it was a new drive so the unit didnt like it and I had to add it to the devicelist.xml file (Thank you to all that put time in to find this. Saved me some time.). Not a big issue at all. Rebooted to be safe and was happy to see the new drive was now marked in green and the raid rebuild started automatically. However…I am a few days in and hung at 99% again?!?
So what is the deal? Do I just need to wait it out again? I am use to working on big servers and have never had to wait days for a mirror set to be rebuilt. I also noticed that in this state the OS is VERY slow. Is this normal even thought resources are about idle. I will be installing PUTTY when I get time and connecting the the controller to take a look.