Philip Trickett wrote:
> The command used was:
> dd if=bootnet.img of=/dev/hda
Ouch!
> It looks as if it took the partition tables with it as well when this
> happened as fdisk cannot see any partitions.
OK - first things first, get a partition table. Let's hope you
had a /boot partition in the first 144, and that you haven't
over-written the root partition. Boot a rescue disk, and re-write
the old partition table to hda using fdisk. You should now have
all your old data, at least. But you've probably nuked the start
of the first partition, which will cause issues. If it's the boot
partition, we're still in business. Re-format the partition, and
copy the kernel from the rescue disk over. Now try rebooting.
In the absence of a paper copy of teh partition table, or at the
very least a binary copy from another machine, you're in trouble.
If needs bee, you can manually edit the patrition table, but
you'd need to know where the partitions were. One good thing -
you only need to re-do the primary partitions, since the extended
partitions will still be OK.
Cheers,
Dave.
--
David Neary,
Marseille, France
E-Mail: bolsh at gimp.org
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
