outdated, dont got answer to #19 above
** Changed in: lilo-installer (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/23835
Title:
lilo + lvm2 don
** Changed in: lilo-installer (Ubuntu)
Assignee: Colin Watson (cjwatson) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/23835
Title:
lilo + lvm2 don't work following upgrade to br
Thank you for posting this bug.
Does this occur in Lucid?
** Changed in: lilo-installer (Ubuntu)
Status: Confirmed => Incomplete
--
lilo + lvm2 don't work following upgrade to breezy
https://bugs.launchpad.net/bugs/23835
You received this bug notification because you are a member of Ubun
In my case it appears that lilo is trying to acccess unavailable USB
disk. I removed the disk from SCSI:
echo "scsi remove-single-device 3 0 0 1" > /proc/scsi/scsi
and run lilo again and everything worked.
--
lilo + lvm2 don't work following upgrade to breezy
https://bugs.launchpad.net/bugs/238
# lilo
Warning: LBA32 addressing assumed
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/dm-0' -> '/dev/leonardo/system'
Warning: Name change: '/dev/dm-1' -> '/dev/leonardo/storage'
Warning: Name change: '/dev/sdb' -> '/dev/sdb'
Warning: Name change: '/
'Me too' for i386 Hardy. I've noticed that /proc/partitions mentions
partitions (and disks) which don't exist.
--
lilo + lvm2 don't work following upgrade to breezy
https://bugs.launchpad.net/bugs/23835
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
** Changed in: lilo-installer (Ubuntu)
Assignee: (unassigned) => Colin Watson (kamion)
** Tags added: qa-jaunty-foundations
--
lilo + lvm2 don't work following upgrade to breezy
https://bugs.launchpad.net/bugs/23835
You received this bug notification because you are a member of Ubuntu
Bugs,
Same problem here.
Installed hardy server amd64 from scratch, /boot is on lvm. Initially
there were no problems. After the first kernel upgrade (probably the
first, not 100% sure) got the directory structure warning. Kept ignoring
the warnings, the system was working fine. Until this last hardy ke
This is still happening on 8.04; every kernel upgrade we do (via apt-get
dist-upgrade) gives these lilo errors. We are fully lvm, with a
separate lvm boot partition. For instance after today's apt-get dist-
upgrade that updated the kernel and initramfs:
update-initramfs: Generating /boot/initrd.
Just in case someone doesn't get the problem fixed: It might be the
stupid problem that "/boot" is not mounted...
--
lilo + lvm2 don't work following upgrade to breezy
https://bugs.launchpad.net/bugs/23835
You received this bug notification because you are a member of Ubuntu
Bugs, which is a dire
Scribit Björn Streicher dies 20/08/2007 hora 18:08:
> Using a volume created from LVM regions to hold /boot is not supported
> at this time.
It is, with LILO. I do that on a regular basis. I thought some recent
versions of GRUB supported that too.
Quickly,
Pierre
--
[EMAIL PROTECTED]
OpenPGP 0xD
I got the same error message as in the initial post running Feisty
(after not having problems for months). After taking out /boot from the
LVM region and mounting it as a simple disk partition via /dev/evms/sda1
it worked fine again - this behaviour is according to the EVMS
installation manual (see
It works for me with Edgy on a fresh install but Feisty fails.
Should I report a new bug or will this be sufficient?
Fresh install from Edgy Alternative with LVM(2) on a software/fakeraid
RAID1 (with mdadm and so on) seems to work just fine on my 2 servers
with this setup. The Feisty doen'st work
This does not appear to be a valid upstream LILO bug, as they don't
support LVM boot partitions.
** Changed in: lilo (Debian)
Status: Unconfirmed => Rejected
--
lilo + lvm2 don't work following upgrade to breezy
https://launchpad.net/bugs/23835
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Fresh edgy install, full lvm system (including /boot/ and /)
Pretty the same here, installer give me two choice, install lilo to mbr
(/dev/sda) or to /boot (/dev/sda1), but it fail to install in both case, but it
says something strange :
"couldn't install lilo in /target/" (free french translati
Just found a solution using "rescue mode" of Edgy install cd, just type
"/etc/init.d/lvm start" then lilo works fine
--
lilo + lvm2 don't work following upgrade to breezy
https://launchpad.net/bugs/23835
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
Still a problem with Edgy, fresh install.
Lilo install works fine during the install, but I tried to reinstall
this bootloader later (using "rescue" from an edgy install cd) and I got
this error too.
I have same the kind of lvm installation than the one described on
description field of this bug.
** Changed in: lilo-installer (Ubuntu)
Assignee: Colin Watson => (unassigned)
--
lilo + lvm2 don't work following upgrade to breezy
https://launchpad.net/bugs/23835
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This sounds pretty confirmed ("I'm having similar problems", "You did
hit a set of bugs here").
** Changed in: lilo-installer (Ubuntu)
Status: Unconfirmed => Rejected
** Changed in: lilo-installer (Ubuntu)
Status: Rejected => Confirmed
--
lilo + lvm2 don't work following upgrade t
I don't think it has anything to do with a newer lilo. I had sometimes problems
with my system that forced me to rerun lilo. I have all my partitions except
the swap under LVM, including / (and no specific partition for /boot).
It worked perfectly for ages, and now I get the same error:
bateleur
** Also affects: lilo (Debian)
Importance: Untriaged
Status: Unconfirmed
--
lilo + lvm2 don't work following upgrade to breezy
https://launchpad.net/bugs/23835
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
21 matches
Mail list logo
