Re: Bad Block Error recovery
- From: "Will" <wdiolnlt@xxxxxxxxxxxxxxx>
- Date: Fri, 20 May 2005 05:37:28 -0700
"Pegasus (MVP)" wrote:
>
> "Will" <wdiolnlt@xxxxxxxxxxxxxxx> wrote in message
> news:BEF83163-4806-4945-A8CA-CB81EFFF88A9@xxxxxxxxxxxxxxxx
> > "Pegasus (MVP)" wrote:
> >
> > >
> > > "Will" <wdiolnlt@xxxxxxxxxxxxxxx> wrote in message
> > > news:21134E84-EAFE-4FAA-8560-A1AB11095B7C@xxxxxxxxxxxxxxxx
> > > > Hi,
> > > >
> > > > I have a Windows 2003 Enterprise Server... due to a brief power
> failure it
> > > > went down ungracefully this evening.
> > > >
> > > > Now, when it boots up, one of the drives is appearing as
> uninitialized.
> > > It
> > > > used to have data on it. The Event Log reports
> > > >
> > > > The device, \Device\Harddisk1, has a bad block.
> > > >
> > > > How can I recover the disk?
> > > > --
> > > > --Will
> > > > Take the dontspam out of the email to email me. (every even letter
> until
> > > > spc.net)
> > >
> > > In a server environment you don't recover flawed disks. You replace
> them.
> > >
> > I'd like to know if there is a method to recover it as well. It is spun
> up
> > & running. There should be a process to repair the damage and either
> recover
> > the data on it as is, or be able to reinitialize/reformat it and use it.
>
> If it is accessible then you can run chkdsk /f /r from a Command Prompt.
> This could take several hours.
>
> If it is inaccessible then you need to retrieve your data from your backup
> medium, or pay a commercial data recovery service to assist you.
>
As a drive letter, no it is not accessible. Disk Manager shows the logical
drive as uninitialized. Is there something akin to the old fdisk /mbr or
something that could possibly restore the partition information?
Fortunately, it wasn't a critical drive in the system (daily remote backup
of another system - but only 1-2 day's worth of backups) and some directories
for FTP data transfer. Since it was non-critical on a development/test
server, I was hoping to just repair rather than purchase something new.
.
- Follow-Ups:
- Re: Bad Block Error recovery
- From: Joshua Bolton
- 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\)
- Bad Block Error recovery
- Prev by Date: Re: registering dll file manually -The Specified module could not be f
- Next by Date: Re: Wierd issue.
- Previous by thread: Re: Bad Block Error recovery
- Next by thread: Re: Bad Block Error recovery
- Index(es):
Relevant Pages
|
Loading