[Parity drive listed errors]

tower-diagnostics-20230625-0200.ziptower-smart-20230625-0159.zip

 

Finally finished the SMART extended self test. 

 

Looks fine I guess? 

On 6/23/2023 at 5:46 PM, JorgeB said:

Run an extended SMART test on party, but should be OK for now.

 

[Parity drive listed errors]

So there was a power outage last night while I let the full SMART extended self test run. So my unraid server was shutdown via the UPS. So I will have to do another test. Will update once it's done.

[Parity drive listed errors]

Unraid Version: 6.11.5

Motherboard: MSI B550 Mortar Wifi

CPU: AMD Ryzen 3900X

MEMORY: 32GB @ 3000mhz (mismatched kits of 2x8)

 

Hello,

 

I noticed this morning some errors were listed when my parity drive span up at 5:00am to run MOVER.

 

Also, then recieved two follow up emails with; 

 

Subject: Warning [TOWER] - reallocated sector ct is 216
Description: ST8000VN004-2M2101_WKD0TW3W (sdc)

 

Subject: Warning [TOWER] - reported uncorrect is 2
Description: ST8000VN004-2M2101_WKD0TW3W (sdc)

 

 

I have had errors on drives before and taken certain measures to fix the issue (replace cables etc) or replace the drive itself, but I have never had any errors show up on the parity drive. So I am wondering if I need to do anything differently in this situation?

 

Also just as a side note, is my spin-down delay of 1 hour on my drives too low? They don't get access too often maybe once or twice a day. I do not want to run the drives 24/7 due to the increased noise and electricity costs.

 

I have uploaded the diagnostics to this post and will await for further instruction, thank you.

 

tower-diagnostics-20230623-1623.zip

[Invalid folder addons contained within /mnt]

Just wanted to post and say I also am getting this error. I have no idea what an 'addons' folder is nor how to even access it. 

 

58 minutes ago, chuckthetekkie said:

That folder is empty but cannot be deleted as it says that the resource is busy. 

 

What are you doing to find the folder?

[Array has errors (64) - do I disregard?]

Okay thanks for the suggestions.

 

I will turn the server off tomorrow and check what cable it's on. (Mobo / SAS card)

 

I thought I was being smart last time with putting labels on all my drives. Now I realise I'm an idiot for not labelling which end of the system they go to.

 

Edit: Can see in devices which drives are on LSI card / Motherboard ports.

 

 

[Array has errors (64) - do I disregard?]

Unraid 6.11.5
Ryzen 3900X
B550M Mortar Wifi

 

Hello,

 

Last night I recieved an email that my server encounter some errors on a disk. This concerned me greatly because just recently (2~ weeks ago) I went through a whole ordeal with a drive seemingly failing, and then the replacement drive I bought failed, so had to buy a 2nd replacement drive to fix. (Context here)

 

Immediately upon seeing this error I began a SMART extended self test on the drive, and it has just completed. It returned without error. I'm attaching the diagnostics to this post.

 

Do I simply disregard this small error of 64 as a one off random thing maybe caused by a memory failure etc, or is this something I should take more seriously? I have had my unRAID server running great for 3 years, up until a couple of weeks ago. The previous incident clearly seemed that the drive itself had failed (under warranty) but now with these errors coming up randomly on a different drive, perhaps something else is also happening that needs to be addressed? I can't really recall ever having errors on drives before outside of a failed drive and faulty SATA cable.

 

What are the next steps I should take? Thanks.

 

 

tower-diagnostics-20230222-1826.zip

[Disk Errors - Disk Disabled - UDMA CRC Errors]

7 minutes ago, trurl said:

Yes, it does do that even though it shouldn't. Just ignore it. And if it really did overwrite parity it wouldn't hurt anything. It would just be a parity rebuild, which has no effect on any of your data disks.

 

Thank you for the help once again! You're a life saver.

 

I have started the array, things appear to be working fine. I have taken a flash backup and am attaching the diagnostics file.

 

About to start running a non-correcting parity check now also.

tower-diagnostics-20230211-1356.zip

[Disk Errors - Disk Disabled - UDMA CRC Errors]

1 minute ago, trurl said:

Just New Config, Retain All, Apply, then reassign the disk. Check Parity Valid box before starting the array. Done.

 

I did the new config > Preserve current assignments = All > Apply.

 

Now when I am about to start the array, it is claiming my parity drive will be overwritten (I have selected parity valid box)

 

Is this what it normally says or has something else gone wrong now? I am scared to start the array with that warning message there. As it still stays there even with the parity is valid check mark ticked.

 

 

[Disk Errors - Disk Disabled - UDMA CRC Errors]

2 minutes ago, trurl said:

Did you perhaps do the rebuild in Maintenance mode?

 

