February 28, 201313 yr Basically I'm pretty sure I screwed up on my part during the upgrade and now I'm looking for some help as a total unRAID noob. I followed the instructions by shutting down my unRAID server then taking the usb flash drive and connected to other PC to overwrite the old bzroot and bzimage files with the new unRAID 5RC11 ones. It started fine so I proceded to upgrade my SimpleFeatures from 1.05 to 1.0.11 and deleted unmenu and it's packages, that went without a hitch as well. The next step is where I went wrong, I accessed the flash from my network and copied my previous config files from 1.05 to the locations where 1.0.11 ones are stored. Then I stopped my array, but the web gui froze and I tried going back in and nothing happened. I went to my server and typed in powerdown, but at this point I didn't realize that I had removed unmenu as well as it's safe powerdown script. The server finally powered down and then when I turned it back on, it had missing drives. So I checked my bios settings and they were infact missing. I rechecked the wiring and went back into the bios, they reappeared again. Starting unRAID I noticed that it kept on trying to reset sata port #7 and lowering it's speed each time, 6gbps to 3gbps to uma 133, then it would finish booting and prompt to the server login prompt. Now all the drives showed up but disk 3 is now redballed and disabled. I reverted back to 5rc8a on my flash drive and started again, same thing happened with the sata port but disk3 is no longer redballed? None the less I did not try to start the array because I would probably do more damage to it. I again upgraded the flash drive to 5rc11, this time with unmenu and simplefeatures 1.0.11 with default configs, reset my bios, changed the cable on sata port 7 and now the sata port issue is solved. I still have the red ball, disabled drive. TL;DR version 1. Upgraded successfully to 5RC11, deleted unmenu folder and packages folder, installed simplefeatures 1.0.11, copied old config files for simplefeatures, attempted to stop array, froze, typed powerdown in shell without unmenu and powerdown script. 2. On power on, drives missing, restarted drives recognized, suffers errors on sata port 7, disk3 red balled (disabled). 3. Powerdown, copied backup of flash drive contents when 5rc8a was running on it, turned server back on, all seems fine, red ball drive is now green again, did not start array because afraid of messing it up more. Still suffer SATA port errors. Power down again. 4. Reset and reconfigured bios, copied back 5rc11 + unmenu and packages + simplefeatures plg files onto flash drive, powered on, disk3 is red balled (disabled). And before I start the array or when I start it, this keeps getting repeated. Feb 27 20:59:14 Server emhttp: shcmd (990): /usr/local/sbin/emhttp_event driver_loaded Feb 27 20:59:14 Server emhttp_event: driver_loaded Feb 27 20:59:14 Server emhttp: shcmd (991): rmmod md-mod |& logger Feb 27 20:59:14 Server emhttp: shcmd (992): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Feb 27 20:59:14 Server emhttp: shcmd (993): udevadm settle Feb 27 20:59:14 Server kernel: md: unRAID driver removed Feb 27 20:59:14 Server kernel: md: unRAID driver 2.1.5 installed Feb 27 20:59:14 Server emhttp: Device inventory: Feb 27 20:59:14 Server emhttp: WDC_WD3200AAJS-65B4A0_WD-(sda) 312571224 Feb 27 20:59:14 Server emhttp: WDC_WD20EFRX-68AX9N0_WD- (sdb) 1953514584 Feb 27 20:59:14 Server emhttp: WDC_WD30EFRX-68AX9N0_WD-sdc) 2930266584 Feb 27 20:59:14 Server emhttp: WDC_WD20EFRX-68AX9N0_WD-(sdd) 1953514584 Feb 27 20:59:14 Server emhttp: WDC_WD20EARX-32PASB0_WD-(sde) 1953514584 Feb 27 20:59:14 Server emhttp: WDC_WD20EFRX-68AX9N0_WD- (sdf) 1953514584 Feb 27 20:59:14 Server emhttp: WDC_WD30EFRX-68AX9N0_WD- (sdg) 2930266584 Feb 27 20:59:14 Server kernel: mdcmd (1): import 0 8,32 2930266532 WDC_WD30EFRX-68AX9N0_WD- Feb 27 20:59:14 Server kernel: md: import disk0: [8,32] (sdc) WDC_WD30EFRX-68AX9N0_WD- size: 2930266532 Feb 27 20:59:14 Server kernel: mdcmd (2): import 1 8,80 1953514552 WDC_WD20EFRX-68AX9N0_WD- Feb 27 20:59:14 Server kernel: md: import disk1: [8,80] (sdf) WDC_WD20EFRX-68AX9N0_WD- size: 1953514552 Feb 27 20:59:14 Server kernel: mdcmd (3): import 2 8,48 1953514552 WDC_WD20EFRX-68AX9N0_WD- Feb 27 20:59:14 Server kernel: md: import disk2: [8,48] (sdd) WDC_WD20EFRX-68AX9N0_WD- size: 1953514552 Feb 27 20:59:14 Server kernel: mdcmd (4): import 3 8,64 1953514552 WDC_WD20EARX-32PASB0_WD- Feb 27 20:59:14 Server kernel: md: import disk3: [8,64] (sde) WDC_WD20EARX-32PASB0_WD- size: 1953514552 Feb 27 20:59:14 Server kernel: mdcmd (5): import 4 8,16 1953514552 WDC_WD20EFRX-68AX9N0_WD- Feb 27 20:59:14 Server kernel: md: import disk4: [8,16] (sdb) WDC_WD20EFRX-68AX9N0_WD- size: 1953514552 Feb 27 20:59:14 Server kernel: mdcmd (6): import 5 8,96 2930266532 WDC_WD30EFRX-68AX9N0_WD- Feb 27 20:59:14 Server kernel: md: import disk5: [8,96] (sdg) WDC_WD30EFRX-68AX9N0_WD- size: 2930266532 Feb 27 20:59:14 Server kernel: mdcmd (7): import 6 0,0 Feb 27 20:59:14 Server kernel: mdcmd (: import 7 0,0 Feb 27 20:59:14 Server kernel: mdcmd (9): import 8 0,0 Feb 27 20:59:14 Server kernel: mdcmd (10): import 9 0,0 Feb 27 20:59:14 Server kernel: mdcmd (11): import 10 0,0 Feb 27 20:59:14 Server kernel: mdcmd (12): import 11 0,0 Feb 27 20:59:14 Server kernel: mdcmd (13): import 12 0,0 Feb 27 20:59:14 Server kernel: mdcmd (14): import 13 0,0 Feb 27 20:59:14 Server kernel: mdcmd (15): import 14 0,0 Feb 27 20:59:14 Server kernel: mdcmd (16): import 15 0,0 Feb 27 20:59:14 Server kernel: mdcmd (17): import 16 0,0 Feb 27 20:59:14 Server kernel: mdcmd (18): import 17 0,0 Feb 27 20:59:14 Server kernel: mdcmd (19): import 18 0,0 Feb 27 20:59:14 Server kernel: mdcmd (20): import 19 0,0 Feb 27 20:59:14 Server kernel: mdcmd (21): import 20 0,0 Feb 27 20:59:14 Server kernel: mdcmd (22): import 21 0,0 Feb 27 20:59:14 Server kernel: mdcmd (23): import 22 0,0 Feb 27 20:59:14 Server kernel: mdcmd (24): import 23 0,0 I just want to know what the course of action at this moment is. Thanks in advance! Specs: Gigabyte B75M-D3P Intel Core i3 3220 8GB 2x4GB DDR3 1600MHz G.Skill Ripjaws X 3x 2TB WD Red 2x 3TB WD Red 1x 2TB WD Green 1x 320GB WD Blue (cache)
February 28, 201313 yr Author After looking at my SMART data for the red ball drive... I found this: 199 UDMA CRC Error Count 0x0032 200 200 000 Old age Always Never 1 I've seen this in the past with a HDD I've had before. Faulty cable perhaps? I should RMA this drive right? I have one 3TB WD Red assigned but nothing is stored on it, how can I reassign this drive to replace the failed drive? Also does anyone know what's going on in the syslog? Thanks in advance.
February 28, 201313 yr After looking at my SMART data for the red ball drive... I found this: 199 UDMA CRC Error Count 0x0032 200 200 000 Old age Always Never 1 I've seen this in the past with a HDD I've had before. Faulty cable perhaps? I should RMA this drive right? I have one 3TB WD Red assigned but nothing is stored on it, how can I reassign this drive to replace the failed drive? Also does anyone know what's going on in the syslog? Thanks in advance. It indicates the SATA cable picked some noise from an adjacent cable and the checksum on the data packet being transferred to or from the disk over the cable did not agree with what was expected. I personally DO NOT think it is a reason to RMA the drive on the end of the cable. It is more a reason to NOT tie-wrap the SATA cables together or to any other wiring.
February 28, 201313 yr Author After looking at my SMART data for the red ball drive... I found this: 199 UDMA CRC Error Count 0x0032 200 200 000 Old age Always Never 1 I've seen this in the past with a HDD I've had before. Faulty cable perhaps? I should RMA this drive right? I have one 3TB WD Red assigned but nothing is stored on it, how can I reassign this drive to replace the failed drive? Also does anyone know what's going on in the syslog? Thanks in advance. It indicates the SATA cable picked some noise from an adjacent cable and the checksum on the data packet being transferred to or from the disk over the cable did not agree with what was expected. I personally DO NOT think it is a reason to RMA the drive on the end of the cable. It is more a reason to NOT tie-wrap the SATA cables together or to any other wiring. Thanks for the reply, I think I will remove my zip ties now like as you said they're all tugging on eachother and making eachother loose in addition to interference. How can I get my unRAID server back to normal? Can I reuse this drive in the array? I have a 3TB drive in my array that is empty can I use it to swap it into the failed drive's place if it can't use the failed drive anymore? Thanks Joe!
March 1, 201313 yr http://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F
Archived
This topic is now archived and is closed to further replies.