Jump to content
Sign in to follow this  
3560freak

Rebuilt parity after unclean shutdown and disabled disk, am I in trouble? [OS build 6.6.7]

30 posts in this topic Last Reply

Recommended Posts

I've been an UnRaid user for some time, however I have been very luck and had few issues over the last 6-8 years (this community has been a tremendous help in the past), however might lack of patience and potential understanding of the processes might have gotten the best of me this time.

 

Logged into my server recently to see that I had a disabled data disk [DISK 1] (browser notices show that the disk was disable over 30 days ago and was being emulated).  I powered down the server, checked the connections, then followed a post that show how to re-enable the disk and tried that.  After the disk "rebuild itself" back into the array, I noticed that the UnRaid OS upgrade was available for ver 6.6.7 and so I processed to do that.  After completed it requested a restart, but the system would not restart, it immediately started throwing tons and tons of read errors on the Parity disk (different than the disk that had previously been disabled).  No matter what I tried, it would not allow the restart, it simply said STOPPING UNRAID for hours.  So I powered the system down manually.  Once bringing it back up I knew that I would have to do a parity check again due to the unclean shutdown, however after I started the parity check, and shortly after data DISK 1 once again disabled itself and the parity check continued.  It has completed now (it does show 168 errors on the Parity drive, assuming from the bad data pulled from DISK 1 before disabling itself), but I am not sure if any data has been overwritten or lost.

 

What can I do at this point to get all drives back up, or is it likely that I have lost a lot of unrecoverable data?

 

 

Thanks for any suggestions.

Share this post


Link to post
2 hours ago, 3560freak said:

(browser notices show that the disk was disable over 30 days ago and was being emulated). 

You should enable email notifications, also please post the diagnostics: Tools -> Diagnostics

 

 

 

 

Share this post


Link to post

Parity is failing, disk1 appears to be suffering from a connection issue, replace cables on disk1 and post new diags.

Share this post


Link to post
19 hours ago, johnnie.black said:

You should enable email notifications

^ This probably would have allowed you to fix a single problem when it occurred instead of getting to a place where you had multiple problems.

Share this post


Link to post
On 4/13/2019 at 1:52 AM, johnnie.black said:

Parity is failing, disk1 appears to be suffering from a connection issue, replace cables on disk1 and post new diags.

Unfortunately with the HP MicroServer Gen 8 that I am using I can't easily replace cabling.  I did however reseat all drives in their respective caddies/cage and unplug/replug the SATA breakout cable.  Updates diags attached.

 

On another note, should I be running individual SMART reports on the drives every so often?

tower2-diagnostics-20190414-0925.zip

Share this post


Link to post
4 hours ago, 3560freak said:

On another note, should I be running individual SMART reports on the drives every so often?

As long as you have Notifications enabled Unraid will inform you if any of the important attributes change.

Share this post


Link to post
On 4/15/2019 at 2:50 AM, johnnie.black said:

Disk1 looks fine, you could swap positions with another one just to rule out slot issue.

 

Thanks for your help.  Based on this updated log you still see that the PARITY is failing/needs to be replaced, correct?

Share this post


Link to post

There were media errors, i.e., bad or failing sectors on the parity disk, these errors some times can be a once off, though they rarely are, you can give it a second chance if it passes an extended SMART test but any more errors replace.

Share this post


Link to post
On 4/17/2019 at 1:44 AM, johnnie.black said:

There were media errors, i.e., bad or failing sectors on the parity disk, these errors some times can be a once off, though they rarely are, you can give it a second chance if it passes an extended SMART test but any more errors replace.

 

Ran the extended SMART test on the PARITY drive and it reported back no errors.  Then did a parity check (which completed successfully) but the status on the MAIN page still shows ERRORS as 1, causing the system to respond as READ ONLY.  How do I get UnRaid to drop the error marker and allow writes to the system again?

Share this post


Link to post

If you are referring to the Errors column in Main, that would not cause Read Only. Post new Diagnostics. 

Share this post


Link to post
8 hours ago, trurl said:

If you are referring to the Errors column in Main, that would not cause Read Only. Post new Diagnostics. 

 

The read only message is coming from an error when trying to update my dockers (PLEX, etc)

 

Updated diagnostics attached.

tower2-diagnostics-20190419-1619.zip

Share this post


Link to post

You have problems communicating with parity and disk2, possibly bad connections or controller issue. And your docker image is corrupt. After you get the connection issue corrected and a good parity check, you will have to delete and recreate docker image, then reinstall your dockers using the Previous Apps feature on the Apps page.

Share this post


