Bug#41440: marked as done ([slink] libfdisk doesn't get along with FreeBSD partitions)
Your message dated 26 Mar 2000 04:50:39 -0500
with message-id <oaitya9i1c.fsf@arroz.fake>
and subject line [slink] libfdisk doesn't get along with FreeBSD partitions
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 17 Jul 1999 06:07:07 +0000
Received: (qmail 4569 invoked from network); 17 Jul 1999 06:07:06 -0000
Received: from cr246114-a.crdva1.bc.wave.home.com (24.113.157.89)
by master.debian.org with SMTP; 17 Jul 1999 06:07:06 -0000
Received: (from vilmos@localhost)
by cr246114-a.crdva1.bc.wave.home.com (8.9.3/8.9.3) id XAA00577
for submit@bugs.debian.org; Fri, 16 Jul 1999 23:04:55 -0700
Date: Fri, 16 Jul 1999 23:04:55 -0700
From: vilmossoti@home.com
Message-Id: <199907170604.XAA00577@cr246114-a.crdva1.bc.wave.home.com>
To: submit@bugs.debian.org
Subject: Critical install bug in slink
package: boot-floppies
version N/A
Hi,
I wanted to install slink (just downloaded from ftp.debian.org
stable dir) and it successfully wiped out another partition. I
tracked down the problem and can provide you with the details. It
seems the kernel's idea about the partitions is different from
the rest of the installation stuff.
Here is the relevant part of dmesg:
hda: WDC AC23200L, 3098MB w/256kB Cache, CHS=787/128/63, DMA
hdb: Maxtor 91303D6, 12427MB w/512kB Cache, CHS=1024/255/63, DMA
........
Partition check:
hda: hda1 hda2 hda3
hdb: hdb1 hdb2 hdb3 < hdb5 hdb6 > hdb4 < hdb7 hdb8 hdb9 hdb10 hdb11 hdb12 hdb13 hdb14 hdb15 hdb16 >
And here is the partition table according to fdisk:
Disk /dev/hdb: 255 heads, 63 sectors, 1024 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 128 1028128+ a6 OpenBSD
/dev/hdb2 129 256 1028160 a9 Unknown
/dev/hdb3 * 257 384 1028160 a5 BSD/386
/dev/hdb4 385 1578 9590805 5 Extended
Partition 4 has different physical/logical endings:
phys=(1023, 254, 63) logical=(1577, 254, 63)
/dev/hdb5 385 512 1028128+ 83 Linux native
/dev/hdb6 513 640 1028128+ 83 Linux native
/dev/hdb7 641 768 1028128+ 83 Linux native
/dev/hdb8 769 896 1028128+ 83 Linux native
/dev/hdb9 897 1024 1028128+ 83 Linux native
/dev/hdb10 1025 1152 1028128+ 83 Linux native
/dev/hdb11 1153 1280 1028128+ 83 Linux native
/dev/hdb12 1281 1408 1028128+ 83 Linux native
/dev/hdb13 1409 1536 1028128+ 83 Linux native
/dev/hdb14 1537 1578 337333+ 82 Linux swap
The disk is "hand-LBAd" due to old BIOS, but it works. So, the problem
is my /dev/hdb3 partition is a FreeBSD 3.2. It has two BSD "partitions"
and it is interpreted by the kernel but not by the other install
programs. I wanted to install slink on hdb7 but it (as I later figured
out) formatted hdb5. Also, it formatted hdb12 as swap partition.
Vilmos Soti
---------------------------------------
Received: (at 41440-done) by bugs.debian.org; 26 Mar 2000 08:58:26 +0000
Received: (qmail 14814 invoked from network); 26 Mar 2000 08:58:25 -0000
Received: from 209-122-226-105.s359.tnt1.nyw.ny.dialup.rcn.com (HELO arroz.fake) (@209.122.226.105)
by master.debian.org with SMTP; 26 Mar 2000 08:58:25 -0000
Received: by arroz.fake (Postfix, from userid 421)
id 2262F9385A; Sun, 26 Mar 2000 04:50:40 -0500 (EST)
Sender: apharris@arroz.fake
To: 41440-done@bugs.debian.org
Subject: [slink] libfdisk doesn't get along with FreeBSD partitions
From: Adam Di Carlo <adam@onshore.com>
Date: 26 Mar 2000 04:50:39 -0500
Message-ID: <oaitya9i1c.fsf@arroz.fake>
Lines: 10
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Since you have not followed up with us on this bug, and no one else
has reported it, we can only assume this problem has been solved in
potato.
If you do have time, please do follow up on this bug. I would hate to
see bad behavior toward FreeBSD partitions get released in potato.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: