[Lucid Beta 2] major failure caused by inconsitent partitioning name scheme

[A.Huck]

Binary package hint: debian-installer

Lucid Beta 2 AMD64 / 10.4

During default and expert installation the partitioning fails - such that
the installation is not possible on SATA-RAID0 due to inconsitent device naming.

I monitored that the created partitions on a Serial ATA-RAID0
/dev/mapper/isw_<someid>_Vol0
(accessed by ahci module) are available as
/dev/mapper/isw_<someid>_Vol0p1
/dev/mapper/isw_<someid>_Vol0p2
/dev/mapper/isw_<someid>_Vol0p5

but just after creating this partitions the installer tries to access

/dev/mapper/isw_<someid>_Vol05 * which is without "p" *

and fails:
"partman-lvm: Device /dev/mapper/isw_<someid>_Vol05 not found
(or ignored by filtering)."

Partition method was "Guided - use entire disk and set up LVM",
the crypted LVM did fail as well.

After the partitioning failed I created symbolic
links to /dev/mapper/isw_<someid>_Vol05 (and 1+2) and the
partitioning and the LVM-setup worked fine.

[Colin Watson (cjwatson)]

Could you please attach the syslog and partman logs from the installer?
They should be in /var/log/installer after installation.

 status incomplete

[A.Huck (ahuck)]

Hi Colin,

Ehm, the logs were in the installer system, which is history by now. I got the
system running - unfortunately not on the ahci-RAID because grub
had some issues as well with that kind of software RAID.
I hope the output from the console will give some hints where to search for
the extra "p" - I assume that there are different naming rules in the code.

If you really really need those logs I will take the time to reinstall it again.
Unfortunately, it's not just a virtual machine and takes time. This brand new
hardware (Z..y Z11) has some other issues as well which I need to solve.

Andreas

[A.Huck (ahuck)]

Hi,

I just reinstalled the system with (K)utuntu-rc and saved the logs which you'll find attached.
The error is reproducible and the workaround (ln -s..., s.o.) works even better since grub
(legacy) did start at least - although the root partition in /boot/grub/menu.lst was as well
the wrong one /dev/mapper/<someid>_Volume0p1 (*with p*) which grub could not find - dropping
a shell instead.

Regards,
Andreas

[A.Huck (ahuck)]

Workaround to continue creating partitions (ln -s ...):

ls -al /dev/mapper

crw-rw---- 1 root root 10, 59 Apr 23 10:20 control
brw-rw---- 1 root root 252, 0 Apr 23 10:50 isw_dihcfebdcd_Volume0
lrwxrwxrwx 1 root root 24 Apr 23 10:50 isw_dihcfebdcd_Volume01 -> isw_dihcfebdcd_Volume0p1
lrwxrwxrwx 1 root root 24 Apr 23 10:50 isw_dihcfebdcd_Volume02 -> isw_dihcfebdcd_Volume0p2
lrwxrwxrwx 1 root root 24 Apr 23 10:50 isw_dihcfebdcd_Volume05 -> isw_dihcfebdcd_Volume0p5
brw-rw---- 1 root root 252, 1 Apr 23 10:50 isw_dihcfebdcd_Volume0p1
brw-rw---- 1 root root 252, 2 Apr 23 10:50 isw_dihcfebdcd_Volume0p2
brw-rw---- 1 root root 252, 3 Apr 23 10:50 isw_dihcfebdcd_Volume0p5

[A.Huck (ahuck)]

"(K)utuntu-rc" should read "(K)ubuntu release candidate", of course.