System drive(C:) also mapped as J: ?!?!?!?!

  • Thread starter Thread starter spinlock
  • Start date Start date
S

spinlock

Guest
From Explorer, I see a second instance of the system drive as J:. This does
not appear on Drive Management screen, only C: associated wuth system drive
there.

Everytime I boot, XPSP3 claims something wrong with J:, it runs chkdsk and
allegedly fixes a bunch of stuff, then it claims something wrong with C:,
runs chkdsk and fixes a bunch of stuff.

2 Events are logged, one for each(C:, J:), claiming that they are corrupt
and that chkdsk should be run. This happens over and over.

What the F is J:? How/where do I get rid of it?

Everything works OK, but having this J: and having "corrupt" NTFS drives is
nerve wraking!!!!!!!!!!!!!!!!
 
Re: System drive(C:) also mapped as J: ?!?!?!?!

I tried fsutil volume dismount J: , but this didn't work.

From Explorer, I see a second instance of the system drive as J:. This does
not appear on Drive Management screen, only C: associated wuth system drive
there.

Everytime I boot, XPSP3 claims something wrong with J:, it runs chkdsk and
allegedly fixes a bunch of stuff, then it claims something wrong with C:,
runs chkdsk and fixes a bunch of stuff.

2 Events are logged, one for each(C:, J:), claiming that they are corrupt
and that chkdsk should be run. This happens over and over.

What is J:? How/where do I get rid of it?

Everything works OK, but having this J: and having "corrupt" NTFS drives is
nerve wraking!!!!!!!!!!!!!!!!
 
Re: System drive(C:) also mapped as J: ?!?!?!?!

spinlock wrote:
> I tried fsutil volume dismount J: , but this didn't work.
>
> From Explorer, I see a second instance of the system drive as J:. This
> does
> not appear on Drive Management screen, only C: associated wuth system drive
> there.
>
> Everytime I boot, XPSP3 claims something wrong with J:, it runs chkdsk and
> allegedly fixes a bunch of stuff, then it claims something wrong with C:,
> runs chkdsk and fixes a bunch of stuff.
>
> 2 Events are logged, one for each(C:, J:), claiming that they are corrupt
> and that chkdsk should be run. This happens over and over.
>
> What is J:? How/where do I get rid of it?
>
> Everything works OK, but having this J: and having "corrupt" NTFS drives is
> nerve wraking!!!!!!!!!!!!!!!!

Ok, you are obviousely bold enough to remove the
J: mountpoint :-)
Maybe fsutil sees J: as system drive, so it rejected
the request.
My tools have no such scruples.

First try DelMountpoint and then DeleteDosDevice:

http://www.uwe-sieber.de/files/delmountpoint.zip
http://www.uwe-sieber.de/files/deletedosdevice.zip


Uwe
 
Re: System drive(C:) also mapped as J: ?!?!?!?!

This is a work PC, so I want to backup and migrate to new workstation that
this bug allowed me to justify!!! :>

I will try your tools by end of weekend.

thanks!

"Uwe Sieber" <mail@uwe-sieber.de> wrote in message
news:6jrk1hF4olqqU1@mid.individual.net...
> spinlock wrote:
>> I tried fsutil volume dismount J: , but this didn't work.
>>
>> From Explorer, I see a second instance of the system drive as J:. This
>> does
>> not appear on Drive Management screen, only C: associated wuth system
>> drive
>> there.
>>
>> Everytime I boot, XPSP3 claims something wrong with J:, it runs chkdsk
>> and
>> allegedly fixes a bunch of stuff, then it claims something wrong with C:,
>> runs chkdsk and fixes a bunch of stuff.
>>
>> 2 Events are logged, one for each(C:, J:), claiming that they are corrupt
>> and that chkdsk should be run. This happens over and over.
>>
>> What is J:? How/where do I get rid of it?
>>
>> Everything works OK, but having this J: and having "corrupt" NTFS drives
>> is
>> nerve wraking!!!!!!!!!!!!!!!!
>
> Ok, you are obviousely bold enough to remove the
> J: mountpoint :-)
> Maybe fsutil sees J: as system drive, so it rejected
> the request.
> My tools have no such scruples.
>
> First try DelMountpoint and then DeleteDosDevice:
>
> http://www.uwe-sieber.de/files/delmountpoint.zip
> http://www.uwe-sieber.de/files/deletedosdevice.zip
>
>
> Uwe
 
Back
Top