Jump to content


  • Posts

  • Joined

  • Last visited

TAdams's Achievements


Newbie (1/3)



  1. Hello, When performing tests with as ssd I noticed that the pool shows Bad and is not aligned to 4k Is this normal?
  2. Christpher, First of all, I thought I had already posted this, so it is late! Thank you for your reply, I had an older 2TB WD Black that I designated as a Cache drive which allowed me to transfer the file. I had previously attempted to increase the SSD Optimizer Options "Fill SSD Drives Up to" (set to max) which did not work. This would be rare and I have set an automatic split to prevent these large files in my automated backup settings for the future. Perhaps it would be good option to have an option to bypass placing files on the SSD if file exceeds drive size? I was about ready to pull the trigger on 2 new 250 GB SSD's for temp transfer but am now thinking that may be to low a capacity (obviously depending on file sizes and future file transfers). This would give me, when I have completed adding all drives to pool, 2 X 250GB SSD Cache drives and a single 1 TB SSD Cache Drive not counting the OS SSD. Regards, Tom
  3. Hello, Does the size of your cache drives (I have SSD's set as cache - largest is 1TB) limit the file size that you can add to a pool? I have tried 3 times now to transfer a 1.01TB file to my pool and it has failed at vatying percentages to complete the process. This last time I waited for the SSD to clear and started it as well as bumped up the fill the drive to X% option. Is there a mechanism for bypassing the cache when the file is larger than the cache size is? or perhaps an option somewhere I may very well be missing? Regards, Tom
  4. Hello, I am wanting to provide hot swap capability and get my storage devices off of my current motherboard storage controller. I have done some searching and ran across a few controllers but having little experience with these cards I thought I could learn from other peoples experiences. The 2 cards I have in my shopping cart are the SAS9211-8I and the LSI Logic SAS 9207-8i at roughly the same price, I do not mind spending more if need be and having raid in the future may be a good option, but at this time I do not have plans for a raid array. I have seen where some of these cards are being flashed with firmware but I am not clear on what the advantage(s) is/are or whether that would apply to my intended usage. My current system is as follows: Case Silverstone Technology CS380B PSU Power and Cooling Silencer MkII 850 Watt Windows Server 2016 Standard Intel Xeon W367024 GB Quad channel memory Gigabyte G1 Sniper (using PIC-e Intel Gigabit NIC) 4X Seagate 8 TB Barracudas 2X Corsair GT 90GB SSD (OS) 1X Mushkin Reactor 1TB SSD (Cache) 1X Intel 250GB SSD (Cache) 2X Seagate 2 TB Barracudas (Old system being phased out) 2X WD Black 2 TB (Old system being phased out) Future Plans of 4X Seagate 8 TB Barracudas or other and two 500 GB SSD's to replace the 2 cache drives (1 which belongs in my main system). My intended use is document mirroring (for redundancy), Video, general storage as well as a large collection of photographs, CAD data, system backups and movies. If I have folder duplication set to 3, would 3 cache drives be required for on the fly duplication? Between the motherboards storage controller and the SAS controller which would allow the SSD's to perform more efficiently? I would really appreciate your input, thank you! Regards, Tom Pardon, I meant to post this in the Hardware section!
  5. First of all, I would like to say thank you all for taking the time to reply and or answer. I currently have an SSD which Windows Server 2016 Standard which has my shares as well as drive pool installed and I have gotten pretty far along in the setup and is pretty close to how I want it. Again, I realized I was missing the "sever essentials" backup system and I installed that. I believe the issues I was seeing is from the way the two flavors deal with file permissions. I initially had them set with Standard and when I added Essentials it added many permissions (per user and or group) to each file. Each mechanism allowing/disallowing rights based on that systems scheme. Which meant I had some doubled up and files that I shouldn't have access to - I did and vice versa for others. In short it seems like the most practical way is to perform a clean install and use which ever system to create and administer the shares - not both or a mix and match of both. I don't think this was a Drive Pool issue at all, simply put it was my lack of understanding of how the two systems apply user permissions. In my first install, I tried Windows Server Essentials and had backups running but did not like the strange folder structure, which is why I tried downloading and installing Standard and added the server role. I believe I could live with it, but the current look is so clean and that of course leaves me without the previously mentioned backup solution. I have checked out Veeam which looks VERY promising I appreciate the suggestion Jaga! I hadn't realized MS had planned on removing the ability to add Essentials Role in the future Umfriend, is there anything in particular you are looking for in WSE 2019? Thank you for the links Christopher, those are put together better than the tidbits I located in my searches. Currently I am trying to decide what I want to purchase, Windows Server 2016 Standard, WSE 2016...They are roughly the same price on Amazon and it seems like the Standard with provide greater flexibility for the future. I am most certainly getting drivepool! Thank you all again! Regards, Tom
  6. Hello, I am making a large jump here, moving from Windows Home Server V1, to Windows Server 2016. I have been taking some time during trial periods of installing various NAS server OS's. The 2 that bring me here are Windows Server 2016 Standard (Windows Server 2016 Standard with the Essentials Roles) and WSE 2016. All of which are supported by Drivepool and in my testing I have been very impressed with Drivepool. My 1st build was without essentials and I soon realized that I didn't have the backups that Essentials provided. So I created a fresh install on another SSD, (pulling all of my drives) and after installing Windows Server 2016 standard immediately installed the Essentials as a role. I then installed Stablebit Drivepool and a second drive, and created my Storage pool using just the single drive for testing. In the Essentials Dashboard>Server Folders I used the move folders command to move the Users, Folder Redirection, etc., etc. to the storage pool I created. I then made a few test user accounts through the essentials dashboard at which time the User folders were automatically created in the Users folder (Users/Tom, Users/Test, etc.) During testing of the permissions from a client machine, I found I was able to delete the User folder (Users/Tom, Users/Test) I am not able to delete Users. And this is not what I would expect, and I am using many tools I am not familiar with, so please keep this in mind. Does the Move operation into the Drivepool, cause some permissions issues? Or is this behavior caused by the way I am using Windows Server 2016 Standard with the Essentials Role added instead of using Windows Server 2016 essentials. I have run across posts from many people coming from WHS but I have not ran across post describing the issue I am seeing. The items I value in my new home server are as follows (no particular order) Pooled drives Folder duplication to protect against drive failure (more flexible than raid solution). WHS V1 type client backups File shares for movies, music, work documents, user files, software, etc. The ability to place a HDD into any Windows PC and have immediate access to my data in the event of a server failure. The reason I am listing the criteria for my build is that perhaps Windows Server 2016 is overkill and it seems to have a steep learning curve. Perhaps it's time to bypass the Windows client backups I am used to and use alternative methods like ToDoBackup or Backupper to automate backups. This would allow me to use Windows 7 or 10 with Drivepool as a file share. I didn't expect that Windows Server 2016 would be easy, however, I have been using computers and different operating systems as well as servers for decades and it seems like it is overly complicated (multiple layers of permissions, forced folder structure for shares, automated tasks that only half-ass the basics). I digress, because obviously I must be doing something wrong as this is a new OS... Or am I? I would appreciate your input and guidance greatly, Regards, Tom
  • Create New...