Help - Corruption in Non-Existent Drive ?

  • Thread starter Thread starter Ariel
  • Start date Start date
A

Ariel

Hello,

I'm getting corruption messages for files and directories
on drives that don't exist. >

Corrupt File : The file or directory P: is corrupt and
unreadable. Please run the Chkdsk utility.

Any ideas? Any suggestions on how to best proceed?

Thanks,
Ariel
 
Ariel said:
Hello,

I'm getting corruption messages for files and directories
on drives that don't exist. >

Corrupt File : The file or directory P: is corrupt and
unreadable. Please run the Chkdsk utility.

Any ideas? Any suggestions on how to best proceed?

Thanks,
Ariel
Click to expand...

What makes you think P: does not exist? What do you get
when you open a Command Prompt and type this command:

dir P:\
or
chkdsk P:
 
I know the drive configuration pretty well. After the
server was rebooted, P:, O: and Q:, all non-existent
drives, disappeared.

My co-worker who rebooted the server, did look at the
phantom drives and all looked like the C: drive at first
glance.

Ariel
 
Are you saying that these drives were visible prior
to the reboot? That the command "dir P:" returned
the contents of drive C:?
 
Yes, the drives were visible before the reboot, but NOT
after.

My co-worker looked at the phantome drives via Explorer,
the UI, not the command line, and yes, they all appeared
to have the contents of the C: drive.

After the reboot, the phantom drives are no longer there.
 
The "phantom" drives were most likely caused by any one
of the following processes:

- Remembered network connections. Run this command
to avoid them:
net use /persistent:no
- By some scheduled task making a connection but
failing to unmake it on termination. Use UNC syntax
for your background tasks.
- By someone making a connection under the "runas"
command, and not disconnecting it on termination.
Disconnect all network drives prior to exiting from a
"runas" session.
 
Ariel said:
We noticed that our backup (over the network using
Veritas's Netbackup) failed at the same time that we
started to get corruption errors on the phantom drives.
We've been having issues with the backups completing
successfully on this server. Upon further investigation,
the backup issues seem to be related only to the C drive
and not the data drives. Do you think Netbackup is
spawning these phantom drives? Do you think C: or
something on it is corrupt and that we should run
chkdsk /f on C:?

Thanks for all of your input.
Click to expand...

Definately!
 
Back
Top