Jump to content


  • Posts

  • Joined

  • Last visited

Yekul's Achievements


Newbie (1/3)



  1. Ahoi hoi, Just wondering what's planned for Windows 10? Does the current Windows 8.1 build workf ine or will there be other issues to address etc? Trying to decide which system to load up for server, however with official release of Windows 10 in a month or so, i'd rather not reinstall everything in a months time! Anyone currently using it on the latest release with success? Or any reasons not to make the jump? Have Windows 8.1 so will be entitled to the upgrade, however don't much like the idea of loading everything up and THEN updating in a month (prefer a cleaner install). Anywho advice/help appreciated!
  2. Agree entirely about that Backblaze data, read it and laughed. I get what they were trying to do, but it was always going to be fairly average data from the outlay. Ok too easy, the 2x750GB WD Blacks sound like the go then, I might actually implement this regardless. Might be reading into this too much, but.... If I were to say download and want to watch something immediately and it hadn't had a chance to copy over yet, added it to a library to watch, and then after watching it was moved onto the proper section of Drivepool storage (archive? not sure on exact term sorry) you wouldnt end up with invalid path info etc right? This is all just magically done behind the scenes and the OS still thinks it is residing in the same place, it's just being shuffled round on the drives by Drivepoool in the background? I am 99.9% certain that's the case and feel silly for asking it but just want to verify this would not cause issues as it may happen every so often (working on/editing video files before they have been fully transferred to the archive drives for example). The file placement rules sound perfect for my local computer backups (only ~300GB total), will store those onto a seperate drive which is regularly cloned most likely. Thank you for providing some feedback of the drives in actual use, that's primarily what I was looking for. I understand the first iteration of these had fairly horrible error rates, but the ST8000AS0002 version of the drives fixed these issues correct?
  3. Ok, so ignoring the slow potential write issues, which as i've said likely will not affect me... And with the solution above of using "SSD Optimizer" shoudl negate that if it happens anyway. Again, fine, yep slow write speeds once the buffer/cache/whatever is used up. No problem at all, it's not being used in the middle of the night so it can sit there and re-write whatever it pleases in the background. My data usage will still not go near the rated 180TB in a year. I'd be lucky to do 20% of that. Read speeds are unchanged here, so no problems so long as I have something like SSD Optimizer to ensure the initial speeds are good (for example if I dragged 100GB off a USB drive, I wouldn't want it to slow down to crawling speed whilst USB3 still has tonnes of bandwidth available). As for the OS issue, I am not sure you're correct here. From what I had read it sounded like the major reason the Seagate Archive 8TB had such slow write speeds is because it DOESNT use the OS for processing. They are drive managed SMR, meaning you can use them with any OS, and similarly any enclosure. After all, that's what the Seagate 8TB external drive is, the archive drive just plonked inside an enclosure with a power/usb connector. I am not trying to discredit everything you say, I am considering it. It's just, you come across very paranoid in the way you present your information. It makes it difficult for me to put much faith into it, just because it has an air of "arghhhh the world is ending if we use SMR". Western Digital Reds in the 6TB variant are even more expensive here, the 3TB being the cheapest (about $150-160 per drive). But with only 8x3.5" bays I dont want to use anything less than 4TB drives to ensure I have enough room down the line should I ever get a half decent internet connection. Can appreciate the major con though, that these are early drives. And quite often they can be a bit "meh". Mmm lots to think about, unless a really nice sale happens...
  4. Ok, but just to give you an idea i'm after 8TB of usable space. I prefer to duplicate my data "just incase", as large chunks of it are photos/videos and I wouldn't want to lose them. So i'm looking at 2x8TB Archive drives. Cost: 2x8TB Archive drives $630 4x4TB WD Red drives $908 (Cheapest prices here in Aus right now, but still like ~45% more expensive for the reds) Then you have the extra power consumption (albeit minor, but this is a HTPC/content server specifically made for low power usage). Without being rude... Are you sure? What would be wrong with using them for data that changes often? Seagate themselves advertise a 180TB a year workload for them, which would tend to assume you are writing data more than just once. Oh this is super cool. I actually have two 2.5" western digital blacks (750GB) that would probably work perfectly for this, would it make it overly complicated needing to RAID them or do I simply attach them both, and then specify in the add-on these are the drives and it will treat them like an SSD-drivepool within the main Drivepool? And if one fails, i'd just swap it out and replace like the others etc? This would essentially give me maxed out 7200rpm write speeds I pressume, which would align perfectly with the Archive drives... Is it possible to use the files whilst this process is occuring? Sorry for all the questions!
  5. Hi all, Just wondering if anyone is using the new Seagate Archive drives yet? The 8TB options are extremely competitively priced here in Aus (were down to 35c/GB other day). The drives certainly have their limitations however, mainly that their sustained write speeds are horrendous. They have a cache which will work very well up to 20GB, then slowly degrade till ~80GB or so where it becomes atrociously slow; this is just the nature of the SMR technology being used in a consumer grade product. I personally have no qualms with this. Yes, it will take forever to copy to initially, and would be quite frustrating for RAID due to the rebuild times. However for someone who typically does a one time write and multiple read (ie WORM), they are fantastic value drives and aside from the initial population this issue would likely rarely occur. I usually only copy over batches of 10-20GB files at a time, normally batches off the DSLR. Looking at grabbing 2-3, but currently only have the currency for 1, so looking to combine with my existing WD greens for the time being. What I am wondering though, is would any of this interact strangely with Drivepool? Are there any limitations I should be aware of or need to address? In particular mixing the archive and green drives in a pool? I pressume the green drives will be limited somewhat by the archive drives if I chew through the archive drives cache. Anyways, any opinions welcome, just works out a crapload cheaper than purchasing WD red drives here in Aus. Cheers, Luke
  • Create New...