Ryand833

Thanks. I definitely won't be adding them to the array until I get up to 5.0+. I might just download Unraid 5.0 to another USB stick and boot up on another system (if I can find one) to pre-clear the drives, just to be safe.

Hello all, I recent sent back two Western Digital 2 TB drives (WD20EARS) that were reporting read errors, and they're sending me back two 3 TB drives (WD30EZRX) since I guess they didn't have any of the 2 TB drives available. At first I'm thinking "woohoo" and then I remembered two things: 1) I'm still on Unraid 4.7 (I can upgrade to 5.0, so that's not a huge deal). 2) My motherboard SATA controller probably isn't going to support the 3.0 TB size, but I'm not 100% sure. Is there a list of SATA controllers floating around that for sure can handle the 3 TB drives? I've done some looking and searching, and saw the Hardware Compatibility page on the wiki, but it makes no mention of drive capacities. The motherboard I'm running is an MSI K8N Neo4 Platinum, which has 8 on-board SATA ports -- 4 from the nForce4 Ultra chipset, and the other 4 from an on-board Silicon Image Sil3114. I know that to use these drives in my array, I'll need to do the upgrade to 5.0. My question is -- if my motherboard just happens to be able to support and detect these drives at their correct size, can I still hook them up to my system and do a pre-clear before I do the upgrade?

Thanks for all of your help guys. I got the two bad drives removed from the system, my new replacement parity drive passed pre-clear, and I'm currently rebuilding parity. Thanks again!

Thanks, I'll add that to my list. I usually try to do one of those once every month, but times makes fools of us all! I may set that up to be automatic after I get everything done.

Thanks for the replies, I appreciate it! What should be my first step once I get all of my data moved off of disk5? Something like stopping the array and removing those two drives from the configuration so I can do the pre-clears? ----------------------------------------------- EDIT OK so here's the situation and here's what I think I want to do about it. -) I've got a new drive on order (2 TB) that should be here on Tuesday. I'd like to use this drive to replace my current parity drive. -) I'm currently making sure that I have everything off of my disk5 data disk. What I'd like to do with this, for now, is to just remove it from the array (with no immediate need to re-add it as I've got plenty of room on my other 4 data drives for now) -) After I get the parity drive swapped, and the disk5 drive removed, I can start pre-clears on them (either on the same system or on an alternate one) so that I can determine if I need to RMA them. Luckily they're both still under warranty (whew!) The big question is, what order do I do everything in? It's almost like I want to just start a new array, using existing data on my 4 data drives. I'll just effectively be building a brand new parity disk based on those 4. I don't know if this is correct, so please correct any of these steps for me or let me know what I should do instead. 1) Stop the array, remove parity and disk5 from the configuration ? 2) Shut system down, put new parity drive in, start system back up. I'm thinking since the configuration is missing parity, the array won't auto-start ? 3) Run pre-clear on new parity drive ? 3) Do an initconfig to wipe the array configuration (after backing up configs, noting all of my configuration settings, drive mappings, etc.) ? 4) Add new parity drive into the array in the parity slot ? 5) Start the array so it can now re-build parity on the brand new drive ? Again, I have question marks behind all of those steps because I'm looking for some to either confirm or correct me on what you think I should do. Any help is greatly appreciated! - Ryan

That's exactly what I'm doing right now. Getting everything moved off of it onto the other drives, which luckily have plenty of free space to accommodate what I've got on disk 5. What would the process be after that's done? 1) I'd have to get disk5 either removed from the array or replaced with a new undamaged drive. 2) Either way, I'd have to rebuild parity, is that right? Which means I'd need to get the parity drive replaced beforehand.

Thanks -- I modified the original post to include that information. System specs are at the bottom and SMART test reports are attached as .txt files.

