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.

Still see these kinds of messages on the Lime Technology 1510 server

Featured Replies

Still see these kinds of messages on the Lime Technology 1510 server:

 

May 11 17:06:13 Serenity kernel: ata9.00: failed command: READ DMA EXT (Minor Issues)

May 11 17:06:13 Serenity kernel: ata9.00: cmd 25/00:08:7f:00:b8/00:00:a6:00:00/e0 tag 0 dma 4096 in (Drive related)

May 11 17:06:13 Serenity kernel: res 51/40:00:7f:00:b8/40:00:a6:00:00/e0 Emask 0x9 (media error) (Errors)

May 11 17:06:13 Serenity kernel: ata9.00: status: { DRDY ERR } (Drive related)

May 11 17:06:13 Serenity kernel: ata9.00: error: { UNC } (Errors)

May 11 17:06:13 Serenity kernel: ata9.00: configured for UDMA/133 (Drive related)

May 11 17:06:13 Serenity kernel: ata9: EH complete (Drive related)

 

Drives have been replaced, etc.

Still see these kinds of messages on the Lime Technology 1510 server:

 

May 11 17:06:13 Serenity kernel: ata9.00: failed command: READ DMA EXT (Minor Issues)

May 11 17:06:13 Serenity kernel: ata9.00: cmd 25/00:08:7f:00:b8/00:00:a6:00:00/e0 tag 0 dma 4096 in (Drive related)

May 11 17:06:13 Serenity kernel: res 51/40:00:7f:00:b8/40:00:a6:00:00/e0 Emask 0x9 (media error) (Errors)

May 11 17:06:13 Serenity kernel: ata9.00: status: { DRDY ERR } (Drive related)

May 11 17:06:13 Serenity kernel: ata9.00: error: { UNC } (Errors)

May 11 17:06:13 Serenity kernel: ata9.00: configured for UDMA/133 (Drive related)

May 11 17:06:13 Serenity kernel: ata9: EH complete (Drive related)

 

Drives have been replaced, etc.

UNC (un-correctable media errors) are always un-readable sectors on disks.   
  • Author

Still see these kinds of messages on the Lime Technology 1510 server:

 

May 11 17:06:13 Serenity kernel: ata9.00: failed command: READ DMA EXT (Minor Issues)

May 11 17:06:13 Serenity kernel: ata9.00: cmd 25/00:08:7f:00:b8/00:00:a6:00:00/e0 tag 0 dma 4096 in (Drive related)

May 11 17:06:13 Serenity kernel: res 51/40:00:7f:00:b8/40:00:a6:00:00/e0 Emask 0x9 (media error) (Errors)

May 11 17:06:13 Serenity kernel: ata9.00: status: { DRDY ERR } (Drive related)

May 11 17:06:13 Serenity kernel: ata9.00: error: { UNC } (Errors)

May 11 17:06:13 Serenity kernel: ata9.00: configured for UDMA/133 (Drive related)

May 11 17:06:13 Serenity kernel: ata9: EH complete (Drive related)

 

Drives have been replaced, etc.

UNC (un-correctable media errors) are always un-readable sectors on disks. 

 

The replaced drives are bad as well? Replace them again or do something else?

Still see these kinds of messages on the Lime Technology 1510 server:

 

May 11 17:06:13 Serenity kernel: ata9.00: failed command: READ DMA EXT (Minor Issues)

May 11 17:06:13 Serenity kernel: ata9.00: cmd 25/00:08:7f:00:b8/00:00:a6:00:00/e0 tag 0 dma 4096 in (Drive related)

May 11 17:06:13 Serenity kernel: res 51/40:00:7f:00:b8/40:00:a6:00:00/e0 Emask 0x9 (media error) (Errors)

May 11 17:06:13 Serenity kernel: ata9.00: status: { DRDY ERR } (Drive related)

May 11 17:06:13 Serenity kernel: ata9.00: error: { UNC } (Errors)

May 11 17:06:13 Serenity kernel: ata9.00: configured for UDMA/133 (Drive related)

May 11 17:06:13 Serenity kernel: ata9: EH complete (Drive related)

 

Drives have been replaced, etc.

UNC (un-correctable media errors) are always un-readable sectors on disks. 

 

The replaced drives are bad as well? Replace them again or do something else?

 

You have my sympathies.  It does look like this replacement drive has a bad sector too, but that does not mean it is a bad drive.  Normal troubleshooting procedures apply (SMART reports and tests, etc).  However this does not look like an RC issue, just a normal support problem, bad as that is.

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.