akiller
-
Posts
13 -
Joined
-
Last visited
-
Days Won
1
Posts posted by akiller
-
-
8 hours ago, tomb10 said:
I'm getting this same same ntfs.sys crash on 1709. If I save a file with Excel 2010 back to the drivepool it crashes. I can save to the raw drive, I can even save to a different filename on the drivepool, but if I save back to the same filename I opened it crashes. For some reason, my ability to roll back was gone so I reinstalled Windows 10 from scratch. I installed just Drivepool and Office 2010 and as soon as I upgraded to the Fall Creators Update (1709 16299.19) I got the same crash. I've now rolled back to the Creators Update from March (1703 15063.674) and this no longer happens.
thanks,
-tom
Interesting, I think I'm on Excel 2016 not 2010 but apart from that it's the same.
Hopefully this means there's more chance of it getting fixed as I don't want to revert to the older version of Windows 10. Everything else that uses my pool seems to work fine though.
-
Hi,
I've been having a few BSODs recently caused by DrivePool. I'm running the latest Windows 10 creators' update, v10.0.16299 - I believe this only started happening after I updated to it. DrivePool is v2.2.0.852.
In this instance I was working on my work PC over remote desktop, saved a file into my DropBox folder which synced it back to my PC (located on my pool) , and it instantly crashed ntfs.sys. I also had this the other week when I was trying to save an excel file locally on my desktop (also located on my pool).
If I move my DropBox folder outside my pool it works fine.
Here's the crash dump, let me know if you want me to send you the full .dmp.:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Kernel Version 16299 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 16299.15.amd64fre.rs3_release.170928-1534 Machine Name: Kernel base = 0xfffff800`23a83000 PsLoadedModuleList = 0xfffff800`23de4fd0 Debug session time: Sun Nov 12 17:30:08.591 2017 (UTC - 5:00) System Uptime: 6 days 22:32:59.653 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8053a9b9215, Address of the instruction which caused the bugcheck Arg3: ffffb7094451d4a0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: NTFS!NtfsDecodeFileObject+49 fffff805`3a9b9215 8b4804 mov ecx,dword ptr [rax+4] CONTEXT: ffffb7094451d4a0 -- (.cxr 0xffffb7094451d4a0) rax=0000000000000000 rbx=ffff82090fd7a4a0 rcx=0000000000000000 rdx=ffffb7094451e118 rsi=ffffcc0f31c1b590 rdi=ffff82090ac464b8 rip=fffff8053a9b9215 rsp=ffffb7094451de90 rbp=0000000000000000 r8=ffffb7094451df48 r9=ffffb7094451df10 r10=ffffb7094451e0b8 r11=ffff82090ac464b8 r12=0000000000000005 r13=ffffcc0f3bb6de50 r14=ffffb7094451e118 r15=ffff82090fd7a4a0 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 NTFS!NtfsDecodeFileObject+0x49: fffff805`3a9b9215 8b4804 mov ecx,dword ptr [rax+4] ds:002b:00000000`00000004=00000000 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: Dropbox.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8053aab994c to fffff8053a9b9215 STACK_TEXT: ffffb709`4451de90 fffff805`3aab994c : ffff8209`0a2018d0 ffff8209`0a201750 ffff8209`0a201830 fffff805`399969da : NTFS!NtfsDecodeFileObject+0x49 ffffb709`4451ded0 fffff805`3aab7091 : 00000000`00000000 00000000`00000000 ffff8208`febe44f0 ffff8208`febee550 : NTFS!NtfsFindTargetElements+0x48 ffffb709`4451df40 fffff805`3aad2cef : ffff8209`0ac46401 ffff8209`0ac464b8 ffffcc0f`00000000 ffff8208`00000000 : NTFS!NtfsSetRenameInfo+0x2d5 ffffb709`4451e340 fffff805`3aad2488 : ffff8209`0ac464b8 ffff8209`17ef2370 ffff8209`17ef2300 ffff8209`0d4d3a00 : NTFS!NtfsCommonSetInformation+0x76f ffffb709`4451e420 fffff800`23ad9339 : ffff8209`0a0d91e0 ffff8209`17ef2370 ffff8209`0ac464b8 ffffb709`4451e460 : NTFS!NtfsFsdSetInformation+0xd8 ffffb709`4451e4c0 fffff805`3c105473 : ffff8209`0a0d91e0 ffff8209`17b620d0 00000000`00000000 ffff8209`17b620d0 : nt!IofCallDriver+0x59 ffffb709`4451e500 ffff8209`0a0d91e0 : ffff8209`17b620d0 00000000`00000000 ffff8209`17b620d0 ffff8209`00000078 : covefs+0x55473 ffffb709`4451e508 ffff8209`17b620d0 : 00000000`00000000 ffff8209`17b620d0 ffff8209`00000078 fffff805`3c0e3c10 : 0xffff8209`0a0d91e0 ffffb709`4451e510 00000000`00000000 : ffff8209`17b620d0 ffff8209`00000078 fffff805`3c0e3c10 00000000`00000000 : 0xffff8209`17b620d0 FOLLOWUP_IP: covefs+55473 fffff805`3c105473 898424e8000000 mov dword ptr [rsp+0E8h],eax SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: covefs+55473 FOLLOWUP_NAME: MachineOwner MODULE_NAME: covefs IMAGE_NAME: covefs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 59bb1a02 STACK_COMMAND: .cxr 0xffffb7094451d4a0 ; kb FAILURE_BUCKET_ID: X64_0x3B_covefs+55473 BUCKET_ID: X64_0x3B_covefs+55473 Followup: MachineOwner ---------
Thanks
-
Did you clone the system drive, or reinstall it?
And could you get the same stuff as I've listed above?
And specifically, StableBit DrivePool uses the Volume IDs (which should be unique) to access the pooled disks.
I cloned it with Macrium Reflect. I've attached the error files - I'm not sure which one it would be to be honest with you so I've attached them all from that day.
I've now manually re-copied everything missing back so all is good, I only just thought I'd mention it as I came across this thread when trying to figure out what happened to me. I was just a little concerned DrivePool got confused and let me eject a disk without moving any data, and most importantly didn't tell me it hadn't moved anything.
Cheers.
-
For what it's worth, if it's worth it, this happened to me last night when I moved my OS to a new drive.
When windows booted up the new drive it assigned a new drive letter to one of my pooled drives ("D") and made it "L".
DrivePool showed what was formally known as "D" in my pooled disks list (and still referred to it as D) but also "L" in the non-pooled disks section. I subsequently changed the drive letter of the new partition back to "D" and ended up with it in both the pooled and non-pooled section, with the exact same name.
I seem to remember when looking at my file and folder placement rules it never showed the "D" partition by name though, and just listed "? (xxx GB") - the amount of free space was correct for the D drive but the question mark was not.
I also tried to remove the "D" partition that was in my pool (the disk is being replaced) and DrivePool quite worryingly completed the removal procedure within a matter of seconds (I hadn't selected the option for quick removal) and didn't move a single thing, so I'm having to manually re-import data from that disk into my pool.
A similar issue has happened to me in the past when drives get moved between SATA ports, their drive letters changed etc and I end up with "duplicate" drives in my pool. It makes me very, very cautious of doing this - I'm assuming DrivePool should be able to cope with moving disks around, given it must use their serial number rather than drive letter for identifying them?
-
Ah, yes the partition was before my main partition. I'm sure windows warned me and I completely ignored it
.I understand why you don't want to support them given their issues, I'm sure most people wouldn't need to use them anyway.
-
By the way, this should probably be in another thread but another "bug" I spotted.
I decided to remove an unused partition on one my drives so that I could extend the main partition which was already added to my pool. For whatever reason Windows decided to convert the disk from basic to dynamic when I did this and DrivePool lost all trace of the drive. I removed the missing drive from the pool but it never re-appeared under the list of available disks like I was expecting.
I was a bit confused as I could still see the drive and its contents in My Computer. After a few hours of pulling my hair out I found out that DrivePool won't work with dynamic disks (and then that my drive had been changed to dynamic) so I had to re-format it back to basic. As soon as I did it appeared again.
To avoid this frustration for other people would it be worth showing a list of unsuitable disks in the UI, with a reason why they're unsuitable?Have to say, I quite like giving software suggestions out, usually (as a developer) I have to fend off people sending me change requests
. -
Hi Chris,
I'm really sorry for the late reply it's been one of those weeks! I think I've identified the problem, and it's not DrivePool
; well.. I believe it does have a bug which I'll explain but it wasn't the root cause of my problem:Basically despite the fact I had ~60GB free on my C partition I discovered there was a process which slowly ate away at that free space overnight by apennding to a log file. Eventually I ended up with a 60GB log file and 0KB free on my C partition. As soon as this happens the DrivePool UI bombs out, but I can still read/write to my pool. Even once the process which created the log cleans itsself up and releases the space, giving me 60GB back, DrivePool fails to recover - even if you restart the service - until you reboot.
Now that I've stopped this process running DrivePool appears (touch wood..) to be rock solid again.
So in summary I think DrivePool may have a bug when you hit 0KB free space. I know it's rare and should never happen but it may be worth you guys investigating. Fortunately it's fairly easy to create a blank file of arbitary length to to simulate:
fsutil file [createnew] <FileName> <Length>
http://technet.microsoft.com/en-gb/library/cc753059.aspx
Cheers,
Andrew.
-
I (and many others I'm sure) use RoboCopy - it already comes installed on your PC.
Here's a batch command I use to backup my users folder off a PC to my server.
robocopy "d:\users" "\\serv\p$\Backup\Server\Users" /MIR /S /MT /R:1 /W:1
- d:\users - source
- \\serv.. - destination (my pool drive)
- /MIR - mirror source to destination
- /S - Copy subfolders (you might not need this with /MIR actually)
- /MT - Multithreaded copying
- /R:1 - If unable to access a file, only retry once (default is 1 million)
- /W:1 - If unable to access a file, wait 1 second before retrying (default is 30)
As I'm mirroring my users folder there's lots of files it can't access which is why i set /R:1 and /W:1 (otherwise it sits there retrying forever).
-
Hi all,
I believe this may be the root cause of a number of issues on my server. DrivePool appears to lose connection to its service despite the fact the service is running. I'm assuming it uses port 27525 for communication and I'm unable to manually telnet to that either. I've tried manually stopping/starting the service and that doesn't help. If you see the attached screenshot it was attempting to do this for over 12 hours.
The only way I can get around it is via a reboot, however I seem to have have to flip the power off because it just gets stuck at the "rebooting" stage once this happens, which is rather annoying! Which leads me to wonder if it's a driver issue?
I've attached the service log if it's of any help. I put a new disk in last night and had set it up to start mirroring my files to it, which I was hoping would have finished by this morning but clearly not.
For the record the scanner is working perfectly fine and I'm assuming you use the same communication method.
Cheers
.
-
Good to hear, thanks for your input
.Obviously I appreciate this is entirely my risk and you guys wouldn't recommend doing it!
-
Hi Chris,
I understand the risk when the pool is not available if all users were on it which is why I thought I'd leave the administrator account sat on my root install. If DrivePool was uninstalled, broke, or unavailable I would still be able to login as an administrator to fix things or login via the recovery console: I'd only temporarily lose access to my pooled user profiles which is fine.
With this in mind, from a DrivePool point of view my idea shouldn't necesarily cause anything to blow up should it? DrivePool clearly loads and is available before user login otherwise I wouldn't be able to login and I highly doubt anything would unnecessarily get corrupted using this approach but I'd like to double check with you guys first
.Thanks.
-
Hi,
I'm currently evaluating DrivePool to figure out if it's for me. So far, things are looking very positive. The flexibility compared to Storage Spaces and the newly added folder placement feature are exactly what I need
.One thing I would like to do however is to place my user accounts on a pool for redundancy. I know i can redirect documents and things easily within Windows, but this doesn't include AppData and all the other special folders.
My plan is to keep the administrator acount on my root install so if the pool's not available I can still login.
I created a user account, "pool" and used this to redirect it to the pool storage. Everything worked fine, I could login to the PC and my data was being written into the pool.
Can you see anything wrong with redirecting my individual user accounts using this method? Or is there a better way I shouild be aware of to do this?
(by the way, one issue I did have is I tried rebooting into safemode just to see what happened and as expected it didn't work as the user folder wasn't available. It logged me into a temporary profile and even after trying to reset the user account back to normal through HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList it still wouldn't work even when back in normal Windows - I'm assumng Windows corrupted something as I restored the user's folder prior to going into the temp profile and it worked fine. Not to worry, I'll just disable temporary logon accounts via GPO so it can't happen again.)
Many thanks
.
Windows 10: BSOD caused by covefs.sys
in General
Posted
I've installed that version and fingers crossed my DropBox has synced and not crashed, cheers :).
Your main website is still showing 852, not sure if this is intended!