Yes I did the rebuild in maintenance mode. Because I was afraid it might write data from things and screw up the data-rebuild. After it completed I then stopped the array, and restarted the array in normal? mode.

 

3 minutes ago, trurl said:

You can New Config/Trust Parity

 

Is this the only option?

[Disk Errors - Disk Disabled - UDMA CRC Errors]

1 minute ago, trurl said:

Do you have diagnostics from then?

 

Your disks assignments is in config/super.dat on flash. Is there any way you might have put the old version of that file on your flash drive?

 

No I do not have diagnostics from after the rebuild because it all went fine so I didn't see a need to. I haven't touched anything regarding flash drive or anything else. PC Has been on permanently since I did that successful data rebuild onto WP00KDEZ. Then today, I did a proper shutdown from Unraid UI (clicking shutdown button) and now I get this.

 

Is there any way for me to edit the super.dat file to think the correct drive is in (which it...is?) or am I now royally screwed.

[Disk Errors - Disk Disabled - UDMA CRC Errors]

Sorry forgot to add the diagnostics. Not sure how much use it will be.

tower-diagnostics-20230211-1307.zip

[Disk Errors - Disk Disabled - UDMA CRC Errors]

@JorgeB @trurl

 

New issue....

 

I turned off the PC to load into BIOS to enable CPU Virtualisation so I can run a VM.

 

When I loaded back into unRAID it is claiming my Disk 5 was missing, and the option to select it claims is the incorrect one.

 

 

It thinks that the correct disk is WP00L646 for Disk 5. Which is that failed new drive I bought last weekend which immediately had errors so I cancelled the rebuild at 19%.

 

The full data rebuild was performed on WP00KDEZ which is the drive I still have in now.

 

How can I get unRAID to recognise this is the correct drive? Or am I now screwed....

I just returned both those 2 failed drives for RMA yesterday.

[Disk Errors - Disk Disabled - UDMA CRC Errors]

Great news.

 

Rebuild on the 2nd new drive went off without a hitch. All my data is secure once again!

 

Thanks trurl and JorgeB for the great help! Definitely calmed my nerves when I was panicking.

[Disk Errors - Disk Disabled - UDMA CRC Errors]

On 2/5/2023 at 11:06 PM, JorgeB said:

Yes.

@trurl

 

New, NEW drive is in. Did a quick 1 min smart-self test and it at least passed that. The previous new drive was failing even those.

 

I decided to keep the drive on my LSI SAS card on a cable I have been using for years, even though I also did recieve brand new sata cables today too. Would rather stick it on a cable I know works fine than risk a new cable that might be faulty and cause the rebuild to fail.

 

Also I understand I'm not in the greatest time-zone (Australia) to be dealing with you, so I'm not expecting immediate responses if something does go wrong again. I'll just post updates as to what is wrong and appreciate any help you can give, when you are able to do so. Thanks!

 

Just started the Data rebuild and will keep you guys updated as to how it goes. 

 

 

[Disk Errors - Disk Disabled - UDMA CRC Errors]

23 minutes ago, JorgeB said:

Yep, you need a new one.

Yeah thanks.

 

Already ordered the new drive so I'll update this thread when that arrives.

 

I have turned off the server completely now because I was unsure what else to do. Is this fine to leave it off for a couple of days?

[Disk Errors - Disk Disabled - UDMA CRC Errors]

Well I am just going to assume this new drive is faulty. RMAing it.

 

Now because I have tried to build parity over to a new drive, am I unable to put the old drive back in to return back to that data? As the old drive will be recognised now as a "new" drive and try rebuild over it?

 

What are my best options here for maintaining data integrity? As I'll now be without a new drive to build parity into for a couple of days. Should I simply turn the PC off? Or is it better to leave the system running but the array stopped?

[Disk Errors - Disk Disabled - UDMA CRC Errors]

Cancelled the rebuild for 2nd time as it had errors again.

 

Swapped to a 4th SATA data cable, and then swapped the cable with a different drive from my LSI SAS card which I know has been running fine.

 

Tried to run an Extended self-test on the new drive and it failed within 10 minutes.

 

Did I seriously get a faulty new drive?

 

Should I try putting the new drive into my actual PC and run some tests on it in Windows to rule out if it's an error with my unRAID PC?

tower-smart-20230205-1848.zip

[Disk Errors - Disk Disabled - UDMA CRC Errors]

Offline Uncorrectable errors went up to 136 by 19% of the rebuild. I decided it was best to cancel the rebuild and power down. Change over to another SATA data cable and different sata port on my motherboard and see what happens when I try again. When I powered the system on again it said the errors were actually 225. I'll post the latest SMART report from after I powered down and changed cable. I'm kind of hoping that maybe it was just faulty cables after all and the original drive might be fine? I don't know how to read SMART reports properly though so I could be wrong on that!

 

