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) Moved my server into a new case, hdd showing up as missing, but appears in Unassigned devices

Featured Replies

Hey all,

Just moved my very basic setup into a new case, it is just a single cache drive and a single drive in the pool (no parity). The cache drive is showing up fine for for some reason it says my disk 1 is missing but if i scroll down to the bottom I see it under unassigned devices (and the drive ID does match as you would expect). (I did try a different SATA cable and port too FYI)

Any ideas?

edit: here is some of the info from the log

 

May 27 14:41:22 Unraid2 kernel: ata1: SATA max UDMA/133 abar m2048@0xa2502000 port 0xa2502100 irq 135
May 27 14:41:22 Unraid2 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to read native max address (err_mask=0x1)
May 27 14:41:22 Unraid2 kernel: ata1.00: HPA support seems broken, skipping HPA handling
May 27 14:41:22 Unraid2 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 27 14:41:22 Unraid2 kernel: ata1.00: supports DRM functions and may not be fully accessible
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable AA (error_mask=0x1)
May 27 14:41:22 Unraid2 kernel: ata1.00: READ LOG DMA EXT failed, trying PIO
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: ATA-9: WDC WD140EDFZ-11A0VA0, 9MG7WE0J, 81.00A81, max UDMA/133
May 27 14:41:22 Unraid2 kernel: ata1.00: 27344764928 sectors, multi 0: LBA48 NCQ (depth 32)
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable Sense Data Reporting, Emask 0x1
May 27 14:41:22 Unraid2 kernel: ata1.00: ATA Identify Device Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: Security Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: supports DRM functions and may not be fully accessible
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable AA (error_mask=0x1)
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable Sense Data Reporting, Emask 0x1
May 27 14:41:22 Unraid2 kernel: ata1.00: ATA Identify Device Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: Security Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: configured for UDMA/133 (device error ignored)
May 27 14:41:22 Unraid2 kernel: sd 1:0:0:0: [sdb] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
May 27 14:41:22 Unraid2 kernel: sd 1:0:0:0: [sdb] Write Protect is off
May 27 14:41:22 Unraid2 kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
May 27 14:41:22 Unraid2 kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 27 14:41:22 Unraid2 kernel: ata1: failed to read log page 10h (errno=-5)
May 27 14:41:22 Unraid2 kernel: ata1.00: exception Emask 0x1 SAct 0x10 SErr 0x0 action 0x0
May 27 14:41:22 Unraid2 kernel: ata1.00: irq_stat 0x40000001
May 27 14:41:22 Unraid2 kernel: ata1.00: failed command: READ FPDMA QUEUED
May 27 14:41:22 Unraid2 kernel: ata1.00: cmd 60/08:20:00:00:00/00:00:00:00:00/40 tag 4 ncq dma 4096 in
May 27 14:41:22 Unraid2 kernel: ata1.00: status: { DRDY ERR }
May 27 14:41:22 Unraid2 kernel: ata1.00: error: { ABRT }
May 27 14:41:22 Unraid2 kernel: ata1.00: both IDENTIFYs aborted, assuming NODEV
May 27 14:41:22 Unraid2 kernel: ata1.00: revalidation failed (errno=-2)
May 27 14:41:22 Unraid2 kernel: ata1: hard resetting link
May 27 14:41:22 Unraid2 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 27 14:41:22 Unraid2 kernel: ata1.00: supports DRM functions and may not be fully accessible
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable AA (error_mask=0x1)
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable Sense Data Reporting, Emask 0x1
May 27 14:41:22 Unraid2 kernel: ata1.00: ATA Identify Device Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: Security Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: supports DRM functions and may not be fully accessible
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable AA (error_mask=0x1)
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable Sense Data Reporting, Emask 0x1
May 27 14:41:22 Unraid2 kernel: ata1.00: ATA Identify Device Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: Security Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: configured for UDMA/133 (device error ignored)
May 27 14:41:22 Unraid2 kernel: ata1: EH complete
May 27 14:41:22 Unraid2 kernel: ata1: failed to read log page 10h (errno=-5)
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ disabled due to excessive errors
May 27 14:41:22 Unraid2 kernel: ata1.00: exception Emask 0x1 SAct 0x20 SErr 0x0 action 0x0
May 27 14:41:22 Unraid2 kernel: ata1.00: irq_stat 0x40000001
May 27 14:41:22 Unraid2 kernel: ata1.00: failed command: READ FPDMA QUEUED
May 27 14:41:22 Unraid2 kernel: ata1.00: cmd 60/08:28:00:00:00/00:00:00:00:00/40 tag 5 ncq dma 4096 in
May 27 14:41:22 Unraid2 kernel: ata1.00: status: { DRDY ERR }
May 27 14:41:22 Unraid2 kernel: ata1.00: error: { ABRT }
May 27 14:41:22 Unraid2 kernel: ata1.00: both IDENTIFYs aborted, assuming NODEV
May 27 14:41:22 Unraid2 kernel: ata1.00: revalidation failed (errno=-2)
May 27 14:41:22 Unraid2 kernel: ata1: hard resetting link
May 27 14:41:22 Unraid2 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 27 14:41:22 Unraid2 kernel: ata1.00: supports DRM functions and may not be fully accessible
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable AA (error_mask=0x1)
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable Sense Data Reporting, Emask 0x1
May 27 14:41:22 Unraid2 kernel: ata1.00: ATA Identify Device Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: Security Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: supports DRM functions and may not be fully accessible
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable AA (error_mask=0x1)
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: NCQ Send/Recv Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: failed to enable Sense Data Reporting, Emask 0x1
May 27 14:41:22 Unraid2 kernel: ata1.00: ATA Identify Device Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: Security Log not supported
May 27 14:41:22 Unraid2 kernel: ata1.00: configured for UDMA/133 (device error ignored)
May 27 14:41:22 Unraid2 kernel: ata1: EH complete
May 27 14:41:22 Unraid2 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 27 14:41:22 Unraid2 kernel: ata1.00: irq_stat 0x40000001

Edited by Blindsay

  • Author

Figured it out.

Forgot in my old case the drives were in a hot swap bay that was built into the case which did NOT supply 3.3V which my new setup did have. Took the 3.3V cable out and everything is back to normal

  • Blindsay changed the title to (Solved) Moved my server into a new case, hdd showing up as missing, but appears in Unassigned devices

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.