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]