I have ordered some new SATA data cables to come tomorrow, but fingers crossed on this 3rd cable being okay?

 

Rebuild is currently beginning again.

tower-smart-20230205-1736.zip

[Disk Errors - Disk Disabled - UDMA CRC Errors]

@trurl I just put in a new replacement drive and I am getting this.

 

 

It's only 12% of the way through the parity rebuild.

 

Any thoughts? Could this be a faulty drive or could this be related to the SATA data cable or something.

 

SMART report attached of the new drive

tower-smart-20230205-1611.zip

[Disk Errors - Disk Disabled - UDMA CRC Errors]

16 minutes ago, trurl said:

The parity array will remember the data for the missing disk, but since you have single parity, you have no redundancy until you rebuild the missing disk. So if another disk has problems you could lose both.

Yeah makes sense. I'll buy a replacement and then begin the warranty return after I rebuild. Can replace my 6tb with 8tb I suppose.

 

Thanks again for all the help! 

[Disk Errors - Disk Disabled - UDMA CRC Errors]

6 minutes ago, trurl said:

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       30%     18804         13059870608

 

Replace

Thanks for finding that.

 

Because I'll be replacing the drive under warranty. Is it safe to simply unmount this drive and my parity drive will remember the data even if I don't get the drive replacement for a month? Or is that risky and I should just buy another 8tb drive to immediately rebuild so nothing gets lost? 

[Disk Errors - Disk Disabled - UDMA CRC Errors]

11 hours ago, JorgeB said:

If it keeps going up yes, you can run an extended SMART test for now.

 

Unraid reported the extended self test failed and to read smart report. I have attached it.

 

Said something in the report about failed read at 30%

 

So does this mean I should replace the drive? It's under warranty still. 

tower-smart-20230203-0654.zip

[Disk Errors - Disk Disabled - UDMA CRC Errors]

3 hours ago, JorgeB said:

If it keeps going up yes, you can run an extended SMART test for now.

 

The errors have not increased in unRAID main tab, and no further warnings. I also done a comparison between a new SMART report and one from hours ago and the uncorrectable errors and reallocated sectors have not increased either. I am now running the Extended smart self-test again. And have re-enabled Mover to run again overnight, and it should write data to that drive at some point so will see if the errors increase and will report back tomorrow.

 

Thanks for all the help so far, I appreciate it!

[Disk Errors - Disk Disabled - UDMA CRC Errors]

I don't know if this is useful or not, but I'll post the disk log from unRAID too. Unsure if this is available in the diagnostics.

 

text  error  warn  system  array  login  

