Jump to content
We're Hiring! Full Stack Developer ×

First RED BALL [4.7 Pro]


graywolf

Recommended Posts

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

Link to comment

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.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...