BTS

Issue971

Title grml-rescueboot does not support lvm and md/raid devices
Priority bug Status resolved
Superseder Nosy List faheem
Assigned To Topics

Created on 2011-03-16.18:07:37 by faheem, last changed 2011-08-04.20:21:14 by mru.

Messages
msg3859 (view) Author: mru Date: 2011-06-13.03:58:42
Sorry that it took so long, but we should have a working version:

Download and install the debian package from http://jenkins.grml.org/debian/pool/main/g/grml-rescueboot/

This will generate a slightly different grub.cfg which should contain all necessary dependencies in the 
live-media parameter.

You will have a iso image which supports the new generated live-media parameter, you can use 
http://jenkins.grml.org/job/grml-medium-amd64/102/artifact/2011-06-13_03-16-27/grml_isos/autobuild_2011-
06-13_03-16-27.iso which is a 64bit medium grml.
msg3729 (view) Author: mru Date: 2011-04-01.11:01:46
* Faheem Mitha wrote [29.03.11 17:14]:

> Ok. Thanks for the clarification. Is lvm on raid etc. a planned feature?

I have some idea, i'll try to implment it this weekend.

Ulrich
msg3728 (view) Author: faheem Date: 2011-03-29.15:14:37
On Tue, 29 Mar 2011, Ulrich Dangel wrote:

>
> Ulrich Dangel <mru@grml.org> added the comment:
>
> Ok, thanks for your input. The problem is that for now only lvm or raid devices
> are supported directly. Neiter lvm on raid nor raid on lvm is currently supported.
>
> The problem is that with the current solution, we are using live-media-path for
> it, we can only specify one device to active. In your case it would be two
> devices (raid and lvm) devices to active which is currently not supported.
>
> Please keep in mind that we can't activate per default all devices as it may
> create problems.
>
> We would have to provide some additional arguments ad support recursive devices
> like lvm on raid on raid (raid10).

Ok. Thanks for the clarification. Is lvm on raid etc. a planned feature?
msg3727 (view) Author: mru Date: 2011-03-29.14:49:23
Ok, thanks for your input. The problem is that for now only lvm or raid devices
are supported directly. Neiter lvm on raid nor raid on lvm is currently supported.

The problem is that with the current solution, we are using live-media-path for
it, we can only specify one device to active. In your case it would be two
devices (raid and lvm) devices to active which is currently not supported.

Please keep in mind that we can't activate per default all devices as it may
create problems.

We would have to provide some additional arguments ad support recursive devices
like lvm on raid on raid (raid10).
msg3726 (view) Author: faheem Date: 2011-03-28.23:21:27
On Mon, 28 Mar 2011, Ulrich Dangel wrote:

>
> Ulrich Dangel <mru@grml.org> added the comment:
>
> Ok, the grub config seems to fine. You can specify debug=y on the cmdline to get
> more debug output.

Ok, I'll try that. Any suggestions for writing to a file or external 
device? Otherwise the output will be lost.

> I am currently not sure what the problem is as i tested it with the sid images.
> Can you maybe use the sid iso to run the tests? What is the physical volume of
> of your volumegroup? An usb device?

Which iso did you use, exactly? I'm on 32 bit here, but otherwise I can 
try to duplicate your iso as closely as possible. The VG is on top of a sw 
RAID 1 setup. See below. Did you do LVM on top of software RAID 1?

orwell:/home/faheem# vgdisplay debian
   --- Volume group ---
   VG Name               debian
   System ID
   Format                lvm2
   Metadata Areas        1
   Metadata Sequence No  5
   VG Access             read/write
   VG Status             resizable
   MAX LV                0
   Cur LV                4
   Open LV               4
   Max PV                0
   Cur PV                1
   Act PV                1
   VG Size               465.76 GiB
   PE Size               4.00 MiB
   Total PE              119234
   Alloc PE / Size       36952 / 144.34 GiB
   Free  PE / Size       82282 / 321.41 GiB
   VG UUID               a1OCIH-gpz9-fGLj-zGfI-dwuM-kw0n-r2tZRQ