Feb  2 15:30:46 Tower kernel: ata4: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580280 irq 85
Feb  2 15:30:46 Tower kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb  2 15:30:46 Tower kernel: ata4.00: ATA-11: ST8000VN004-2M2101, SC60, max UDMA/133
Feb  2 15:30:46 Tower kernel: ata4.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Feb  2 15:30:46 Tower kernel: ata4.00: Features: NCQ-sndrcv
Feb  2 15:30:46 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:30:46 Tower kernel: sd 4:0:0:0: [sdd] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
Feb  2 15:30:46 Tower kernel: sd 4:0:0:0: [sdd] 4096-byte physical blocks
Feb  2 15:30:46 Tower kernel: sd 4:0:0:0: [sdd] Write Protect is off
Feb  2 15:30:46 Tower kernel: sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Feb  2 15:30:46 Tower kernel: sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb  2 15:30:46 Tower kernel: sdd: sdd1
Feb  2 15:30:46 Tower kernel: sd 4:0:0:0: [sdd] Attached SCSI disk
Feb  2 15:31:01 Tower wsdd2[1463]: starting.
Feb  2 15:32:00 Tower emhttpd: ST8000VN004-2M2101_WKD3HD7N (sdd) 512 15628053168
Feb  2 15:32:00 Tower kernel: mdcmd (6): import 5 sdd 64 7814026532 0 ST8000VN004-2M2101_WKD3HD7N
Feb  2 15:32:00 Tower kernel: md: import disk5: (sdd) ST8000VN004-2M2101_WKD3HD7N size: 7814026532 
Feb  2 15:32:00 Tower emhttpd: read SMART /dev/sdd
Feb  2 15:32:00 Tower wsdd2[1463]: 'Terminated' signal received.
Feb  2 15:32:00 Tower wsdd2[1463]: terminating.
Feb  2 15:32:02 Tower root:                  /usr/sbin/wsdd2 -d 
Feb  2 15:32:02 Tower wsdd2[4129]: starting.
Feb  2 15:33:31 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x200000 SErr 0x0 action 0x0
Feb  2 15:33:31 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:33:31 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:33:31 Tower kernel: ata4.00: cmd 60/08:a8:80:64:09/00:00:00:02:00/40 tag 21 ncq dma 4096 in
Feb  2 15:33:31 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:33:31 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:33:31 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:33:31 Tower kernel: sd 4:0:0:0: [sdd] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:33:31 Tower kernel: sd 4:0:0:0: [sdd] tag#21 Sense Key : 0x3 [current] 
Feb  2 15:33:31 Tower kernel: sd 4:0:0:0: [sdd] tag#21 ASC=0x11 ASCQ=0x4 
Feb  2 15:33:31 Tower kernel: sd 4:0:0:0: [sdd] tag#21 CDB: opcode=0x88 88 00 00 00 00 02 00 09 64 80 00 00 00 08 00 00
Feb  2 15:33:31 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590550144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb  2 15:33:31 Tower kernel: ata4: EH complete
Feb  2 15:33:34 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x0
Feb  2 15:33:34 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:33:34 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:33:34 Tower kernel: ata4.00: cmd 60/08:10:88:5c:09/00:00:00:02:00/40 tag 2 ncq dma 4096 in
Feb  2 15:33:34 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:33:34 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:33:34 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:33:34 Tower kernel: sd 4:0:0:0: [sdd] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:33:34 Tower kernel: sd 4:0:0:0: [sdd] tag#2 Sense Key : 0x3 [current] 
Feb  2 15:33:34 Tower kernel: sd 4:0:0:0: [sdd] tag#2 ASC=0x11 ASCQ=0x4 
Feb  2 15:33:34 Tower kernel: sd 4:0:0:0: [sdd] tag#2 CDB: opcode=0x88 88 00 00 00 00 02 00 09 5c 88 00 00 00 08 00 00
Feb  2 15:33:34 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590548104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb  2 15:33:34 Tower kernel: ata4: EH complete
Feb  2 15:33:37 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x0
Feb  2 15:33:37 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:33:37 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:33:37 Tower kernel: ata4.00: cmd 60/08:20:90:58:09/00:00:00:02:00/40 tag 4 ncq dma 4096 in
Feb  2 15:33:37 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:33:37 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:33:37 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:33:37 Tower kernel: sd 4:0:0:0: [sdd] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:33:37 Tower kernel: sd 4:0:0:0: [sdd] tag#4 Sense Key : 0x3 [current] 
Feb  2 15:33:37 Tower kernel: sd 4:0:0:0: [sdd] tag#4 ASC=0x11 ASCQ=0x4 
Feb  2 15:33:37 Tower kernel: sd 4:0:0:0: [sdd] tag#4 CDB: opcode=0x88 88 00 00 00 00 02 00 09 58 90 00 00 00 08 00 00
Feb  2 15:33:37 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590547088 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb  2 15:33:37 Tower kernel: ata4: EH complete
Feb  2 15:33:41 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x0
Feb  2 15:33:41 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:33:41 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:33:41 Tower kernel: ata4.00: cmd 60/08:40:10:58:09/00:00:00:02:00/40 tag 8 ncq dma 4096 in
Feb  2 15:33:41 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:33:41 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:33:41 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:33:41 Tower kernel: sd 4:0:0:0: [sdd] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:33:41 Tower kernel: sd 4:0:0:0: [sdd] tag#8 Sense Key : 0x3 [current] 
Feb  2 15:33:41 Tower kernel: sd 4:0:0:0: [sdd] tag#8 ASC=0x11 ASCQ=0x4 
Feb  2 15:33:41 Tower kernel: sd 4:0:0:0: [sdd] tag#8 CDB: opcode=0x88 88 00 00 00 00 02 00 09 58 10 00 00 00 08 00 00
Feb  2 15:33:41 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590546960 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb  2 15:33:41 Tower kernel: ata4: EH complete
Feb  2 15:33:44 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x800 SErr 0x0 action 0x0
Feb  2 15:33:44 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:33:44 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:33:44 Tower kernel: ata4.00: cmd 60/08:58:f0:57:09/00:00:00:02:00/40 tag 11 ncq dma 4096 in
Feb  2 15:33:44 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:33:44 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:33:44 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:33:44 Tower kernel: sd 4:0:0:0: [sdd] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:33:44 Tower kernel: sd 4:0:0:0: [sdd] tag#11 Sense Key : 0x3 [current] 
Feb  2 15:33:44 Tower kernel: sd 4:0:0:0: [sdd] tag#11 ASC=0x11 ASCQ=0x4 
Feb  2 15:33:44 Tower kernel: sd 4:0:0:0: [sdd] tag#11 CDB: opcode=0x88 88 00 00 00 00 02 00 09 57 f0 00 00 00 08 00 00
Feb  2 15:33:44 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590546928 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb  2 15:33:44 Tower kernel: ata4: EH complete
Feb  2 15:33:48 Tower kernel: ata4.00: exception Emask 0x0 SAct 0xf400 SErr 0x0 action 0x0
Feb  2 15:33:48 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:33:48 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:33:48 Tower kernel: ata4.00: cmd 60/18:50:f8:57:09/00:00:00:02:00/40 tag 10 ncq dma 12288 in
Feb  2 15:33:48 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:33:48 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:33:48 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:33:48 Tower kernel: sd 4:0:0:0: [sdd] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:33:48 Tower kernel: sd 4:0:0:0: [sdd] tag#10 Sense Key : 0x3 [current] 
Feb  2 15:33:48 Tower kernel: sd 4:0:0:0: [sdd] tag#10 ASC=0x11 ASCQ=0x4 
Feb  2 15:33:48 Tower kernel: sd 4:0:0:0: [sdd] tag#10 CDB: opcode=0x88 88 00 00 00 00 02 00 09 57 f8 00 00 00 18 00 00
Feb  2 15:33:48 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590546936 op 0x0:(READ) flags 0x0 phys_seg 3 prio class 0
Feb  2 15:33:48 Tower kernel: ata4: EH complete
Feb  2 15:33:51 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x1e000 SErr 0x0 action 0x0
Feb  2 15:33:51 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:33:51 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:33:51 Tower kernel: ata4.00: cmd 60/58:68:98:58:09/00:00:00:02:00/40 tag 13 ncq dma 45056 in
Feb  2 15:33:51 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:33:51 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:33:51 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:33:51 Tower kernel: sd 4:0:0:0: [sdd] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=6s
Feb  2 15:33:51 Tower kernel: sd 4:0:0:0: [sdd] tag#13 Sense Key : 0x3 [current] 
Feb  2 15:33:51 Tower kernel: sd 4:0:0:0: [sdd] tag#13 ASC=0x11 ASCQ=0x4 
Feb  2 15:33:51 Tower kernel: sd 4:0:0:0: [sdd] tag#13 CDB: opcode=0x88 88 00 00 00 00 02 00 09 58 98 00 00 00 58 00 00
Feb  2 15:33:51 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590547096 op 0x0:(READ) flags 0x0 phys_seg 11 prio class 0
Feb  2 15:33:51 Tower kernel: ata4: EH complete
Feb  2 15:33:54 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x40100 SErr 0x0 action 0x0
Feb  2 15:33:54 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:33:54 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:33:54 Tower kernel: ata4.00: cmd 60/78:40:18:58:09/00:00:00:02:00/40 tag 8 ncq dma 61440 in
Feb  2 15:33:54 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:33:54 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:33:55 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:33:55 Tower kernel: sd 4:0:0:0: [sdd] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=10s
Feb  2 15:33:55 Tower kernel: sd 4:0:0:0: [sdd] tag#8 Sense Key : 0x3 [current] 
Feb  2 15:33:55 Tower kernel: sd 4:0:0:0: [sdd] tag#8 ASC=0x11 ASCQ=0x4 
Feb  2 15:33:55 Tower kernel: sd 4:0:0:0: [sdd] tag#8 CDB: opcode=0x88 88 00 00 00 00 02 00 09 58 18 00 00 00 78 00 00
Feb  2 15:33:55 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590546968 op 0x0:(READ) flags 0x0 phys_seg 15 prio class 0
Feb  2 15:33:55 Tower kernel: ata4: EH complete
Feb  2 15:33:58 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x0
Feb  2 15:33:58 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:33:58 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:33:58 Tower kernel: ata4.00: cmd 60/00:a0:f0:58:09/01:00:00:02:00/40 tag 20 ncq dma 131072 in
Feb  2 15:33:58 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:33:58 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:33:58 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:33:58 Tower kernel: sd 4:0:0:0: [sdd] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:33:58 Tower kernel: sd 4:0:0:0: [sdd] tag#20 Sense Key : 0x3 [current] 
Feb  2 15:33:58 Tower kernel: sd 4:0:0:0: [sdd] tag#20 ASC=0x11 ASCQ=0x4 
Feb  2 15:33:58 Tower kernel: sd 4:0:0:0: [sdd] tag#20 CDB: opcode=0x88 88 00 00 00 00 02 00 09 58 f0 00 00 01 00 00 00
Feb  2 15:33:58 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590547184 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:33:58 Tower kernel: ata4: EH complete
Feb  2 15:34:02 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x800002 SErr 0x0 action 0x0
Feb  2 15:34:02 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:02 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:02 Tower kernel: ata4.00: cmd 60/00:b8:f0:59:09/01:00:00:02:00/40 tag 23 ncq dma 131072 in
Feb  2 15:34:02 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:02 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:02 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:02 Tower kernel: sd 4:0:0:0: [sdd] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:02 Tower kernel: sd 4:0:0:0: [sdd] tag#23 Sense Key : 0x3 [current] 
Feb  2 15:34:02 Tower kernel: sd 4:0:0:0: [sdd] tag#23 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:02 Tower kernel: sd 4:0:0:0: [sdd] tag#23 CDB: opcode=0x88 88 00 00 00 00 02 00 09 59 f0 00 00 01 00 00 00
Feb  2 15:34:02 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590547440 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:02 Tower kernel: ata4: EH complete
Feb  2 15:34:05 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x50000001 SErr 0x0 action 0x0
Feb  2 15:34:05 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:05 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:05 Tower kernel: ata4.00: cmd 60/00:e0:f0:5a:09/01:00:00:02:00/40 tag 28 ncq dma 131072 in
Feb  2 15:34:05 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:05 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:05 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:05 Tower kernel: sd 4:0:0:0: [sdd] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:05 Tower kernel: sd 4:0:0:0: [sdd] tag#28 Sense Key : 0x3 [current] 
Feb  2 15:34:05 Tower kernel: sd 4:0:0:0: [sdd] tag#28 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:05 Tower kernel: sd 4:0:0:0: [sdd] tag#28 CDB: opcode=0x88 88 00 00 00 00 02 00 09 5a f0 00 00 01 00 00 00
Feb  2 15:34:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590547696 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:05 Tower kernel: ata4: EH complete
Feb  2 15:34:08 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x1d SErr 0x0 action 0x0
Feb  2 15:34:08 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:08 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:08 Tower kernel: ata4.00: cmd 60/98:00:f0:5b:09/00:00:00:02:00/40 tag 0 ncq dma 77824 in
Feb  2 15:34:08 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:08 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:08 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:08 Tower kernel: sd 4:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:08 Tower kernel: sd 4:0:0:0: [sdd] tag#0 Sense Key : 0x3 [current] 
Feb  2 15:34:08 Tower kernel: sd 4:0:0:0: [sdd] tag#0 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:08 Tower kernel: sd 4:0:0:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 02 00 09 5b f0 00 00 00 98 00 00
Feb  2 15:34:08 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590547952 op 0x0:(READ) flags 0x0 phys_seg 19 prio class 0
Feb  2 15:34:08 Tower kernel: ata4: EH complete
Feb  2 15:34:12 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x240 SErr 0x0 action 0x0
Feb  2 15:34:12 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:12 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:12 Tower kernel: ata4.00: cmd 60/60:30:90:5c:09/00:00:00:02:00/40 tag 6 ncq dma 49152 in
Feb  2 15:34:12 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:12 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:12 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:12 Tower kernel: sd 4:0:0:0: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=6s
Feb  2 15:34:12 Tower kernel: sd 4:0:0:0: [sdd] tag#6 Sense Key : 0x3 [current] 
Feb  2 15:34:12 Tower kernel: sd 4:0:0:0: [sdd] tag#6 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:12 Tower kernel: sd 4:0:0:0: [sdd] tag#6 CDB: opcode=0x88 88 00 00 00 00 02 00 09 5c 90 00 00 00 60 00 00
Feb  2 15:34:12 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590548112 op 0x0:(READ) flags 0x0 phys_seg 12 prio class 0
Feb  2 15:34:12 Tower kernel: ata4: EH complete
Feb  2 15:34:15 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x2000 SErr 0x0 action 0x0
Feb  2 15:34:15 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:15 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:15 Tower kernel: ata4.00: cmd 60/00:68:f0:5c:09/01:00:00:02:00/40 tag 13 ncq dma 131072 in
Feb  2 15:34:15 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:15 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:15 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:15 Tower kernel: sd 4:0:0:0: [sdd] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:15 Tower kernel: sd 4:0:0:0: [sdd] tag#13 Sense Key : 0x3 [current] 
Feb  2 15:34:15 Tower kernel: sd 4:0:0:0: [sdd] tag#13 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:15 Tower kernel: sd 4:0:0:0: [sdd] tag#13 CDB: opcode=0x88 88 00 00 00 00 02 00 09 5c f0 00 00 01 00 00 00
Feb  2 15:34:15 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590548208 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:15 Tower kernel: ata4: EH complete
Feb  2 15:34:19 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0
Feb  2 15:34:19 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:19 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:19 Tower kernel: ata4.00: cmd 60/00:30:f0:5d:09/01:00:00:02:00/40 tag 6 ncq dma 131072 in
Feb  2 15:34:19 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:19 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:19 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:19 Tower kernel: sd 4:0:0:0: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:19 Tower kernel: sd 4:0:0:0: [sdd] tag#6 Sense Key : 0x3 [current] 
Feb  2 15:34:19 Tower kernel: sd 4:0:0:0: [sdd] tag#6 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:19 Tower kernel: sd 4:0:0:0: [sdd] tag#6 CDB: opcode=0x88 88 00 00 00 00 02 00 09 5d f0 00 00 01 00 00 00
Feb  2 15:34:19 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590548464 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:19 Tower kernel: ata4: EH complete
Feb  2 15:34:22 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x400 SErr 0x0 action 0x0
Feb  2 15:34:22 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:22 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:22 Tower kernel: ata4.00: cmd 60/00:50:f0:5e:09/01:00:00:02:00/40 tag 10 ncq dma 131072 in
Feb  2 15:34:22 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:22 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:22 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:22 Tower kernel: sd 4:0:0:0: [sdd] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:22 Tower kernel: sd 4:0:0:0: [sdd] tag#10 Sense Key : 0x3 [current] 
Feb  2 15:34:22 Tower kernel: sd 4:0:0:0: [sdd] tag#10 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:22 Tower kernel: sd 4:0:0:0: [sdd] tag#10 CDB: opcode=0x88 88 00 00 00 00 02 00 09 5e f0 00 00 01 00 00 00
Feb  2 15:34:22 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590548720 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:22 Tower kernel: ata4: EH complete
Feb  2 15:34:25 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x2000 SErr 0x0 action 0x0
Feb  2 15:34:25 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:25 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:25 Tower kernel: ata4.00: cmd 60/00:68:f0:5f:09/01:00:00:02:00/40 tag 13 ncq dma 131072 in
Feb  2 15:34:25 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:25 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:25 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:25 Tower kernel: sd 4:0:0:0: [sdd] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:25 Tower kernel: sd 4:0:0:0: [sdd] tag#13 Sense Key : 0x3 [current] 
Feb  2 15:34:25 Tower kernel: sd 4:0:0:0: [sdd] tag#13 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:25 Tower kernel: sd 4:0:0:0: [sdd] tag#13 CDB: opcode=0x88 88 00 00 00 00 02 00 09 5f f0 00 00 01 00 00 00
Feb  2 15:34:25 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590548976 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:25 Tower kernel: ata4: EH complete
Feb  2 15:34:29 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x0
Feb  2 15:34:29 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:29 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:29 Tower kernel: ata4.00: cmd 60/00:80:f0:60:09/01:00:00:02:00/40 tag 16 ncq dma 131072 in
Feb  2 15:34:29 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:29 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:29 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:29 Tower kernel: sd 4:0:0:0: [sdd] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:29 Tower kernel: sd 4:0:0:0: [sdd] tag#16 Sense Key : 0x3 [current] 
Feb  2 15:34:29 Tower kernel: sd 4:0:0:0: [sdd] tag#16 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:29 Tower kernel: sd 4:0:0:0: [sdd] tag#16 CDB: opcode=0x88 88 00 00 00 00 02 00 09 60 f0 00 00 01 00 00 00
Feb  2 15:34:29 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590549232 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:29 Tower kernel: ata4: EH complete
Feb  2 15:34:32 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x80000 SErr 0x0 action 0x0
Feb  2 15:34:32 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:32 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:32 Tower kernel: ata4.00: cmd 60/00:98:f0:61:09/01:00:00:02:00/40 tag 19 ncq dma 131072 in
Feb  2 15:34:32 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:32 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:32 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:32 Tower kernel: sd 4:0:0:0: [sdd] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:32 Tower kernel: sd 4:0:0:0: [sdd] tag#19 Sense Key : 0x3 [current] 
Feb  2 15:34:32 Tower kernel: sd 4:0:0:0: [sdd] tag#19 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:32 Tower kernel: sd 4:0:0:0: [sdd] tag#19 CDB: opcode=0x88 88 00 00 00 00 02 00 09 61 f0 00 00 01 00 00 00
Feb  2 15:34:32 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590549488 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:32 Tower kernel: ata4: EH complete
Feb  2 15:34:35 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x2000 SErr 0x0 action 0x0
Feb  2 15:34:35 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:35 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:35 Tower kernel: ata4.00: cmd 60/00:68:f0:62:09/01:00:00:02:00/40 tag 13 ncq dma 131072 in
Feb  2 15:34:35 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:35 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:35 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:35 Tower kernel: sd 4:0:0:0: [sdd] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:35 Tower kernel: sd 4:0:0:0: [sdd] tag#13 Sense Key : 0x3 [current] 
Feb  2 15:34:35 Tower kernel: sd 4:0:0:0: [sdd] tag#13 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:35 Tower kernel: sd 4:0:0:0: [sdd] tag#13 CDB: opcode=0x88 88 00 00 00 00 02 00 09 62 f0 00 00 01 00 00 00
Feb  2 15:34:35 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590549744 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:35 Tower kernel: ata4: EH complete
Feb  2 15:34:39 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x0
Feb  2 15:34:39 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:39 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:39 Tower kernel: ata4.00: cmd 60/00:80:f0:63:09/01:00:00:02:00/40 tag 16 ncq dma 131072 in
Feb  2 15:34:39 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:39 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:39 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:39 Tower kernel: sd 4:0:0:0: [sdd] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:39 Tower kernel: sd 4:0:0:0: [sdd] tag#16 Sense Key : 0x3 [current] 
Feb  2 15:34:39 Tower kernel: sd 4:0:0:0: [sdd] tag#16 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:39 Tower kernel: sd 4:0:0:0: [sdd] tag#16 CDB: opcode=0x88 88 00 00 00 00 02 00 09 63 f0 00 00 01 00 00 00
Feb  2 15:34:39 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590550000 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:39 Tower kernel: ata4: EH complete
Feb  2 15:34:42 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x80000 SErr 0x0 action 0x0
Feb  2 15:34:42 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:42 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:42 Tower kernel: ata4.00: cmd 60/00:98:f0:64:09/01:00:00:02:00/40 tag 19 ncq dma 131072 in
Feb  2 15:34:42 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:42 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:42 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:42 Tower kernel: sd 4:0:0:0: [sdd] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:42 Tower kernel: sd 4:0:0:0: [sdd] tag#19 Sense Key : 0x3 [current] 
Feb  2 15:34:42 Tower kernel: sd 4:0:0:0: [sdd] tag#19 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:42 Tower kernel: sd 4:0:0:0: [sdd] tag#19 CDB: opcode=0x88 88 00 00 00 00 02 00 09 64 f0 00 00 01 00 00 00
Feb  2 15:34:42 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590550256 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:42 Tower kernel: ata4: EH complete
Feb  2 15:34:45 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0
Feb  2 15:34:45 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:45 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:45 Tower kernel: ata4.00: cmd 60/00:b0:f0:65:09/01:00:00:02:00/40 tag 22 ncq dma 131072 in
Feb  2 15:34:45 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:45 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:45 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:45 Tower kernel: sd 4:0:0:0: [sdd] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:45 Tower kernel: sd 4:0:0:0: [sdd] tag#22 Sense Key : 0x3 [current] 
Feb  2 15:34:45 Tower kernel: sd 4:0:0:0: [sdd] tag#22 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:45 Tower kernel: sd 4:0:0:0: [sdd] tag#22 CDB: opcode=0x88 88 00 00 00 00 02 00 09 65 f0 00 00 01 00 00 00
Feb  2 15:34:45 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590550512 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:45 Tower kernel: ata4: EH complete
Feb  2 15:34:49 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0
Feb  2 15:34:49 Tower kernel: ata4.00: irq_stat 0x40000008
Feb  2 15:34:49 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED
Feb  2 15:34:49 Tower kernel: ata4.00: cmd 60/00:c8:f0:66:09/01:00:00:02:00/40 tag 25 ncq dma 131072 in
Feb  2 15:34:49 Tower kernel: ata4.00: status: { DRDY SENSE ERR }
Feb  2 15:34:49 Tower kernel: ata4.00: error: { UNC }
Feb  2 15:34:49 Tower kernel: ata4.00: configured for UDMA/133
Feb  2 15:34:49 Tower kernel: sd 4:0:0:0: [sdd] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Feb  2 15:34:49 Tower kernel: sd 4:0:0:0: [sdd] tag#25 Sense Key : 0x3 [current] 
Feb  2 15:34:49 Tower kernel: sd 4:0:0:0: [sdd] tag#25 ASC=0x11 ASCQ=0x4 
Feb  2 15:34:49 Tower kernel: sd 4:0:0:0: [sdd] tag#25 CDB: opcode=0x88 88 00 00 00 00 02 00 09 66 f0 00 00 01 00 00 00
Feb  2 15:34:49 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8590550768 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Feb  2 15:34:49 Tower kernel: ata4: EH complete
Feb  2 15:34:51 Tower wsdd2[4129]: 'Terminated' signal received.
Feb  2 15:34:51 Tower wsdd2[4129]: terminating.
Feb  2 15:34:53 Tower root:                  /usr/sbin/wsdd2 -d 
Feb  2 15:34:53 Tower wsdd2[5457]: starting.

** Press ANY KEY to close this window ** 

 

Fix Common Problems plugin also said | If the disk has not been disabled, then Unraid has successfully rewritten the contents of the offending sectors back to the hard drive.

 

I'm about to try skimming through a bunch of media files on Disk 5 to see if any more errors happen.

[Disk Errors - Disk Disabled - UDMA CRC Errors]

Turned off Server. Changed SATA cable.

 

When I tried to start the array, this time it took far longer than normal and got stuck on starting up Disk 5 (the disk with errors). It did eventually start the array but now it's pumping out errors.

 

tower-smart-20230202-1535.zip