From: "Jim C. Brown" <jbrown106@phreaker.net>
To: linux-admin@vger.kernel.org
Subject: Re: mbr dd'd
Date: Mon, 13 Dec 2004 10:59:23 -0500 [thread overview]
Message-ID: <20041213155923.GA24850@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <1102944601.2248.31.camel@Kaushal>
On Mon, Dec 13, 2004 at 07:00:02PM +0530, kaushal wrote:
> hi,
> My friends' system is in a critical situation.
> Hdd. is /dev/hdc.
> CD-WR is /dev/hdd.
> created a bootable linux iso img.
> MISTAKE part:
> dd if=iso.img of=/dev/hdc.Instead of hdd.
>
I did that once.
> Net connectivity is available.Is there anyway he can recover the mbr
> ?Other os is windows 2000.He did backup the entire data and the system
> is working fine now.
He backuped all the data and the system is working fine now?
If that is the case, then why do you need to recover the mbr?
You can't recover the mbr, no matter what you do. Unless you actually made a
backup copy with dd prior to the accident, it doesn't exist anymore.
However, if you have hackup copies, you can use fdisk to repartition the disk
(and make a new mbr in the process). And then you can restore data from backup.
The reason grub and lilo failed may have been because the hard disk no longer
looked like a valid hard disk. fdisk will fix that.
If you have no backups (I'm assuming he only backuped the Windows part), you
can try guessing the location of the partition by playing with partition table
numbers, or you can try to use a program like Partition Magic to restore it ..
but this is likely to fail if the file system was overwritten.
There is also the possibility that, for some reason not clear in your email,
the hard disk is not recongized by the BIOS at all ... if that is the case
then you'll need to enter CMOS configuration and tell it about the hard disk
again.
>
> Desperately waiting for a solution.
>
> Thanks a lot in advance.
>
> kaushal.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2004-12-13 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 13:30 mbr dd'd kaushal
2004-12-13 14:31 ` chuck gelm
2004-12-13 15:59 ` Jim C. Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041213155923.GA24850@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).