Traxxus

Both those are what you want.

Can you access it when you type in the location of it (browse to disk2, replace disk2 in address bar with disk1)? Check to make sure it's being exported and security settings under the settings page for that disk.

You shouldn't need to set the static IP at the server itself, use address reservation on your router instead. It will reserve that address for that particular mac address, and always assign it to that computer. On my router it's under Advanced>Setup>LAN setup. Click add, choose the machine, set the IP, and it's done. I have everything using static IPs for ease of use, and got tired of Windows bitching about it and screwing it up now and then.

I don't think that's the right cable, unless your case uses backplanes. If you are connecting to SATA such as HDDs directly or a cage with SATA ports, then you want something like this, SAS->SATA. http://www.monoprice.com/Product?c_id=102&cp_id=10254&cs_id=1025406&p_id=8186&seq=1&format=2

I think disk2 and 7 will be a loss. Ideally you would have rebuilt disk2 on a new drive and this wouldn't be happening, or you would have rebuilt disk7 on a new drive, and your option now would be to attempt to use the original disk7 to rebuild disk2 again. I don't think that will be possible since you already started a rebuild on disk7 and it's contents are compromised. Disk7 seems fine from the smart reports so it's likely there was never anything really wrong with it. I have had a couple red balls, but they ended up being a loose connection.

I'd be looking at hardware first, not the hard drives. Cables, enclosure, etc. Smart reports can help find out if it's a bad drive. Is there no syslog on your flash drive?

You can disable the parity drive, it will be invalid since it won't be current, so it will do a parity sync when you start the array with the parity disk assigned. Won't hurt anything though, it's the same thing it would have done if you had just transferred the files then enabled parity. You shouldn't try to stop the array while actually transferring files though.

Decided to check this out after reading the v6 Unraid changes, it's very slick, modern, and easy to use. Wish I'd known about it sooner. I also vastly prefer the dark theme.

Do you have your split levels set correctly? Sounds like it isn't the renaming of files that's the cause, it's just causing you to notice there are multiple folders.

I'm seeing it on the shares page. I think Orange means there are files on the Cache disk for the share. By that definition a cache-only share will always be Orange. You're right, I decided to install Dynamix, and it says on hover, that it means "Cache contains files". Small distinction, but it does explain it.

Is this normal? Orange ball means it's a share that has files waiting to be written to it from the cache drive correct? So why would a cache only share (apps/sabnzbd, CP, NZBDrone)have an orange ball?

Can't answer most of those, but changing the hardware is easy, changed all my hardware a year or so ago, just take a ss of the drive assignment page so you know what drive goes where just in case. Just changed the hardware, stuck the USB in, changed BIOS settings, and off it went.

On the Unraid flash drive, in preclear_reports folder.

Yes, I have a SASLP with 3 6TB Reds on it, works fine, nothing needed.

That's only for drives less then 2.2 TB. It's ignored on larger drives, even if you do attempt to use it. Thought I would add this for those who haven't precleared 6 TB drives yet, or to add to the benchmark section of the wiki. WD 6TB Red (WD60EFRX) Preclear Successful ... Total time 54:43:12 ... Pre-Read time 13:55:07 (119 MB/s) ... Zeroing time 12:46:33 (130 MB/s) ... Post-Read time 28:00:32 (59 MB/s) Preclear Successful ... Total time 54:50:58 ... Pre-Read time 14:02:36 (118 MB/s) ... Zeroing time 12:46:51 (130 MB/s) ... Post-Read time 28:00:32 (59 MB/s)

It's not a good idea to make major changes like that all at once. Should have done it one step at a time, making sure there were no problems along the way, that way you know what caused what. Sounds like you did it that way this time though, live and learn.

Sounds good. I checked out some of v6 and it does seem to solve most of my gripes with Unraid as far as disk monitoring/health goes, but we'll see. If it isn't acceptable I'd be up for starting a bounty for implementing something, because I don't think it's good enough as it is, especially for NAS software. Waiting for a drive to fail and using rebuilds to "fix" it doesn't seem right, that should be a last resort, not the standard. I'm hoping it will at least track the common errors and display them in the gui similar to Unmenu, have a way to initiate (and schedule) smart tests/parity checks, and notifications by email at least, if not by growl or something similar.