Link to post

Strange there's a simultaneous read error on two disks, though in different but very close sectors, and it's reported as a media error, that's usually a disk problem, but in this case not so sure, very strange, something weird is going on with that server.

Share this post


Link to post
6 hours ago, johnnie.black said:

Strange there's a simultaneous read error on two disks, though in different but very close sectors, and it's reported as a media error, that's usually a disk problem, but in this case not so sure, very strange, something weird is going on with that server.

Maybe power supply voltage sag?

Share this post


Link to post
23 minutes ago, jonathanm said:

Maybe power supply voltage sag?

Possible, could also be the miniSAS cable, just strange being reported as a media error.

Share this post


Link to post

Well did another reboot/reseating of drives and parity check, then all came up as normal... but after about 12 hours DISK1 is showing errors again.  I guess I will begin the search for a new backplane cabling harness.  I've got the server running off of an APC (1500VA / 900W) UPS, so with such a relatively low power microserver likely not a voltage sag.

Share this post


Link to post

Update:

 

Ended up moving DISK1 to another spot in the backplane and still having issues, so now I am sure that it is the drive.  Cannot run extended SMART test now b/c the drive is disabled/offline, but I did get this from the disk log information tab.  Does this mean anything in regards to the drive health, or are they just communication message errors from Unraid?

 

