Jump to content
Covecube Inc.

Philmatic

Members
  • Content Count

    24
  • Joined

  • Last visited

  • Days Won

    1
  1. I'm running a Windows Server 2019 VM on VMware ESXi, 6.7.0. The host is a dual proc E5-2670 v1 whitebox. The VMWare datastore is an NVMe disk (HP EX920 512GB) and the guest VM is using the VMWare Virtual NVME controller device driver. The smart data coming from the virtual NVMe driver is... interesting. I'm not expecting it to work, I just figured Alex may want some denug data so it can be fixed. Attached are my test details.
  2. Are you asking if DrivePool is compatible on a Hyper-V guest running on a Hyper-V host? If so, yes. I run it this way and it works fine, you just have to pass each disk individually and the guest OS (With DrivePool) sees it just fine. In fact, I went form a full physical setup on Server 2012 and Virtualized Server 2019 on Hyper-V, passed all the disks (Was a huge pain, not being able to pass thru controllers is a huge PITA, VMWare FTW here) and DrivePool picked up the entire pool (32 disks) within a minute or so and that was it. Or are you asking if DrivePool is compatible with the Hyper-V Hypervisor itself (Either in Hyper-V Server or Server Core with the Hyper-V role) as in you want to pool drives inside the Hypervisor and present them as large disks to guests? I've tried this, and it DOES work, but it's not a good idea. DrivePool is not a traditional RAID technology can isn't well suited for large random writes, it's just not recommended. It's best to pass the disk individually and let DrivePool on the guest pool everything together.
  3. With Windows Server 2016 RTM right around the corner, I am re-evaluating my server software and looking to upgrade whenever possible. Do the improvements in DrivePool to support Windows 10 extend automatically to Windows Server 2016? I would imagine they would considering the shared kernel, but I just wanted to make sure. Has this been tested?
  4. I'm over here sitting on 32.7TB like I'm king of the world, lol.
  5. I wouldn't recommend Alex spend any time fixing this as even Microsoft have given up on the Windows 8/8.1 way of syncing OneDrive. Windows 10 will use a separate executable that syncs directories, like the client for Windows 7 did, versus use the junction points and symbolic links that Windows 8/8.1 uses. As a user, I MUCH prefer the Windows 8/8.1 way of doing it, but I guess there are issues with it under the hood.
  6. The defragger built into Windows Server 2012 can defrag multiple disks at the same time, just select them all like you would select multiple files and hit Optimize. Worked fine for my 24 drive server, it did all 24 at the same time.
  7. Yes, totally. I have a 150mbps downstream connection running 50 or so torrents at a time and DP has absolutely no issues with it. I do two things though, to be safe: I disable duplication on the folder I download to, it's just not needed I increase the cache on uTorrent and tell it to use up to 1GB of my System RAM for write caches. I have never seen "Disk Overloaded".
  8. Yep, I did exactly this. You don't even need to pull the drives, but I do just to be safe. Make sure you don't forget to release the license on the old machine before formatting. Otherwise you will have to open a ticket with support so they can release it on their end.
  9. Steps #1, #2, and #3 will work just fine. It's that simple. Drivepool with recognize that your folders are duplicated and will already know what to do.
  10. That's all you need to do, it'll work exactly like that.
  11. I've always done a "Reinitialize disk surface" using Hard Disk Sentinel and it has never failed me, it always forces the hard drive to reallocate the bad sectors. It's not free, but well worth the cost. I expect any software that can write zeros to the entire drive (Low level format) would work too, I have never been able to get chkdsk to work to fix the sectors.
  12. .copytemp files are the temporary files DrivePool creates as it's copying the file. It will disappear when the file has completed duplication.
  13. Doing it in reverse order gets you what you want, mark the bad blocks unchecked, then mark the unchecked blocks as good. The entire drive is then considered good. You should really rescan the drives though, if your wipe did not reallocate the bad sectors then you are still in danger of losing data.
  14. Well, if Task Manager isn't showing DrivePool taking up that amount of memory, then it's not. Using the latest beta, I'm seeing 33.9MB of memory usage for the UI application and 35.2MB for the service. That's it, it is a ridiculously small amount for an application to take in 2014. Not to mention the UI is not running all the time. Overall my server is using 2.2GB out of 8GB, this is Server 2012 R2 Essentials. I would look into the Resource Monitor to get a better idea of what exactly is going on.
×
×
  • Create New...