orwell:/home/faheem# pvs
   PV         VG         Fmt  Attr PSize   PFree
   /dev/md0   testdebian lvm2 a-   111.75g  34.22g
   /dev/md1   debian     lvm2 a-   465.76g 321.41g
   /dev/sdc6  olddebian  lvm2 a-   186.26g  21.26g
   /dev/sdd1  backup     lvm2 a-   186.26g  96.26g

orwell:/home/faheem# mdadm -D /dev/md1
/dev/md1:
         Version : 1.2
   Creation Time : Thu Jan 13 16:45:39 2011
      Raid Level : raid1
      Array Size : 488383352 (465.76 GiB 500.10 GB)
   Used Dev Size : 488383352 (465.76 GiB 500.10 GB)
    Raid Devices : 2
   Total Devices : 2
     Persistence : Superblock is persistent

     Update Time : Tue Mar 29 04:49:38 2011
           State : clean
  Active Devices : 2
Working Devices : 2
  Failed Devices : 0
   Spare Devices : 0

            Name : chrestomanci:1
            UUID : 157f39b8:13bf0624:8810a5a9:d520c548
          Events : 136

     Number   Major   Minor   RaidDevice State
        0       8        1        0      active sync   /dev/sda1
        1       8       17        1      active sync   /dev/sdb1
msg3725 (view) Author: mru Date: 2011-03-28.22:32:38
Ok, the grub config seems to fine. You can specify debug=y on the cmdline to get 
more debug output.

I am currently not sure what the problem is as i tested it with the sid images. 
Can you maybe use the sid iso to run the tests? What is the physical volume of 
of your volumegroup? An usb device?
msg3724 (view) Author: faheem Date: 2011-03-28.21:35:56
On Mon, 28 Mar 2011, Ulrich Dangel wrote:

>
> Ulrich Dangel <mru@grml.org> added the comment:
>
> Did you update your grml.iso? That features requires a current iso image.
>
> If you have a current iso, did the install process regenerate the grub config?
> If not can you please run update-grub and test again? If you updated the grub
> config and it did not work either can you please paste the generated grub config
> for your iso images?

Nope, still doesn't work. Tried with 3/28 grml-small_squeeze_latest.iso. 
Drops to initramfs shell as before. How can I get some debugging output?

The iso is here

orwell:/home/faheem# ls -la /boot/grml/grml-small_squeeze_latest.iso
-rw-r--r-- 1 faheem faheem 123731968 Mar 28 05:10 /boot/grml/grml-small_squeeze_latest.iso

Entire grub.cfg follows.

                                                                  Faheem

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
   load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
   set saved_entry="${prev_saved_entry}"
   save_env saved_entry
   set prev_saved_entry=
   save_env prev_saved_entry
   set boot_once=true
fi

function savedefault {
   if [ -z "${boot_once}" ]; then
     saved_entry="${chosen}"
     save_env saved_entry
   fi
}

function load_video {
   insmod vbe
   insmod vga
   insmod video_bochs
   insmod video_cirrus
}

insmod raid
insmod mdraid1x
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(debian-root)'
search --no-floppy --fs-uuid --set=root 82ade8eb-1533-4129-aa44-ffe590e3be69
if loadfont /usr/share/grub/unicode.pf2 ; then
   set gfxmode=640x480
   load_video
   insmod gfxterm
fi
terminal_output gfxterm
insmod raid
insmod mdraid1x
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(debian-boot)'
search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
set locale_dir=($root)/grub/locale
set lang=en_US
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod raid
insmod mdraid1x
insmod lvm
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(debian-root)'
search --no-floppy --fs-uuid --set=root 82ade8eb-1533-4129-aa44-ffe590e3be69
insmod png
if background_image /usr/share/images/desktop-base/spacefun-grub.png; then
   set color_normal=light-gray/black
   set color_highlight=white/black
