Ubuntu
udev package

Feisty Xubuntu LVM over RAID1 won't boot

Bug #102410 reported by Joe Baker
2
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: debian-installer

Xubuntu Alternate Install Alpha 5
I performed the LTSP install.

Here I describe what I can recall of performing custom partitioning from the installer.
I created a RAID1 device from two single partitions each on a 40 gig drive.
Next I created a single volume group "vg_root"
I created three Logical Volumes "lv_root" , "lv_home" and "lv_swap"
I created ext3 on "lv_root" and mapped the mount point to /
I created ext3 on "lv_home" and mapped the mount point to /home
When the installer asked where to install Lilo it offered MD0 and advanced as options.

I chose MD0.
After the install the system wouldn't boot.
Earlier in the install and perhaps related...
The "Create LTSP Chroot" section failed, but I continued on.

If necessary I may be able to obtain log files from the system if I can mount the partitions from a LiveCD successfully.

It does seem that Lilo starts upon rebooting. I'll have to reboot to write down the details and attach them to the ticket.

I do have a Ubuntu 6.10 alternate install system installed with a similiar LVM over RAID1 with Lilo install. I'm really nervous about performing kernel upgrades on that box before disk imaging the drives.

Revision history for this message
Oliver Brakmann (obrakmann) wrote :

Hi,

thanks for your bug report.

Could you perhaps explain in a little more detail what "the system wouldn't boot" means? ie. do you get any error messages, at which stage of the boot process does it stop etc.

Also, be advised that feisty is currently pretty buggy wrt to booting from raid. Please see bug #75681 and check whether you see the same symptoms.

Thanks.

Changed in debian-installer:
status: Unconfirmed → Needs Info
Revision history for this message
Joe Baker (joebaker) wrote :

This bug report could be related to #75681 as you mentioned. I'll type here what I see when the system tries to boot after the install...
Hopefully I've scrolled back far enouth. It seems like mdadmin can't read the config file which should have been written into the initrd, right?
---
[ 22.986214] hash matches device ptyr0
[ 22.988318] Time: tsc clocksource has been installed.
Loading, please wait...
[ 23.003442[ input: AT Translated Set 2 keyboard as /class/input/input1
Begin: Loading essential drivers... ...
[ 23.302955] Capability LSM initialized
[ 23.334316] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialized: <email address hidden>
Done.
Begin: Running /scripts/init-premount ...
[ 23.399047] ACPI Exception (acpi_processor-0677): AE_NOT_FOUND, Processor Device is not present [20060707]
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Begin: Loading MD modules ...
[ 23.603812] md: raid1 personality registered for level 1
Success: loaded module raid1.
Done.
Begin: Assembling all MD arrarys ...
mdadm: No devices listed in conf file were found.
Failure: failed to assemble all arrays.
Done.
Done.
/init: /init: 1 : cannot open /dev/root: No such device or address
Begin: Running /scripts/local-premount ...
Done.
Usage: modprobe [-v] [-V] [-C config-file] [-n] [-i] [-q] [-Q] [-b] [-o <modname>] <modname> [parameters...]
modeprobe -r [-n] [-i] [-v] <modulename> ...
modeprobe -l -t <dirname> [ -a <modulename> ...]
mount: Cannot read /etc/fstab: No such file or directory
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory
Done.
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init

BusyBox v1.1.3 (Debian 1:1.1.1-3-3ubuntu2) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)

Revision history for this message
Oliver Brakmann (obrakmann) wrote :

Hi Joe,

thanks for the clarification. Yes, it is the same bug.

As Scott requested he'd like a new bug to work on this, so I'll point people over there to this bug.

I'm assigning this to the udev package, although you could argue that mdadm or initramfs-tools might be appropriate as well.

Changed in debian-installer:
status: Needs Info → Confirmed
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Already fixed

Changed in udev:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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