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.

Does this make sense to anyone?

Featured Replies

I have a hard drive, and when added, it will time out during parity checks and causing random parity check errors. I tried it in another hotswap bay and it still times out. The only thing I can think of is that the drive is bad but it seems to do everything correctly other than parity check. It will even do a parity sync, but as soon as I try to verify that sync with a parity check.. it times out.

 

I just transfered 1.5TB of data off of it, verified the data with CRC checks, and found no errors and it didn't time out. I have to cold boot, disconnect the drive, and plug it back in to get it to redetect the drive. Even restarting doesn't redetect the drive after it times out.

 

1) Smart is FINE.

2) Power Supply is not the issue, I tried adding another drive of the same model.

3) Passes SMART long test.

4) Cables are not the issue, I tried 3 different power and sata cables, and 2 hotswap bays with 2 different SATA controllers.

 

Mar 14 11:50:42 Server kernel: ata15.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Mar 14 11:50:42 Server kernel: ata15.00: failed command: READ DMA EXT

Mar 14 11:50:42 Server kernel: ata15.00: cmd 25/00:78:97:d6:88/00:00:46:00:00/e0 tag 0 dma 61440 in

Mar 14 11:50:42 Server kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

Mar 14 11:50:42 Server kernel: ata15.00: status: { DRDY }

Mar 14 11:50:42 Server kernel: ata15: hard resetting link

Mar 14 11:50:48 Server kernel: ata15: link is slow to respond, please be patient (ready=0)

Mar 14 11:50:52 Server kernel: ata15: SRST failed (errno=-16)

Mar 14 11:50:52 Server kernel: ata15: hard resetting link

Mar 14 11:50:58 Server kernel: ata15: link is slow to respond, please be patient (ready=0)

Mar 14 11:51:02 Server kernel: ata15: SRST failed (errno=-16)

Mar 14 11:51:02 Server kernel: ata15: hard resetting link

Mar 14 11:51:08 Server kernel: ata15: link is slow to respond, please be patient (ready=0)

Mar 14 11:51:37 Server kernel: ata15: SRST failed (errno=-16)

Mar 14 11:51:37 Server kernel: ata15: limiting SATA link speed to 1.5 Gbps

Mar 14 11:51:37 Server kernel: ata15: hard resetting link

Mar 14 11:51:42 Server kernel: ata15: SRST failed (errno=-16)

Mar 14 11:51:42 Server kernel: ata15: reset failed, giving up

Mar 14 11:51:42 Server kernel: ata15.00: disabled

Mar 14 11:51:42 Server kernel: ata15.00: device reported invalid CHS sector 0

Mar 14 11:51:42 Server kernel: ata15: EH complete

Mar 14 11:51:42 Server kernel: sd 15:0:0:0: [sdh] Unhandled error code

Mar 14 11:51:42 Server kernel: sd 15:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00

Mar 14 11:51:42 Server kernel: sd 15:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 46 88 d6 97 00 00 78 00

Mar 14 11:51:42 Server kernel: end_request: I/O error, dev sdh, sector 1183372951

Mar 14 11:51:42 Server kernel: sd 15:0:0:0: [sdh] Unhandled error code

Mar 14 11:51:42 Server kernel: sd 15:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00

Mar 14 11:51:42 Server kernel: sd 15:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 46 88 d7 0f 00 03 90 00

Mar 14 11:51:42 Server kernel: end_request: I/O error, dev sdh, sector 1183373071

Mar 14 11:51:42 Server kernel: sd 15:0:0:0: [sdh] Unhandled error code

Mar 14 11:51:42 Server kernel: sd 15:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00

Mar 14 11:51:42 Server kernel: sd 15:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 46 88 da 9f 00 04 00 00

Mar 14 11:51:42 Server kernel: end_request: I/O error, dev sdh, sector 1183373983

Mar 14 11:51:42 Server kernel: sd 15:0:0:0: [sdh] Unhandled error code

What were the pre_clear results?

Any chance this was a Seagate 1.5TB 7200.11 drive? ie, The ata15: hard resetting link was something I was seeing as well.

Any chance this was a Seagate 1.5TB 7200.11 drive? ie, The ata15: hard resetting link was something I was seeing as well. I tried all of the stuff you suggested and even RMAed the drive at Lime Tech's suggestion but it was still happening with brand new drives.

 

  • Author

What were the pre_clear results?

 

There were no errors on it. I'm going to preclear it again and see if anything changes.

 

Any chance this was a Seagate 1.5TB 7200.11 drive? ie, The ata15: hard resetting link was something I was seeing as well.

 

1.5TB Western Digital Green (EADS)

 

I have 12 greens in my system, the other 11 are fine.

 

 

 

-------

 

I setup an RMA for the drive.. but i'm still puzzled because the drive seems fine, and i'd hate to send it in for a replacement just to have the new one do the same thing. I don't see any other possible hardware issues though, everything points to the drive.

I'm not sure they're related then, but I did RMA the drive(s) based on a recommendation from Lime Tech and I wound still seeing the same problems with new drives. I wound swapping ALL of them for WD20EARS because Tom suggested it was a Seagate firmware problem.

 

Like you, I'm still puzzled by it. I haven't seen the problems I was seeing before with the WD20EARS but I'm seeing bug crashes that is really annoying me now.

 

ETA: Maybe you email Lime Tech too...if they're related problems it tells me it isn't the drives that are at fault.

  • Author

I just tried to preclear the disc again and it failed almost instantly. Going to RMA it.

 

My logic is that the drive can handle reads and writes of around 50MB/s (transferring files off the disc, parity sync, etc). But preclearing (90MB/s) and parity check (80MB/s) is causing it to fail.

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.