Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[solved]disk errors

Featured Replies

Hi everyone, I have a problem and am unsure where to start, about a week ago while I was watching a movie it started buffering a lot, I thought it might just be network traffic. Then when I tried writing to the disk it started writing then the disk would become unavailable.

 

When I check the drive it showed a ton of errors. I ran a smart report and it came back as passed, So I removed all the cables and reseated everything thinking it was a cabling issue. the errors still persisted but I had an extra drive, ran the preclear on it with no problem, then added the new disk to the array. Everything seemed fine for a few days and then last night I started getting errors again and am not sure where to start. I have attached a syslog in hopes that someone can help me as to where to start.

 

Thanks

Treefour

syslog-2013-11-24.zip

Hi everyone, I have a problem and am unsure where to start, about a week ago while I was watching a movie it started buffering a lot, I thought it might just be network traffic. Then when I tried writing to the disk it started writing then the disk would become unavailable.

 

When I check the drive it showed a ton of errors. I ran a smart report and it came back as passed, So I removed all the cables and reseated everything thinking it was a cabling issue. the errors still persisted but I had an extra drive, ran the preclear on it with no problem, then added the new disk to the array. Everything seemed fine for a few days and then last night I started getting errors again and am not sure where to start. I have attached a syslog in hopes that someone can help me as to where to start.

 

Thanks

Treefour

Disk 2 has a number of media errors in the syslog. 

(it is NOT a cabling issue, it is a disk with un-readable sectors)

 

Please post the SMART report from it by typing

smartctl -a /dev/sdd

Nov 23 19:34:49 Tower kernel: md: import disk2: [8,48] (sdd) WDC_WD10EADS-00L5B1_WD-WCAU45776019 size: 976762552

 

Nov 23 21:27:58 Tower kernel: end_request: I/O error, dev sdd, sector 214697520

Nov 23 21:27:58 Tower kernel: ata4: EH complete

Nov 23 21:27:58 Tower kernel: md: disk2 read error, sector=214697456

Nov 23 21:28:02 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 23 21:28:02 Tower kernel: ata4.00: BMDMA stat 0x64

Nov 23 21:28:02 Tower kernel: ata4.00: failed command: READ DMA

Nov 23 21:28:02 Tower kernel: ata4.00: cmd c8/00:08:80:cc:2b/00:00:00:00:00/ec tag 0 dma 4096 in

Nov 23 21:28:02 Tower kernel:          res 51/40:00:80:cc:2b/00:00:00:00:00/ec Emask 0x9 (media error)

Nov 23 21:28:02 Tower kernel: ata4.00: status: { DRDY ERR }

Nov 23 21:28:02 Tower kernel: ata4.00: error: { UNC }

Nov 23 21:28:02 Tower kernel: ata4.00: configured for UDMA/133

Nov 23 21:28:02 Tower kernel: ata4.01: configured for UDMA/133

Nov 23 21:28:02 Tower kernel: sd 4:0:0:0: [sdd] Unhandled sense code

Nov 23 21:28:02 Tower kernel: sd 4:0:0:0: [sdd] 

Nov 23 21:28:02 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08

Nov 23 21:28:02 Tower kernel: sd 4:0:0:0: [sdd] 

Nov 23 21:28:02 Tower kernel: Sense Key : 0x3 [current] [descriptor]

Nov 23 21:28:02 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Nov 23 21:28:02 Tower kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 23 21:28:02 Tower kernel:        0c 2b cc 80

Nov 23 21:28:02 Tower kernel: sd 4:0:0:0: [sdd] 

Nov 23 21:28:02 Tower kernel: ASC=0x11 ASCQ=0x4

Nov 23 21:28:02 Tower kernel: sd 4:0:0:0: [sdd] CDB:

Nov 23 21:28:02 Tower kernel: cdb[0]=0x28: 28 00 0c 2b cc 80 00 00 08 00

Nov 23 21:28:02 Tower kernel: end_request: I/O error, dev sdd, sector 204196992

Nov 23 21:28:02 Tower kernel: ata4: EH complete

Nov 23 21:28:02 Tower kernel: md: disk2 read error, sector=204196928

Nov 23 21:28:05 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 23 21:28:05 Tower kernel: ata4.00: BMDMA stat 0x64

Nov 23 21:28:05 Tower kernel: ata4.00: failed command: READ DMA

