On Tue, April 27 1999, Eran Tromer <[EMAIL PROTECTED]> wrote:
|I know you already solved this by reinstalling, but in case others are
|interested, here's a solution. I had to find one after a silly incident
|involving a new harddisk and 'dd' seized at the wrong end.
Thanks a lot for the pointers.
Hello,
Amos Shapira wrote:
> Another way I heard about (but haven't tried) is to dd(1) the first
> 512 bytes of the hard disk. That way you have a copy of both the
> partition table and the boot sector.
Assuming you save a copy in advance...
Actually, LILO does half the job for you. If you ins
Hello,
Amos Shapira wrote:
> I've just compiled a new kernel and when I tried to reboot it I got
> messages like "can't find ... 03:02". Booting to the Debian rescue
> disk and running fdisk I see that these partitions are simply gone.
> The only one recognized is the Solaris partition. The fir
On Tue, April 20 1999, Gaal Yahas <[EMAIL PROTECTED]> wrote:
|On Tue, Apr 20, 1999 at 06:53:44PM +0400, Amos Shapira wrote:
|
|> Does anyone know of a way for me to restore the partition entries
|> without remembering the exact sizes?
|
|Ouch. I don't have a particularly clever suggestion, but as
On Tue, Apr 20, 1999 at 06:53:44PM +0400, Amos Shapira wrote:
> Does anyone know of a way for me to restore the partition entries
> without remembering the exact sizes?
Ouch. I don't have a particularly clever suggestion, but as a
last resort try using dd with skip= and count=, pipe the output
t
Hi,
I've just compiled a new kernel and when I tried to reboot it I got
messages like "can't find ... 03:02". Booting to the Debian rescue
disk and running fdisk I see that these partitions are simply gone.
The only one recognized is the Solaris partition. The first two
entries were simply zero
