Nightstalk3rs

Great! Thank you for the quick response. The drive has currently been rebuilding for a few hours and I don't anticipate any issues. Thanks again!

Hello all, I just recently ran into an issue in my UnRAID setup in which one of my disks randomly became disabled. I believe it was during the process of me cleaning my server and possibly knocking the SATA cable loose. After shutting down and checking/fixing the SATA cable, the disk was available to add to the array, but still remains disabled. I have completed a SMART report on the drive and have uploaded it here. While the UnRAID GUI reports that it completed without error, I just feel more comfortable posting it here for someone to take a look at. I believe that this is simply just an issue due to a loose SATA cable, but I just wanted to be safe and have the SMART report reviewed in case there is any potential that the drive is failing. If the drive is okay, I believe I will still have to rebuild the drive due to a potential write failure to the drive, hence why the drive became disabled. If so, what are the available options to do such a process? I read in a previous post that it's as simple as: Stop the array Set the disk to be not installed Start the array Stop the array Set the disk to be the appropriate disk Start the array I appreciate any assistance I can get, and I would much rather be safe than sorry. Thank you in advance! WDC_WD20EARS-00MVWB0_WD-WMAZA0659735-20170425-1838.txt

Thank you both again for your help! Just an update on my situation. Last night I installed WD Data Lifeguard on two computers and hooked up each drive to one of the PCs, one via SATA directly and one via an SATA to USB3 adapter (with it's own power source) as demonmaestro had suggested, and of which I actually had purchased a few weeks ago from Tigerdirect. I ran the extended test on both 5TB drives and it took roughly about 7-8 hours, both passing the test fine. I only ran it once, but I'm considering running it again if it's recommended to do so, and can't see being a bad thing to do. I also was considering doing the "write zeros" option, but thought that might be unnecessary to do with the brand new drives. Thank you again to everyone! Such a helpful community, and it's good to learn about this for the future so I don't have to waste anyone's time, and also for a sense of enlightenment

Thank you both for the suggestions! It seems to me that the easiest and quickest route for me would be to not pre-clear and use a diagnostics tool in Windows to test the drive. However, I don't see that Toshiba has any official diagnostics tool for their drives, so I was wondering if you guys or anyone else could suggest another utility that may work? I see that demonmaestro recommended the WD Data Lifeguard Diagnostic tool, but I'm just wondering if it would work with a different manufacturer's drive. I imagine there may also be 3rd party software in existence, but I'm not 100% familiar with any that may exist.

Hello all! As this is something I haven't yet done before, I always look to the helpful community here for advice before proceeding with the unfamiliar. I just posted a thread recently asking for help with replacing a dead data drive, which was a fairly simple process. Currently, my parity drive is the same type of Seagate 3TB HDD (ST3000DM001) as the data disk that just recently failed. As this drive model is known to have a high failure rate, I do not trust having it in my system anymore. I also wanted to use this opportunity to slowly upgrade my drives to 4TB drives over time to increase array capacity. My server is currently at maximum capacity for drives, so I am unable to add anything new without having to replace a drive. My goal here is the following: [*]Replace 3TB parity drive with a new, pre-cleared 4TB drive [*]Also replace a currently in use 3TB data drive with a new, pre-cleared 4TB drive to begin making my array larger Ultimately I want to pre-clear both drives before adding to my array. Since I do not have any free slots to add a new drive into my current array to pre-clear, I thought this may be difficult to do. I would hate to have my old parity and data drives removed (although not at the same time) while the new drives are being pre-cleared and then subsequently rebuilt, even though the array would be stopped. I feel that might leave me open to issues, but I could be thinking about it incorrectly. Since I'm out of capacity to add new drives without removing an old one first, what might be the best way to pre-clear both of these drives and replace my parity and a data drive consecutively? Any advice would be greatly appreciated! I did try searching the forums and wiki and found some similar situations, but I'm always cautious to do anything before consulting with the experts Thank you so much in advance!

Not a problem. Attached is another screenshot of the completed rebuild if it is at all helpful. The drive has rebuilt successfully and everything is now back to normal. Thanks to you and everyone else for assistance with my issue!

I do have a problem, and it's keeping my drives too full I need to convert some of those 2TB drives since I'm out of SATA ports! I've read conflicting arguments on here that it does and doesn't matter how much free space you have on your drives, so I'd love to hear what you suggest is an adequate amount

@itimpi - Thank you for the quick explanation. I have attached the new drive and it is currently, seemingly with no issues, rebuilding the drive as we speak. I expect this to take a fairly long time, maybe a full day, so I will report back once it is done if there are any issues. @RobJ - I followed the instructions you laid out and had no problems so far. I admit I got a little excited and forgot to take a screenshot of what it said for the "I'm sure" portion of the instructions. The wording had mentioned something about "rebuilding the drive," but I forgot to copy it down before proceeding. What I did was the following, starting with removing the old drive because my server was already shutdown: [*]Removed problem drive from server [*]Installed new drive with the same SATA cable and power cable, also keeping the drive connected to the same port the troubled drive was connected to [*]Booted up server (noticed that the SuperMicro splash boot screen did not sit there for a minute as it previously had, presumably because the troubled drive was no longer delaying boot.) [*]Opened up UnRAID GUI to the "Main" tab (default) [*]Clicked the drop down list next to "Disk 1" (currently reporting "no device") and selected the new drive [*]Clicked the "Yes, I'm sure" check box next to the information explaining that the drive will be rebuilt upon hitting the "Start" button [*]Clicked on the "Start" button and the rebuilding process started, with the UnRAID GUI displaying orange-colored toast pop-ups in the top right corner. The toast pop-ups said the following: [*]unRAID Disk 1 error: 2015-08-16 04:11 PM Warning [TOWER] - Disk 1, drive not ready, content being reconstructed WDC_WD30EZRX-00D8PB0_WD-WMC4N0K9ALWF (sdf) [*]unRAID Data rebuild:: 2015-08-16 04:11 PM Notice [TOWER] - Data rebuild: started Parity size: 3 TB [*]Data build currently in progress I've attached a screenshot of the current screen for possibly posting on the wiki post if it is of any help. In the meantime while the drive re-builds, I want to try and see if I can diagnose the drive that stopped working. I have a SystemRescueCD USB drive that I will use to boot up into Linux and try and see if I can get the drive to be detected. If anyone has any suggestions on things to do when trying to diagnose a potentially bad drive, that would be greatly appreciated. In the meantime, off to Google I go. Nonetheless, thank you to everyone who has been a help in this post. I hope that this will be a simple solution to my issue!

@RobJ - Thank you for taking the time to update the Wiki article! I just received a replacement drive, and I wanted to ask a few questions before I start. [*]You mention in the updated instructions to "Unassign the old drive" of which I'm not sure I am able to or need to do because it is listed as "not installed." I've attached an image of my UnRAID GUI to illustrate what I am seeing. [*]You also mentioned that all of the contents of the old drive will be copied onto the new drive, making it an exact replacement, except possibly bigger. I worry about that last part as 3TB is the largest drive I can install since that is the size of my parity drive, and I (stupidly, I know) kept my drive pretty full, so much so that there were only roughly 6GB left on the drive before it died. Will I have to worry about anything happening if it is indeed larger since I suspect 6GB isn't a large buffer for any overflow Thank you again for all of your help as always, and I will begin the rebuild process as soon as I get confirmation on those two items!

Okay so I just swapped drives and it appears that the error has followed the drive and not the port. As suspected, it looks like my drive has died. Time to go purchase a 3TB or larger drive to replace this one. Just so I'm clear about the rebuild process, I was going to follow the steps found on this wiki post (https://lime-technology.com/wiki/index.php/Replacing_a_Data_Drive): A data drive needs to be replaced for whatever reason. backup 'config/super.dat' and 'config/disk.cfg' files to workstation Stop the array Power down Replace harddrive with new drive. Turn on Replaced drive appears with blue dot Tick the "I'm sure" checkbox, and press "Start will bring the array on-line, start Data-Rebuild, and then expand the file system." Hefty disk activity and main page will show lots of reading on "the other" disks and writing on new disk as data is being rebuilt. End I just want to make sure that the process hasn't changed it any way since this was written. I would also optionally opt to use preclear on the drive to test it first before rebuilding. Thank you!

@RobJ - Thank you for your reply! Once I get home from work I will give this a go. I have a suspicion that it is the drive as well, mainly because I know this particular Seagate 3TB drive has a high failure rate. Nonetheless, I will give the cable swap a try and see what happens when doing so. I'm almost hoping it is the SATA port as I have been wanting to upgrade my server to something more powerful, and that would certainly give me a reason I will report my results back, but the resolution to either a bad port or bad drive is pretty straightforward. Thank you again!

Okay so I tried two new SATA cables but no luck. Next I'm going to try using a different SATA port. Unfortunately I do not have any open SATA ports at this time. Would there be any issues with unplugging one of my currently working drives and using its SATA and power cables? That would allow me to test both the SATA port and the power if so. Not sure if it would mess up anything with the UnRAID array configuration by doing so, so I wanted to play it safe first and ask. Also, this is what happens when I try to run a SMART report on the drive from UnRAID: === START OF INFORMATION SECTION === Device Model: ST3000DM001 Serial Number: W1F1N7ZW LU WWN Device Id: 5 000c50 05ce42712 Firmware Version: CC24 User Capacity: 137,438,952,960 bytes [137 GB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s Local Time is: Thu Aug 13 20:05:48 2015 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Read SMART Data failed: Input/output error === START OF READ SMART DATA SECTION === Error SMART Status command failed: Input/output error SMART overall-health self-assessment test result: UNKNOWN! SMART Status, Attributes and Thresholds cannot be read. Read SMART Log Directory failed: Input/output error Read SMART Error Log failed: Input/output error Read SMART Self-test Log failed: Input/output error Selective Self-tests/Logging not supported I've attached my latest syslog if it is of any help as well to my current issue. Thank you again to everyone as always! syslog.zip

Good to know and thank you for the input! That could be really good news in the case of an SATA cable, or bad news in the case of an SATA port or power issue :'( I will try a new SATA cable first and then work my way from there. Thanks again!

Well after doing a bit of research, it appears that it could be a number of things, including bad cable, bad SATA port or a bad drive, with the drive appearing to me to be the most likely case. I did a some Googling with parts of my syslog seen below and found some threads on here and some other forums that seem to indicate a similar problem. Aug 11 20:23:56 Tower kernel: ata7.00: status: { DRDY ERR } Aug 11 20:23:56 Tower kernel: ata7.00: error: { ABRT } Aug 11 20:23:56 Tower kernel: ata7.00: configured for UDMA/133 Aug 11 20:23:56 Tower kernel: ata7: EH complete Aug 11 20:23:56 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 11 20:23:56 Tower kernel: ata7.00: irq_stat 0x40000001 Aug 11 20:23:56 Tower kernel: ata7.00: failed command: READ DMA Aug 11 20:23:56 Tower kernel: ata7.00: cmd c8/00:02:00:00:00/00:00:00:00:00/e0 tag 28 dma 1024 in Aug 11 20:23:56 Tower kernel: res 51/04:02:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Aug 11 20:43:38 Tower kernel: sd 7:0:0:0: [sdf] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Aug 11 20:43:38 Tower kernel: sd 7:0:0:0: [sdf] tag#28 Sense Key : 0xb [current] [descriptor] Aug 11 20:43:38 Tower kernel: sd 7:0:0:0: [sdf] tag#28 ASC=0x0 ASCQ=0x0 Aug 11 20:43:38 Tower kernel: sd 7:0:0:0: [sdf] tag#28 CDB: opcode=0x28 28 00 00 00 00 04 00 00 04 00 Aug 11 20:43:38 Tower kernel: blk_update_request: I/O error, dev sdf, sector 4 Aug 11 20:43:38 Tower kernel: Buffer I/O error on dev sdf, logical block 2, async page read Aug 11 20:43:38 Tower kernel: Buffer I/O error on dev sdf, logical block 3, async page read When I get home from work, I will try a new SATA cable first, then I suppose the next step is to try a different SATA port. I unfortunately don't have any free SATA ports, so I'll have to swap out a drive to see if UnRAID detects the potentially problematic one. Question: Would it be okay to upgrade to UnRAID 6.0.1 final just to get access to the diagnostic tool in the UnRAID GUI? If so, I can do that as well in order to post what I hope is more beneficial information. Thank you all in advance!

Thank you, but I can't actually click on the drive because it says Disk 1 is "not installed" in main with a red square next to it (device disabled.) That's true. Doing that would give me access to the new diagnostics feature. I wonder if the diagnostics work even work though if it's not detecting the drive. On a side note, I noticed it says in the syslog for sda1 (my UnRaid flash drive) that the "Volume was not properly unmounted. Some data may be corrupt. Please run fsck." Not sure that has anything to do with my issue though!