JoeS

Hurray, the `automount` helped! Thanks guys!

Hi, I came here to ask if something changed so DP can't see unmounted drives anymore. I had all my drives unmounted for years, but now it doesn't work anymore. As soon as I assign volume letters and restart the service it sees them again. Then after reboot and unassigning them, it forgets them again. The only change on my end is, that I cloned my system disk and use a bigger SSD now (unrelated to DP). Is there anything I can do to get this feature back? Thanks

uninstalled .896, installed .913, everything works

Hi, true the balancing cleaned up over time. I have 2x 4TB an 1x new 6TB. but what initially triggered me to look closer at this was, that the pie chart ratios are wrongly displayed. unsuable is 4tb, free is 5tb. so unsuable<free but in the pie chart the unsuable (gray area) is way bigger than the free area (white).

haha, yeah, been there, done that! at least you could fix it quickly, going to give it a try when I have to do backups this week.

Thank you for the reply

Thanks for the reply. Uninstall I got to work, I even could install .896 then. Which I then uninstalled also. What I couldn't to is installing a clean .907 because a) it couldnt start the service b.) if service started manually, the service threw an error that it couldn't find CoveFS (service I suspect)

Hi, today I installed a new 6TB to my 8TB pool. While balancing I looked at the pie chart and it seems it's ratios are wrong. Unusuable for duplication (~4TB/gray) should be smaller than free space (5TB/white). Also actually there are no other files on this hard disk than DP, so unusable for duplication is simply wrong. Later after balancing it corrected that accordingly. But measuring was already done at that point when I took this screenshot, so it still should not be wrong Thx

Hi, today I tried to update from 2.2.0.906 to 2.2.1.907 (so I could extend my beta license for another 30days) and it seems the installer may be broken. 2 (maybe related) Problems: First the update to .907 didn't stick (also later with trying to update from .896, it also didn't work). When installing .907 after deinstalling and deleting folders in `Program Files`, it can't start the service (error: couldn't find CoveFS). Second, when uninstalling .906 it doesn't actually delete files in `Program Files`, after an restart DP just opens again, just like I didn't uninstall it. The entry in "Program and Feature" is gone though. So to really uninstall I have to remove the files in `Program Files` manually I could upgrade from .896 to .906 though. Thx

Thx Drashna, uploading troubleshooting logs right now. Disk is an intern one, afaik it's not failing/disappearing intermittently. Also I see this errors every time and always the same file path.

And the files the service can't find, I can still normally open via explorer?

What I don't get, HarddiskVolume15 is neither the corrosponding disk15 or volume15 in diskpart. Is the intern numbering different from the windows one?

Sadly it's still not working. In my frustration I even just deleted big temp data I didn't need anymore from the hidden drivepool. So now it's just about ~7GB, but it's still not moving. I will attach a typical log from yesterday. Another question, what can I do about this error: $filepath\$filename is something I substituted for the real thing, because these are kind of sensible. This filepath has nothing to do with deleted tempdate I wrote above, btw. Thx DrivePool.Service-2017-11-26.log.zip

Thx for still trying to figure this out. The drives are about 86% full, the ssd optimizer settings was on 90% OR 100MB. I now set it too 100% or 500MB. I will get back to you, if it still helps, but I suppose this wasn't the issue, unless it calculates the to be moved filesize into the limit?

sadly still not happening

np, already did, they are in the imgur album in the top post

Is there something else I can do? Like post or a log or something?

The only option is re-balance, which it does for a few seconds or so, than turns back to red as before can I just move the stuff from the hidden `PoolPart.d834d980-c73e-4e2a-80c0-ff60812d6eee` folder on C: into the `Poolpart.numbers` folder on one of the archive disks? or will this mess up drivepool somehow? And it only wants to move stuff from A: anyway, even though there is nothing there to move...

Thx for the reply. It doesn't give me an issue though:

Hi, I'm using Drivepool (Beta) since 2015, recently bought it because it's a great tool. But nowadays I have problem, there are some data hogging my SSD space. I read all the stickies and it seems Drivepool want to move my data but it somehow can't? I will post some images, hopefully somebody can point me into the right direction, thx! A: & C: are my SSDs, every fileplacement rule is the same as the first one! Imgur Album with more screenshots (imgs are to big for uplaoding?): https://imgur.com/a/AnJy9

Hi, how do I know if it is numbered? When it is mentioned in the changes.txt? Thx, Joe

I just uploaded them to the "StableBit DrivePool 2.X File Submissions" Dropbox form

Hi, it seems since updating to 763 I got 10 of BSODs in the last 20 Days. All are IRQL_NOT_LESS_OR_EQUAL and with ntoskrnl.exe as the Adress in Stack. I also just opened a minidump file with WinDBG and used !thread, here covefs is mentioned a few time (with not much else). I recently transfered some data (1-2TB) from another drivepool to a an older one. I just updated my drivepool to 773, but I figured you guys maybe want to to look into it? Should I upload my .DMP files? If yes, where to (it's 741KB big)?

I just did that. It worked. Yeah! Also another little Bug Report. If you press ESC in one of the config dialogs, it still accept the changes you made instead of reversing it. Like it would if you pressed Apply. Found the counterintuitive

yeah, I'm able to see the data there. should I just move it out of the hidden poolpart folder and then remove the disk in drivepool and readd it? Yes, I have moved/copied data to N:, exclusivly, since I haven't give the other disk a drive letter, I just use it as a big homogenous pool without duplication because it's just suppose to be the backup of the backup