Jump to content
Covecube Inc.

akshoslaa

Members
  • Content Count

    4
  • Joined

  • Last visited

  1. Playing around with the 'Work Folders' feature of 2012r2 and I've run up against a wall. Works fine if I put the server path for the sync share on an actual drive (VHD, or Physical) however when I specify the target as being on the pool drive - it lets me configure it, and from the client it successfully creates the user folder on the server, but then gives the error: 'Sync Stopped. A problem occurred' 'Incorrect function (0x80070001)' I was on v.420 so I updated to the latest beta (v.528) in the hopes that it might be related to 'Issue #51' * [D] [issue #51] WSS storage service would not recognize the pool drives because the drives were reporting that they were virtual drives. This was causing all kinds of problems with the Dashboard. No luck unfortunately. It's pretty clear that it's something funky MS is doing, and I highly doubt it's documented - but who knows, maybe you'll see a simple work-around on your end. (What I'm trying to achieve, is real-time one-way sync of updated files located on users PCs back to a central location where they can be maintained/backed up, and so far none of the 'self-hosted dropbox equivalents or folder-sync apps I've tried have worked reliably. 'Work Folders' has (in limited testing) so far achieved all of my requirements, _except_ being on the pooled drive...)
  2. akshoslaa

    Beta 320 BSOD

    Hi all, Had a bluescreen yesterday morning. Everything came back without an issue - and has been fine since - but looking into the cause, seems covefs.sys tripped over. windbg on the minidump yeilds: covefs+301a - KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. memory.dmp uploading now - it's automatic, not kernel though - so not sure if it'll do you any good. BSOD occured at 6:45 AM, no one was accessing the server at the time. Balancing kicks off at 2am, and backups at 8am.
  3. akshoslaa

    DrivePoolUI Hang

    Has anyone else experienced the UI hanging? (2.0.0.260) I recently switched to DrivePool, While importing all of the data from each disk into the pool, I turned off balancing to stop it from shifting stuff between disks until I was done. Once all the data on the disks was on the pool, I kicked off a manual balance, the next morning I found the UI hung. according the the image the balancing looked as though is was complete, but I couldn't interact with the software at all. Killed the process, and relaunched - the process starts, but nothing comes up on the screen. Tried a service restart - no change. Reboot - UI was working normally again. No other problems (aside from the srv2.sys BSODs) for the next few days, until I went ot remove a disk that was shown with a SMART warning. Removal ran overnight, and in the morning - the UI had hung again, the same symptoms as before. Haven't rebooted yet - so I can't access the UI, but I can confirm it completed the removal of the disk from the pool. In both of these cases it was a long running, intensive process that was the last action I took before it hung. I'm fairly certain (but not 100%) that I'd left the UI open for an extended period _without_ running any task, and hadn't experienced a hang. Performance Tab was not expanded at the time of the hang.
  4. Weighing in: I switched to DrivePool about a week ago, from DriveBender - which was experiencing BSODs with exactly the same symptoms - only the driver that was falling down was vhyperdrive4.sys (one of their files). Their software bloat had been irritating me a lot of late, so I was happy enough to blame them, and switch - but when the BSODs continued with the new software I started looking more closely. They seem to occur more frequently while performing a lot of IO across the network, which would certainly fit with your finding above. (Also, as above - I have DP installed on a Hyper-V host). Analysis of the srv2.sys minidumps shows the same srv2!Smb2ContinueUncachedRead crash. Analysis of the vhyperdrive4.sys minidumps doesn't give me much (ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.) A lot of the issues I've had with DriveBender over the years have beem down to disks that were going funky. Looked yesterday with your Scanner software, and found a SMART warning on one of the disks. (LOAD CYCLE COUNT on a WD Green Disk - not unexpected - but removed the disk from the pool anyway.) No BSOD _yet_ after removing the disk, but I haven't been thrashing network IO, so I doubt it's really made a difference. If any of my minidumps will help you in tracking this down, let me know - happy to help if I can. Bluescreens aside, I'm really liking DrivePool so far.
×
×
  • Create New...