fido666

Can I just check I have the drive swap out process down correctly? Assuming I want to swap out the disabled disk with a larger drive (i.e. my WD EARS 2TB) :- 1. Stop the array. 2. Unassign disabled disk. 3. Power down the server. 4. Replace disabled 1.5TB disk with 2TB disk ** all other array disks incl the parity disk are 2TBs ** 5. Power up the unit. 6. Assign new disk to the array. 7. Start the array. The drive being replaced is not the Parity disk so will I need to run parity and/or file system checks after replacing the drive?

It will be less painful to replace the drive . I actually think the existing drive may be OK and it was just a loose power cable, not 1 peep out of it durung the long test last night. I'll still test it externally just to be sure which means swapping it out, might just have to use the WD EARS 2TB from my external case for that.

So UnRAID won't re-adjust the remaining drives to take over for a missing one?

Thanks for clearing that up Joe, I was under the impression all 4K sector drives needed the -A. I actually have a WD 2TB EARS drive that I was thinking of using to swap out a suspect drive, don't know if it has the jumper or not as it's currently in an external housing. I'm assuming it's Ok to run a mix of non-4K and 4K sector drives in the same array?

Manufacturer's specs, UnRAID's GUI won't tell you. There is a warning at the start of the preclear but without knowing the drive's specs it's not much help. I'd say your drive has 4K sectors based on the info in the Details tab :- http://www.newegg.com/Product/Product.aspx?Item=N82E16822148844

Well there you go, learned something new tonight

Any drive with "Advanced Format" in its specs will need the -A. The preclear might keep running but you would lose sight of the progress of each stage of the preclear process. Considering a 2TB HDD takes 24hrs+ to run a single pass preclear you don't want to have to restart it if you can avoid it.

I've run many preclears from Telnet sessions, works fine but don't let the PC you telnet from shutdown while the session is active. Your steps sound about right but don't forget to include the "-A" attribute for any disks that need to be 4k sector aligned. This may help refresh your knowledge :- http://lime-technology.com/forum/index.php?topic=2817

I've fired my UnRAID box up tonight and had 3 drives in various states of being MIA. On the UnMenu console the array was listed as "Error:Too many missing disks" and was stopped. The states of the 3 drives in question were :- DISK_NP_MISSING /dev/md4 Hitachi_HDS5C302_ML0220F30GNJ3D - Disk was OK yesterday but shown as spun down DISK_DSBL_NP /dev/md5 SAMSUNG_HD154UI_S1XWJDWZ316644 - This is the squeaking & clicking drive which passed both short and long tests in UnMenu Not listed WD Black 500 GB - This was my cache drive After powering down and disconnecting and reconnecting all the sata cables at the drive end I have restarted and can now see all 3 drives again however /dev/md5 is still marked as disabled. Is it just a matter of unassigning it and re-assigning it to re-enable it? I'm still concerned about those smart attributes I posted earlier and the noisy drive (which strangely enough is silent at the moment). I'm guessing it would be wise to remove it and test thoroughly with something like Seatools but can I just unassign it and leave it out or do I have to swap it out with another drive? My array is nowhere near full so the other drives should have more than enough capacity. Have attached current Syslog in case it helps with an answer syslog-2012-06-121.txt

Yet UnRAID disabled it, presumably for a write error? Is that what the Multi Zone error stat relates to? I have not fired it up yet today, too scared and have to go to work shortly; will look at it again when I get home. I first noticed a rattling noise coming from the drive, fairly soft too. I didn't hear the squeaking till I ran the long test, might be a result of some action it was taking.

Hmmm, the long test completed without error. Previously reported SMART values are unchanged. SMART report attached. smart_report_sda_long.txt

Update: The drive made a loud squeaking noise for the last few hours (test around 70% completed). Test is now 80% completed and the squaking noise has stopped. It was like the one in this YouTube clip :- The drive in the clip also happens to be a Samsung 1.5TB but I don't know if it's the same model that I have (mine's an internal drive).

Yeah will try but won't keep my hopes up. BTW, it's making a noise very similar to the HDD in this YouTube clip, has been doing this for the last few hours and still has 30% of the long test to go. The drive in the clip also happens to be a Samsung 1.5TB but I don't know if it's the same model that I have (mine's an internal drive).

Maybe the pre-ship option is not available to AU customers, it's not mentioned on the AU Returns Policy page:- http://www.seagate.com/au/en/support/warranty-and-returns/packing-and-shipping-instructions/

Which region are you in? I have a Samsung 1.5TB which appears to be dying and Seagate now handles the RMA process for Samsung drives in AU. It costs about $15 AUD to return a drive to Seagate in Sydney (I'm in Melbourne). I'm still testing it but these are the SMART attributes which make me think it's sick (that and it is disabled in the UnRAID status window):- 183 Runtime_Bad_Block = 39 (raw value) 195 Hardware_ECC_Recovered = 1997 (RAW value) 200 Multi_Zone_Error_Rate = 1 (RAW value) It's about 50% through the long test now and is making alarm beep type noises every second now, not sure if it's just seek noise but it's loud.

Update: Still waiting for the long test to complete but I can see some stats in the SMART status already which concern me :- 183 Runtime_Bad_Block = 39 (RAW value) 195 Hardware_ECC_Recovered = 1997 (RAW value) 200 Multi_Zone_Error_Rate = 1 (RAW value)

I'm running UnRAID Plus 4.7 with 7 drives connected (6 array & 1 cache). There are 5 drives running off my server's motherboard controller and 2 running off a PCIe Sil3132 based controller card. Last night I heard some unusual rattling noises coming from the UnRAID box so fired up the web GUI to check the console. One of the array drives was showing > 700 errors and the cache drive was in red status; both these drives are hanging off the PCIe controller. I stopped the array and shut down the server but when it came back the cache drive was no longer showing in the device list and the errored array drive was showing as disabled. My questions are:- a) What can I do to check what caused the error (i.e. logs, etc)? b) What are my chances of the controller having failed rather than the drives? c) What steps should I take to remove the failed drives assuming I don't have a large enough drive to swap out the array drive? I've had a look at the Wiki but I'm a little hesitant to follow the steps outlined there since I have 2 failed drives (albeit one is only the cache drive). I'm fairly new to UnRAID so forgive my ignorance. I have attached my Syslog in case it helps. Edit: Have also attached the smart data report for the failed drive, short test only so far. The short test passed so I'm now running the long test, will post log once complete. Edited to mark as solved. syslog-2012-06-11.txt smart_report_sda.txt

