[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

2.1r1 Install kills bsd- and other partitions



Hi,

IIRC:

(1) after trying to install Debian in hda5 (this or hda9 were proposed by
dselect) (see Fdisk1 below) and using hda10 as swap partition, I found hda8
and hda2(?) killed. I couldn't boot Debian, because LILO didn't want to
install in hda5.

(2) So I killed hda2 and created hda2 for BSD and hda3 for debian with
BSD-fdisk (see Fdisk2 below). I installed Debian with hda3 as / and hda5 as
/usr and hda10 as swap. The kernel reported the following hd-structure:
hda: hda1 hda2 < hda5 > hda3 hda4 < hda6 hda7 hda8 hda9 hda10 hda11 hda12 >
mount reported hda3 as / and hda5 as /usr.
Starting redhat on hda9, "linux2" still had its old (pre-Debian-inst)
content!
Starting debian, mount still reported hda3 as / and hda5 as /usr. "Save"
could be mounted as hda8.
(3) Did some work with Debian, I think.

(4) I must have reinstalled Debian, it now runs with hda3 used as /, no
other ext2-partitions, no swap.
(5) After adding a BSD swap partition as a BSD partition to hda2 (reducing
the / of BSD) and reinstalling FreeBSD 3.1, the kernel reports the following
hd-structure:
hda: hda1 hda2 < hda5 hda6 > hda3 hda4 < hda7 hda8 hda9 hda10 hda11 hda12
hda13 >
hda2 keeps running, even after using Debian. But now, hda9 is killed. "Save"
can be mounted now as hda9, I think.

It seems to me, that some parts of the install process (dselect and fdisk,
cfdisk see other post) don't see
BSD partions and name "linux2" hda5, giving this as parameter to some
lower-level linux
tools (mfs.ext2fs?), which see the BSD partitions as "extended" partitions
and name them hda5 etc, so "linux2" gets hda6 or hda7 (depending on the
number of BSD partitions), but don't check for the partition type (!!!).

(My personal opinion is, that naming extended partitions with increasing
numbers is stupid. Whatever I do on the hd, it shoudn't change the name of
the partition (except deleting it). Fdisk1 shows, that primary partitions
seem to work that way. But that's something for the kernel developers.)

BTW: Due to the size of hda8 and because it should have been written soon to
CDs, I have no backup. Does someone know a hint, how to reconstruct the
partition?

Ben

Fdisk1: (guessed)
Disk /dev/hda: 255 heads, 63 sectors, 1232 cylinders
Units = cylinders of 16065 * 512 bytes
   Device Boot   Start      End   Blocks   Id  System
/dev/hda1   *        1       13   104391    6  DOS 16-bit >=32M  (Boot)
/dev/hda2           14      110   779152?  a5  BSD/386           (FreeBSD)
/dev/hda4          111     1232  9012465    5  Extended
... (same as Fdisk2)

Fdisk2:
Disk /dev/hda: 255 heads, 63 sectors, 1232 cylinders
Units = cylinders of 16065 * 512 bytes
   Device Boot   Start      End   Blocks   Id  System
/dev/hda1   *        1       13   104391    6  DOS 16-bit >=32M  (Boot)
/dev/hda2           14       75   498015   a5  BSD/386           (FreeBSD)
/dev/hda3           76      110   281137+  83  Linux native      (Debian)
/dev/hda4          111     1232  9012465    5  Extended
/dev/hda5          366      625  2088418+  83  Linux native      (Linux "2")
/dev/hda6          626      690   522081    6  DOS 16-bit >=32M  (Data)
/dev/hda7          691      950  2088418+   6  DOS 16-bit >=32M  (Save)
/dev/hda8          951     1232  2265133+   6  DOS 16-bit >=32M  (Music)
/dev/hda9          111      238  1028097   83  Linux native      (Redhat)
/dev/hda10         239      247    72261   82  Linux swap
/dev/hda11         248      365   947803+   6  DOS 16-bit >=32M  (Windows)


Reply to: