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

Bug #564771 reported by A.Huck
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
New
Undecided
Unassigned

Bug Description

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.

Revision history for this message
Colin Watson (cjwatson) wrote : Re: [Bug 564771] [NEW] [Lucid Beta 2] major failure caused by inconsitent partitioning name scheme

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

 status incomplete

Changed in debian-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
A.Huck (ahuck) wrote :

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

Revision history for this message
A.Huck (ahuck) wrote :

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

Revision history for this message
A.Huck (ahuck) wrote :
Revision history for this message
A.Huck (ahuck) wrote :

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

Revision history for this message
A.Huck (ahuck) wrote :

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

A.Huck (ahuck)
Changed in debian-installer (Ubuntu):
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.