mark_anderson_us

Hi All Bought one of the lime-tech servers a few years ago. just moved house and it's much closer to home theater and fans are WAY too loud. Anyone know of any much quieter compatible fans? Thanks mark

Thought some of you may be interested in this: http://blog.backblaze.com/2014/01/21/what-hard-drive-should-i-buy/

That may be it then. i'm copying ISO's and MKV's

is it worth spending that much on a cache. i'm getting > 100MByte/sec to a 5900 RPM drive, so we're approaching wire speed on Ethernet. Unless you have multiple network adapters AND the CPU could keep them going full tilt, I wouldn't think you'd see much benefit

Great deal with 3 year warranty. Snagged 4 for my backup server

U got a link. I'm seeing 139

Yes, they do have a shorter warranty (I believe 2 years but would have to check), but in my experience if a drive survives the infant mortality stage it will last for at least 4 years, if not longer. I do seem to recall something called the bathtub reliability curve for electronics and it generally holds true in my experience. This says that the likelihood of failure is significantly higher in the first 10% and last 10% of it's life. Naturally, we want the start of the end curve to be as far out as possible :-)

I'm with the dirtysanchez on this one. So am I. I started replacing all my older drives (mixture of WD Greens and older Seagates) with the ST3000DM001 3TB drives a year ago. I have been buying two at a time, over time - just in case this model turned out to be a lemon and to minimize bad batch problems. To date, there have been zero failures (probably shouldn't say that - tempting fate ). They run cooler than the drives they replaced and are much faster. If I get three to four years out of them, I will consider it a total success. I see the helium drives are just around the corner. By the time my next replacement cycle starts, this new technology should be proven out or not, reducing risk. Only 2 year warranty though, no? Realistically how much faster do you think parity calc is?

That is a pretty big assertion. If you cannot provide a reliabile source of data to backup such a statement then it is only your opinion. Plus, WD will not warranty desktop drives in a NAS/RAID. Of course, they need to figure out it was in a RAID/NAS

For 5400 RPM I use WD RED or Seagate NAS

Matter of opinion. Cost/TB isn't the only factor to consider. The lowest cost drives are good extra drives for backups; but for the drives I'm running 24/7 I want the reliability of a NAS-qualified unit. Agreed. I buy the cheapies for temp storage and stuff like DVR recordings, but my media lib and archives are on NAS-specific drives. Will be putting backup server (local backup of NAS) in garage and will use cheapies for that too.

I'm looking for 4TB WD Red or Seagate NAS. Already picked up a two 4TB Seagte externals for $119 and $139 each (after rebates and offers), but there just for temp desktop storage and ISO backups on desktop

Anyone got any idea where this link is? I don't see it anywhere on Amex site Found it under My Account -> Offers for You (mine is Amex Open card)

Anyone got any idea where this link is? I don't see it anywhere on Amex site

It's not, it's in general support: Lime Technology - unRAID Server Community » Support » General Support

Yeah, DVD's are a piece of cake. BD's are whole different kettle of fish

Since you apparently planned to re-rip anyway, I suppose that's not all that bad. But "... a few weeks ..." of time sure seems like a good case for backups !! Note that your comment that "... it was all movie ISO's and I'm going to start replacing those with MKV's, so would have to re-rip anyway " isn't correct => if you've already got the ISO's, there's no need to re-rip, you can simply create MKV's from the ISO [MUCH faster and easier than re-ripping]. In fact, you can set up a batch transcode to do an entire folder full of ISO's without intervention [i.e. you could do your entire collection if you wanted => obviously the transcoding would run for a LONG time, but it'd take about 5 minutes of "your" time vs. all those hours of "computer" time. I'm in the process of building a backup server (building new main server and current will become backup). I've never backup up my ISO's, because a) I have the original data on disk and b) it would have cost over $1000 to build a device, which would be in same structure as main server, so fire, etc. would wipe them both out. Currently trying to figure out how to get an environmentally acceptable enclosure in detached garage in Chicago (separate thread) Regarding making the MKV's, a few comments 1. I've yet to find a tool to do it all automatically. DVD Fab is closest, but still have to makes sure it's selected correct title (e.g. theatrical vs director's cut and correct sound (e.g. TrueHD or DTS-MA) 2. I don't have enough disk space to do them all at once. I'd want to check every MKV before deleting ISO. (Still deciding whether it's worth investing in more drive capacity to keep ISO's - current thinking is, it's not) 3. My time is same (give or take) even if batched, because of 1. Even doing over a few weeks, the net time is same. I still have to load every disk/iso (agreed it would be a bit quicker to load ISO if DVDFab supports this), make/check selection and add to queue. I accept, I could add 10 to a queue in ten minutes and that would take 3 days to do my way (1 every morning and two every evening), but there's no rush to get it all back (first world problem)

Good tip. Never occurred to me. For some reason I was thinking I could start the array without a parity drive

Thanks for reply Bob. It was a few hours into parity rebuild when I noticed. I assumes it would clear the parity drive first, so didn't bother trying any recover anything. As it was movies I'm going to rerip anyway, was no big deal, will just take a few weeks of putting 2-3 movies a night into my PC to re-rip

I accept it was my mistake, and I'm not looking to blame anyone. it was all movie ISO's and I'm going to start replacing those with MKV's, so would have to re-rip anyway. I did have screen shots of all config screens, but having several drives from the same manufacturer, means the numbers are similar. A few take always: The FAQ (which seems to be the manual), should fully detail what's going to happen and cautionary notes I think it's poor that there is no simple "Remove Drive" function in the UI (even if, in the background it disbands and recreates the array) IMHO, it would make sense for unRAID to put some kind of identifier on each drive (e.g. a simple text file) and warn the user if they assigned, for example, the previous drive 1 to drive 2 when starting the array. It's better to have a single nag when doing something as critical as managing the array's drives, than making the mistake I made.

Not at all happy. wanted to remove a drive from array, so looked in FAQ here: http://lime-technology.com/wiki/index.php/FAQ_remove_drive Says nothing about it forgetting all your drive assignments. Mixed up 2 hitachi drives when I reassigned them (one data and one parity), now its rebuilding parity on my data drive: so 2TB gone. It's shocking the FAQ says nothing about it destroying the config. With flexraid, I can easily split up a raid and reassemble using meaningful names, etc.

That explains it! Thanks

Searched everywhere and cannot find the download

Like I said, it's not critical that I can restore x-TB of ISO's from the cloud. I will eventually have a local backup and worst case I have the discs. I works perfectly for my critical data and meta data. If it works, it's a bonus, if not it'll cost me a few minutes here and there to insert a disc and make a new ISO and there's certainly no rush to do it.

I've never tested their restore, but it's there as an option. Even if it takes 3 months, it's a lot less work that manually re-ripping. I don't watch that many movies, so I could give my BD player a workout for a month or while everything is restored. Again it's a nice to have backup and not the key reason I use CrashPlan. Only having an unheated, uninsulated, detached garage in Chicago gives me little option for a proper local backup that would survive fire/theft/flood in the main structure. I've tried having a disk that I take to work and every week with the current backup. That lasted a month. Regards Mark