else
   set menu_color_normal=cyan/blue
   set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-vserver-686-bigmem' --class debian --class gnu-linux --class gnu --class os {
 	insmod raid
 	insmod mdraid1x
 	insmod lvm
 	insmod part_msdos
 	insmod part_msdos
 	insmod ext2
 	set root='(debian-boot)'
 	search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
 	echo	'Loading Linux 2.6.32-5-vserver-686-bigmem ...'
 	linux	/vmlinuz-2.6.32-5-vserver-686-bigmem root=/dev/mapper/debian-root ro  quiet
 	echo	'Loading initial ramdisk ...'
 	initrd	/initrd.img-2.6.32-5-vserver-686-bigmem
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-vserver-686-bigmem (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
 	insmod raid
 	insmod mdraid1x
 	insmod lvm
 	insmod part_msdos
 	insmod part_msdos
 	insmod ext2
 	set root='(debian-boot)'
 	search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
 	echo	'Loading Linux 2.6.32-5-vserver-686-bigmem ...'
 	linux	/vmlinuz-2.6.32-5-vserver-686-bigmem root=/dev/mapper/debian-root ro single
 	echo	'Loading initial ramdisk ...'
 	initrd	/initrd.img-2.6.32-5-vserver-686-bigmem
}
menuentry 'Debian GNU/Linux, with Linux 2.6.26-2-vserver-686-bigmem' --class debian --class gnu-linux --class gnu --class os {
 	insmod raid
 	insmod mdraid1x
 	insmod lvm
 	insmod part_msdos
 	insmod part_msdos
 	insmod ext2
 	set root='(debian-boot)'
 	search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
 	echo	'Loading Linux 2.6.26-2-vserver-686-bigmem ...'
 	linux	/vmlinuz-2.6.26-2-vserver-686-bigmem root=/dev/mapper/debian-root ro  quiet
 	echo	'Loading initial ramdisk ...'
 	initrd	/initrd.img-2.6.26-2-vserver-686-bigmem
}
menuentry 'Debian GNU/Linux, with Linux 2.6.26-2-vserver-686-bigmem (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
 	insmod raid
 	insmod mdraid1x
 	insmod lvm
 	insmod part_msdos
 	insmod part_msdos
 	insmod ext2
 	set root='(debian-boot)'
 	search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
 	echo	'Loading Linux 2.6.26-2-vserver-686-bigmem ...'
 	linux	/vmlinuz-2.6.26-2-vserver-686-bigmem root=/dev/mapper/debian-root ro single
 	echo	'Loading initial ramdisk ...'
 	initrd	/initrd.img-2.6.26-2-vserver-686-bigmem
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
 	insmod raid
 	insmod mdraid1x
 	insmod lvm
 	insmod part_msdos
 	insmod part_msdos
 	insmod ext2
 	set root='(debian-boot)'
 	search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
 	linux16	/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
 	insmod raid
 	insmod mdraid1x
 	insmod lvm
 	insmod part_msdos
 	insmod part_msdos
 	insmod ext2
 	set root='(debian-boot)'
 	search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
 	linux16	/memtest86+.bin console=ttyS0,115200n8
}
menuentry "Memory test (memtest86+, experimental multiboot)" {
 	insmod raid
 	insmod mdraid1x
 	insmod lvm
 	insmod part_msdos
 	insmod part_msdos
 	insmod ext2
 	set root='(debian-boot)'
 	search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
 	multiboot	/memtest86+_multiboot.bin
}
menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
 	insmod raid
 	insmod mdraid1x
 	insmod lvm
 	insmod part_msdos
 	insmod part_msdos
 	insmod ext2
 	set root='(debian-boot)'
 	search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
 	multiboot	/memtest86+_multiboot.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  $prefix/custom.cfg ]; then
   source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

### BEGIN /etc/grub.d/42_grml ###
menuentry "Grml Rescue System (grml-small_squeeze_latest.iso)" {
         insmod raid
         insmod mdraid1x
         insmod lvm
         insmod part_msdos
         insmod part_msdos
         insmod ext2
         set root='(debian-boot)'
         search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
         iso_path="/grml/grml-small_squeeze_latest.iso"
         export iso_path
         kernelopts=" ssh=foobarbaz live-media=/dev/mapper/debian-boot "
         export kernelopts
         loopback loop "/grml/grml-small_squeeze_latest.iso"
         set root=(loop)
         configfile /boot/grub/loopback.cfg
}
### END /etc/grub.d/42_grml ###

