Bug#783089: debian-installer: Cannot rescue a system installed on a raid1 lvm
Package: debian-installer
Severity: normal
Tags: d-i
Dear Maintainer,
I created a virtual server with 2 disks of the same size. (Problem wil
be the same on a physical server with 2 disks of the same size)
I did a minimum installation with :
- a partition on the whole disk on each disk of type LVM. (/dev/vda1,
/dev/vda2)
- a volume group with name rootvg with /dev/vda1
- Everything on lvm, with /dev/rootvg/slashlv mounted on / and
/dev/rootvg/swaplv for swap (a minimum partitioned system, I create more
logical volume on my servers)
- grub on /dev/vda
And did a reboot after the installation...
I can work on the server without problem...
After a successul login under root, I did :
- vgextend /dev/rootvg /dev/vdb1
- lvconvert --type raid1 -m 1 /dev/rootvg/slashlv
- lvconvert --type raid1 -m 1 /dev/rootvg/swaplv
- wait for the raid to be completely rebuilded (I checked with the "lvs"
command)
I can work on the server without problem...
But If I reboot, grub can't regnosize my installation... The message
(recopied manually) is :
"Booting from Hard Disk...
error: disk
`lvmid/Gwx3dG-v00h-9hJU-FVuk-Il8Z-bFUK-i6DkfU/KpVdER-OEMM-MWik-vKwM-hWxp-MeJf-LMnsf7'
not found.
Entering rescue mode...
grub rescue>"
So I try to reboot with the rescue mode but the CD of debian lack the
module "dm-raid" on the kernel part. (Probably on a udeb package but
don't know yet exactly which one, so I created this bug report against
debian-installer), so I cannot access my disk anymore !!! Imagine you do
this on a production server and you did'nt reboot before a long time.
For the record, I already filled a bug report for the grub problem
on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782591
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Reply to: