Jump to content
Division-M Community


  • Content Count

  • Joined

  • Last visited

  • Days Won

  1. Why does CRC validation not offer any real benefit? The documentation for Drive Bender says otherwise: Safety Enable CRC file validation: Enabling CRC file validation provide an added degree of security by ensuring events (such as physical drive issues) do no corrupt or modify any duplicated file. Important - Disabling this option means that files are validated by file size and time stamp only. Having this option enabled ensures any duplicated files validated against the original is done using a CRC value, however this can impact the time required to validate a file.
  2. Hello, I have a 4GB Drive Bender log folder (C:\Program Files\Division-M\Drive Bender\Logs\). The largest logs have a prefix of "HealthMonitorAudit" and are about 325MB each, e.g. *C:\Program Files\Division-M\Drive Bender\Logs\HealthMonitorAudit-{395DBF95-A9E9-4FB5-9694-3BCAC3BC9BD1}-151121210234.csv*. Logging level is set to None and I'm using version The log files are usually created about 3 days apart, and some of them were created recently so they aren't old logs left around from some time when I had logging turned on. It's not urgent that I delete this folder but I was wondering if the size of the log folder was normal.
  3. I swapped out the underlying RAID/HBA card that I was connecting my HDs to. Upon reboot Windows sees the hard disks in Disk Management and the one that had a drive letter assigned is viewable in Explorer. So everything is still just fine but Drive Bender isn't creating the mount point. If I go into DB, the mount point is there but it is stuck saying "Overall pool health - The server is creating mount points..." and if I try to change the mount point drive letter I get the error "the mount point name cannot be changed while the existing mount point is attempting to mount." I should note that I'm not using any RAID functionality on the RAID cards. I am just using them to connect HDs. Is this an operation that takes a long time and I should just let it sit? Or is something wrong?
  4. Anthony from support was able to help me out. It looks like what happened is: I got Drive Bender to detect the pool but it didn't create a mount point. The files are tied to the mount point, and so the new mount point I created did NOT contain my files. Here's what Anthony said: So that's what I did: mounted all the drives, every drive had two folders with names that were GUIDs, the same two GUIDs for every drive. One folder had all my files and the other did not. I renamed all the folders that did NOT have my files from <GUID> to <GUID>.bak. Then I renamed all the folders that did have my files from <WRONGGUID> to <GUID>. After rebooting the server all my files were present on the Drive Bender drive safe and sound and all looks good. I'm not sure why I ran into these problems in the first place but I'm glad they're all fixed. Thanks, Anthony!
  5. Yup that's how I added the pool in the first place actually, but the pool is empty and that option isn't finding any files.
  6. Nope I deleted the automatically created pool. Also, it took all my hard drives and put them in the pool, I didn't add them. It is partially reporting the correct usage stats: 6.2TB free, 0TB used. It says non-pool used: 12.9TB. So my files are there, just not in the pool. Not sure what to do now.
  7. I installed Windows Server 2012 Essentials over WHS 2011 and I'm having nothing but trouble. Right now my issue is that the existing pool was discovered by DB, but there are no files on the drive and "Repair this pool" does nothing. Has anyone experienced this? I have a support ticket open but they might not be able to get back to me until Tuesday which would suck, so I was hoping someone here might have had experience with that problem. I tried "Repair this pool" which immediately reports back that 0 files were discovered. For others, here are some other issues I hit that might be helpful: 1) Upon reboot, my DB drives were set to "Offline" in Disk Management, so nothing could see them. I had to right-click each drive and "Online" them. I then manually removed the drive letter from each drive. 2) Upon initial boot and installation of WS and DB, DB couldn't find my existing pool, even after I onlined the drives. I'm not sure why. I came back to the problem a day later and rebooted the server, and it immediately was able to find the pool via the "Restore pool(s) from connected drives" option.
  8. I'm hitting the same issue, although my drive is stalling for 5+ minutes not seconds. I have a support ticket open so hopefully they'll help with that, but I'm not expecting much since it is Thanksgiving after all.
  9. That makes sense. Can anyone confirm the setting is customizable, since revingineer isn't sure? Sent from my RM-893_nam_att_206 using Tapatalk
  10. Hello All, I'm looking to improve the performance of my DB array, which currently doesn't come close to saturating gbE since I only have mechanical disks. I thought I'd start by upgrading to v2 and adding a faster drive as a Landing Zone. I mostly use the server only over gbE, so saturating that would be good enough for me, although I sometimes use the array locally and will eventually upgrade to 10gbE as soon as its feasible, so faster wouldn't be wasted. Is there anything that would definitely saturate 1gbE, even for random small writes, and is either cheaper and/or larger than a 1TB Samsung Evo SSD? That SSD is overkill in terms of performance, but also expensive and small. Mechanical disks are much larger and cheaper, but not fast enough to saturate 1gbE. Should I just get a smaller SSD on the assumption that DB will be balancing the files off quickly anyway?
  11. The machine just blue-screened again 30m after the first one. I have filed the ticket but I'm really freaked out right now...
  12. I just got exactly the same issue with I didn't upgrade: this was a clean install. I just migrated from Intel RAID-5 to Drive Bender. I'm not happy. Going to file a ticket now =\
  • Create New...