Nov 23 21:28:05 Tower kernel: ata4.00: cmd c8/00:08:20:cc:2b/00:00:00:00:00/ec tag 0 dma 4096 in

Nov 23 21:28:05 Tower kernel:          res 51/40:00:20:cc:2b/00:00:00:00:00/ec Emask 0x9 (media error)

Nov 23 21:28:05 Tower kernel: ata4.00: status: { DRDY ERR }

Nov 23 21:28:05 Tower kernel: ata4.00: error: { UNC }

Nov 23 21:28:05 Tower kernel: ata4.00: configured for UDMA/133

Nov 23 21:28:05 Tower kernel: ata4.01: configured for UDMA/133

Nov 23 21:28:05 Tower kernel: sd 4:0:0:0: [sdd] Unhandled sense code

Nov 23 21:28:05 Tower kernel: sd 4:0:0:0: [sdd] 

Nov 23 21:28:05 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08

Nov 23 21:28:05 Tower kernel: sd 4:0:0:0: [sdd] 

Nov 23 21:28:05 Tower kernel: Sense Key : 0x3 [current] [descriptor]

Nov 23 21:28:05 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Nov 23 21:28:05 Tower kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 23 21:28:05 Tower kernel:        0c 2b cc 20

Nov 23 21:28:05 Tower kernel: sd 4:0:0:0: [sdd] 

Nov 23 21:28:05 Tower kernel: ASC=0x11 ASCQ=0x4

Nov 23 21:28:05 Tower kernel: sd 4:0:0:0: [sdd] CDB:

Nov 23 21:28:05 Tower kernel: cdb[0]=0x28: 28 00 0c 2b cc 20 00 00 08 00

Nov 23 21:28:05 Tower kernel: end_request: I/O error, dev sdd, sector 204196896

Nov 23 21:28:05 Tower kernel: ata4: EH complete

Nov 23 21:28:05 Tower kernel: md: disk2 read error, sector=204196832

Nov 23 21:28:08 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 23 21:28:08 Tower kernel: ata4.00: BMDMA stat 0x64

Nov 23 21:28:08 Tower kernel: ata4.00: failed command: READ DMA

Nov 23 21:28:08 Tower kernel: ata4.00: cmd c8/00:08:c0:b4:59/00:00:00:00:00/ec tag 0 dma 4096 in

Nov 23 21:28:08 Tower kernel:          res 51/40:00:c0:b4:59/00:00:00:00:00/ec Emask 0x9 (media error)

Nov 23 21:28:08 Tower kernel: ata4.00: status: { DRDY ERR }

Nov 23 21:28:08 Tower kernel: ata4.00: error: { UNC }

Nov 23 21:28:08 Tower kernel: ata4.00: configured for UDMA/133

Nov 23 21:28:08 Tower kernel: ata4.01: configured for UDMA/133

Nov 23 21:28:08 Tower kernel: sd 4:0:0:0: [sdd] Unhandled sense code

Nov 23 21:28:08 Tower kernel: sd 4:0:0:0: [sdd] 

Nov 23 21:28:08 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08

Nov 23 21:28:08 Tower kernel: sd 4:0:0:0: [sdd] 

Nov 23 21:28:08 Tower kernel: Sense Key : 0x3 [current] [descriptor]

Nov 23 21:28:08 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Nov 23 21:28:08 Tower kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 23 21:28:08 Tower kernel:        0c 59 b4 c0

Nov 23 21:28:08 Tower kernel: sd 4:0:0:0: [sdd] 

Nov 23 21:28:08 Tower kernel: ASC=0x11 ASCQ=0x4

Nov 23 21:28:08 Tower kernel: sd 4:0:0:0: [sdd] CDB:

Nov 23 21:28:08 Tower kernel: cdb[0]=0x28: 28 00 0c 59 b4 c0 00 00 08 00

Nov 23 21:28:08 Tower kernel: end_request: I/O error, dev sdd, sector 207205568

Nov 23 21:28:08 Tower kernel: ata4: EH complete

Nov 23 21:28:08 Tower kernel: md: disk2 read error, sector=207205504

 

 

Current_Pending_Sector  0x0032  192  192  000    Old_age  Always      -    1464

 

You have 1464 unreadable sectors that are pending re-allocation (the next time they are written)

 

replace the disk ASAP.   

 

Joe L.

  • Author

Thanks Joe, that's weird I guess both of them were failing at the same time. Thanks for the help will get a new one ordered up today. Thanks a lot for the help.

 

Treefour

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.