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.

Diagnosing drive failure

Featured Replies

Problem: One of my system hard drives will not mount, and I see "no device" under its device slot. 

 

Question: What command(s) should I run to identify whether this is a minor issue that can be fixed with a resierfsck or its a complete drive failure?

 

Symptoms:

  • On boot, the server makes a series of short beeps 10 or so times over 30 seconds
  • The drive in question is /dev/sdc and is older (so reiserfs I think, but not sure)
  • In syslog I see a series of repeated messages similar to this:
May 16 09:36:17 Tower kernel: ata2.00: status: { DRDY ERR }
May 16 09:36:17 Tower kernel: ata2.00: error: { ABRT }
May 16 09:36:17 Tower kernel: ata2.00: configured for UDMA/133 (device error ignored)
May 16 09:36:17 Tower kernel: ata2: EH complete
May 16 09:36:17 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 16 09:36:17 Tower kernel: ata2.00: irq_stat 0x40000001
May 16 09:36:17 Tower kernel: ata2.00: failed command: READ DMA
May 16 09:36:17 Tower kernel: ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 30 dma 4096 in
May 16 09:36:17 Tower kernel:         res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
  • blkid output:
# blkid
/dev/sda1: LABEL="UNRAID" UUID="BF62-0F17" TYPE="vfat"
/dev/sdb1: UUID="e13ec16e-c13c-421e-adef-fc05dbd418e2" TYPE="xfs"
/dev/sdd1: UUID="d60236ff-eefd-417f-808f-aedd587f2ff1" TYPE="reiserfs"
/dev/sde1: UUID="7383a197-8092-422c-9b28-745ad67a7b44" UUID_SUB="8861b6e3-06f7-4be1-ad09-a1b1a64300a5" TYPE="btrfs"
/dev/sdf1: UUID="e13ec16e-c13c-421e-adef-fc05dbd418e2" TYPE="xfs"
  • Device inventory from syslog
May 16 09:38:06 Tower emhttp: Device inventory:
May 16 09:38:06 Tower emhttp: shcmd (11): udevadm settle
May 16 09:38:06 Tower emhttp: WDC_WD20EFRX-68EUZN0_WD-WCC4M6LFZU1H (sdb) 1953514584
May 16 09:38:06 Tower emhttp: ST_M13FQBL_QNR_BFW (sdc) 4044975
May 16 09:38:06 Tower emhttp: TOSHIBA_DT01ACA200_Z2UB15RGS (sdd) 1953514584
May 16 09:38:06 Tower emhttp: WDC_WD20EFRX-68EUZN0_WD-WCC4M0FSKEHZ (sde) 1953514584
May 16 09:38:06 Tower emhttp: WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3JJX5NS (sdf) 1953514584
May 16 09:38:06 Tower emhttp: array slots: 24
May 16 09:38:06 Tower emhttp: cache slots: 1

 

Edited by PleaseWork

  • Community Expert

Try using a different SATA port and cable, if still not detected post your diagnostics.

  • Author
Quote

post your diagnostics.

What command will dump the diagnostic logs you're looking for?

  • Community Expert

Tools -> Diagnostics

  • Community Expert

Syslog just show same error repeating, can't see the beginning of the problem, powerdown, connect that disk to different SATA port and replace/swap cables, power back up, start the array and grab and post new diags.

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.