Bug#554506: cryptsetup: unable to find root volume
severity 554506 grave thanks raising the severity since this issue leaves the system unbootable after installation. mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554506: cryptsetup: unable to find root volume
i've run into this issue as well while attempting to install a new squeeze instance in a virtualbox vm. if you're having trouble reproducing the problem, the following steps should be able to reproduce it: 1. use a recent image such as [0], and start the installation 2. once you get to partitioning, go into LVM setup (not encrypted LVM yet) 3. create an LVM volume (i used the whole virtualbox disk image for this) 4. create a logical volume called boot 5. create a logical volume called swap 6. create a logical volume called root 7. finish LVM setup 8. go into the encrypted LVM setup 9. select the existing swap and root logical volumes to encrypt 10. finish encrypted LVM setup (entering passphrase, erasing, etc) 11. format the boot logical volume as ext2 mounted at /boot 12. format the crypto root logical volume as ext3 mounted at / 13. format the crypto swap logical volume as swap 14. finish partitioning and write changes 15. complete the rest of the installation 16. reboot to find error lvm device name (...) does not begin with /dev/mapper/ mike [0] http://cdimage.debian.org/cdimage/daily-builds/daily/current/i386/iso-cd/debian-testing-i386-netinst.iso note: i had originally run into the problem with the squeeze alpha 1 image, but there were additional warnings about device renaming, so i chose to use the newer media to avoid that as a potential cause http://cdimage.debian.org/cdimage/squeeze_di_alpha1/i386/iso-cd/debian-testing-i386-netinst.iso -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554506: [pkg-cryptsetup-devel] Bug#554506: cryptsetup: unable to find root volume
On Sun, Jun 20, 2010 at 14:54 +0200, Jonas Meurer wrote: [...] i just tried to reproduce the bug, and failed. can you confirm, that this bug no longer applies? otherwise please give exact information about your system: /etc/fstab, /etc/crypttab, and from inside the initramfs: /conf/conf.d/cryptroot. I've tested the provided packages, the original ones as well as those that recently migrated to squeeze and still run into this bug. I agree that we all might run into different bugs and am unsure what exactly is causing it for me. Short description: -- My Thinkpad T60 SATA controller can be configured to operate in two modes, AHCI and Compatible. I have been using it in Compatible mode ever since, but when I switch to AHCI I get the following error: --- snip --- Unable to find LVM volume name_of_lvm/swap cryptsetup: lvm device name (/dev/disk/by-uuid/...) does not begin with /dev/mapper cryptsetup: evms_activate is not available --- snip --- kind regards Wolodja -- .''`. Wolodja Wentlandwentl...@cl.uni-heidelberg.de : :' : `. `'` 4096R/CAF14EFC `- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC signature.asc Description: Digital signature
Bug#554506: [pkg-cryptsetup-devel] Bug#554506: cryptsetup: unable to find root volume
hey Riku, On 24/06/2010 Riku Voipio wrote: On Thu, Jun 24, 2010 at 11:58:08AM +0300, Riku Voipio wrote: -crypttab- hda2_crypt /dev/hda2 none luks -- switching this from hda2-sda2 makes it now boot. hrmh. Still, the error message remains. which error message do you mean? volume group aardvark not found skipping volume group aardvark. or cryptsetup: lvm device name (/dev/hda1 does not begin with /dev/mapper/. greetings, jonas signature.asc Description: Digital signature
Bug#554506: cryptsetup: unable to find root volume
hey Philip, Wolodja, Christoph, Denis, Riku and Matúš, It's hard to track this bug, and to be honest I'm not even sure whether all of you spotted the same bug. Thus it would be helpful if you could try to reproduce the bug once again with preliminary cryptsetup packages that I prepared. You can find the packages (i386 and amd64) at http://people.debian.org/~mejo/cryptsetup/ I'm looking forward to receive your reports :-) greetings, jonas signature.asc Description: Digital signature
Bug#554506: cryptsetup: unable to find root volume
Hi, Running squeeze, encountered this bug after an upgrade of udev from 157-1 to 158-1 was done and the initrd was rebuilt. The root device to unlock is defined by '/dev/disks/by-uuid/uuid here' in crypttab. After failing to unlock the root device busybox drops in and I was able to check nodes under /dev; there were no hdx nor sdx files created here, however dmesg shows they were found (I'm not in front of affected PC now, cannot verify whether they were 'sda' or 'hda'). Another thing noticed (I was able to boot a different kernel w/ older initrd) - following the udev update the nodes of my PATA HDD (root device) were shown as 'sda' instead of being 'hda' w/ the earlier version of udev. I can provide you w/ more details once I get to that PC. Looking forward to see this bug resolved. Hope this helps, Matus +421 908 652713 http://tilosaza.blogspot.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554506: cryptsetup: unable to find root volume
Hi, I have now with lenny-squeeze upgrade: volume group aardvark not found skipping volume group aardvark. cryptsetup: lvm device name (/dev/hda1 does not begin with /dev/mapper/. -fstab- /dev/mapper/aardvark-root / ext3 errors=remount-ro,noatime,nodiratime 0 1 -- -crypttab- hda2_crypt /dev/hda2 none luks -- No UUID's anywhere - are they mandatory now? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554506: cryptsetup: unable to find root volume
On Thu, Jun 24, 2010 at 11:58:08AM +0300, Riku Voipio wrote: -crypttab- hda2_crypt /dev/hda2 none luks -- switching this from hda2-sda2 makes it now boot. hrmh. Still, the error message remains. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554506: [pkg-cryptsetup-devel] Bug#554506: Bug#554506: Bug#554506: cryptsetup: unable to find root volume
hey again, On 25/02/2010 Jonas Meurer wrote: On 05/11/2009 Max Vozeler wrote: We recently changed d-i to use UUID in crypttab entries, which is likely to be causing this problem. Jonas, do you think the initramfs script can be adapted to allow UUID or should partman-crypto go back to /dev/mapper for the root backing device for now? (No time to look deeper into it right now, sorry.) i take a deeper look now, and figued out what the real problem is here: in case that the setup is LUKS on LVM, the cryptroot initramfs script needs to determine the volume group to start in order to make the underlying logical volume available before unlocking it with cryptsetup. this is done by parsing the cryptsetup source device. for example the source device /dev/mapper/vg00-root leads to volume group vg00 being activated. when the UUID is given instead, no information about the volume group can be extracted. i don't know what the propper fix is yet. i might change the cryptroot hook script to always transfer UUID to path for /conf/conf.d/cryptroot in initramfs. but then i don't see a reason to use UUIDs in initramfs at all. any other solution that i see now (e.g. to detect LUKS over LVM in cryptroot hook and save the volume group name in /conf/conf.d/cryptroot) would require intrusive changes to the cryptroot implementation. i just tried to reproduce the bug, and failed. can you confirm, that this bug no longer applies? otherwise please give exact information about your system: /etc/fstab, /etc/crypttab, and from inside the initramfs: /conf/conf.d/cryptroot. greetings, jonas signature.asc Description: Digital signature
Bug#554506: [pkg-cryptsetup-devel] Bug#554506: Bug#554506: cryptsetup: unable to find root volume
hey, On 05/11/2009 Max Vozeler wrote: On Thu, Nov 05, 2009 at 12:44:36AM +0100, Philip Frei wrote: volume group debian not found. skipping volume group debian. unable to find LVM volume debian/root volume group debian not found. cryptsetup: lvm device name (dev/disk/by-uuid/$FOO) does not begin with /dev/mapper We recently changed d-i to use UUID in crypttab entries, which is likely to be causing this problem. Jonas, do you think the initramfs script can be adapted to allow UUID or should partman-crypto go back to /dev/mapper for the root backing device for now? (No time to look deeper into it right now, sorry.) i take a deeper look now, and figued out what the real problem is here: in case that the setup is LUKS on LVM, the cryptroot initramfs script needs to determine the volume group to start in order to make the underlying logical volume available before unlocking it with cryptsetup. this is done by parsing the cryptsetup source device. for example the source device /dev/mapper/vg00-root leads to volume group vg00 being activated. when the UUID is given instead, no information about the volume group can be extracted. i don't know what the propper fix is yet. i might change the cryptroot hook script to always transfer UUID to path for /conf/conf.d/cryptroot in initramfs. but then i don't see a reason to use UUIDs in initramfs at all. any other solution that i see now (e.g. to detect LUKS over LVM in cryptroot hook and save the volume group name in /conf/conf.d/cryptroot) would require intrusive changes to the cryptroot implementation. greetings, jonas signature.asc Description: Digital signature
Bug#554506: cryptsetup: unable to find root volume
I had the same problem with a new installation of debian sqeeze. Even if i recreate the missing directory /dev/disk/by-uuid and the symlinks for the lvm and crypto devices, it does not work. Only the change from uuid to device names at the file /etc/crypttab worked for me. I do not know, why you want to use the uuid, if even the file /etc/fstab is not using them. Regards, Dennis signature.asc Description: OpenPGP digital signature
Bug#554506: cryptsetup: unable to find root volume
Package: cryptsetup
Version: 2:1.1.0~rc2-1
Severity: normal
I can confirm this bug on my platform, but I am not sure if it is
related to UUIDs. I only run into this issue if I set my SATA controller
to operate in AHCI mode and it works fine when I use the Compatibility
mode. The same bug also occurs if I use the following crypttab:
,-- /etc/crypttab ---
| sda3_crypt /dev/sda3 none luks
`---
I tried mounting the lv groups from a Live CD (grml) in AHCI mode and it
works as expected (maybe incomplete set of commands):
# cryptsetup luksOpen /dev/sda3 sda3_crypt
# vgscan
# lvchange -ay /dev/kikutani
# mount /dev/mapper/kikutani-{root,home} /mnt/target/{,home}
If you need further information please do no hesitate to contact me.
regards
Wolodja Wentland
-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.30-2-amd64 root=/dev/mapper/kikutani-root ro quiet
-- /etc/crypttab
sda3_crypt UUID=c81ab368-c7c3-4e78-87cd-fd42200fb60b none luks
-- /etc/fstab
# /etc/fstab: static file system information.
#
# file system mount point type options dump pass
proc/proc procdefaults0 0
UUID=8a22312c-6c5f-47b5-b5f9-85de76359409 / ext3
user_xattr,errors=remount-ro 0 1
UUID=7b5ad619-271e-4588-ad90-cd38904eae4b /boot ext3
defaults0 2
UUID=42556b6e-1013-47aa-8169-cc6becfd1bc9 /home ext3user_xattr
0 2
/dev/mapper/kikutani-swap noneswapsw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
-- lsmod
Module Size Used by
radeon141984 2
drm 172672 3 radeon
ipt_REJECT 3248 6
xt_multiport3216 1
xt_recent 9600 2
xt_tcpudp 3328 40
xt_state2400 42
ipt_LOG 5796 3
sco10980 2
xt_limit3044 8
bridge 48240 0
stp 2868 1 bridge
bnep 13792 2
iptable_mangle 4032 0
iptable_nat 6240 0
nf_nat 20164 1 iptable_nat
nf_conntrack_ipv4 15240 45 iptable_nat,nf_nat
rfcomm 35984 4
nf_conntrack 70192 4 xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4
uinput 8448 1
l2cap 21104 16 bnep,rfcomm
nf_defrag_ipv4 2288 1 nf_conntrack_ipv4
iptable_filter 3776 1
ip_tables 17392 3 iptable_mangle,iptable_nat,iptable_filter
x_tables 22440 9
ipt_REJECT,xt_multiport,xt_recent,xt_tcpudp,xt_state,ipt_LOG,xt_limit,iptable_nat,ip_tables
ppdev 7784 0
lp 10612 0
parport38224 2 ppdev,lp
acpi_cpufreq8912 0
cpufreq_userspace 3652 0
cpufreq_conservative 7928 0
cpufreq_powersave 1792 0
cpufreq_stats 4660 0
kvm_intel 47560 0
kvm 159544 1 kvm_intel
loop 15980 0
snd_hda_codec_analog74864 1
snd_hda_intel 26680 0
snd_hda_codec 75248 2 snd_hda_codec_analog,snd_hda_intel
btusb 12756 2
snd_hwdep 8152 1 snd_hda_codec
arc42048 2
snd_pcm_oss37200 0
bluetooth 55108 9 sco,bnep,rfcomm,l2cap,btusb
snd_mixer_oss 15072 1 snd_pcm_oss
pcmcia 27640 0
ecb 3072 2
snd_pcm78472 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi6976 0
iwl394570340 0
snd_rawmidi23008 1 snd_seq_midi
snd_seq_midi_event 7712 1 snd_seq_midi
iwlcore 106896 1 iwl3945
yenta_socket 24940 1
snd_seq51376 2 snd_seq_midi,snd_seq_midi_event
rsrc_nonstatic 10224 1 yenta_socket
snd_timer 21824 2 snd_pcm,snd_seq
snd_seq_device 7476 3 snd_seq_midi,snd_rawmidi,snd_seq
pcmcia_core37108 3 pcmcia,yenta_socket,rsrc_nonstatic
i2c_i801 10464 0
mac80211 161424 2 iwl3945,iwlcore
snd63912 11
snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
joydev 11072 0
uhci_hcd 22208 0
i2c_core 25456 2 drm,i2c_i801
soundcore 7984 1 snd
nsc_ircc 17104 0
sg 24040 0
ehci_hcd 33996 0
e1000e111680 0
rng_core4872 0
cfg80211 65464 3 iwl3945,iwlcore,mac80211
snd_page_alloc 9984 2 snd_hda_intel,snd_pcm
thinkpad_acpi 65404 0
intel_agp 28976 0
sr_mod 15908 0
irda 114164 1 nsc_ircc
rfkill 12116 4
Bug#554506: cryptsetup: unable to find root volume
Package: cryptsetup Version: 2:1.0.7-2 Severity: important I installed today's testing netinstall image on a new laptop with lvm an crypto root. After the first boot it can't find the root volume: volume group debian not found. skipping volume group debian. unable to find LVM volume debian/root volume group debian not found. cryptsetup: lvm device name (dev/disk/by-uuid/$FOO) does not begin with /dev/mapper After waiting some time it gives me a shell -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
