Re: Bad Block Error recovery
- From: "Pegasus \(MVP\)" <I.can@xxxxxxx>
- Date: Sat, 21 May 2005 22:49:42 +1000
The OP wrote "As a drive letter, no it is not accessible.
Disk Manager shows the logical drive as uninitialized."
AFAIK, the recovery console works under much the
same constraints as the Disk Manager: If the disk does
not have a drive letter then none of the commands you
suggest will have any effect.
"Todd J Heron" <todd_heron_no_spam@xxxxxxxxxxx> wrote in message
news:Of9erxfXFHA.1040@xxxxxxxxxxxxxxxxxxxxxxx
> Will,
>
> Reboot the server into the recovery console. Then, try this assortment of
> tools:
>
> fixmbr, followed by a chkdsk <drive> /f /r
>
> -if that doesn't do it-
>
> Reboot the server into the recovery console again.
>
> chkdsk drive /p
>
> The /p switch instructs the Chkdsk tool to do an exhaustive check of the
> drive even if the drive is not marked with problems, and then corrects any
> errors that are found.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> --------------------------------------------------------------------------
--
> This posting is provided "as is" with no warranties and confers no rights
>
.
- Follow-Ups:
- Re: Bad Block Error recovery
- From: Todd J Heron
- Re: Bad Block Error recovery
- References:
- Bad Block Error recovery
- From: Will
- Re: Bad Block Error recovery
- From: Pegasus \(MVP\)
- Re: Bad Block Error recovery
- From: Will
- Re: Bad Block Error recovery
- From: Pegasus \(MVP\)
- Re: Bad Block Error recovery
- From: Will
- Re: Bad Block Error recovery
- From: Joshua Bolton
- Re: Bad Block Error recovery
- From: Will
- Re: Bad Block Error recovery
- From: Todd J Heron
- Bad Block Error recovery
- Prev by Date: Re: Trust Issues, Please Help (VPN)
- Next by Date: RDC
- Previous by thread: Re: Bad Block Error recovery
- Next by thread: Re: Bad Block Error recovery
- Index(es):
Relevant Pages
|