Jump to content
Covecube Inc.

Steve Pitts

  • Content Count

  • Joined

  • Last visited

  • Days Won


Steve Pitts last won the day on April 25 2015

Steve Pitts had the most liked content!

About Steve Pitts

  • Rank

Profile Information

  • Gender
  • Location
    Kings Langley, England
  1. Fair enough, although it does feel a bit daft when the manufacturer and description of the drive have fundamentally changed but the scanner sees it as the same disk. I don't see exactly that form of words, only Mark all Readable blocks unchecked. Is that what you meant or am I looking in the wrong place?? Given that this drive is now due to be checked again in a few days I may decide not to bother anyway and just let it be checked on the schedule.
  2. Folks, Running v2.5.1.3062 of Scanner on a fully patched Windows Storage Server 2012 R2 Essentials system. A couple of weekends ago the system disk in my Thecus W5000 box died without warning. After much fun and games I eventually succeeded in bringing the system back to life with a BMR from the last backup before the failure but once I got around to checking the status of the various components (I run both Drivepool and Scanner on this system) it became apparent that Scanner had apparently not noticed that the system disk had changed from the 500GB Seagate SSHD that Thecus supply in t
  3. I can't work out whether what I'm seeing is an occurrence of this issue or just something similar. I am using FreeFileSync to copy from a Windows 7 64-bit system (not running DrivePool) to a Windows Storage Server 2012 R2 Essentials 64-bit box running DrivePool v2.2.0.651 and where the target location is on the pooled drive. One file was failing with error code 1450 (Insufficient system resources exist to complete the requested service) and nothing I could do would eliminate that error. All other files copied across fine and to add to the mystery when I manually copied the affected file to a W
  4. Did you ever figure this one out?? I have exactly the same issue but I am fairly convinced that it isn't DrivePool but rather that it's a network related issue because a) if I move the music files to a drive not in the pool then the same problem occurs and b ) if I use iperf to test the network without involving the disks I see similar issues with pauses as long as eight or nine seconds when no data is transmitted between the server and the client.
  5. Having installed the latest beta version (or at least, the one linked to above) do I need to re-run the verifier process or does that stick??
  6. Folks, I have had another crash with pretty much identical details (the addresses change, obviously, but the rest of the WinDbg output was unchanged) just 24 hours after the last one. Is it worth me uploading that dump file too?? FWIW both crashes seemed to be initiated by trying to access a file in one of the ServerFolders that are marked for duplication (some are, some aren't). A lot of the file access on this box is to folders that are not duplicated (eg. client backups, my music collection) but there is also regular access to folders that are (eg. file history backups)
  7. Well, I turned the drive verifier on a day or two after my last post, whilst still running, and yesterday evening I got the following crash: Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Only kernel address space is available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*d:\symbols*http://msdl.microsoft.com/download/symb
  8. I have next to nothing installed: plus SysInternals, from which I have Process Explorer running most of the time the machine is up. I will give that a go when I get a chance.
  9. Except that it won't install on R2 (the only available version is flagged as 8 RTM, although I tried to install it anyway) so that option is out.
  10. Well it might, but it reads like a bit of a fudge. Without understanding exactly what is causing this and why, it is difficult to say whether extending the timeout is going to help. However, it probably isn't going to do any harm either, so I'll install it anyway. Given that this issue has only happened twice in the four months I've been running DrivePool (I had my fingers crossed when I typed that to try and avoid the obvious jinx!?) it is going to be difficult to say whether a fix has had the desired effect or not. Yes. I ran Prime95, with three worker tasks, for over a week without a
  11. Which does not report any errors. The reason for the vagueness of my initial response to this relates not to the tools (I already have a bootable stick with a standalone version of memtest86+, plus UBCD, SystemRescueCD, Paragon's Hard Disk Manager, a variety of Linux live CDs and various manufacturer specific tools) but the fact that I've had difficulty getting the Thecus box to boot from USB sticks, to the extent that I went out and bought a USB DVD drive in order to rebuild the box a week or two after I first got it (and even that took several attempts to get it to boot). So I will try
  12. I seem to remember doing that last time, but will repeat the exercise and see if I can use something more thorough than the Windows Memory Diagnostics. Given the nature of the issue I am loathe to do that without some indication of a relevant fix. Assuming that this is another representation of the same issue then whatever mitigations Alex put in place last time obviously aren't sufficient to cover all cases.
  13. Sadly not, as it turns out. Just had another occurrence of this today, running beta build (as requested last time) on the same system, still fully up-to-date with Windows updates. I've uploaded the dump file (again as .7z format). Debugger output looks like this: Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Only kernel address space is available ************* Symbol Path validation summary ************** Response Tim
  14. Using 'dir /o:n' resolves the issue in cmd.exe and doesn't rely on any default behaviour (which has changed between releases of Windows). Of course it means changing your batch files but that is a one time hit.
  15. Apologies for jumping in here, but this doesn't seem worthy of its own thread. Is there any way of mapping the output from that command to the \device\harddisk... format that Microsoft use in some of their messages/event log entries (or vice versa, come to that)??
  • Create New...