March 2, 201412 yr I'm running ver. 5.0.4 and one of the drives is reporting a red ball. I have checked all the cabling, reseated the Promise Controller card, etc., but I am still unable to enable the drive. The drive is rather new so I'm not sure that is the problem. I have included excerpts from the log which shows error reports (memory, ATA 3, etc). Can someone give an educated guess as to what is causing the drive to be disabled? On another note, I think I need to begin thinking about migrating to ver. 6 and I am wondering if it is similar to moving from ver 4 to ver 5? Will I be able to move my drives from version 5 to version 6 without loosing any data? My goal in moving to ver 6 is to be able to run Media Browser 3 Server on unRaid. Thanks for any input Excerpts from log: Mar 1 05:19:31 Tower kernel: [mem 0x00000000-0x000fffff] page 4k (Errors) Mar 1 05:19:31 Tower kernel: init_memory_mapping: [mem 0x37800000-0x379fffff] Mar 1 05:19:31 Tower kernel: [mem 0x37800000-0x379fffff] page 2M (Errors) Mar 1 05:19:31 Tower kernel: init_memory_mapping: [mem 0x34000000-0x377fffff] Mar 1 05:19:31 Tower kernel: [mem 0x34000000-0x377fffff] page 2M (Errors) Mar 1 05:19:31 Tower kernel: init_memory_mapping: [mem 0x00100000-0x33ffffff] Mar 1 05:19:31 Tower kernel: [mem 0x00100000-0x001fffff] page 4k (Errors) Mar 1 05:19:31 Tower kernel: [mem 0x00200000-0x33ffffff] page 2M (Errors) Mar 1 05:19:31 Tower kernel: init_memory_mapping: [mem 0x37a00000-0x37bfdfff] Mar 1 05:19:31 Tower kernel: [mem 0x37a00000-0x37bfdfff] page 4k (Errors) Mar 1 05:19:31 Tower kernel: BRK [0x0162b000, 0x0162bfff] PGTABLE BREAK Mar 1 05:19:32 Tower logger: Verifying package libav-i486-rj.txz. Mar 1 05:19:32 Tower kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0xe frozen (Errors) Mar 1 05:19:32 Tower kernel: ata3: hotplug_status 0x8 (Drive related) Mar 1 05:19:32 Tower kernel: ata3: SError: { 10B8B Dispar } (Errors) Mar 1 05:19:32 Tower kernel: ata3: hard resetting link (Minor BREAK Mar 1 05:20:10 Tower emhttp_event: driver_loaded (System) Mar 1 05:20:10 Tower kernel: ata3: drained 65536 bytes to clear DRQ (Drive related) Mar 1 05:20:10 Tower kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x4190002 action 0xe frozen (Errors) Mar 1 05:20:10 Tower kernel: ata3.00: hotplug_status 0x8 (Drive related) Mar 1 05:20:10 Tower kernel: ata3: SError: { RecovComm PHYRdyChg 10B8B Dispar DevExch } (Errors) Mar 1 05:20:10 Tower kernel: ata3.00: failed command: SMART (Minor Issues) Mar 1 05:20:10 Tower kernel: ata3.00: cmd b0/d8:00:01:4f:c2/00:00:00:00:00/00 tag 0 (Drive related) Mar 1 05:20:10 Tower kernel: res ff/ff:ff:ff:ff:ff/00:00:00:00:00/ff Emask 0x12 (ATA bus error) (Errors) Mar 1 05:20:10 Tower kernel: ata3.00: status: { Busy } (Drive related) Mar 1 05:20:10 Tower kernel: ata3.00: error: { ICRC UNC IDNF ABRT } (Errors) Mar 1 05:20:10 Tower kernel: ata3: hard resetting link (Minor Issues) BREAK Mar 1 05:21:08 Tower kernel: ata3: reset failed, giving up (Minor Issues) Mar 1 05:21:08 Tower kernel: ata3.00: disabled (Errors) Mar 1 05:21:08 Tower kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x9 t4 (Errors) Mar 1 05:21:08 Tower kernel: ata3: hotplug_status 0x88 (Drive related) Mar 1 05:21:08 Tower kernel: ata3: hard resetting link (Minor Issues) BREAK Mar 1 05:21:08 Tower kernel: ata3: reset failed, giving up (Minor Issues) Mar 1 05:21:08 Tower kernel: ata3.00: disabled (Errors) Mar 1 05:21:08 Tower kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x9 t4 (Errors) Mar 1 05:21:08 Tower kernel: ata3: hotplug_status 0x88 (Drive related) BREAK Mar 1 05:34:09 Tower kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0xe frozen (Errors) Mar 1 05:34:09 Tower kernel: ata3: hotplug_status 0x8 (Drive related) Mar 1 05:34:09 Tower kernel: ata3: SError: { 10B8B Dispar } (Errors) Mar 1 05:34:09 Tower kernel: ata3: hard resetting link (Minor Issues) BREAK Mar 1 05:35:09 Tower kernel: ata3: reset failed, giving up (Minor Issues) Mar 1 05:35:09 Tower kernel: ata3.00: disabled (Errors) Mar 1 05:35:09 Tower kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x9 t4 (Errors) Mar 1 05:35:09 Tower kernel: ata3: hotplug_status 0x88 (Drive related) Mar 1 05:35:09 Tower kernel: ata3: hard resetting link (Minor Issues) BREAK ar 1 05:37:25 Tower kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x4190002 action 0xe frozen (Errors) Mar 1 05:37:25 Tower kernel: ata3.00: hotplug_status 0x8 (Drive related) Mar 1 05:37:25 Tower kernel: ata3: SError: { RecovComm PHYRdyChg 10B8B Dispar DevExch } (Errors) Mar 1 05:37:25 Tower kernel: ata3.00: failed command: READ DMA (Minor Issues) Mar 1 05:37:25 Tower kernel: ata3.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 1 05:37:25 Tower kernel: res ff/ff:ff:ff:ff:ff/00:00:00:00:00/ff Emask 0x12 (ATA bus error) (Errors) Mar 1 05:37:25 Tower kernel: ata3.00: status: { Busy } (Drive related) Mar 1 05:37:25 Tower kernel: ata3.00: error: { ICRC UNC IDNF ABRT } (Errors) Mar 1 05:37:25 Tower kernel: ata3: hard resetting link (Minor Issues)
March 2, 201412 yr Author Trul: I read that before I posted. I ran Samrtct, l but was not able to read the report. I am using Win 8 and did not see the utility to telnet in. I don't know much about it anyway, and probably would not recognize it if it hit me in the face. Dale, I intend to wait until things settle down, but at this point I need to become educated on what new hardware I should buy, what VM is all about, etc.
March 2, 201412 yr Trul: I read that before I posted. I ran Samrtct, l but was not able to read the report. I am using Win 8 and did not see the utility to telnet in. I don't know much about it anyway, and probably would not recognize it if it hit me in the face. Dale, I intend to wait until things settle down, but at this point I need to become educated on what new hardware I should buy, what VM is all about, etc. Don't know what Samrtct is, did you mean smartctl? If so, what do you mean you were not able to read the report? Can't access the report? Or can access the report but don't understand it? That wiki article has links to further information. If you can access the report then post it here and maybe we can help. Further down in the wiki it goes into more detail on how to replace a failed drive, but we should probably start with the report. Don't think Win8 comes with a native telnet. Even the older Windows telnet was not often used. Many of us are using puTTY. Just download the Windows installer.
March 2, 201412 yr Author I Googled telnet for Win 8 and was able to set it up. The report from the Smartctl short test seam to indicate no problems. I followed the WIKI instructions for reconstructing the drive and this is where I am currently stuck. The last step states the system should indicate there is a, "new drive to replace the disabled one. Check the confirmation box and click Start." I not quite sure of what to look for in the way of a confirmation box. Where is it located? Thanks Edit: I just clicked on the Start button and that started the rebuild process. I think I'm ok.
Archived
This topic is now archived and is closed to further replies.