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.

DISK_DSBL in v5.0.5 - please help

Featured Replies

Hi guys,

 

I got one disk with DISK_DSBL status.. I can access the disks fine, SMART status is fine also. I tried to reboot the server and this disk is again to DISK_DSBL status. Any ideas as to what I might do? Any help is highly appreciated.

 

The icon in front of the disk in unRaid-Main is red instead of the usual green.

 

The disk in question is a Seagate ST3000DM001-9YN166, 3TB.

Attached the SMART report:

 

 

# smartctl -A -t short -d ata /dev/sdi

smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen

Home page is http://smartmontools.sourceforge.net/

 

=== START OF READ SMART DATA SECTION ===

SMART Attributes Data Structure revision number: 10

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate    0x000f  110  099  006    Pre-fail  Always      -      27410217

  3 Spin_Up_Time            0x0003  092  092  000    Pre-fail  Always      -      0

  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      58

  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x000f  081  060  030    Pre-fail  Always      -      4434600671

  9 Power_On_Hours          0x0032  076  076  000    Old_age  Always      -      21669

10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      21

183 Unknown_Attribute      0x0032  100  100  000    Old_age  Always      -      0

184 Unknown_Attribute      0x0032  100  100  099    Old_age  Always      -      0

187 Reported_Uncorrect      0x0032  094  094  000    Old_age  Always      -      6

188 Unknown_Attribute      0x0032  100  085  000    Old_age  Always      -      154621181989

189 High_Fly_Writes        0x003a  094  094  000    Old_age  Always      -      6

190 Airflow_Temperature_Cel 0x0022  070  052  045    Old_age  Always      -      30 (Lifetime Min/Max 21/36)

191 G-Sense_Error_Rate      0x0032  100  100  000    Old_age  Always      -      0

192 Power-Off_Retract_Count 0x0032  100  100  000    Old_age  Always      -      7

193 Load_Cycle_Count        0x0032  001  001  000    Old_age  Always      -      305055

194 Temperature_Celsius    0x0022  030  048  000    Old_age  Always      -      30 (0 20 0 0)

197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0

198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      5

240 Head_Flying_Hours      0x0000  100  253  000    Old_age  Offline      -      34522947137611

241 Unknown_Attribute      0x0000  100  253  000    Old_age  Offline      -      232084347696300

242 Unknown_Attribute      0x0000  100  253  000    Old_age  Offline      -      184453617049243

 

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===

Sending command: "Execute SMART Short self-test routine immediately in off-line mode".

Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.

 

You need to wait at least 2 minutes for the smart test to finish after telling it to start the test. It should be finished by now so see what the results are by issuing: smartctl -A /dev/sdi

 

There should be a line in a table at the end of the report indicating the test ran and what the results were.

 

The reason the drive is red balled is that a write to the device failed. That is the only way the drive will be marked as disabled.

 

  • Author

Below the SMART output after the test being complete.

Reallocated_Sector_Ct and Current_Pending_Sector are both 0.

 

In the SMART history of unMenu however, I see for this drive:

ATA_Error_Count is 1

 

In unRAID-Main there is no temp reading for this drive.

 

How should I proceed? Should I re-enable the drive again and how? 

Or should I swap it against a new drive?

 

 

 

# smartctl -A /dev/sdi

smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen

Home page is http://smartmontools.sourceforge.net/

 

=== START OF READ SMART DATA SECTION ===

SMART Attributes Data Structure revision number: 10

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate    0x000f  110  099  006    Pre-fail  Always      -      27410217

  3 Spin_Up_Time            0x0003  092  092  000    Pre-fail  Always      -      0

  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      58

  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x000f  081  060  030    Pre-fail  Always      -      4434600866

  9 Power_On_Hours          0x0032  076  076  000    Old_age  Always      -      21670

10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      21

183 Unknown_Attribute      0x0032  100  100  000    Old_age  Always      -      0

184 Unknown_Attribute      0x0032  100  100  099    Old_age  Always      -      0

187 Reported_Uncorrect      0x0032  094  094  000    Old_age  Always      -      6

188 Unknown_Attribute      0x0032  100  085  000    Old_age  Always      -      154621181989

189 High_Fly_Writes        0x003a  094  094  000    Old_age  Always      -      6

190 Airflow_Temperature_Cel 0x0022  069  052  045    Old_age  Always      -      31 (Lifetime Min/Max 21/36)

191 G-Sense_Error_Rate      0x0032  100  100  000    Old_age  Always      -      0

192 Power-Off_Retract_Count 0x0032  100  100  000    Old_age  Always      -      7

193 Load_Cycle_Count        0x0032  001  001  000    Old_age  Always      -      305074

194 Temperature_Celsius    0x0022  031  048  000    Old_age  Always      -      31 (0 20 0 0)

197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0

198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      5

240 Head_Flying_Hours      0x0000  100  253  000    Old_age  Offline      -      243752278962252

241 Unknown_Attribute      0x0000  100  253  000    Old_age  Offline      -      232084347696300

242 Unknown_Attribute      0x0000  100  253  000    Old_age  Offline      -      184453617049243

  • Author

Thanks for the link. SMART didn't show anything suspicious and also cabling & co is fine (server is stable in a 19" rack), I however decided to replace the red balled disk, just to be sure 100%. Will check and pre clear it extensively after data rebuild has finished. Thanks again!

starcat, have you discovered what went wrong with your drive? I have also an issue with this Seagate drive:

  • it was showing 88 errors yesterday (in the webGUI), hence got disabled
  • i saw that there is a firmware update available but the process ended with a "FAILURE" message
  • i have attached the drive to my test&backup server and these were the error messages that I received:

preclear_disk.sh -A /dev/sdg
BLKRRPART: Input/output error
Sorry: Device /dev/sdg is not responding to an fdisk -l /dev/sdg command.
You might try power-cycling it to see if it will start responding.

smartctl -a -A /dev/sdg
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.16.2-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-1CH166
Serial Number:    Z1F0XQYH
LU WWN Device Id: 5 000c50 04dff3930
Firmware Version: CC43
User Capacity:    137,438,952,960 bytes [137 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s
Local Time is:    Thu Sep 18 10:24:58 2014 CEST

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/223651en

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Data failed: scsi error aborted command

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.
Read SMART Log Directory failed: scsi error aborted command
Read SMART Error Log failed: scsi error aborted command
Read SMART Self-test Log failed: scsi error aborted command
Selective Self-tests/Logging not supported

smartctl -t short /dev/sdg
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.16.2-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

Read SMART Data failed: scsi error aborted command

 

...and a ton of syslog messages:

Sep 18 10:22:09 Tower2 kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 18 10:22:09 Tower2 kernel: ata8.00: irq_stat 0x40000001
Sep 18 10:22:09 Tower2 kernel: ata8.00: failed command: READ DMA
Sep 18 10:22:09 Tower2 kernel: ata8.00: cmd c8/00:02:00:00:00/00:00:00:00:00/e0 tag 11 dma 1024 in
Sep 18 10:22:09 Tower2 kernel: res 51/04:02:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
Sep 18 10:22:09 Tower2 kernel: ata8.00: status: { DRDY ERR }
Sep 18 10:22:09 Tower2 kernel: ata8.00: error: { ABRT }
Sep 18 10:22:09 Tower2 kernel: ata8.00: configured for UDMA/133
Sep 18 10:22:09 Tower2 kernel: ata8: EH complete

 

A question to the experts: I do believe that this drive is just broken? Thanks a lot.

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.