Apr 24 20:37:58 Tower2 kernel: ata2: SATA max UDMA/133 abar m2048@0xfacd0000 port 0xfacd0180 irq 33
Apr 24 20:37:58 Tower2 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 24 20:37:58 Tower2 kernel: ata2.00: ATA-10: WDC WD40EFRX-68N32N0, WD-WCC7K7EPCH2V, 82.00A82, max UDMA/133
Apr 24 20:37:58 Tower2 kernel: ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Apr 24 20:37:58 Tower2 kernel: ata2.00: configured for UDMA/133
Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] 4096-byte physical blocks
Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] Write Protect is off
Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 24 20:37:58 Tower2 kernel: sdc: sdc1
Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] Attached SCSI disk
Apr 24 20:38:25 Tower2 emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V (sdc) 512 7814037168
Apr 24 20:38:25 Tower2 kernel: mdcmd (2): import 1 sdc 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V
Apr 24 20:38:25 Tower2 kernel: md: import disk1: (sdc) WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V size: 3907018532
Apr 24 20:38:26 Tower2 emhttpd: shcmd (27): /usr/local/sbin/set_ncq sdc 1
Apr 24 20:38:26 Tower2 root: set_ncq: setting sdc queue_depth to 1
Apr 24 20:38:26 Tower2 emhttpd: shcmd (28): echo 128 > /sys/block/sdc/queue/nr_requests
Apr 24 20:59:03 Tower2 emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V (sdc) 512 7814037168
Apr 24 21:00:07 Tower2 emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V (sdc) 512 7814037168
Apr 24 21:00:07 Tower2 kernel: mdcmd (2): import 1 sdc 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V
Apr 24 21:00:07 Tower2 kernel: md: import disk1: (sdc) WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V size: 3907018532
Apr 24 21:00:14 Tower2 emhttpd: shcmd (1436): /usr/local/sbin/set_ncq sdc 1
Apr 24 21:00:14 Tower2 emhttpd: shcmd (1437): echo 128 > /sys/block/sdc/queue/nr_requests
Apr 24 21:00:52 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:52 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:52 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 1 dma 688128 out
Apr 24 21:00:52 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:52 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to read native max address (err_mask=0x1)
Apr 24 21:00:52 Tower2 kernel: ata2.00: HPA support seems broken, skipping HPA handling
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:52 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:52 Tower2 kernel: ata2: EH complete
Apr 24 21:00:52 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:52 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:52 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 2 dma 688128 out
Apr 24 21:00:52 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:52 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:52 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:52 Tower2 kernel: ata2: EH complete
Apr 24 21:00:52 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:52 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:52 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 3 dma 688128 out
Apr 24 21:00:52 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:52 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:52 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:52 Tower2 kernel: ata2: EH complete
Apr 24 21:00:52 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:52 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:52 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 4 dma 688128 out
Apr 24 21:00:52 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:52 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:52 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:52 Tower2 kernel: ata2: EH complete
Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 5 dma 688128 out
Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:53 Tower2 kernel: ata2: EH complete
Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 6 dma 688128 out
Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#6 Sense Key : 0x5 [current]
Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#6 ASC=0x21 ASCQ=0x4
Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#6 CDB: opcode=0x8a 8a 00 00 00 00 00 00 03 8d 40 00 00 05 40 00 00
Apr 24 21:00:53 Tower2 kernel: print_req_error: I/O error, dev sdc, sector 232768
Apr 24 21:00:53 Tower2 kernel: ata2: EH complete
Apr 24 21:00:53 Tower2 kernel: ata2: limiting SATA link speed to 3.0 Gbps
Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 9 dma 4096 out
Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:53 Tower2 kernel: ata2: hard resetting link
Apr 24 21:00:53 Tower2 kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:53 Tower2 kernel: ata2: EH complete
Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 10 dma 4096 out
Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:53 Tower2 kernel: ata2: EH complete
Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 11 dma 4096 out
Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:53 Tower2 kernel: ata2: EH complete
Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 12 dma 4096 out
Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:53 Tower2 kernel: ata2: EH complete
Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 13 dma 4096 out
Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:53 Tower2 kernel: ata2: EH complete
Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 14 dma 4096 out
Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 Sense Key : 0x5 [current]
Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 ASC=0x21 ASCQ=0x4
Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 CDB: opcode=0x8a 8a 00 00 00 00 00 e9 0f 50 f8 00 00 00 08 00 00
Apr 24 21:00:53 Tower2 kernel: print_req_error: I/O error, dev sdc, sector 3910095096
Apr 24 21:00:53 Tower2 kernel: print_req_error: I/O error, dev sdc, sector 3910095096
Apr 24 21:00:53 Tower2 kernel: ata2: EH complete
Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 17 dma 688128 out
Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:53 Tower2 kernel: ata2: EH complete
Apr 24 21:00:53 Tower2 kernel: ata2: limiting SATA link speed to 1.5 Gbps
Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 18 dma 688128 out
Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:53 Tower2 kernel: ata2: hard resetting link
Apr 24 21:00:54 Tower2 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:54 Tower2 kernel: ata2: EH complete
Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 19 dma 688128 out
Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:54 Tower2 kernel: ata2: EH complete
Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 20 dma 688128 out
Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:54 Tower2 kernel: ata2: EH complete
Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 21 dma 688128 out
Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:54 Tower2 kernel: ata2: EH complete
Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 22 dma 688128 out
Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:54 Tower2 kernel: sd 2:0:0:0: [sdc] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Apr 24 21:00:54 Tower2 kernel: sd 2:0:0:0: [sdc] tag#22 Sense Key : 0x5 [current]
Apr 24 21:00:54 Tower2 kernel: sd 2:0:0:0: [sdc] tag#22 ASC=0x21 ASCQ=0x4
Apr 24 21:00:54 Tower2 kernel: sd 2:0:0:0: [sdc] tag#22 CDB: opcode=0x8a 8a 00 00 00 00 00 00 03 92 80 00 00 05 40 00 00
Apr 24 21:00:54 Tower2 kernel: print_req_error: I/O error, dev sdc, sector 234112
Apr 24 21:00:54 Tower2 kernel: ata2: EH complete
Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:80:c0:97:03/00:01:00:00:00/e0 tag 25 dma 196608 out
Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:54 Tower2 kernel: ata2: EH complete
Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:80:c0:97:03/00:01:00:00:00/e0 tag 26 dma 196608 out
Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored)
Apr 24 21:00:54 Tower2 kernel: ata2: EH complete
Apr 24 21:00:54 Tower2 kernel: ata2.00: limiting speed to UDMA/100:PIO4
Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT
Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:80:c0:97:03/00:01:00:00:00/e0 tag 27 dma 196608 out
Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR }
Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT }
Apr 24 21:00:54 Tower2 kernel: ata2: hard resetting link
Apr 24 21:00:54 Tower2 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to set xfermode (err_mask=0x1)
Apr 24 21:00:59 Tower2 kernel: ata2: hard resetting link
Apr 24 21:01:00 Tower2 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 24 21:01:00 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:01:00 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:01:00 Tower2 kernel: ata2.00: failed to set xfermode (err_mask=0x1)
Apr 24 21:01:00 Tower2 kernel: ata2.00: limiting speed to UDMA/100:PIO3
Apr 24 21:01:05 Tower2 kernel: ata2: hard resetting link
Apr 24 21:01:05 Tower2 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 24 21:01:05 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:01:05 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1)
Apr 24 21:01:05 Tower2 kernel: ata2.00: failed to set xfermode (err_mask=0x1)
Apr 24 21:01:05 Tower2 kernel: ata2.00: disabled
Apr 24 21:01:05 Tower2 kernel: ata2: EH complete
Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] tag#28 CDB: opcode=0x8a 8a 00 00 00 00 00 00 03 97 c0 00 00 01 80 00 00
Apr 24 21:01:05 Tower2 kernel: print_req_error: I/O error, dev sdc, sector 235456
Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00
Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] Sense not available.
Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00
Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] Sense not available.
Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] 4096-byte physical blocks
Apr 24 21:01:05 Tower2 kernel: sdc: detected capacity change from 4000787030016 to 0
Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#9 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#11 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00
Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#16 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00
Apr 25 00:13:28 Tower2 emhttpd: shcmd (1890): /usr/local/sbin/set_ncq sdc 1
Apr 25 00:13:28 Tower2 emhttpd: shcmd (1891): echo 128 > /sys/block/sdc/queue/nr_requests
Apr 25 00:13:28 Tower2 kernel: sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 25 00:13:28 Tower2 kernel: sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Apr 25 00:13:28 Tower2 kernel: sd 2:0:0:0: [sdc] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 25 00:13:28 Tower2 kernel: sd 2:0:0:0: [sdc] tag#2 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00
Apr 25 00:13:29 Tower2 emhttpd: shcmd (1900): /usr/local/sbin/set_ncq sdc 1
Apr 25 00:13:29 Tower2 emhttpd: shcmd (1901): echo 128 > /sys/block/sdc/queue/nr_requests
Apr 25 00:13:50 Tower2 emhttpd: shcmd (1911): /usr/local/sbin/set_ncq sdc 1
Apr 25 00:13:50 Tower2 emhttpd: shcmd (1912): echo 128 > /sys/block/sdc/queue/nr_requests
Apr 25 00:13:50 Tower2 kernel: sd 2:0:0:0: [sdc] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 25 00:13:50 Tower2 kernel: sd 2:0:0:0: [sdc] tag#25 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Apr 25 00:13:50 Tower2 kernel: sd 2:0:0:0: [sdc] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 25 00:13:50 Tower2 kernel: sd 2:0:0:0: [sdc] tag#27 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00
Apr 25 00:13:50 Tower2 emhttpd: shcmd (1921): /usr/local/sbin/set_ncq sdc 1
Apr 25 00:13:50 Tower2 emhttpd: shcmd (1922): echo 128 > /sys/block/sdc/queue/nr_requests
Apr 25 00:17:41 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:41 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:42 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:42 Tower2 kernel: sd 2:0:0:0: [sdc] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 25 00:17:42 Tower2 kernel: sd 2:0:0:0: [sdc] tag#17 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Apr 25 00:17:42 Tower2 kernel: sd 2:0:0:0: [sdc] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Apr 25 00:17:42 Tower2 kernel: sd 2:0:0:0: [sdc] tag#19 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00
Apr 25 00:17:43 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:44 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:45 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:46 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:47 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:48 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:49 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:50 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:51 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:52 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:54 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:55 Tower2 emhttpd: device /dev/sdc has size zero
Apr 25 00:17:56 Tower2 emhttpd: device /dev/sdc has size zero

