Disk drive "Dissapears"

[I.E.]

Hi,

I have a process that takes data from one drive, processes it, then
writes it to a second drive. Sometimes during the process I'll start
getting delayed-write errors (ID 50 and 51). And sometimes a disk
will "dissapear". Checking the event log the disk dissapeared due to
an Event 132 (Received a REMOVAL notification for device ...)... Upon
scanning for new devices, the hard disk "re-appears". Any idea what's
causing this or how to get around it? I don't think it's a hardware
problem as it's happened on multiple machines.

Thanks




.................................................................
Posted via TITANnews - Uncensored Newsgroups Access-=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=-

 

[Guest]

-----Original Message-----
Hi,

I have a process that takes data from one drive, processes it, then
writes it to a second drive. Sometimes during the process I'll start
getting delayed-write errors (ID 50 and 51). And sometimes a disk
will "dissapear". Checking the event log the disk dissapeared due to
an Event 132 (Received a REMOVAL notification for device ...)... Upon
scanning for new devices, the hard disk "re-appears". Any idea what's
causing this or how to get around it? I don't think it's a hardware
problem as it's happened on multiple machines.

Thanks




.......................................................... ........
Posted via TITANnews - Uncensored Newsgroups Access
-=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=-

.

Do you have adequate space on the destination hard
drive ?? Perhaps it's failing for that reason.

 

[I.E.]

Do you have adequate space on the destination hard
drive ?? Perhaps it's failing for that reason.

Yes.. there's 2 80GB disks... The data is about 40GB so that leaves
about 50GB on each disk free. It has something to do with an I/O
error occuring when trying to write to a disk when there's still data
in the write behind cache. (I don't want to switch to write-through
caching becasue of the performance hit).



.................................................................
Posted via TITANnews - Uncensored Newsgroups Access-=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=-

 

[Steve Nielsen]

Yes.. there's 2 80GB disks... The data is about 40GB so that leaves
about 50GB on each disk free. It has something to do with an I/O
error occuring when trying to write to a disk when there's still data
in the write behind cache. (I don't want to switch to write-through
caching becasue of the performance hit).

Just some thoughts... what type drives, what file system (FAT or NTFS),
what file sizes?

Steve

 

[I.E.]

Just some thoughts... what type drives, what file system (FAT or NTFS),
what file sizes?

Steve

There are 2 Seagate Barracuda disks. The file system is NTFS and
there's about 40GB of data in 5MB chunks being processed then copied.




.................................................................
Posted via TITANnews - Uncensored Newsgroups Access-=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=-

 

[I.E.]

There are 2 Seagate Barracuda disks. The file system is NTFS and
there's about 40GB of data in 5MB chunks being processed then copied.

I think I may have tracked it down...

Several of these two errors will occur:
Event ID 51: An error was detected on device \Device\Harddisk1\DR1
during a paging operation.
Final status code: c000000e

Event ID 50: Lost Delayed-Write Data
Final status code: c000000e

From ntstatus.h:
#define STATUS_NO_SUCH_DEVICE 0xC000000E

This will be followed by:
Event ID 135: received a device interface REMOVAL notification for
device
at which point the drive "dissapears"

Then finally:
Event ID 26: Delayed Write Failed

Does this sound feasible? (I have to come up with a reason)



.................................................................
Posted via TITANnews - Uncensored Newsgroups Access-=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=-

 

[Steve Nielsen]

I think I may have tracked it down...

Several of these two errors will occur:
Event ID 51: An error was detected on device \Device\Harddisk1\DR1
during a paging operation.
Final status code: c000000e

Event ID 50: Lost Delayed-Write Data
Final status code: c000000e

From ntstatus.h:
#define STATUS_NO_SUCH_DEVICE 0xC000000E

This will be followed by:
Event ID 135: received a device interface REMOVAL notification for
device
at which point the drive "dissapears"

Then finally:
Event ID 26: Delayed Write Failed

Does this sound feasible? (I have to come up with a reason)

I assume this was working until something happened to change it? Service
Packs, patches, updated disk drivers? If not how about seeing if there
are updated disk drivers available?

Steve