Bug 498231
Summary: | Entries in /etc/crypttab are not mounted on boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mark Watts <markrwatts> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | extras-orphan, notting, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-04-30 19:27:56 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mark Watts
2009-04-29 14:38:19 UTC
What happens if you remake the initrd?b No change: # mkinitrd -f test.img 2.6.27.21-170.2.56.fc10.i686.PAE # lsinitrd test.img | grep luksOpen plymouth ask-for-password --command "cryptsetup luksOpen /dev/sda2 luks-9867d209-846c-4de8-8d78-479f42ecce2a" init Compared to: # lsinitrd /boot/initrd-2.6.27.21-170.2.56.fc10.i686.PAE.img | grep luksOpen plymouth ask-for-password --command "cryptsetup luksOpen /dev/sda2 luks-9867d209-846c-4de8-8d78-479f42ecce2a" init Hm, what happens if you remove/recreate /etc/blkid/blkid.tab? On boot, blkid.tab appears to be regenerated automatically, and contains this: <device DEVNO="0x0801" TIME="1241078809" LABEL="/boot" UUID="e51ffd53-fddd-4d0e-9204-38e8d5dd5779" TYPE="ext3" SEC_TYPE="ext2">/dev/sda1</device> <device DEVNO="0x0802" TIME="1241078297" UUID="9867d209-846c-4de8-8d78-479f42ecce2a" TYPE="crypt_LUKS">/dev/sda2</device> <device DEVNO="0xfd00" TIME="1241078297" UUID="sgWWKy-SLBW-2cGy-hi62-pa8M-H4uv-qXB88c" TYPE="lvm2pv">/dev/dm-0</device> <device DEVNO="0xfd01" TIME="1241078297" LABEL="F10-i686-Live" UUID="354b94c6-01ce-4126-9c93-29f0ba74a015" TYPE="ext3">/dev/dm-1</device> <device DEVNO="0xfd02" TIME="1241078297" TYPE="swap">/dev/dm-2</device> <device DEVNO="0x0811" TIME="1241078297" UUID="b94a0dc2-b333-4196-9e15-0cd94b594473" TYPE="crypt_LUKS">/dev/sdb1</device> The latter entry is the correct UUID for my new sdb1 LUKS volume. Note that I've manually luksOpen'd and mounted sdb1 by the time I've looked at this file. However, the blkid.tab file that was present before I rebooted looked different: <device DEVNO="0x0802" TIME="1241021981" UUID="9867d209-846c-4de8-8d78-479f42ecce2a" TYPE="crypt_LUKS">/dev/sda2</device> <device DEVNO="0x0801" TIME="1241021981" LABEL="/boot" UUID="e51ffd53-fddd-4d0e-9204-38e8d5dd5779" TYPE="ext3" SEC_TYPE="ext2">/dev/sda1</device> <device DEVNO="0xfd01" TIME="1241021981" PRI="45" LABEL="F10-i686-Live" UUID="354b94c6-01ce-4126-9c93-29f0ba74a015" TYPE="ext3">/dev/mapper/VolGroup00-LogVol00</device> <device DEVNO="0xfd02" TIME="1241021981" PRI="45" TYPE="swap">/dev/mapper/VolGroup00-LogVol01</device> <device DEVNO="0xfd00" TIME="1241021981" PRI="40" UUID="sgWWKy-SLBW-2cGy-hi62-pa8M-H4uv-qXB88c" TYPE="lvm2pv">/dev/mapper/luks-9867d209-846c-4de8-8d78-479f42ecce2a</device> <device DEVNO="0xfd01" TIME="1241021981" LABEL="F10-i686-Live" UUID="354b94c6-01ce-4126-9c93-29f0ba74a015" TYPE="ext3">/dev/VolGroup00/LogVol00</device> <device DEVNO="0xfd02" TIME="1241021981" TYPE="swap">/dev/VolGroup00/LogVol01</device> <device DEVNO="0x0811" TIME="1241021981" UUID="b94a0dc2-b333-4196-9e15-0cd94b594473" TYPE="crypt_LUKS">/dev/sdb1</device> <device DEVNO="0xfd03" TIME="1241021981" UUID="tsc7tj-4qDK-1IQ4-dhP1-KSgG-g1Hs-nZ89z7" TYPE="lvm2pv">/dev/mapper/luks-b94a0dc2-b333-4196-9e15-0cd94b594473</device> <device DEVNO="0xfd04" TIME="1241021981" UUID="92d7f012-9c0a-44c8-9193-0a3330da5acc" TYPE="ext4">/dev/mapper/VolGroup01-LogVol00</device> Also, the same file after running "blkid" looks like this: <device DEVNO="0x0801" TIME="1241079217" LABEL="/boot" UUID="e51ffd53-fddd-4d0e-9204-38e8d5dd5779" TYPE="ext3" SEC_TYPE="ext2">/dev/sda1</device> <device DEVNO="0x0802" TIME="1241079217" UUID="9867d209-846c-4de8-8d78-479f42ecce2a" TYPE="crypt_LUKS">/dev/sda2</device> <device DEVNO="0xfd00" TIME="1241079217" UUID="sgWWKy-SLBW-2cGy-hi62-pa8M-H4uv-qXB88c" TYPE="lvm2pv">/dev/dm-0</device> <device DEVNO="0xfd01" TIME="1241079217" LABEL="F10-i686-Live" UUID="354b94c6-01ce-4126-9c93-29f0ba74a015" TYPE="ext3">/dev/dm-1</device> <device DEVNO="0xfd02" TIME="1241079217" TYPE="swap">/dev/dm-2</device> <device DEVNO="0x0811" TIME="1241079217" UUID="b94a0dc2-b333-4196-9e15-0cd94b594473" TYPE="crypt_LUKS">/dev/sdb1</device> <device DEVNO="0xfd03" TIME="1241079217" UUID="tsc7tj-4qDK-1IQ4-dhP1-KSgG-g1Hs-nZ89z7" TYPE="lvm2pv">/dev/dm-3</device> <device DEVNO="0xfd04" TIME="1241079217" UUID="92d7f012-9c0a-44c8-9193-0a3330da5acc" TYPE="ext4">/dev/dm-4</device> In each case, the UUID of the /dev/sdb1 LUKS volume is correct, but its just not being processed. I don't even get asked for a second passphrase (even though the passphrase is the same on both /dev/sda2 and /dev/sdb1). Just to confirm; you're running the errata initscripts, correct? Are /dev/sda and /dev/sdb on the same controller? initscripts-8.86.3-1.i386 /dev/sda is a SATA disk connected to my motherboard. /dev/sdb is a Hardware RAID-1 on an Adaptec 2410SA card. It's a gross hack, but... what happens if you add a 'sleep 5' before the 'scsi_wait_scan' lines in rc.sysinit? I added a "sleep 10" (for good measure :) where you said. I see the boot process pausing for 10 seconds right after setting the hostname, and then we're back to square one - no Logical Volumes found. After typing my root password to enter "disk fixing mode", I checked dmesg and the Adaptec controller is being detected just fine, before my ethernet cards. And presumably: - the partition check for those disks occurs there as well (early, during udev) - changing the entry in crypttab to /dev/disk/by-uuid/b94a0dc2-b333-4196-9e15-0cd94b594473 does not help? *sigh* luks-9867d209-846c-4de8-8d78-479f42ecce2a UUID=9867d209-846c-4de8-8d78-479f42ecce2a none luks-b94a0dc2-b333-4196-9e15-0cd94b594473 UUID-b94a0dc2-b333-4196-9e15-0cd94b594473 none Spot the typo... Nothing to see here... move along... Although, nothing complained about incorrect syntax, which would have been nice. We have: [ -b "$src" ] || continue I suppose we could instrument that to throw an error/warning. In any case, closing. |