Bug#398464: root on ext3 over lvm over dm-crypt over raid 1 fails to boot
On Tue, November 14, 2006 14:01, Mario Schubert said: > On Tuesday 14 November 2006 09:48, you wrote: >> The problem is a disagreement between partman-md and >> partman-crypto which results in a bogus /etc/fstab on the target fs and >> after that everything goes downhill (see #393728 for more details). > > Is there a way to fix the installation? > /etc/fstab ? > /etc/crypttab ? Both are potentionally wrong. You'd need to get the (unencrypted) fs setup, chroot into it, fix those two files and regenerate the initramfs image. This can either be done from the limited rescue shell included in the initramfs image (boot with the "break" command line option) or with debian-installer (boot it with the "rescue" option). In the intramfs/d-i rescue shell you'll need to manually setup the target fs (probably with manual invocations of mdadm and cryptsetup), chroot into it (chroot /target), do the fixes and then run "initramfs-update -u" and reboot. Whether you'll be able to sort it out mostly depends on your skills :) Another alternative is to redo the install and just before the last (reboot) step, change to VT2 (alt + F2), your installed system should still be available under /target which will allow you to apply the necessary fixes (unfortunately I can't tell you exactly what needs to be changed cause I don't know what the contents of those two files will be after the installation). I'm sorry if these instructions are a bit vague, but it's hard to provide better ones with the information I have at hand. >> Hopefully I'll have time to look into this soon or we'll have to mention >> that crypto and md are not compatible in the debian-installer errata. > > This would be great. Tell me, if I can help. E.g. Testing it. I'll let you know when some progress has been made. Please keep [EMAIL PROTECTED] CC:ed on any further mails you send regarding this problem so that others are also kept up-to-date. -- David Härdeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#398464: root on ext3 over lvm over dm-crypt over raid 1 fails to boot
reassign 398464 partman-crypto forcemerge 393728 397872 398464 thanks On Mon, November 13, 2006 23:57, martin f krafft said: > also sprach Mario Schubert <[EMAIL PROTECTED]> [2006.11.13.2314 > +0100]: >> device-mapper: ... initialised ... >> Volume group "vg0" not found >> No cryptroot configured, skipping > > cryptroot is defined to run after lvm, for whatever reason. The > cryptsetup people can probably tell you why and suggest a fix. That's not the problem (cryptsetup takes care of both post and pre-setup of lvm if necessary). The problem is a disagreement between partman-md and partman-crypto which results in a bogus /etc/fstab on the target fs and after that everything goes downhill (see #393728 for more details). Hopefully I'll have time to look into this soon or we'll have to mention that crypto and md are not compatible in the debian-installer errata. -- David Härdeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#398464: root on ext3 over lvm over dm-crypt over raid 1 fails to boot
reassign 398464 cryptsetup thanks also sprach Mario Schubert <[EMAIL PROTECTED]> [2006.11.13.2314 +0100]: > device-mapper: ... initialised ... > Volume group "vg0" not found > No cryptroot configured, skipping cryptroot is defined to run after lvm, for whatever reason. The cryptsetup people can probably tell you why and suggest a fix. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#398464: root on ext3 over lvm over dm-crypt over raid 1 fails to boot
Package: installation-reports Boot method: CD Netinst by Peppercon Eric Samba mounted image Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: 20061113 21:00 image: 119910400 Nov 11 07:31 Machine: hosted server Processor: AMD Athlon Memory: 1 GB Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O ] Detect network card:[O ] Configure network: [O ] Detect CD: [O ] Load installer modules: [O ] Detect hard drives: [O ] Partition hard drives: [O ] Install base system:[O ] Clock/timezone setup: [O ] User/password setup:[O ] Install tasks: [O ] Install boot loader:[O ] Overall install:[O ] Comments/Problems: The reboot fails, because the root partition is not found. ... mdadm: look O.K. Sucess: assembled all arrays. Done. device-mapper: ... initialised ... Volume group "vg0" not found No cryptroot configured, skipping Done. Begin: Waiting for root file system... ... My wished configuration: two harddisks partitions for /boot (RAID1), swap and the rest. The rest is RAID1, then encrypted with dm-crypt, then lvm and finally a root volume with ext3. I was able to configure it with the installer, but the reboot failed. I think the devices are set up in the wrong order. Thank you for your help. Ciao, Mario - Mario Schubert, Munich, Germany [EMAIL PROTECTED] -
