System.IO.IOException: The drive cannot find the sector requested.

[KgCobra1]

I had a drive that was reporting this error.  I was able to successfully remove the drive, replaced it with a brand-new enterprise drive.  It added successfully and files loaded properly.  Now when I am moving files into the pool, I am getting this same error on the new drive (using the same bay).  I have tried manually putting files into the pool in and get the same error.  

I also tried to remove another drive in my setup and DrivePool is now reporting this error on this drive as well.  Hard to believe I have 3 bad drives.  Is it possible DrivePool has a filesystem error?  

I have ran chkdsk on both the original drive, new drive, and 3rd drive that I tried to remove from the pool and all reported no errors or bad sectors.

I am out of options here.

 

Andrew

[CyberSimian]

On 12/9/2022 at 4:10 AM, KgCobra1 said:

I have ran chkdsk on both the original drive, new drive, and 3rd drive that I tried to remove from the pool and all reported no errors or bad sectors.

I have been experiencing a similar problem with my four USB-disk drive pool.
On wake from hibernation, Drivepool would detect a missing disk, and the
Windows event log contained "The driver detected a controller error".  This did
not happen every time, but it was sufficiently frequent to be annoying.
Assuming the USB disk was developing a fault, I replaced it (and the USB cable)
with a different disk, but the error still occurred, and what is more it
occurred on the replacement disk(!).  I then unplugged the USB disks from the
motherboard sockets, and plugged them all into a USB hub, and the error still
occurred.

The drive pool concept is great, but I don't know anything about the
complexities of implementing it on Windows.  My simple-minded assessment of the
Drivepool product is that it is too fussy, and diagnoses errors when there are
none.

I am currently in the process of copying all of the files in the pool to
non-pooled areas of the disks, and will be uninstalling Drivepool when that is
complete.  If I then still get errors, I will know that Drivepool was not to
blame.

-- from CyberSimian in the UK

 

[CyberSimian]

Just now, CyberSimian said:

I am currently in the process of copying all of the files in the pool to
non-pooled areas of the disks, and will be uninstalling Drivepool when that is
complete.  If I then still get errors, I will know that Drivepool was not to
blame.

I completed emptying the pool, and then deactivated the licence, uninstalled
Drivepool, and rebooted.  All disks had worked OK during the file copying
(which took several days, with the PC on continuously), but the first time that
the system woke from hibernation subsequently, one of the disks was missing
again!  So the problem was clearly not caused by Drivepool. 

While trying to diagnose the cause of the problem, I had changed USB disks,
changed USB cables, and changed USB sockets, none of which cured the problem.
It then dawned on me that the one element that I had not changed was the USB
power supply.  The disks that failed had all used the same USB power supply.  I
have now replaced that power supply with a spare one, and I am pleased to
report that so far the problem seems solved.

I have measured the USB power supply voltage using a multimeter, and it reads
12.3 volts, which seems reasonable.  But of course this was effectively open
circuit, and I suspect that when loaded, the voltage would drop to the point
where it is unable to spin up the disk, resulting in the "missing disk"
condition.

The erratic symptoms experienced by the original poster seem similar to mine,
so I would suggest that he checks the power supply, and replaces it with
another if he has a spare one.  A point to remember is that a hard disk
requires significantly more power during spin-up than it does during
steady-state operation.  A few years ago I checked the specs of the disks that
I had at that time.  Steady-state operation required around 5 watts for slower
disks, increasing to 8-10 watts for faster disks.  But during spin-up, the
disks required 25-30 watts (but only for a second or two).  If the power supply
cannot provide 30 watts simultaneously to each of the disks connected to it,
spin-up failures may occur.

-- from CyberSimian in the UK

[KgCobra1]

Hey there,

The error I was getting was apparently coming from a faulty controller in my enclosure.  I ended up having to replace it and the issue was resolved after putting in a ticket and Chris was able to help me determine this.

Good luck.