### BEGIN /etc/grub.d/43_plop ###
menuentry 'Plop Boot Manager' {
 	  insmod raid
           insmod mdraid1x
           insmod lvm
           insmod part_msdos
           insmod part_msdos
 	  insmod ext2
           set root='(debian-boot)'
           search --no-floppy --fs-uuid --set=root 93ea47bb-16a1-4b52-a7eb-f17ea430d6cf
           linux16 /plpbt.bin
}
### END /etc/grub.d/43_plop ###
msg3723 (view) Author: faheem Date: 2011-03-28.19:11:24
On Mon, 28 Mar 2011, Michael Prokop wrote:

>
> Michael Prokop <mika@grml.org> added the comment:
>
> * Faheem Mitha wrote in grml's BTS on 20110328 / 19:41:
>
>>> Did you update your grml.iso? That features requires a current iso image.
>
>> No. It is the same iso as I had before, namely grml_2010.12.iso. What is a
>> current iso image?
>
> The ones from daily.grml.org, featuring latest development.

Ok, I'll try those. Thanks.

            Regards, Faheem
msg3722 (view) Author: mika Date: 2011-03-28.18:36:42
* Faheem Mitha wrote in grml's BTS on 20110328 / 19:41:

> > Did you update your grml.iso? That features requires a current iso image.

> No. It is the same iso as I had before, namely grml_2010.12.iso. What is a 
> current iso image?

The ones from daily.grml.org, featuring latest development.

regards,
-mika-
msg3721 (view) Author: faheem Date: 2011-03-28.17:41:14
On Mon, 28 Mar 2011, Ulrich Dangel wrote:

>
> Ulrich Dangel <mru@grml.org> added the comment:
>
> Did you update your grml.iso? That features requires a current iso image.

No. It is the same iso as I had before, namely grml_2010.12.iso. What is a 
current iso image?

> If you have a current iso, did the install process regenerate the grub config?
> If not can you please run update-grub and test again? If you updated the grub
> config and it did not work either can you please paste the generated grub config
> for your iso images?
>
> _____________________________________
> GRML issue tracker <bts@bts.grml.org>
> <http://bts.grml.org/grml/issue971>
> _____________________________________
>
>
msg3720 (view) Author: mru Date: 2011-03-28.16:32:42
Did you update your grml.iso? That features requires a current iso image. 

If you have a current iso, did the install process regenerate the grub config? 
If not can you please run update-grub and test again? If you updated the grub 
config and it did not work either can you please paste the generated grub config 
for your iso images?
msg3719 (view) Author: faheem Date: 2011-03-28.16:12:08
Hi,

I tried with 0.3.3, and I see exactly the same problem. It drops down to 
an initramfs prompt instead of booting the Grml live cd.

                                                          Regards, Faheem

On Fri, 25 Mar 2011, Christian Hofstaedtler wrote:

