The problem still persists on current Feisty with linux-image 2.6.20-12,
udev 103-0ubuntu13, and lvm2 2.02.06-2ubuntu8.
--
Root fs on LVM fails to boot
https://launchpad.net/bugs/87745
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I just saw that in /etc/udev/rules.d/70-lvm.rules the device is tested
against ENV{ID_FS_TYPE}=="lvm*|LVM*" to trigger the vgchange/vgscan.
But
$ grep ID_FS_TYPE /var/log/udev
ID_FS_TYPE=ext3
ID_FS_TYPE=vfat
ID_FS_TYPE=swap
ID_FS_TYPE=ntfs
ID_FS_TYPE=ext3
ID_FS_TYPE=ext3
ID_FS_TYPE=reiserfs
ID_FS_
Hi,
I also confirm the behaviour. The volumes mount fine when I do:
'lvm vgscan'
'lvm vgchange -ay; exit'
as mentioned in the first post. The boot process works with a 2.6.19
kernel but not 2.6.20.
Regards,
Fast
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You recei
I've also observed this problem in gutsy: LVM on md (raid1) fails to
boot, an "lvm vgchange -ay" on at the (initramfs) prompt is sufficient
to get it working.
My investigations show two parts to the problem. First, udev's 65
-persistent-storage.rules file explicitly excludes md* devices from
anal
Here's an update:
1) I started my system with the latest 2.6.22-6 kernel
2) Used "lvm vgchange -a y"
3) Mounted the root FS and continued booting.
4) Used my system a little with the new kernel.
and now I'm unable to boot with my 2.6.19 xen kernel anymore. It used to
work OK before I mounted my
I can confirm this on a gutsy system with lvm2_2.02.24-6ubuntu1
installed.
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => High
Status: Unconfirmed => Confirmed
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you ar
No news? It's really an annoying bug... Could anybody reach a solution?
Thanks, Fastguy
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
according to the bugtrail, this is rather a problem of mdadm, or more
specifically, the udev rules mdadm is supposed to ship. reassigning
** Changed in: mdadm (Ubuntu)
Sourcepackagename: lvm2 => mdadm
** Summary changed:
- Root fs on LVM fails to boot
+ Root fs on LVM on mdadm fails to boot
--
No news? It's really an annoying bug... Could anybody reach a solution?
Thanks, Fastguy
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
according to the bugtrail, this is rather a problem of mdadm, or more
specifically, the udev rules mdadm is supposed to ship. reassigning
** Changed in: mdadm (Ubuntu)
Sourcepackagename: lvm2 => mdadm
** Summary changed:
- Root fs on LVM fails to boot
+ Root fs on LVM on mdadm fails to boot
--
Hi,
I also confirm the behaviour. The volumes mount fine when I do:
'lvm vgscan'
'lvm vgchange -ay; exit'
as mentioned in the first post. The boot process works with a 2.6.19
kernel but not 2.6.20.
Regards,
Fast
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You recei
I've also observed this problem in gutsy: LVM on md (raid1) fails to
boot, an "lvm vgchange -ay" on at the (initramfs) prompt is sufficient
to get it working.
My investigations show two parts to the problem. First, udev's 65
-persistent-storage.rules file explicitly excludes md* devices from
anal
Here's an update:
1) I started my system with the latest 2.6.22-6 kernel
2) Used "lvm vgchange -a y"
3) Mounted the root FS and continued booting.
4) Used my system a little with the new kernel.
and now I'm unable to boot with my 2.6.19 xen kernel anymore. It used to
work OK before I mounted my
The problem still persists on current Feisty with linux-image 2.6.20-12,
udev 103-0ubuntu13, and lvm2 2.02.06-2ubuntu8.
--
Root fs on LVM fails to boot
https://launchpad.net/bugs/87745
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I just saw that in /etc/udev/rules.d/70-lvm.rules the device is tested
against ENV{ID_FS_TYPE}=="lvm*|LVM*" to trigger the vgchange/vgscan.
But
$ grep ID_FS_TYPE /var/log/udev
ID_FS_TYPE=ext3
ID_FS_TYPE=vfat
ID_FS_TYPE=swap
ID_FS_TYPE=ntfs
ID_FS_TYPE=ext3
ID_FS_TYPE=ext3
ID_FS_TYPE=reiserfs
ID_FS_
I can confirm this on a gutsy system with lvm2_2.02.24-6ubuntu1
installed.
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => High
Status: Unconfirmed => Confirmed
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you ar
The problem still persists on current Feisty with linux-image 2.6.20-12,
udev 103-0ubuntu13, and lvm2 2.02.06-2ubuntu8.
--
Root fs on LVM fails to boot
https://launchpad.net/bugs/87745
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I just saw that in /etc/udev/rules.d/70-lvm.rules the device is tested
against ENV{ID_FS_TYPE}=="lvm*|LVM*" to trigger the vgchange/vgscan.
But
$ grep ID_FS_TYPE /var/log/udev
ID_FS_TYPE=ext3
ID_FS_TYPE=vfat
ID_FS_TYPE=swap
ID_FS_TYPE=ntfs
ID_FS_TYPE=ext3
ID_FS_TYPE=ext3
ID_FS_TYPE=reiserfs
ID_FS_
I can confirm this on a gutsy system with lvm2_2.02.24-6ubuntu1
installed.
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => High
Status: Unconfirmed => Confirmed
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you ar
No news? It's really an annoying bug... Could anybody reach a solution?
Thanks, Fastguy
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
according to the bugtrail, this is rather a problem of mdadm, or more
specifically, the udev rules mdadm is supposed to ship. reassigning
** Changed in: mdadm (Ubuntu)
Sourcepackagename: lvm2 => mdadm
** Summary changed:
- Root fs on LVM fails to boot
+ Root fs on LVM on mdadm fails to boot
--
Hi,
I also confirm the behaviour. The volumes mount fine when I do:
'lvm vgscan'
'lvm vgchange -ay; exit'
as mentioned in the first post. The boot process works with a 2.6.19
kernel but not 2.6.20.
Regards,
Fast
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You recei
I've also observed this problem in gutsy: LVM on md (raid1) fails to
boot, an "lvm vgchange -ay" on at the (initramfs) prompt is sufficient
to get it working.
My investigations show two parts to the problem. First, udev's 65
-persistent-storage.rules file explicitly excludes md* devices from
anal
Here's an update:
1) I started my system with the latest 2.6.22-6 kernel
2) Used "lvm vgchange -a y"
3) Mounted the root FS and continued booting.
4) Used my system a little with the new kernel.
and now I'm unable to boot with my 2.6.19 xen kernel anymore. It used to
work OK before I mounted my
The problem still persists on current Feisty with linux-image 2.6.20-12,
udev 103-0ubuntu13, and lvm2 2.02.06-2ubuntu8.
--
Root fs on LVM fails to boot
https://launchpad.net/bugs/87745
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I just saw that in /etc/udev/rules.d/70-lvm.rules the device is tested
against ENV{ID_FS_TYPE}=="lvm*|LVM*" to trigger the vgchange/vgscan.
But
$ grep ID_FS_TYPE /var/log/udev
ID_FS_TYPE=ext3
ID_FS_TYPE=vfat
ID_FS_TYPE=swap
ID_FS_TYPE=ntfs
ID_FS_TYPE=ext3
ID_FS_TYPE=ext3
ID_FS_TYPE=reiserfs
ID_FS_
No news? It's really an annoying bug... Could anybody reach a solution?
Thanks, Fastguy
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
according to the bugtrail, this is rather a problem of mdadm, or more
specifically, the udev rules mdadm is supposed to ship. reassigning
** Changed in: mdadm (Ubuntu)
Sourcepackagename: lvm2 => mdadm
** Summary changed:
- Root fs on LVM fails to boot
+ Root fs on LVM on mdadm fails to boot
--
I can confirm this on a gutsy system with lvm2_2.02.24-6ubuntu1
installed.
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => High
Status: Unconfirmed => Confirmed
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you ar
Hi,
I also confirm the behaviour. The volumes mount fine when I do:
'lvm vgscan'
'lvm vgchange -ay; exit'
as mentioned in the first post. The boot process works with a 2.6.19
kernel but not 2.6.20.
Regards,
Fast
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You recei
I've also observed this problem in gutsy: LVM on md (raid1) fails to
boot, an "lvm vgchange -ay" on at the (initramfs) prompt is sufficient
to get it working.
My investigations show two parts to the problem. First, udev's 65
-persistent-storage.rules file explicitly excludes md* devices from
anal
Here's an update:
1) I started my system with the latest 2.6.22-6 kernel
2) Used "lvm vgchange -a y"
3) Mounted the root FS and continued booting.
4) Used my system a little with the new kernel.
and now I'm unable to boot with my 2.6.19 xen kernel anymore. It used to
work OK before I mounted my
The problem still persists on current Feisty with linux-image 2.6.20-12,
udev 103-0ubuntu13, and lvm2 2.02.06-2ubuntu8.
--
Root fs on LVM fails to boot
https://launchpad.net/bugs/87745
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I just saw that in /etc/udev/rules.d/70-lvm.rules the device is tested
against ENV{ID_FS_TYPE}=="lvm*|LVM*" to trigger the vgchange/vgscan.
But
$ grep ID_FS_TYPE /var/log/udev
ID_FS_TYPE=ext3
ID_FS_TYPE=vfat
ID_FS_TYPE=swap
ID_FS_TYPE=ntfs
ID_FS_TYPE=ext3
ID_FS_TYPE=ext3
ID_FS_TYPE=reiserfs
ID_FS_
No news? It's really an annoying bug... Could anybody reach a solution?
Thanks, Fastguy
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
according to the bugtrail, this is rather a problem of mdadm, or more
specifically, the udev rules mdadm is supposed to ship. reassigning
** Changed in: mdadm (Ubuntu)
Sourcepackagename: lvm2 => mdadm
** Summary changed:
- Root fs on LVM fails to boot
+ Root fs on LVM on mdadm fails to boot
--
Hi,
I also confirm the behaviour. The volumes mount fine when I do:
'lvm vgscan'
'lvm vgchange -ay; exit'
as mentioned in the first post. The boot process works with a 2.6.19
kernel but not 2.6.20.
Regards,
Fast
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You recei
I've also observed this problem in gutsy: LVM on md (raid1) fails to
boot, an "lvm vgchange -ay" on at the (initramfs) prompt is sufficient
to get it working.
My investigations show two parts to the problem. First, udev's 65
-persistent-storage.rules file explicitly excludes md* devices from
anal
Here's an update:
1) I started my system with the latest 2.6.22-6 kernel
2) Used "lvm vgchange -a y"
3) Mounted the root FS and continued booting.
4) Used my system a little with the new kernel.
and now I'm unable to boot with my 2.6.19 xen kernel anymore. It used to
work OK before I mounted my
I can confirm this on a gutsy system with lvm2_2.02.24-6ubuntu1
installed.
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => High
Status: Unconfirmed => Confirmed
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you ar
Hi,
I also confirm the behaviour. The volumes mount fine when I do:
'lvm vgscan'
'lvm vgchange -ay; exit'
as mentioned in the first post. The boot process works with a 2.6.19
kernel but not 2.6.20.
Regards,
Fast
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You recei
I've also observed this problem in gutsy: LVM on md (raid1) fails to
boot, an "lvm vgchange -ay" on at the (initramfs) prompt is sufficient
to get it working.
My investigations show two parts to the problem. First, udev's 65
-persistent-storage.rules file explicitly excludes md* devices from
anal
Here's an update:
1) I started my system with the latest 2.6.22-6 kernel
2) Used "lvm vgchange -a y"
3) Mounted the root FS and continued booting.
4) Used my system a little with the new kernel.
and now I'm unable to boot with my 2.6.19 xen kernel anymore. It used to
work OK before I mounted my
The problem still persists on current Feisty with linux-image 2.6.20-12,
udev 103-0ubuntu13, and lvm2 2.02.06-2ubuntu8.
--
Root fs on LVM fails to boot
https://launchpad.net/bugs/87745
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I just saw that in /etc/udev/rules.d/70-lvm.rules the device is tested
against ENV{ID_FS_TYPE}=="lvm*|LVM*" to trigger the vgchange/vgscan.
But
$ grep ID_FS_TYPE /var/log/udev
ID_FS_TYPE=ext3
ID_FS_TYPE=vfat
ID_FS_TYPE=swap
ID_FS_TYPE=ntfs
ID_FS_TYPE=ext3
ID_FS_TYPE=ext3
ID_FS_TYPE=reiserfs
ID_FS_
No news? It's really an annoying bug... Could anybody reach a solution?
Thanks, Fastguy
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
according to the bugtrail, this is rather a problem of mdadm, or more
specifically, the udev rules mdadm is supposed to ship. reassigning
** Changed in: mdadm (Ubuntu)
Sourcepackagename: lvm2 => mdadm
** Summary changed:
- Root fs on LVM fails to boot
+ Root fs on LVM on mdadm fails to boot
--
I can confirm this on a gutsy system with lvm2_2.02.24-6ubuntu1
installed.
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => High
Status: Unconfirmed => Confirmed
--
Root fs on LVM fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you ar
48 matches
Mail list logo