http://lime-technology.com/forum/index.php?topic=2135.msg16679#msg16679 It generates the smart reports, saves them in drive specific folders, and creates a summary. It does not start the tests, do diffs, or notifications.

I've never thought this. In fact over the course of hundreds of hard drives I've owned, it's been useful to predict a problem or a potential problem in recovering. While I'm no blackblaze, I've had hard drives with SMART since it's inception and it's predicted failures and saved my butt a few times. The 5 parameters mentioned in the article is what I look for. Plus any FAILING NOW attributes. Mostly increasing or high amount of reallocated sectors and pending sectors > 0. and uncorrectable sectors. I also do SMART long tests periodically. If I get an LBA error, you know there's a problem reading the hard drive. Any logged problem reading any sector could equate to the inability to rebuild a failed drive on the array. Each of these attributes should be reviewed periodically with a periodic smart long test to insure your array. How often do you do the long tests? I use Joe's script to save smart reports regularly (I like how it sorts them into their own folders by drive and includes the date in the title), and try to run short tests before the monthly parity check, but long tests I tend to slack on. I just ran them on all of my drives because some are getting on 5+years old and 50k+ hours, and I'm adding new drives so I've been watching them a bit more closely. I wish smart monitoring/logging/notifications were more integrated with Unraid though, similar to MyMain, it should be.

Oh I also wanted to add something else about the cache drive that I forgot I setup, since you seemed a little worried about the redundancy portion. You can enable or disable the cache drive for any share independently. So for Movies, TV, Music, cache is enabled. For Backups, Photographs, Videos, etc things that I desire to be protected, I just create a separate share and disable the cache drive for it, and it will copy directly to the array bypassing the cache drive.

This part.

Yep. Yeah it won't affect the array or other drives in any way, just the potential to lose what was on the cache drive. I've never seen it as a big deal, only things I could lose in that event would be stuff I could easily get again. Important things, I certainly wouldn't move it to the server then delete every other copy anyway. I don't know. Probably just bypass it like bkastner said, though I'm sure someone can answer definitively. Copying directly to the array isn't a bad thing, just slower since parity needs to update in real time. Speaking of which, when you are adding your drives, and copying data, you may want to wait to enable your parity drive until you have copied everything over and added all your drives. Without a parity drive adding drives will be instantaneous, and copy speeds will be roughly double what they would be with if the parity drive is enabled. Then you can enable the parity drive and will do it's thing from there.

Hmm. I planned for this to be my parity drive, but not being able to see the differential bothers me a bit. If it were a data drive I'd probably be okay with it, but I think I'll just wait and not be hasty. Adding the drive cages and cabling is the time consuming part which I can still get done, I don't need the extra capacity yet so no need to rush it. I think I'll let it finish, and if the differential isn't available, then I'll just add the bays and cabling, then I'll have space to preclear all the drives at once, and I'll just redo it on that one at the same time. And next time I'll earmark some of my upgrade funds for a UPS. I'm pretty sure a brown out is what killed my last power supply a few months back, but I was away so not positive on that.

Yes, that's one of the benefits of Unraid, that a spot isn't taken up by a HDD just for an OS. Cache drive is still handy, it will have faster write speeds than the array itself does since the parity drive is out of the equation. Also good to have a place to install addons like sabnzbd, couchpotato, torrent clients, etc. Installing that kind of stuff to the thumbdrive will wear it out fast. How big a cache drive depends on you. Mover will automatically move everything off the cache drive to it's proper place (the usage of the cache drive is invisible to you) every night, default is 3 am. So however much you would add in a day, is how big your cache drive needs to be. Mine is an old 300 GB Maxtor, though I've been thinking about going with a SSD since I could mount it outside of the hotswap bays and gain another slot for a HDD. Downside to cache is that since it outside the protected array (remember that's why write speeds are so much faster, since parity is not involved), if the cache drive fails, it will not be able to rebuild the drive like with the other drives, and you may lose that data.

I had my preclear interrupted (power outage) during the post read stage. I verified it does have the preclear signature, and then initiated just a post read session. Is this "okay"? I would just do the preclear over again but it's a 6 TB drive, takes a while, I have 3 more to preclear and I have some hardware changes to make this weekend. Got some new drive cages + cables to max out my SASLP so I can preclear more than one drive at a time, only had one slot left, and less than 500 GB of 12 TB left.