Share this post


Link to post
2 hours ago, 3560freak said:

Does this mean anything in regards to the drive health

It's not communicating correctly with the disk, if it's a connection problem or an actual disk problem difficult to say by those.

Share this post


Link to post
On 4/25/2019 at 2:34 AM, johnnie.black said:

It's not communicating correctly with the disk, if it's a connection problem or an actual disk problem difficult to say by those.

Is there a good/proper way to test the drive outside of the server?  I moved the drive to another spot on the backplane and still have the issue, so I am trying to completely rule out the backplane.

Share this post


Link to post

If you stop the array, unassign the disk, then start the array, it should appear as an Unassigned Device. Then you can run an extended SMART test on it.

 

Until you rebuild the disk, it is being emulated by the rest of the array (and you are running without parity protection) and Unraid isn't using it anyway. So it doesn't matter whether it is assigned or not.

Share this post


Link to post

But are you sure it won't let you run an extended SMART test on the disable disk? I don't see any reason why that wouldn't be allowed, or any reason to exclude it from the functionality. I haven't had a disabled disk in a long time so I don't know.

Share this post


Link to post
Posted (edited)

My server has been out of commission for almost 2 months now due to this issue, but I have finally ordered/received a replacement drive (I will RMA the questionable one later for a backup).  However, should I just let UnRAID rebuild the image on this new disk, or should I attach the old disk via USB and try and copy data from it to the new drive?  I assume there is the potential issue of data not copying correctly due to the disk in question failing, but wasn't sure if this was better than letting UnRAID rebuild.  Thanks for the info.

Edited by 3560freak

Share this post


Link to post

Unless there's reason to believe parity is out of sync the best way would be to do a standard rebuild.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this