Ulvan

I'm removing my cache drive entirely and turning it into a second parity drive. My Resilio Sync Docker is hosted on my cache drive. How do I migrate it to the main server? Is it enough to move the Sync config folder to the new drive, and point the UI to the new location?

I ran three rounds of pre-clear with a brand new WD Red, and got the following error on the third run, full log attached. It says SMART error, but I don't see an error below. Log shows earlier events: Not exactly descriptive, but looks more like a pre-clear script error than a drive error? Or is the drive DOA? (Forum doesn't work properly with Ghostery, and code snippet puts it all in one line wtf) preclear_disk_WD-WX52D31RYVY4_3942.txt

Is there a step-by-step guide on installing this? Never installed any Docker components as far as I know.

Apologies for necro, but big thanks for this, it has happened to me several times and only now I realized that I have one of those sessions running!

Moved my entire 32TB array to XFS over two weeks. Parity check was error-free, and I switched my smallest data drive to become cache in the process. I tried to speed things up by moving drives from different SATA cards, not sure how big of a difference that makes. Didn't really help anyway, since it was about a drive a day as I didn't sit at the computer waiting for each transfer to finish to fire up the next one. I recommend moving drives around in order, or if not, making a list of the order so you don't have to start figuring out what you moved, what to format, etc. Had to triple check a few ones just to be sure I wasn't about to format a non-duplicated drive Has anyone done any tests on speed improvement over RFS? Forgot to test that... My parity check certainly went faster, was blazing fast at only 26 hours @ 42.0 MB/sec when it used to be 30+ hours. Thank you to all the contributors in this thread, was very helpful!

Not clear at what point you intend to add it to the array. You should do this before you format it to XFS since unRAID will want a clear drive if adding it as an additional array drive. A clear drive is not at all the same as an empty filesystem drive. So I should 1. empty cache drive 2. format it to XFS 3. add to array 4. start moving files from existing array drives to the XFS drive formerly known as cache Assuming you don't want to do a new config and rebuild parity, you should preclear the drive, then add it to the array, then format it. If you try to add a drive that is not clear to the array, unRAID will clear it, taking the array offline until it's done, then you will have to format it. The only way to maintain valid parity when adding a drive is to add a clear drive. A clear drive is all zeroes, so has no effect on parity. A formatted drive is not all zeroes, because it has a filesystem written to it. So, you should: 1. preclear drive 2. add to array 3. format Wasn't aware of the part in italics. The cache drive has been pre-cleared but of course has data, and has a file system, so it needs to be pre-cleared again from what you said. Thank you, now it's clear!

Not clear at what point you intend to add it to the array. You should do this before you format it to XFS since unRAID will want a clear drive if adding it as an additional array drive. A clear drive is not at all the same as an empty filesystem drive. So I should 1. empty cache drive 2. format it to XFS 3. add to array 4. start moving files from existing array drives to the XFS drive formerly known as cache

I'm considering changing my cache drive to an array drive, which would offer a convenient way to move to XFS. Would I just re-format the (emptied) cache drive to XFS, and start then the transfer of files from each data drive to it?

Does the default (9999) depth setting really read every file and directory on the array? I used to run with depth of 3 or 4 in a previous version to limit memory usage; I have 8 gigs, so shouldn't be an issue, but still. Reading the post above it appears that you could leave it at default and get dynamic/smart caching without having to worry about depth setting.

Quick query on depth. Does that option count the root as depth zero, or one? ie: root/folder 1/2/3 or root/2/3/4 In first case you'd have to set cache_depth to 3, in latter to 4 to cache all dirs. I'm trying to figure out how to get caching to work while allowing the disks to spin down. I'm lowering the value to see if it could be an issue with running out of memory. As Tom mentioned to me. with NFS and the SHFS/USER share, FUSE let's go of internal file handle structures after a certain amount of time when unused. This is the reason for the NFS stale file handle issue that crops up on the user shares. then, it (-u) might be something to try if you use NFS. This is largely gibberish to me. To a layman who uses SMB instead of NFS (hope I got that right), is there a situation when you'd use -u?