Hello All, I'm getting some errors show up on two of my drives on the web interface and I'm not sure where to go from here. I guess I've had these errors for a while but haven't noticed them until now. I have 6 drives in my array (parity + 5 for data). The errors are showing up on parity, and on disk5. I attached a quick screenshot of my web interface main page, and also my full syslog. I had to put the syslog in a zip file otherwise it wouldn't fit, I hope that's OK. I'm running unRAID version 4.7. The short SMART tests are also attached for both drives. It seems to have encountered a few of them when I did a parity check on Nov 12th: Nov 12 11:36:42 nas0 kernel: md: recovery thread woken up ... Nov 12 11:36:42 nas0 kernel: md: recovery thread checking parity... Nov 12 11:36:42 nas0 kernel: md: using 1152k window, over a total of 1953514552 blocks. Nov 12 11:37:00 nas0 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 12 11:37:00 nas0 kernel: ata1.00: BMDMA stat 0x25 Nov 12 11:37:00 nas0 kernel: ata1.00: failed command: READ DMA EXT Nov 12 11:37:00 nas0 kernel: ata1.00: cmd 25/00:00:40:f2:08/00:04:00:00:00/e0 tag 0 dma 524288 in Nov 12 11:37:00 nas0 kernel: res 51/40:7f:b8:f5:08/40:00:00:00:00/e0 Emask 0x9 (media error) Nov 12 11:37:00 nas0 kernel: ata1.00: status: { DRDY ERR } Nov 12 11:37:00 nas0 kernel: ata1.00: error: { UNC } Nov 12 11:37:00 nas0 kernel: ata1.00: configured for UDMA/133 Nov 12 11:37:00 nas0 kernel: ata1: EH complete Nov 12 11:37:03 nas0 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 12 11:37:03 nas0 kernel: ata1.00: BMDMA stat 0x25 Nov 12 11:37:03 nas0 kernel: ata1.00: failed command: READ DMA EXT Nov 12 11:37:03 nas0 kernel: ata1.00: cmd 25/00:00:40:f2:08/00:04:00:00:00/e0 tag 0 dma 524288 in Nov 12 11:37:03 nas0 kernel: res 51/40:7f:b8:f5:08/40:00:00:00:00/e0 Emask 0x9 (media error) Nov 12 11:37:03 nas0 kernel: ata1.00: status: { DRDY ERR } Nov 12 11:37:03 nas0 kernel: ata1.00: error: { UNC } Nov 12 11:37:03 nas0 kernel: ata1.00: configured for UDMA/133 Nov 12 11:37:03 nas0 kernel: ata1: EH complete And then some more on Nov 27: Nov 27 11:17:10 nas0 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Nov 27 11:17:10 nas0 kernel: res 51/40:08:c0:61:c7/40:00:d5:00:00/e0 Emask 0x9 (media error) (Errors) Nov 27 11:17:10 nas0 kernel: ata3.00: error: { UNC } (Errors) And then a whole bunch on Dec 20: Dec 20 16:33:08 nas0 apcupsd[1706]: Power failure. Dec 20 16:33:10 nas0 apcupsd[1706]: Power is back. UPS running on mains. Dec 20 17:22:58 nas0 mountd[30357]: authenticated mount request from 192.168.210.40:52483 for /mnt/user/media (/mnt/user/media) Dec 20 17:26:45 nas0 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 20 17:26:45 nas0 kernel: ata3.00: BMDMA stat 0x25 Dec 20 17:26:45 nas0 kernel: ata3.00: failed command: READ DMA EXT Dec 20 17:26:45 nas0 kernel: ata3.00: cmd 25/00:00:a0:4e:ff/00:04:d5:00:00/e0 tag 0 dma 524288 in Dec 20 17:26:45 nas0 kernel: res 51/40:bf:d8:51:ff/40:00:d5:00:00/e0 Emask 0x9 (media error) Dec 20 17:26:45 nas0 kernel: ata3.00: status: { DRDY ERR } Dec 20 17:26:45 nas0 kernel: ata3.00: error: { UNC } Dec 20 17:26:45 nas0 kernel: ata3.00: configured for UDMA/133 Dec 20 17:26:45 nas0 kernel: ata3: EH complete Dec 20 17:26:54 nas0 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 20 17:26:54 nas0 kernel: ata3.00: BMDMA stat 0x25 Dec 20 17:26:54 nas0 kernel: ata3.00: failed command: READ DMA EXT Dec 20 17:26:54 nas0 kernel: ata3.00: cmd 25/00:00:38:24:01/00:04:d6:00:00/e0 tag 0 dma 524288 in Dec 20 17:26:54 nas0 kernel: res 51/40:5f:d8:25:01/40:02:d6:00:00/e0 Emask 0x9 (media error) Dec 20 17:26:54 nas0 kernel: ata3.00: status: { DRDY ERR } Dec 20 17:26:54 nas0 kernel: ata3.00: error: { UNC } Dec 20 17:26:54 nas0 kernel: ata3.00: configured for UDMA/133 Dec 20 17:26:54 nas0 kernel: ata3: EH complete Dec 20 17:31:11 nas0 apcupsd[1706]: Power failure. Dec 20 17:31:13 nas0 apcupsd[1706]: Power is back. UPS running on mains. . (more errors omitted -- see full syslog) . I seem to have had some power issues on Dec 20, not sure if that had anything to do with it... I have the system connected to an APC battery backup, and the system stayed running for the entire duration. If anyone is available to help me on what my next step should be, I'd greatly appreciate it. System specs: CPU: AMD Athlon64 4000+ Motherboard: MSI K8N Neo4 Platinum Power Supply: Ultra X4 750W RAM: 2 GB DDR Storage: Parity - Western Digital 2TB SATA Storage: Disk1 - Western Digital 2TB SATA Storage: Disk2 - Western Digital 750GB SATA Storage: Disk3 - Western Digital 1TB SATA Storage: Disk4 - Seagate 1.5 TB SATA Storage: Disk5 - Western Digital 2TB SATA syslog-2013-01-04.zip SMART-parity.txt SMART-disk5.txt