I have a related qeury, apologies for the hijack. Yesterday I swapped out my router without shutting down the UnRAID box first. I couldn't see the box on the network after this so initiated a Powerdown/Reboot directly from the console (not with the power button, I used the shutdown command). Upon restarting the box a parity check was started automatically which completed with 14940 errors. The status page now shows parity as being valid so do I need to worry about lost/corrupted data now? My config includes a cache drive if that matters. ETA: Found this topic in the FAQs which suggests I have no cause for concern :- http://www.lime-technology.com/wiki/index.php/FAQ#Why_am_I_getting_repeated_parity_errors.3F I'm running another parity check now to see if it finds anymore errors. Update: Parity Check completed with 0 errors. Does this mean the previous errors were corrected during the previous check?

The support page for my CyberPower BR850ELCD isn't very descriptive, it just lists the software as "Linux_64bit for TAR". The support page is here - http://www.cpsww.com.au/support/product_support.htm (you have to select the appropriate categories, I can't link directly to the TAR files). ETA: It downloads a file called "PPL-1.2.1-x86_64.tar.gz" if that helps; I'm assuming that's a TAR archive.

I'm relatively new to UnRAID and a total noob where Slackware is concerned; hoping someone can tell me if the standard Plus install includes TAR support. The reason for my query is that I have a UPS that has monitoring software with TAR compliant 32 & 64 bit versions but I have no idea how to integrate the code into my current UnRAID install.

I just realised I never came back to say how I went with the mesh panel. It fits fine with a little bending and twisting, doesn't need anything else to hold it in place too. I have 7 HDDs all running happily in my Tardis now, 6 x 3.5" and 1 x 2.5". Temps are good, the bottom HDD in the double stack running just a few degrees Celsius higher than the rest even during parity checks (have one running right now and temp is 35c, other 6 are 31/32c). The hardest part of getting all the drives in was shoehorning the Nexus DoubleTwin into the ODD rails, don't want to think about having to do that again in a hurry.

That's what I wanted to clarify since Raj mentioned the transfer wouldn't spill over. OK, thanks for confirming. How can you tell when the mover script has done it's thing? Should the Cache drive then be empty? I'm not sure if it just does a copy rather than a pure move. Nevermind, answered my own question by forcing a move and waiting to see what happened to the cache (it's now empty for those wondering). Good point, it actually appears as a 465GB disk under Windows Properties for the drive. It was left transferring overnight and seems to have completed OK; I'm assuming the Mover script kicked in while the rest of the transfer was still going and moved the files not marked as in-use.

At the start of this thread Raj makes the point that "If you attempt a data transfer that is larger than the size of your cache drive, the transfer will fail. The transfer will not automatically 'spill over' into the parity protected array ". Does that mean if I start a transfer that is say 600GB in total (as in all selected directories/files) and my Cache drive is 500GB that the transfer will not complete or that it won't start at all? Also, can I force the mover script to run mid-transfer or do I have to wait till there is no disk activity to the cache drive? Sorry if this has been answered already, in a bit of a panic as my OH has started transferring files to the Tardis (my UnRAID box) and I'm not sure how large the total size of the transfer is. Edit: Just looked at the disk transfer on the Windows PC and it's only 480GB so hopefully will not have any issues (my Cache drive is 500GB).

I put out a call on the WTB forum of Overclockers AU (OCAU) and a fellow member had one spare. It's from a Coolermaster Elite 3xx series case and as near as I can tell the dimensions match those of the cutout on the Microserver. I don't have it as yet so cant say for sure if it will fit or what it will look like. Can anyone tell me why the status light on my Cache drive in the UnRAID console is flashing green, not solid? I also can't see the temperature of the drive now. NVM, all good now.

I've acquired a mesh bay cover so I can add a 6th array drive. I have a 2TB WD Green I can use but it's an Advanced Format drive. Would I be OK to re-assign this as the parity drive and re-allocate the current Parity drive to the array? Will having Parity on a 64K sector drive cause any issues? Also, I'm a little dissappointed with my performance results after adding my Cache drive (WD Black 500GB 7200RPM). Not much write improvement and read speed actually dropped (albeit only marginally). BIOS is currently set to have Write Caching enabled, should I disable it? NVM, answered my own question by trying it, write speeds died big time! Read speed a tiny bit better, just lucky there I think. Nastester creates a temp file for the write part of the test. It doesn't try and read an existing file, just reads the temp file back. I'm assuming if the data I'm trying to access had already been moved to the array then reads would need to go there. Nastester points to a drive letter but wouldn't the read/write still go via the cache drive first? Update: Doh! I didn't have cache enabled for the share Nastester was using, didn't realise it was disabled by default. It helps if you read the manual LOL! Much better figures now :- Also found a easy ghetto mod to hold the 2.5" cache drive in place in the void under the ODD bay, slices of wine cork cut to an appropriate thickness