Public bug reported:
I built a system with the following filesystem, using the manual partitioning
tool in Ubuntu 8.04 alternate server install CD for amd64:
/dev/sda1 -\
/dev/sdb1 -+-> /dev/md0 -> ext3 (for /boot)
/dev/sda2 -\
/dev/sdb2 -+> /dev/md1 -> LUKS encryption (md1_crypt) -> LVM physical Volume ->
LVM -> root (ext3), /tmp (ext3), /var (ext3, and also swap
(Aside: It took a couple of attempts to arrive at this layering -- I had
originally figured I would put the the encryption on top of LVM, so as
to make booting and troubleshooting easy. However, the layering that I
describe above seemed natural in the installer, and the system only
prompts me for the passphrase once on boot.)
PROBLEM: The problem is that the installer neglected to put any entries
in /etc/crupttab.When I attempted to boot the system for the first time,
it entered the initrd shell.
WORKAROUND: In the initrd shell, I had to run "cryptsetup luksOpen
md1_crypt /dev/md1", "vgscan", and "continue" to be able to boot. Once
the system booted, I manually filled in /etc/crypttab (based on what I
had to enter in the initrd shell), ran "dpkg-reconfigure initramfs-
tools", and rebooted. After these changes, the system boots normally,
and I got on with life.
SOLUTION: The alternate installer on Hardy Server should write
/etc/crypttab when doing a manual install.
** Affects: ubuntu
Importance: Undecided
Status: New
** Description changed:
I built a system with the following filesystem, using the Ubuntu 8.04
alternate server install CD for amd64.
/dev/sda1 -\
/dev/sdb1 -+-> /dev/md0 -> ext3 (for /boot)
/dev/sda2 -\
- /dev/sdb2 -+> /dev/md1 -> LUKS encryption (md1_crypt) -> LVM physical Volume
-> root (ext3), /tmp (ext3), /var (ext3, and also swap
+ /dev/sdb2 -+> /dev/md1 -> LUKS encryption (md1_crypt) -> LVM physical Volume
-> LVM -> root (ext3), /tmp (ext3), /var (ext3, and also swap
(Aside: It took a couple of attempts to arrive at this layering -- I had
originally figured I would put the the encryption on top of LVM, so as
to make booting and troubleshooting easily. However, the layering that
I describe above seemed natural in the installer, and only prompts me
for the passphrase once on boot. The encrypted LVM root volume
automatic-configuration works wonderfully on a single-drive system --
but I couldn't figure out how to install onto an md device with the
automatic installer. So using the manual installer with the
configuration I describe above was my choice.)
PROBLEM: The problem is that the installer neglected to put any entries
in /etc/crupttab.When I attempted to boot the system for the first time,
it entered the initrd shell.
WORKAROUND: In the initrd shell, I had to run "cryptsetup luksOpen
md1_crypt /dev/md1", "vgscan", and "continue" to be able to boot. Once
the system booted, I manually filled in /etc/crypttab (based on what I
had to enter in the initrd shell), ran "dpkg-reconfigure initramfs-
tools", and rebooted. After these changes, the system boots normally,
and I got on with life.
SOLUTION: The alternate installer on Hardy Server should write
/etc/crypttab when doing a manual install.
** Description changed:
- I built a system with the following filesystem, using the Ubuntu 8.04
alternate server install CD for amd64.
+ I built a system with the following filesystem, using the manual partitioning
tool in Ubuntu 8.04 alternate server install CD for amd64.
/dev/sda1 -\
/dev/sdb1 -+-> /dev/md0 -> ext3 (for /boot)
/dev/sda2 -\
/dev/sdb2 -+> /dev/md1 -> LUKS encryption (md1_crypt) -> LVM physical Volume
-> LVM -> root (ext3), /tmp (ext3), /var (ext3, and also swap
(Aside: It took a couple of attempts to arrive at this layering -- I had
originally figured I would put the the encryption on top of LVM, so as
- to make booting and troubleshooting easily. However, the layering that
- I describe above seemed natural in the installer, and only prompts me
- for the passphrase once on boot. The encrypted LVM root volume
- automatic-configuration works wonderfully on a single-drive system --
- but I couldn't figure out how to install onto an md device with the
- automatic installer. So using the manual installer with the
- configuration I describe above was my choice.)
+ to make booting and troubleshooting easy. However, the layering that I
+ describe above seemed natural in the installer, and the system only
+ prompts me for the passphrase once on boot.)
PROBLEM: The problem is that the installer neglected to put any entries
in /etc/crupttab.When I attempted to boot the system for the first time,
it entered the initrd shell.
WORKAROUND: In the initrd shell, I had to run "cryptsetup luksOpen
md1_crypt /dev/md1", "vgscan", and "continue" to be able to boot. Once
the system booted, I manually filled in /etc/crypttab (based on what I
had to enter in the initrd shell), ran "dpkg-reconfigure initramfs-
tools", and rebooted. After these changes, the system boots normally,
and I got on with life.
SOLUTION: The alternate installer on Hardy Server should write
/etc/crypttab when doing a manual install.
** Description changed:
- I built a system with the following filesystem, using the manual partitioning
tool in Ubuntu 8.04 alternate server install CD for amd64.
+ I built a system with the following filesystem, using the manual partitioning
tool in Ubuntu 8.04 alternate server install CD for amd64:
/dev/sda1 -\
/dev/sdb1 -+-> /dev/md0 -> ext3 (for /boot)
/dev/sda2 -\
/dev/sdb2 -+> /dev/md1 -> LUKS encryption (md1_crypt) -> LVM physical Volume
-> LVM -> root (ext3), /tmp (ext3), /var (ext3, and also swap
(Aside: It took a couple of attempts to arrive at this layering -- I had
originally figured I would put the the encryption on top of LVM, so as
to make booting and troubleshooting easy. However, the layering that I
describe above seemed natural in the installer, and the system only
prompts me for the passphrase once on boot.)
PROBLEM: The problem is that the installer neglected to put any entries
in /etc/crupttab.When I attempted to boot the system for the first time,
it entered the initrd shell.
WORKAROUND: In the initrd shell, I had to run "cryptsetup luksOpen
md1_crypt /dev/md1", "vgscan", and "continue" to be able to boot. Once
the system booted, I manually filled in /etc/crypttab (based on what I
had to enter in the initrd shell), ran "dpkg-reconfigure initramfs-
tools", and rebooted. After these changes, the system boots normally,
and I got on with life.
SOLUTION: The alternate installer on Hardy Server should write
/etc/crypttab when doing a manual install.
--
crypttab not updated when building an md->LUKS->LVM root device using Hardy
alternate installcd on amd64
https://bugs.launchpad.net/bugs/274913
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
