I had a 1TB drive turn up red balled in a 4.6 array. Parity check turned up write errors so I got a new 2TB drive and swapped it in. I also upgraded to 4.7... which wasn't intentional, but I grabbed the identical, but wrong jump drive. Despite marking them clearly. I rebooted and overlooking the troubling fan noises I'm hearing now, I've got an unRAID box that's spinning the HDDs according to the activity light, but the box itself is unreachable by telnet, ping, etc.

 

Is this expected behavior during a rebuild? Apologies if this is laid out somewhere, I did a fast search, but I also have various children either going to the doctor or getting booted back out of school for same. I had high hopes I could plop their miserable selves in front of some shows after I round them up!

 

Thanks!

I had a 1TB drive turn up red balled in a 4.6 array. Parity check turned up write errors so I got a new 2TB drive and swapped it in. I also upgraded to 4.7... which wasn't intentional, but I grabbed the identical, but wrong jump drive. Despite marking them clearly. I rebooted and overlooking the troubling fan noises I'm hearing now, I've got an unRAID box that's spinning the HDDs according to the activity light, but the box itself is unreachable by telnet, ping, etc.

No, it is not normal to be unreachable.

Can you access it via the system console?

I haven't connected a keyboard or monitor to it in years, but will do so. Thanks (once again) for the advice, Joe L.!

I finally figured out the reason it wasn't booting was the BIOS had the boot order/devices completely goofed. I fixed, booted and reached the unRAID web server. And now I've got the new disk listed and blue, as expected, but unRAID's drive 2 is now red. So, no array. Not panicking immediately, I shut it down, fiddled with the cables and such and rebooted.

 

I've got no array. I also have no idea why the drive went away. It's unRAID drive1, which is SATA4 or SATA6, depending on when I took the syslog.

 

syslog is... forum is returning an error when a post includes URLs? So, searching pastebin.com for "unRAID syslog 20120112" should turn it up. Thanks for the help.

syslog_20120112a.zip

zip the syslog and attach it to a post.

zip the syslog and attach it to a post.

 

Thanks and done. As a bonus, the BIOS refuses to keep the boot configuration past the save and reboot. I've tried the tips for working with an AMI BIOS, but no joy.

I've replaced the SATA cable, swapped out ports... I can't get the drive to show up in the BIOS. Anyone have any other suggestions, short of pulling it and trying it in a different motherboard?

 

Also, if it is toast, this does mean I've lost the entire array, correct?

I've replaced the SATA cable, swapped out ports... I can't get the drive to show up in the BIOS. Anyone have any other suggestions, short of pulling it and trying it in a different motherboard?

 

Also, if it is toast, this does mean I've lost the entire array, correct?

Yo will only loose data that was on the failed drive(s).

 

 

If the drive is not seen by the BIOS then you might well be SOL.  You can try the freezer trick and see what happens.

Yo will only loose data that was on the failed drive(s).

 

With one drive red and one blue, I'm "only" going to lose the red? Thanks for the response, by the way.

 

As an aside, it's uncanny and immensely frustrating how changing anything at all in the box causes me issues. Losing a 2TB drive while replacing a 2TB drive seems a harsh penalty.

Swapping cables eventually got the BIOS to see the drive, but it returned a warning of "SMART Capable but Command Failed" and unRAID considers it missing. I'm going to call that dead.

 

While googling about to see what I could find on that warning, I discovered Western Digital has a pretty slick, painless way of checking if your drive is still under warranty here. That's a silver lining, I suppose.

Reboot with the correct flash and try to rebuild the failed drive on a new disk.