>
> Christian Hofstaedtler <ch@grml.org> added the comment:
>
> We believe that your issue has been closed by the upload of
> Version 0.3.2 of grml-rescueboot from Christian Hofstaedtler <ch@grml.org>.
> The explanation is attached below
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Format: 1.8
> Date: Fri, 25 Mar 2011 22:52:36 +0100
> Source: grml-rescueboot
> Binary: grml-rescueboot
> Architecture: source all
> Version: 0.3.2
> Distribution: unstable
> Urgency: low
> Maintainer: Andreas "Jimmy" Gredler <jimmy@grml.org>
> Changed-By: Christian Hofstaedtler <ch@grml.org>
> Description:
> grml-rescueboot - Integrates ISO-booting into grub
> Changes:
> grml-rescueboot (0.3.2) unstable; urgency=low
> .
>   [ Ulrich Dangel ]
>   * [e5a68ae] Refactored 42_grml and support lvm devices [Closes: issue971].
> Checksums-Sha1:
> 1bebe31698b0864a16a2dfc397857ad5d9585569 1472 grml-rescueboot_0.3.2.dsc
> ec6db71561ba6953adc47100178d1587bba925e2 4449 grml-rescueboot_0.3.2.tar.gz
> d5bd284240842c69e18a17340b6c62cf31afdf5c 4208 grml-rescueboot_0.3.2_all.deb
> Checksums-Sha256:
> 45b8c918d6737f11df944859a473f0c32b5d50b4e464c29ef7eda8a867298918 1472 grml-rescueboot_0.3.2.dsc
> ac0d6dd0822765e5d0962a917de4a78d1699e42c63e2833240164b75cbb09090 4449 grml-rescueboot_0.3.2.tar.gz
> 95aed38f554f450e89e4413b5037f00cce79e990eb88c51f7a513c453f528058 4208 grml-rescueboot_0.3.2_all.deb
> Files:
> b194b22a43bc76187455839ff8185281 1472 misc extra grml-rescueboot_0.3.2.dsc
> e433875b12eb5349dc5f6027fda5df58 4449 misc extra grml-rescueboot_0.3.2.tar.gz
> ade2323d9d506333eb41d371400c683a 4208 misc extra grml-rescueboot_0.3.2_all.deb
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
>
> iQIcBAEBCAAGBQJNjQ/XAAoJEL7IfitBhWKaSNEP/RjSxjtV3VGxANMx/DSy9QCQ
> ohuE5/uy2zxGdl3PdtomOuuSis80cSiezZOhGqD5wLSf9ldrr3vi8qp8HJB/T2QE
> qszXL/nN/kCvpzZWw8X3usK/coFwWh7DiGRX+Gz1pgcwjXnUbZ7eN+yIxbv9TaXT
> gQJj7Z+OHnCwdX4TfISAnvgzNsbyWFRXmE6JM1P8MSTt6L2uDURx+MQiGoLmihPi
> oQYNTlqk5vX8/r/LqpvrzimJz0GDUwvibaJUQvTupi32ZKX04RZkBTaIMXDLKqMo
> AcgLb/OieTm3xQvv6k4LRGIOkFGzscyEsh/JRHbBJZ49dJc8qOjoqsVCwvT23wj/
> Uxk70FBmVN8HV4ggJ9PQKk8Bg7doen4VZdQHBE1/8SAFinFNFIZaH/KA7ZaTle1f
> NncDwJJvbbwDWET1V6RSwvwcC6FwiO6rl/VtE9NrhUhuRLOGC2sq5Nsu2ZlRSjPX
> TRzrINoe6KyJZewKiu7XYsrtRKdWNUleBx3cQQ/Zec+DNJzSQZPFozJosoN0b/7A
> ZVtfTBVpggbO35fl3MBj6PibK/hHR0VAW2sH2ufsHmIJ5bHTkhOntTq88zPihOIf
> cQin4BapeP9pSdQa8YTl4NVzlI9omlys99LaRnOpc7q8P9NZgLuGGrY5z3jKkqBP
> KCi1MQwos6X8BA7Tse55
> =m/9X
> -----END PGP SIGNATURE-----
>
> ----------
> status: unread -> resolved
>
> _____________________________________
> GRML issue tracker <bts@bts.grml.org>
> <http://bts.grml.org/grml/issue971>
> _____________________________________
>
>
msg3718 (view) Author: ch Date: 2011-03-25.22:16:32
We believe that your issue has been closed by the upload of
Version 0.3.2 of grml-rescueboot from Christian Hofstaedtler <ch@grml.org>.
The explanation is attached below

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 25 Mar 2011 22:52:36 +0100
Source: grml-rescueboot
Binary: grml-rescueboot
Architecture: source all
Version: 0.3.2
Distribution: unstable
Urgency: low
Maintainer: Andreas "Jimmy" Gredler <jimmy@grml.org>
Changed-By: Christian Hofstaedtler <ch@grml.org>
Description: 
 grml-rescueboot - Integrates ISO-booting into grub
Changes: 
 grml-rescueboot (0.3.2) unstable; urgency=low
 .
   [ Ulrich Dangel ]
   * [e5a68ae] Refactored 42_grml and support lvm devices [Closes: issue971].
Checksums-Sha1: 
 1bebe31698b0864a16a2dfc397857ad5d9585569 1472 grml-rescueboot_0.3.2.dsc
 ec6db71561ba6953adc47100178d1587bba925e2 4449 grml-rescueboot_0.3.2.tar.gz
 d5bd284240842c69e18a17340b6c62cf31afdf5c 4208 grml-rescueboot_0.3.2_all.deb
