Package: installation-reports Version: 2.12 Severity: normal
-- Package-specific info: Boot method: network Image version: AMD64 daily on 02Mar2006 from http://amd64.debian.net/debian-installer/daily/netboot/netboot.tar.gz Date: <Date and time of the install> Machine: Biostar IDEQ 330P, Dual Core Athlon 64 Partitions: <df -Tl will do; the raw partition table is preferred> Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card: [O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Create file systems: [ ] Mount partitions: [ ] Install base system: [ ] Install boot loader: [ ] Installed system ok: [ ] Comments/Problems: Partman can't see the windows dynamic disk partitions, even though the kernel can. # cat /proc/partitions major minor #blocks name 8 0 244198584 sda 8 1 39070048 sda1 8 2 205125632 sda2 8 16 244198584 sdb 8 17 39062016 sdb1 8 18 205125632 sdb2 Which is just fine (these are the partitions created by the windows install -- I'm looking to install Debian in /dev/sdb1) However, the partman partition editor screen looks like this: SCSI4 (0,0,0) (sda) - 250.1 GB ATA WDC WD2500SD-01K > #1 primary 40.0 GB B ntfs > #2 primary 210.0 GB SCSI5 (0,0,0) (sdb) - 250.1 GB ATA WDC WD2500SD-01K > #1 primary 250.1 GB ext3 Which means that partman is reading the dos partition table on the discs :( Can partman be made to use the kernel's idea of where the partitions are, even if it can't create or change them? (parted doesn't understand ldm at this juncture AFAIK) Given that the kernel is happy with the partitions, it seems a shame to have to abort the installation at this point. cheers, Phil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