What does -u = also scan /mnt/user (scan user shares) actually do different than without that option? Also, my disks aren't spinning down although I don't have force them busy set up, I suspect caching might not be set up correctly. Any other option which might cause this?

Very good write-up, wiki-worthy! The necessity of backups can't be stressed enough. I know a guy who lost all record and photographs of the first five years of his son's life due to a HDD failure - he didn't have backups, and they were gone. I can't even imagine how that made him feel. As garycase said, re-ripping hundreds of movies will take a long time. I ripped all my 300+ CDs 10+ years ago, and it took me weeks - and I woved I'm never going to do that again. The checksum idea is very good. I'd verify them at least once a quarter to avoid creeping data corruption or drive failure due to unuse. I'm not aware of any research on drive failure rates when they go unused for long periods of time, but like all mechanical machines, I can see it as a potential risk. garycase, how do you do your checksums? Do you run a massive checksum list for every file on each disk? How do you deal with changing data disk content, or is your data all static? For Windows, SyncBack Pro does checksum checks for you. Here my basic tutorial for running MD5 checksums for Linux systems. I'll tweak it as I get my unRAID backup system up and running. Below what I used to do on my non-unRAIDed Windows system that I wrote on another thread. I will tweak this now that I have unRAID, utilizing the checksum approach. When I was on Windows, I used SyncBack Pro as well. Here overview of my backup system. I had Incremental backups that ran every day of the week, full refresh once a week. Then I had a full backup once a week on another drive, full clear at every run. And another full backup which was refreshed once a month, culling deleted files every six months. Latter two drives were "offline", ie. not attached to my desktop for security purposes in case there's data corruption or electricity issues (I have an UPS but I'm paranoid ). That way I would have daily backups of all critical data, and multiple backup levels as a fallback. If I accidentally delete a file or notice data corruption, I'd have it handy for up to six months. Going forward, I will be rotating two HDDs on an offsite location (one at home, other at work), which protects me from theft, fire, water damage, etc. Crashplan used to fill that role - I will continue using it, but will also rotate HDDs.

The mobo (below) on my current computer has Fan Xpert which controls the speed of case fans attached to the mobo based on (I think) three temp sensors. It works very well - I can hear when SETI@Home kicks in by the fan speed and LED brightness Haven't looked at mobo options for unRAID, but I'm sure some suitable ones have it or similar tech. http://www.asus.com/product.aspx?P_ID=gXUQex0X4rGOOh5E

So that would imply that a fan controller would be useful? I'd prefer to have an automated system, though (software or mobo).

I'm in the planning phase of my first unRAID box. The goal is to build an expandable system to stream HD content, do torrents, and store my photos. Space and expandability is a priority, quietness second, cooling third. I'm not sure how much cooling is really needed for an unRAID box - I'd imagine less than for a gaming rig or a photo editing box, for example? Here the shortlist of cases in order of current preference. All have plenty of space for HDDs, quite a few fans, and are supposed to be solid premium contenders and relatively quiet. Does anyone have any pluses or minuses why one would be preferred over the others? NZXT Phantom http://www.nzxt.com/new/products/crafted_series/phantom Fractal Design Define XL http://www.fractal-design.com/?view=product&category=2∏=55 Bitfenix Colossus http://www.bitfenix.com/global/en/products/chassis/colossus#overview Thermaltake Spedo Advance Package http://www.thermaltakeusa.com/product.aspx?c=1400&id=1829#Tab1 Thermaltake VA8003BWS http://www.thermaltakeusa.com/Product.aspx?C=1277&ID=1405#Tab1 Antec DF-85 http://store.antec.com/Product/darkFleet/df-85/0-761345-15238-9.aspx Corsair Graphite Series 600T http://www.corsair.com/cases/graphite-series/graphite-series-600t.html