Search the Community
Showing results for tags 'Partition'.
(Edit: this issue has changed, please read the last posts for more relevant info. This ended up being primarily an SSD Optimizer issue) 1st of all, thanks for this great program & the amount of customer support it has. I have learnt a lot about these programs (scanner & drivepool) from reading many forum posts but unfortunately with 7 days left on my trial I am unable to find an answer to this & can't seem to solve it myself. Anyway, short story long... I have set some file placement rules to move small regularly accessed files to the pooled C: drive since it does not spin down. I decided to use the SSD Optimizer on a HDD (C:) to stop multiple small writes throughout the day on drives that have spun down & instead rebalance at night. But before I installed the plugin I read that it will evacuate the drive chosen as SSD unless I disable the "unless the drive is being emptied" option, but I'm concerned that if I disable that option then if Scanner detects a failing drive it won't be able to evacuate the drive to other drives (I have specific drives assigned to specific folders). So instead I repartitioned the C: drive to make an extra 50GB partition to set as the Cache, but when I tested it, it just wrote directly to one of the other HDDs (one that was not assigned to the location that I placed the test file in!?). After several attempts at trying to figure out what I was doing wrong I disabled the SSD balancer & assigned a rule to place files in a specific cache folder onto the 50GB cache partition, but when I dropped a file into that folder it just saved it to an incorrect disk again even though I checked the option to "never allow files to be placed on any other disks"! For the record, the 50GB cache is a logical partition, I currently have no duplicated files & real-time duplication is disabled. Also the incorrect drive that is being written to is only assigned to a "backups" folder, so shouldn't be getting any other files. If anything, the file should have gone to my "other" drive as it has a placement rule of "*" at the bottom of the placement rules. Thanks for taking the time to read my lengthy post. Sorry that I didn't simplify it, I just wanted you to get the full story so we can hopefully get to the bottom of this. Thanks, Scott
OK, I'm positive this has been spoken to before, I did find several posts similar but none that put it all in the same thread. My machine is running WHS 2011 and StableBit 22.214.171.12485. I have 4 internal drives connected to the motherboard (SATA) and 1 USB3 drive (2 GB) attached to the pool. There are 2 additional USB drives attached, 1 for C: drive backups and 1 as a (manual) mirror for a few folders in the pool. I'm getting ready to remove two drives (1 TB each) from my pool and install 2 new 4 TB drives, What is the BEST way to handle this? Microsoft "server backups" are not an issue for me. I do use that function to backup the c: drive to a dedicated USB drive but don't run local backups on the pool drives. I consider the built in duplication plus an offsite mirror of the pool to be sufficient. I hate the thought of having to recover from the cloud (would take weeks) but hope to never have to do it. My plan is to slap the new drives into the hot swap bay of my Windows 10 machine, format them GPT with 2 equal sized NTFS partitions. Once that is done I'll run an extended SMART test and assuming there are no errors install into the server and add the partitions to the pool. Once the pool balances I'll do the 2nd drive the same way. ---->> Questions <<----------- Is there a better plan? My research indicates that WHS is fine with GPT and I like the extra protection against MBR failures it offers. StableBit shouldn't care one way or the other should it? I don't HAVE to partition at 2 TB but if I change my mind about "server backup" doing it that way keeps this option open. Is there any downside to partitioning the drives (aside from the microscopic capacity decrease)? Thanks in advance for your advice and thanks for an awesome product. I'm 34 months in without a single issue. Flawless work guys!!
Question: What should I do with a second partition of a 3tb drive that is in my pool? First off, here is my pool 3 drives, 2, 2tb drives, and one 3tb drives. I’m just not sure of the best way to use a 3tb drive in the pool, where I rely on duplication as a form of saving data if a drive were to fail. I hope this makes sense…. Here is my concern. DrivePool duplicates my duplicated data among the same 3tb drive within the 2 partitions not knowing it is the same drive, now if that drive fails I will lose the first and second copy of data. Thanks in advance.