Jump to content
Covecube Inc.

keithcc

Members
  • Content Count

    3
  • Joined

  • Last visited

  1. keithcc

    Disk is missing error

    Thanks for the reply Christopher. No, the disk is not cloned(also no raid or striping etc), it is a basic disk, and it's formatted NTFS. Just a regular run-of-the-mill sata-attached drive with no special setup/configuration. It looks just like the other 8 or 9 drives that are attached in the same box. It seems odd to me that this one, which just happened to be the one I replaced a few weeks back, was singled out for a problem.
  2. keithcc

    Disk is missing error

    I recently had a drive go to "Disk is Missing" in the DrivePool(2.2.2.394) dashboard on Windows 10 Build 1909. The disk appeared fine in Scanner, no SMART errors, showed up in Disk Management, files were present in Windows Explorer. The disk was mounted into a directory (vs a drive letter) No idea what precipitated the error -- although a couple weeks ago, I removed a bad drive and replaced it with a refurbished one. The error showed up upon a reboot, but not the first reboot after the drive replacement. No UltraDMA SMART errors, like you might expect with a questionable connection.....in case that was in play. I upgraded to 2.2.3.1019 and clicked Remove on the disk. This forced a Measuring.....then a Checking..... and then all was good. But never presented options to remove the drive, nor did it actually remove the drive. I think whatever process evaluates it as missing was failing to detect it again. I tried unmounting then re-mounting via Disk Management, that did not work, the disk still showed as missing. I've also noticed that the emailed drive notification always seem to be too late -- I already know there's a problem before the notification is sent. I'm also not sure when that's evaluated, but it seems almost require an application restart, which seems odd to me. Thought I'd share in case anyone else is seeing. Thanks
  3. While I'm not sure exactly when this happened, all of my disk location with the case/bay information appears to have been lost. I'm running 2.5.3216 (website says 2.5.4.3216, but programs and features reports 2.5.3216) on Windows 10. Is this a known issue? I've got like 10-12 disks on this machine, and what's worse is that I don't think I actually have this information easily available without taking stuff offline. Not the end of the world, but obviously inconvenient. I actually have a full system backup going back 2 weeks, 6 months, and almost a year.....is that data stored somewhere, like in a config file? Why do you think this might have happened? An upgrade to a newer version fails to preserve it? Is this a symptom described here in the release notes: I use mount points like c:\array\diskxyz within Windows 10. Can I fix this? Thanks, Keith
×
×
  • Create New...