My BIL added a new SATA card and it wasn't showing up in unRaid.  We updated the BIOS on the SATA card and rebooted.  When unRaid finished booting, we saw the red ball for disk1 with 2 errors.  I thought my BIL might have jostled the SATA cable to disk1.  We powered down unRaid and re-attached the SATA cable to disk1.  We powered up the unRaid server.  We stopped the array, un-assigned disk1, started the array, stopped the array, assigned disk1, and started the arrary.  The redball came back for disk1.  This is way out of my league. 

 

I need some expert help.  I have attached a screen capture of the red ball.  Here is the syslog:

 

http://pastebin.com/nX6XQvNj

 

CJ

My BIL added a new SATA card and it wasn't showing up in unRaid.  We updated the BIOS on the SATA card and rebooted.  When unRaid finished booting, we saw the red ball for disk1 with 2 errors.  I thought my BIL might have jostled the SATA cable to disk1.  We powered down unRaid and re-attached the SATA cable to disk1.  We powered up the unRaid server.  We stopped the array, un-assigned disk1, started the array, stopped the array, assigned disk1, and started the arrary.  The redball came back for disk1.  This is way out of my league.  

 

I need some expert help.  I have attached a screen capture of the red ball.  Here is the syslog:

 

http://pastebin.com/nX6XQvNj

 

CJ

 

You've basically done everything right so far.   You've atttempted to re-seat the connectors on the SATA cable to disk1.

When you un-assigned, started array, stopped array, re-assigned disk1 the unRAID server attemppted to write to the drive to re-construct it:

Nov 29 21:28:29 unraid emhttp: shcmd (69): mkdir /mnt/disk1
Nov 29 21:28:29 unraid emhttp: shcmd (70): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 | logger
Nov 29 21:28:29 unraid kernel: mdcmd (14): check
Nov 29 21:28:29 unraid kernel: md: recovery thread woken up ...
Nov 29 21:28:29 unraid kernel: md: recovery thread rebuilding disk1 ...
Nov 29 21:28:29 unraid emhttp: shcmd (71): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger
Nov 29 21:28:29 unraid kernel: md: using 1152k window, over a total of 976762552 blocks.
Nov 29 21:28:29 unraid kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal
Nov 29 21:28:29 unraid kernel: REISERFS (device md2): using ordered data mode
Nov 29 21:28:29 unraid kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal
Nov 29 21:28:29 unraid kernel: REISERFS (device md1): using ordered data mode
Nov 29 21:28:29 unraid kernel: sd 6:0:0:0: [sdb] Unhandled error code
Nov 29 21:28:29 unraid kernel: sd 6:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00
Nov 29 21:28:29 unraid kernel: sd 6:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 00 00 00 3f 00 04 00 00
Nov 29 21:28:29 unraid kernel: end_request: I/O error, dev sdb, sector 63
Nov 29 21:28:29 unraid kernel: md: disk1 write error
Nov 29 21:28:29 unraid kernel: handle_stripe write error: 0/1, count: 1
Nov 29 21:28:29 unraid kernel: md: disk1 write error
Nov 29 21:28:29 unraid kernel: handle_stripe write error: 8/1, count: 1
Nov 29 21:28:29 unraid kernel: md: disk1 write error
Nov 29 21:28:29 unraid kernel: handle_stripe write error: 16/1, count: 1
Nov 29 21:28:29 unraid kernel: md: disk1 write error

 

It was unable to write to the drive, therefore it is still marked as "red"

 

You either have.

  A bad disk drive.

  A bad power connection to the drive (unlikely, since it seems to be seen by the BIOS)

  A bad SATA cable.

  A bad disk controller port.

 

Not knowing your hardware, it might be easy to try a different cable, or a different slot on a backplane.  If you do use a different port on the disk controller you'll need to use the "devices" page to assign the disk to its logical slot for disk1 in the array.

Just be very careful not to dislodge the cables to the other drives.. It would only complicate your recovery as you would then have multiple failed drives.

 

If the drive is working (because the cable/port was replaced) you should be able to get a SMART report from it by typing:

smartctl -d ata -a /dev/sdb

(if it is not plugged into the same disk controller port, the /dev/sdb device might be /dev/sdc, /dev/sdd etc.   Don't worry, just use the device as it shows in (parens) on the devices page.)

 

If the drive has failed, then your next step is to get a replacement drive.   You are not the first who has had a disk failure...  You will not be the last.

 

Joe L.

Thanks for your help Joe.    I will try your suggestions tonight with my BIL. 

 

CJ

 

Well, I thought I would give an update.  We attempted to try Joe's suggestions and my BIL's unRAID server would not boot into unRAID.  No matter what we tried, it would not boot into unRAID, or windows.  We ended up getting a this motherboard, processor, and memory from Newegg.

 

AMD Sempron 140 2.7GHz Socket AM3 45W Single-Core Processor

Foxconn A78AX-S ATX AMD Motherboard

G.SKILL 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 667 (PC2 5300) Dual Channel Kit Desktop Memory

 

After swapping to the new Motherboard, we booted into unRAID.  We make sure the drives were in the correct assignments.  The red ball turned into an orange ball.  We then started the array and unRAID rebuilt the drive (I'm guessing that is what it did).  After running over night, my BIL unRAID server was all green.

 

My BIL was thrilled that he did not lose any data.  I was impressed as well.  This is a great piece of software.

 

CJ