July 10, 201114 yr Using XBMC I suddenly started getting file not found errors. So I went and checked the server, and the files really were gone. After checking with unmenu it said I had a "DISK_DSBL" error and was giving all kinds of errors and warnings in the logs. The only thing I can think of is the drive died on me with no warning? We did have a 3 second power failure 4 days ago. I'm not sure how to check smart as every time I go the the smart menu it says "Sorry: cannot run smarthistory. The /boot/smarthistory directory does not exist." So my question is, is it really a dead drive? if so will replacing the drive fix the problem, without losing data? Also if the drive died on me why would the array not shut itself down? My Specs are: Unraid 4.7 M4A89GTD Pro/USB3 8 Gigs 1333 Athlon II X4 600e Processor Intel Gigabyte CT Desktop Adapter (PCIe x1) Supermicro AOC-SASLP-M 11 Hard Drives, 2TB parity Edit: I figured out how to check the SMART status of the drive. Basically SMART says all my drives are fine, but the one that is disabled SMART will not even see. So I suppose the drive really is a goner. Can anyone look at my log and give me some advice? syslog-2011-07-10.zip
July 10, 201114 yr Using XBMC I suddenly started getting file not found errors. So I went and checked the server, and the files really were gone. After checking with unmenu it said I had a "DISK_DSBL" error and was giving all kinds of errors and warnings in the logs. The only thing I can think of is the drive died on me with no warning? We did have a 3 second power failure 4 days ago. I'm not sure how to check smart as every time I go the the smart menu it says "Sorry: cannot run smarthistory. The /boot/smarthistory directory does not exist." So my question is, is it really a dead drive? if so will replacing the drive fix the problem, without losing data? Also if the drive died on me why would the array not shut itself down? My Specs are: Unraid 4.7 M4A89GTD Pro/USB3 8 Gigs 1333 Athlon II X4 600e Processor Intel Gigabyte CT Desktop Adapter (PCIe x1) Supermicro AOC-SASLP-M 11 Hard Drives, 2TB parity Edit: I figured out how to check the SMART status of the drive. Basically SMART says all my drives are fine, but the one that is disabled SMART will not even see. So I suppose the drive really is a goner. Can anyone look at my log and give me some advice? 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. Joe L.
August 16, 201114 yr I've just had the exact same thing happen to me on Beta 5.07 (Red Ball appeared on Disk3) from unmenu: DISK_DSBL /dev/md3 /mnt/disk3 /dev/hdd 00S2B0_WD-WCAVY1999822 I'm running a short smart test on the drive now via unmenu. Is the procedure exactly the same as above to correct for Beta 5.07 as 4.7? Many thanks, Thomas.
August 29, 201312 yr I had this happen recently as well. The steps above fixed the issue; however, I'm not sure why it happened in the first place. Anyone have ideas / suggestions?
Archived
This topic is now archived and is closed to further replies.