Jump to content

runewa

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by runewa

  1. I have a follow-up question to this. This is (part of) my set up: The markers for my SSD (drive 2-5) correctly shows the placement limiters at 90%. But why do my archive drives (2-2, 2-4 and 3-1) say 0%? From the settings in Options I would expect these to show 95% Or am I not getting this correctly?
  2. Is there any way of hiding drives from the list of non-pooled drives? I'd really like to be able to hide my C:\ -drive and all of my parity drives as well, as I'll never use these in my pool. Like a right-click and hide option? In that case, there should be an option to un-hide a drive if I want to swap a parity drive with a pooled drive for some reason later on. (Maybe this post belong in a suggestion section somewhere?) -runewa
  3. +1 I've been playing around with the same scenario/thought lately. Either by script, or a configuration setting in the UI. Or both
  4. Christopher, Any updates on the official support of Scanner and DrivePool on Windows Server Core? The reason I ask is that I'm about to set up a Core server, and given that the thread is almost 3 years old, I thouht I should check in with you before I get started Regards Rune
  5. Happy new year! In the past, when installing a new OS on the same PC, I´ve always had to rescan all drives, as Stablebit doesn´t recognize the drives as being previously scanned. Is there a way around this? If this is a new feature request I´d really like to see this implemented as a cloud feature based on the drive´s serial no. (or other drive id) and the licence no. -rune
  6. Is it possible to somehow manually start the DP-service to enable DrivePool i Windows Safe Mode? I found this solution on how to enable TightVNC in safe mode: REG COPY HKLM\system\CurrentControlSet\services\tvnserver HKLM\system\CurrentControlSet\control\safeboot\network\tvnserver /s /f Don't know if this can be altered to fit the DP-service?
  7. I'm running Windows Server 2008R2 with version 2.1.1.561 of DrivePool and version 1.0.3.5 of the SSD Optimizer. I disabled all other balancers, but that did not solve the problem. I'be uploaded the logs and named them 1896-ssd-optimizer-placing-files-on-archive-disks-not-the-ssd.rar. The filed I copied to the pool was actually placed on my P:\ -drive, not the D:\ -drive (which is marked as the SSD-drive). The file was indeed moved to the correct disk/folder once the balancing was run manually.
  8. I'm seeing the same behavior on my system. Running the 556-beta. I've uploaded my logs and named the file 1626-partially-deleted-clouddrive-amazon-s3.
  9. The checkboxes were already checked as described above.
  10. I've created a cloud drive, included it to the pool, and used File Placement to make all files in a certain folder be stored on the cloud drive. I've installed and configured the SSD Optimizer plugin, but whenever I copy a file to this folder on the pool, the files are not stored on the SSD, but instead stored on one of my mechanical drives (not marked as SSD, of course). However, the files do get moved to my Cloud drive once the balancer runs. Any pointers?
  11. 1. Run diskmgmt.msc from a command prompt (or the Run command) and right click on the disk you want to disable the drive letter from. Click on Change Drive Letter and Paths and hit Remove and then OK 2. You can (in theory) use the same approach to change the drive letter of the pool as well, but I'm not sure if this will cause any unexpected problems for the DrivePool-app -rune
×
×
  • Create New...