EVMS breaks LILO RAID1 /boot in Hoary

Bug #16600 reported by Mike Bird
10
Affects Status Importance Assigned to Milestone
lilo (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

In Hoary EVMS preempts MD, using DM devices for RAID1 which Hoary's LILO doesn't
understand:

  # grep /boot /proc/mounts
  /dev/md0 /boot ext3 rw 0 0
  # cat /proc/mdstat
  Personalities : [raid1]
  md0 : active raid1 dm-6[1] dm-5[0]
        96256 blocks [2/2] [UU]
  # lilo
  Fatal: is_primary: Not a valid device 0xFD05

Revision history for this message
Mike Bird (mgb-ubuntu) wrote :

*** WORKAROUND ***

Do not use this workaround unless you understand it and how to adapt it to your
system. You could easily lose all your data.

  # start-stop-daemon --stop --name=klogd
  # umount /boot
  # mdadm --stop /dev/md0
  # mdadm --assemble /dev/md0
  mdadm: /dev/md0 has been started with 2 drives.
  # cat /proc/mdstat
  Personalities : [raid1]
  md0 : active raid1 hda1[0] hdb1[1]
        96256 blocks [2/2] [UU]

Revision history for this message
Jeff Bailey (jbailey) wrote :

Unassigning from me, I'm not the one to fix this.

Changed in lilo:
assignee: jbailey → nobody
Revision history for this message
Paul Dufresne (paulduf) wrote :

A dup of bug #48618 ?

Revision history for this message
Christian Rishøj (christian-rishoj) wrote :

After an upgradre from Edgy to Feisty, I'm seeing this as well. Output from lilo -v5 attached. I can't use the above workaround as / is my boot device. Please advise.

Revision history for this message
Marcus Asshauer (mcas) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in lilo:
status: New → Incomplete
Revision history for this message
Connor Imes (ckimes) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in lilo:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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