October 4, 20169 yr Running 6.2 So, a few days ago I got a read error notification via Push Bullet on my Parity 2 drive. Several hours later, I got a read error notification on another of my new drives. Recently I added three 3TB drives to the array, and I pre cleared them, with 3 runs, and there were no issues. I stopped the array, and upon doing so, unRaid showed "no device" in the spot where it was supposed to be. So, I restarted and one of them appeared, one of them did not. At this point, I shut down, checked all of the cables to make sure they were all securely connected, and it appeared that they were. I rebooted and both drives showed up. Neither showed any smart errors (like reallocated sectors, the one's you pay the most attention to). The Parity 2 drive immediately started rebuilding when I started the array, while the other drive stated that its "contents were emulated. drive not available" or something of that sort. It recognized the drive, as on the drop down menu the drive was there along with the option for "no device". Parity rebuilt on Parity 2 just fine, with no errors. I then unassigned the data drive, started the array, stopped the array, and upon starting the array this time, the data drive has started rebuilding. I just wanted to post both SMART reports because I'm not sure what the errors that are showing mean. These drives are only about 20 days old, so should I RMA them for new ones, or are they ok? WL3000GSA6454_WOL240356115-20161004-0135.txt WL3000GSA6454_WOL240356112-20161004-0134.txt
October 4, 20169 yr Hello, I haven't done much posting here, but I thought I might chip in my discoveries as I, too, have had similar issues with drives dropping off. I am currently (still) using 5.0.6 and have found that some drives would randomly get 'read-errors'. When I would stop the array, I noticed that the drive were actually not seen at all!. So although it was a read/write error, it was because it read or write to the non-existant drive. A re-boot usually solved this, but this past weekend, it finally happened that during a rebuild, another drive dropped off! Well, After removing the two 'bad' drives, I found that the software wasn't seeing the correct hardware. It was still seeing one of the old drives! (which is why formatting was failing) After multiple attempts to fix the mounting problems, I finally reset the configuration with the drives that were in place. This allowed the software to see the correct drives. I remapped the physical drive to drive numbers and the server just finished building the parity. The server is running smooth once again. I am really hoping that it stays this way for a while. I also disabled all the drives from spinning down. Someone did a $$$ savings for spinning the drives down and it wasn't worth it in a work environment. I am not sure if it helped or not, but I am certain it didn't hurt. I am now recovering the data on the two removed drives using the recovery mentioned here. http://lime-technology.com/forum/index.php?topic=27028.msg236889#msg236889 I hope this helps!
October 4, 20169 yr Running 6.2 So, a few days ago I got a read error notification via Push Bullet on my Parity 2 drive. Several hours later, I got a read error notification on another of my new drives. Recently I added three 3TB drives to the array, and I pre cleared them, with 3 runs, and there were no issues. I stopped the array, and upon doing so, unRaid showed "no device" in the spot where it was supposed to be. So, I restarted and one of them appeared, one of them did not. At this point, I shut down, checked all of the cables to make sure they were all securely connected, and it appeared that they were. I rebooted and both drives showed up. Neither showed any smart errors (like reallocated sectors, the one's you pay the most attention to). The Parity 2 drive immediately started rebuilding when I started the array, while the other drive stated that its "contents were emulated. drive not available" or something of that sort. It recognized the drive, as on the drop down menu the drive was there along with the option for "no device". Parity rebuilt on Parity 2 just fine, with no errors. I then unassigned the data drive, started the array, stopped the array, and upon starting the array this time, the data drive has started rebuilding. I just wanted to post both SMART reports because I'm not sure what the errors that are showing mean. These drives are only about 20 days old, so should I RMA them for new ones, or are they ok? When you see these errors you must capture diagnostics and post them here. Could be any number of issues including: bad hard drive, bad cables, bad controller, bad power, insufficient power. Also SMART is generally unreliable at predicting drive failures.
October 4, 20169 yr Author Ok, if it happen again, I will post diagnostics, but which diagnostics should I post?
October 4, 20169 yr Author Hello, I haven't done much posting here, but I thought I might chip in my discoveries as I, too, have had similar issues with drives dropping off. I am currently (still) using 5.0.6 and have found that some drives would randomly get 'read-errors'. When I would stop the array, I noticed that the drive were actually not seen at all!. So although it was a read/write error, it was because it read or write to the non-existant drive. A re-boot usually solved this, but this past weekend, it finally happened that during a rebuild, another drive dropped off! Well, After removing the two 'bad' drives, I found that the software wasn't seeing the correct hardware. It was still seeing one of the old drives! (which is why formatting was failing) After multiple attempts to fix the mounting problems, I finally reset the configuration with the drives that were in place. This allowed the software to see the correct drives. I remapped the physical drive to drive numbers and the server just finished building the parity. The server is running smooth once again. I am really hoping that it stays this way for a while. I also disabled all the drives from spinning down. Someone did a $$$ savings for spinning the drives down and it wasn't worth it in a work environment. I am not sure if it helped or not, but I am certain it didn't hurt. I am now recovering the data on the two removed drives using the recovery mentioned here. http://lime-technology.com/forum/index.php?topic=27028.msg236889#msg236889 I hope this helps! Thank you for the info. If it happens again, I will try this
Archived
This topic is now archived and is closed to further replies.