Ok, so I thought I was good to go with the data-rebuild of a failed drive with a larger 3TB drive.

 

The rebuild completed fine, then I switched my parity drive, because I was getting SATA reset on my main board controllers and thought it might be the drive. After continually getting those errors even with the new drive, I thought maybe the motherboard was at fault.

 

I suspected this, because now it was also locking up one of the CPU cores solid, had to physically reboot the server to regain control. All of this was happening, of course while it was doing a parity re-build.

 

So, at my last physical reset, I decided to replace the motherboard. New board is in, still getting SATA resets. Changed SATA cables, still getting resets. At this point the only old piece of equipment in the server is the CPU itself and the PSU. It's a 56A, single-rail PSU so I think it should be ok.

 

Anyway, as I was bringing the system up, I noticed that the new 3TB "rebuilt" drive was in read-only mode. So, I stopped the array to perform reiserfsck on it. As I was doing that, another disc went into disabled mode (after throwing up 5 trillion reads, writes and errors on the web interface).

 

Now, I've got an "unformatted" disc and no parity disc (since it would not finish rebuilding). I'm nearly done the reiserfsck on the 3TB drive, so I'm hoping that's going to fix it.

 

I guess the question now is, have I lost all the data on that "unformatted" drive, or if I put in another disc can the other discs "rebuild" it, even without a working parity drive?

 

Le augh.

 

I'm running 5RC8 and I'd post a syslog, but I currently can't get to one.

Let me start by saying DO NOT press format.

 

If the drive was working and now says unformatted, that simply means unraid could not detect a filesystem. The drive is recoverable. If you press format, you WILL lose that data.

 

Honestly I would replace the PSU. It sounds like it has shit itself. Get a replacement PSU then see where things stand.

 

If the drive still shows up unformatted, we have knowledgeable users who can help you recover the filesystem.

 

Edit: reason I suspect the PSU, CPUs rarely lock up without good cause, and its unusual for every aspect of your system to go on the fritz at the same time.

 

During a rebuild your server is using the most power it ever will, and that is when your issues occurred. A read only drive means a write failed, could be any number of issues but added to the CPU issue, the sata errors and the fact the CPU and PSU are the only things left...

 

If it were the CPU I wouldnt expect data errors, but a under or overpowered system could easily see those symptoms.