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] Second DISK_DSBL in a week on the same disk

Featured Replies

So I want to send it back as RMA since it's less than a year old, but I wonder if I'm doing something wrong.

 

The first time it went DISK_DSBL was after a proper powerdown, and a few hours of being shut down. Booted up to a red dot. I followed steps found in other DISK_DSBL threads:

 

stop the array
power down
re-seat the connectors to the disabled drive
power up
see if you can get a smart report now
If yes, good.
if no, RMA the drive (or try a different cable/disk controller  port)
if smart report is possible
stop the arraya
un-assign the drive
start the srray with it un-assigned
stop the array
re-assign the drive that was disabled
start the array once more.  This time it will re-construct the drive onto itself.  It was disabled when a "write" to it failed.  The re-construction onto itself should get it back to where it should be.

 

Odd thing was it took two reboots for the rebuild to begin. Both times, the box was there to confirm that I wanted to continue with the process, and when I clicked begin, the page refreshed and nothing happened. Retry, retry, and finally it started. 36 hours later, I'm good. All data is accessible, etc.

 

Today, I'm rebooting again (against my own minor reservations) to see if I can prevent spinup when opening a folder with cache_dirs installed. When it comes back online, the disk is red again.

 

smartctl -t short -d ata /dev/sdg: Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)

 

Before I rebuild a second time or wait for a replacement disk and rebuild then, I want to find out if I'm the problem here. Thanks.

 

Server:

 

OS 4.7

WD 2TB EARS connected to a SUPERMICRO AOC-SASLP-MV8.

syslog-2012-03-27.zip

  • Author

Post a SMART report.

 

Couldn't pull one:

 

smartctl -t short -d ata /dev/sdg: Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)

Power cycle the system. If there is still no SMART report then RMA then drive.

  • Author

Thanks. I'll try that!

  • Author

Yeah, no luck. The disk is now removed.

 

What's going to occur if I power up with that disk no longer in the case? I'd like to have access to the data on the other disks if possible.

Yeah, no luck. The disk is now removed.

 

What's going to occur if I power up with that disk no longer in the case? I'd like to have access to the data on the other disks if possible.

As long as you have a parity disk, you'll have access to all the data on all the disks, including the removed one.

 

the removed disk will be simulated by accessing and re-constructing its contents from all the other remaining disks.

  • Author

Thanks, Joe.

If a second disk fails you will lose data. It's safest to keep the server off until the replacement is ready.

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.