Yes, I asked him to try again last night to reset his password and the re-activation e-mail never arrived. Is there something else you'd like me to have him do?

Hello, I have a friend who's registered with this forum but is unable to remember his password -- He's trying to use the "Forgot Password" form but it seems that his e-mail provider is blocking emails from the lime-technology.com domain (they're not going into spam, apparently they show lime-technology.com as being on some e-mail blacklist so the e-mails are getting dropped immediately). Could someone (mod, admin) please work with me through PM's to help him get his password reset? I can provide his information through PM's if someone can contact me. Thanks!

Great, thanks for the info! I looked up that board, and it has the ICH7R south bridge -- It seems to me that generally the ICH?R chipsets are the ones with better hotplug support, but I haven't really found any info to back this up on *nix systems, so I'm not too sure. For anyone curious, here's the newegg page with motherboard specs on the X7SLA-H-O: http://www.newegg.com/Product/Product.aspx?Item=N82E16813182205 Has anyone had any luck with hot-plugging SATA (or eSATA) on a board with an ICH10 south bridge?

Hello, We will soon be building a new unRAID server to use at work as our new backup solution. Part of this plan is to use two (or more) SATA drives as "off-site" drives that we will keep copies of the backups on. Ideally we would like to use a hot-swappable drive drawer for this. As an example, we are looking at the DRW115SATBK from StarTech (http://www.newegg.com/Product/Product.aspx?Item=N82E16817604005). These drives will not be part of the unRAID array, they will just be separately-mounted (using unMENU) drives that we'll do manual copies to. Now, the big question.... is this possible? I've done some research into SATA hot-plugging and I'm not very confident that this can be done on unRAID but I wanted to ask here first before throwing out the idea. First, here's the hardware selection. Case: Aerocool VS-9 http://www.newegg.com/Product/Product.aspx?Item=N82E16811196039 Power supply: Corsair TX650 V2 http://www.newegg.com/Product/Product.aspx?Item=N82E16817139020 Motherboard: Supermicro MBD-C2SEA http://www.newegg.com/Product/Product.aspx?Item=N82E16813182161 Processor: Intel Celeron E3400 2.5GHz http://www.newegg.com/Product/Product.aspx?Item=N82E16819116348 RAM: Kingston 2 GB DDR3 1333 http://www.newegg.com/Product/Product.aspx?Item=N82E16820134812 Hard Drives: Western Digital 2 TB WD20EARS x 5 http://www.newegg.com/Product/Product.aspx?Item=N82E16822136514 3 of these drives will be part of the array, 2 will be for the off-site copies. Hot Swap Drive Bay: StarTech Drive Bay http://www.newegg.com/Product/Product.aspx?Item=N82E16817604005 Hot Swap Spare Tray: StarTech Spare Tray http://www.newegg.com/Product/Product.aspx?Item=N82E16817998008 Here's the process that we'd like to do: 1) Our automatic backup to the unRAID array will take place every night, starting at 10:00 PM, should finish by morning (we'll be doing rsync backups, so the incrementals should be done very quickly). 2) The next day, we will bring in one of these drives that is seated in the StarTech removable tray. The drive will be inserted into the StarTech drive drawer. 3) We will then mount the drive in unRAID (not as part of the array, just as a normal drive). 4) The copy will then be done manually 5) We would then un-mount the drive 6) Drive would be physically removed from the StarTech drawer and taken home. Now, based on the research I've done, the Supermicro board we've selected has an ICH10 south bridge chipset, and doesn't (natively?) support SATA hot-plugging, unless you're using Windows Vista and enable AHCI on the sata controller. I don't even really know 100% what that means, but yeah. Apparently boards with an ICH10R south bridge have better native hot-pluggable support. I guess I'm just looking for a "Yeah, I'm doing that, it works" or a "No, that's not possible, here's why..."

I believe on the first reboot, the array automatically came up with the drive disabled. OK, I'll do that -- I'm also going to move the server somewhere else, I'm worried that the low temperature might be just a tad too low (drives are between 12 and 18 C when spun down) Thanks!

I'm running unRAID 4.7 on a new system, and I have 5 drives (1 parity, 4 data). Today, I went to bring the array down to do a quick reboot, and one of my data drives was listed as 'disabled', and it couldn't read the temperature on it. The array still successfully stopped, so I rebooted the system anyway. When it came back up, the drive was not even seen by the system. I left it the way it was for a few minutes and decided to do another reboot (after the array was safely brought down). Now, when it came back up, it sees the drive again, except this time it sees it as a "Disabled Disk Replaced" and I have the option to: "Start will bring the array on-line, start Data-Rebuild, and then expand the file system (if possible)." Is this what I should do at this point? I'm worried that the drive may be bad (I just pre-cleared it less than a week ago, 0 problems).

Yeah, I like that about this case too. I mean, look... ...talk about low-bling! LOL OTOH, it's all black, tool-less; so it's easy to work on and super-light. If I can pack these iStars in there, I'll be pretty happy. Gonna take a run at it tomorrow. CD Good luck! Here are a few more pics of the inside of mine, did a little bit of re-wiring and opted for the 90° SATA connectors for easier management. It's not the best cable management, but it's good enough for me

I bought two of the Western Digital WD20EARS drives -- one of them pre-cleared successfully, but every time I attempted to do the second one, it would start the pre-read, going about half the speed it should (around 40 MB/s) -- The pre-read got up to 3% and then went all the way down to 0 MB/s and stayed there. I tried different cables, different SATA slots on the motherboard, different power connectors from the PSU, but nothing fixed it. I plugged the drive into my windows system to run WD's LifeGuard diagnostic program and it said it would take over 16000 hours to do the "extended test". I ended up RMA'ing the drive and they sent me a new one -- New one works perfectly fine.

OK here are a few pics of mine, including the small case mod I had to make. (And yes, I know, the cabling is sloppy -- this is not the final result, it's a work in progress ) Click on the image for higher resolution. And now, the guts and the mod for the front-panel wires...

Yeah, I've been meaning to. As soon as I finish this drive pre-clear, I'll take the front panel off and take some pics of what I had to do.

The system automatically executes the script at /boot/config/go -- you can add the startup line there. I added this at the end of my /boot/config/go file: /boot/unmenu/uu As long as that's where you have it installed, that'll get the job done.

Thank you -- I think I will run a few more pre-clears on it just to make sure. The drive is fairly old, I'd have to go dig up some receipts to see if it's still under warranty (probably is, just need to make sure).

Would someone mind taking a look at these results for me? I've run this drive 3 times now (actually 4, but the 3rd time I was running it, my PC that I had the telnet session open on froze up during the post-read). The first two times, I saw increases in the number of re-allocated sectors -- and the 3rd time, it stayed the same, but I'm concerned about some of the other values: ========================================================================1.6 == ST31500341AS 9VS1S5Y6 == Disk /dev/sde has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 105 6 ok 190690543 Spin_Retry_Count = 100 100 97 near_thresh 1 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 331 Airflow_Temperature_Cel = 66 67 45 In_the_past 34 Temperature_Celsius = 34 33 0 ok 34 Hardware_ECC_Recovered = 57 53 0 ok 190690543 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 133 sectors had been re-allocated before the start of the preclear. 133 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. Should I be worried about the Raw_Read_Error_Rate, Spin_Retry_Count, End-to-End_Error, High_Fly_writes, etc? This drive came out of a Seagate External Enclosure, and it's been working fine for me for a while now, I just want to make absolutely sure before I put it in my array.

Yes, the coolermaster cages are pretty short -- I do have a full ATX motherboard, and I will say that it doesn't really leave a lot of room for cables (even with a modular power supply). But, as you said, at $50 bucks, it's unbeatable. I did have to do a little modding on it -- the cables on the front panel for the power button, LED's, etc., ran inside where the 5.25" bays are -- just drilled a few holes to run them outside of it, took 30 minutes tops.

Not that it has anything to do with your build, but I just wanted to chime in -- I bought an Aerocool VS-9 case and three of the 4-in-3 CoolerMaster enclosures to use in it, and I am very happy with how it turned out. I'll be taking pics and posting them sometime this weekend hopefully.