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.

First RED BALL [4.7 Pro]

Featured Replies

unRAID 4.7 Pro, syslog attached. Looks like it started approx 19:51 last night (Sep 8).

 

Going to start reading the WIKI but would appreciate guidance also.

Don't want to mess this up and end up in the dog house  ::)

syslog1.zip

  • Author

tried smartctl on /dev/sdd but got nothing, guess it couldn't see the drive

power down server.

checked cables

powered up server

unRAID menu still shows red ball

unMenu says DISK_DSBL

ran smarctl on /dev/sdd and got the attached.

also attached is the current syslog. not seeing the errors but not sure why still red ball

 

Noticed the 2 Current_Pending_Sector. Best course of action for this?

 

Does everything else look good?

What else should I do prior to "re-enabling the drive"?

 

Are the following the proper next steps? Or should I do other stuff prior/instead?

 

You can re-enable the hard drive and reconstruct it as follows:

 

    * Stop the array, go to the Devices page and un-assign the disk.

    * Reboot (use the button on the Main page)

    * Stop the array, go to the Devices page and re-assign the disk

    * Go to the Main page - system should detect a "new" drive for the disabled one, click Start to start a parity-reconstruct of the disk.

 

 

smartctl-sdd.txt

syslog.txt

The red ball is because a write to the drive failed...which may have been attributed to sata/power connection. The smart report looks good (2) pending sectors <do you know if these are new?>

http://lime-technology.com/wiki/index.php?title=Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F

 

Stop the array, go to the Devices page and un-assign the disk.

Reboot (use the button on the Main page)

Stop the array, go to the Devices page and re-assign the disk

Go to the Main page - system should detect a "new" drive for the disabled one, click Start to start a parity-reconstruct of the disk.

No reboot is necessary. Just Stop, unassign, start, stop, assing, start.

 

Peter

  • Author

ok...

stopped arrary

unassigned disk

started array

stopped array

reassigned disk

started array (checkbox are you sure)

 

data rebuild in progress

 

checked a smartctl report (attached) I had on the drive from 2011-09-04 and it had 0 Current_Pending_Sector

smartctl-sdd-20110904.txt

keep an eye on the drive...plenty of sectors available to reallocate. Watch the "pending" and "reallocated" sector count.

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.