Checksums-Sha256: 
 45b8c918d6737f11df944859a473f0c32b5d50b4e464c29ef7eda8a867298918 1472 grml-rescueboot_0.3.2.dsc
 ac0d6dd0822765e5d0962a917de4a78d1699e42c63e2833240164b75cbb09090 4449 grml-rescueboot_0.3.2.tar.gz
 95aed38f554f450e89e4413b5037f00cce79e990eb88c51f7a513c453f528058 4208 grml-rescueboot_0.3.2_all.deb
Files: 
 b194b22a43bc76187455839ff8185281 1472 misc extra grml-rescueboot_0.3.2.dsc
 e433875b12eb5349dc5f6027fda5df58 4449 misc extra grml-rescueboot_0.3.2.tar.gz
 ade2323d9d506333eb41d371400c683a 4208 misc extra grml-rescueboot_0.3.2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJNjQ/XAAoJEL7IfitBhWKaSNEP/RjSxjtV3VGxANMx/DSy9QCQ
ohuE5/uy2zxGdl3PdtomOuuSis80cSiezZOhGqD5wLSf9ldrr3vi8qp8HJB/T2QE
qszXL/nN/kCvpzZWw8X3usK/coFwWh7DiGRX+Gz1pgcwjXnUbZ7eN+yIxbv9TaXT
gQJj7Z+OHnCwdX4TfISAnvgzNsbyWFRXmE6JM1P8MSTt6L2uDURx+MQiGoLmihPi
oQYNTlqk5vX8/r/LqpvrzimJz0GDUwvibaJUQvTupi32ZKX04RZkBTaIMXDLKqMo
AcgLb/OieTm3xQvv6k4LRGIOkFGzscyEsh/JRHbBJZ49dJc8qOjoqsVCwvT23wj/
Uxk70FBmVN8HV4ggJ9PQKk8Bg7doen4VZdQHBE1/8SAFinFNFIZaH/KA7ZaTle1f
NncDwJJvbbwDWET1V6RSwvwcC6FwiO6rl/VtE9NrhUhuRLOGC2sq5Nsu2ZlRSjPX
TRzrINoe6KyJZewKiu7XYsrtRKdWNUleBx3cQQ/Zec+DNJzSQZPFozJosoN0b/7A
ZVtfTBVpggbO35fl3MBj6PibK/hHR0VAW2sH2ufsHmIJ5bHTkhOntTq88zPihOIf
cQin4BapeP9pSdQa8YTl4NVzlI9omlys99LaRnOpc7q8P9NZgLuGGrY5z3jKkqBP
KCi1MQwos6X8BA7Tse55
=m/9X
-----END PGP SIGNATURE-----
msg3695 (view) Author: faheem Date: 2011-03-16.18:07:37
When trying to use grml-rescueboot with a Grml iso on my system, which has lvm 
logical volumes on top of a RAID 1 soft raid array, the machine boots as far as  
a Grml prompt, and then drops down to a initramfs prompt with any explanation.
History
Date User Action Args
2011-08-04 20:21:14mrusetstatus: chatting -> resolved
2011-06-13 03:58:42mrusetmessages: + msg3859
2011-04-01 11:01:46mrusetmessages: + msg3729
2011-03-29 15:14:37faheemsetmessages: + msg3728
2011-03-29 14:49:23mrusetmessages: + msg3727
2011-03-28 23:21:29faheemsetmessages: + msg3726
2011-03-28 22:32:39mrusetmessages: + msg3725
2011-03-28 21:35:57faheemsetmessages: + msg3724
2011-03-28 19:11:25faheemsetmessages: + msg3723
2011-03-28 18:36:43mikasetmessages: + msg3722
2011-03-28 17:41:15faheemsetmessages: + msg3721
2011-03-28 16:32:43mrusetmessages: + msg3720
2011-03-28 16:12:09faheemsetstatus: resolved -> chatting
messages: + msg3719
2011-03-25 22:16:33chsetstatus: unread -> resolved
messages: + msg3718
2011-03-16 18:07:37faheemcreate