Bug#597621: installation-reports: installer failed to mount when two or more encrypted partitions were set up
reassign 597621 partman-crypto thanks Quoting Douglas A. Augusto (daaugu...@gmail.com): Christian PERRIER bubu...@debian.org wrote: Before this bug report is reassigned to partman-crypto, could you test the daily builds of D-I? Go to http://www.debian.org/devel/debian-installer and take care to pick one of the daily builds, preferrably the netboot image (*not* netinst!). I'm sorry, but since the system is already installed and in operation (I formatted the filesystems and created the mounting points manually for the other three partitions after booting), at this time I cannot repeat the installation procedure. Although I didn't use the netboot image, I did use a recent netinst image (from 19-Sep-2010, md5sum: c6cfcaee07d8f96c0afbca177a18068d). Yes...but a recent netinst image is using a quite old D-I release (D-I alpha 1)...which is why I now suggest using recent builds from scratch. Is there something in the installation logs that could be useful? For instance, in installer/syslog there is: Maybe. At this point, the only opportunity we have is reassigning this bug to partman-crypto. Please send the entire D-I logs to the bug report (no need to CC me) if you haven't done it already (I can't check right now, being offline). signature.asc Description: Digital signature
Bug#597621: installation-reports: installer failed to mount when two or more encrypted partitions were set up
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: Installation done on 19-Sep-2010 (ISO image from this date) Machine: Custom built computer (M/B ECS A890GXM-AU v1.0) Processor: AMD Phenom II X6 1090T Memory: 8GB (4x2GB) DDR3 1333MHZ OCZ Gold Partitions: # fdisk -l /dev/sdb Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00089278 Device Boot Start End Blocks Id System /dev/sdb1 * 1 49 390144 83 Linux Partition 1 does not end on cylinder boundary. /dev/sdb2 49199415625216 82 Linux swap / Solaris /dev/sdb31994 64242 49744 83 Linux /dev/sdb4 64242 182402 949122048 83 Linux # fdisk -l /dev/sda Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000c21bf Device Boot Start End Blocks Id System /dev/sda1 1 32 247808 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 32197715625216 82 Linux swap / Solaris /dev/sda31977 243202 1937639512 83 Linux # df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/sdb3 ext4 492153872 19767808 462386072 5% / tmpfstmpfs 3840176 0 3840176 0% /lib/init/rw udev tmpfs 3801224 280 3800944 1% /dev tmpfstmpfs 3840176 2932 3837244 1% /dev/shm /dev/sdb1 ext4 377831 40351325776 12% /boot /dev/mapper/sdb4_crypt ext4 934227060 28707236 905519824 4% /home /dev/mapper/sda3_crypt ext4 1907175504 1123091716 784083788 59% /mnt Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS780 Host Bridge Alternate [1022:9601] Subsystem: Elitegroup Computer Systems Device [1019:2257] 00:01.0 PCI bridge [0604]: Elitegroup Computer Systems Device [1019:9602] 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] (rev 40) Subsystem: Elitegroup Computer Systems Device [1019:4391] Kernel driver in use: ahci 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Subsystem: Elitegroup Computer Systems Device [1019:2257] Kernel driver in use: ohci_hcd 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Subsystem: Elitegroup Computer Systems Device [1019:2257] Kernel driver in use: ehci_hcd 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Subsystem: Elitegroup Computer Systems Device [1019:2257] Kernel driver in use: ohci_hcd 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Subsystem: Elitegroup Computer Systems Device [1019:2257] Kernel driver in use: ehci_hcd 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 41) Subsystem: Elitegroup Computer Systems Device [1019:2257] Kernel driver in use: piix4_smbus 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) Subsystem: Elitegroup Computer Systems Device [1019:2257] Kernel driver in use: HDA Intel 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] (rev 40) Subsystem: Elitegroup Computer Systems Device [1019:2257] 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] (rev 40) 00:14.5 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller [1002:4399] Subsystem: Elitegroup Computer Systems Device [1019:2257] Kernel driver in use: ohci_hcd 00:15.0 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a0] Kernel driver in use: pcieport 00:15.1 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a1] Kernel driver in use: pcieport 00:16.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Subsystem: Elitegroup Computer Systems Device [1019:2257] Kernel driver in use: ohci_hcd 00:16.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Subsystem: Elitegroup Computer Systems Device [1019:2257] Kernel driver in use: ehci_hcd 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration
Bug#597621: installation-reports: installer failed to mount when two or more encrypted partitions were set up
tags 597621 moreinfo thanks I did the installation in expert mode. Unfortunately I had two problems concerning the setup of LUKS encrypted partitions and filesystems. The first and critical one was that the installer couldn't setup more than one encrypted partition. Whenever I tried to specify two or more encrypted partitions the installer failed after formatting them, during the mounting phase. It seemed that the installer arbitrarily corrupted the filesystems right after creating/formatting them. I was trying to create four encrypted partitions: /dev/sdb4 (ext4) as /home (see disks layout above), /dev/sdb2 as swap, /dev/sda3 (ext4) as /mnt and /dev/sda2 as second swap. Unfortunately I had to create only one (sdb4) and to leave the remaining three to be done after the system installation. Before this bug report is reassigned to partman-crypto, could you test the daily builds of D-I? Go to http://www.debian.org/devel/debian-installer and take care to pick one of the daily builds, preferrably the netboot image (*not* netinst!). Suggestion: I would like to suggest that in expert mode the user should be able to choose to continue the installation process even if a previous phase has failed. When I experienced the major issue reported above, I was able to switch to a terminal and create/format/mount the encrypted partitions manually. But unfortunately the installation process didn't let me continue to the next stage because the previous stage had failed. All internal logic of D-I is based on such dependencies. So I very much doubt this happens before a major rewrite of many parts. I don't really see the benefit anyway (at least in real installsthere may be some use cases in D-I development itself but other hacks such as putting exit 0 at the top of the failing component postinst, are often enough signature.asc Description: Digital signature
Bug#597621: installation-reports: installer failed to mount when two or more encrypted partitions were set up
Christian PERRIER bubu...@debian.org wrote: Before this bug report is reassigned to partman-crypto, could you test the daily builds of D-I? Go to http://www.debian.org/devel/debian-installer and take care to pick one of the daily builds, preferrably the netboot image (*not* netinst!). I'm sorry, but since the system is already installed and in operation (I formatted the filesystems and created the mounting points manually for the other three partitions after booting), at this time I cannot repeat the installation procedure. Although I didn't use the netboot image, I did use a recent netinst image (from 19-Sep-2010, md5sum: c6cfcaee07d8f96c0afbca177a18068d). Is there something in the installation logs that could be useful? For instance, in installer/syslog there is: [...] Sep 19 07:54:13 kernel: [ 5226.997031] EXT4-fs (sdb3): mounted filesystem with ordered data mode Sep 19 07:54:13 kernel: [ 5227.072577] EXT4-fs (sdb1): mounted filesystem with ordered data mode Sep 19 07:57:54 kernel: [ 5447.520629] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Sep 19 07:58:55 main-menu[493]: (process:12660): mount: mounting /dev/mapper/sdb4_crypt on /target/home failed: Invalid argument Sep 19 07:58:55 main-menu[493]: WARNING **: Configuring 'partman-base' failed with error code 2 Sep 19 07:58:55 main-menu[493]: WARNING **: Menu item 'partman-base' failed. Sep 19 07:59:02 main-menu[493]: DEBUG: resolver (libncurses5): package doesn't exist (ignored) Sep 19 07:59:08 main-menu[493]: INFO: Menu item 'partman-base' selected [...] Sep 19 08:29:45 kernel: [ 7359.057726] EXT4-fs (sdb3): mounted filesystem with ordered data mode Sep 19 08:29:45 kernel: [ 7359.133290] EXT4-fs (sdb1): mounted filesystem with ordered data mode Sep 19 08:33:24 kernel: [ 7578.260988] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Sep 19 08:36:31 kernel: [ 7765.121220] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Sep 19 08:36:31 kernel: [ 7765.121405] EXT2-fs: dm-3: couldn't mount because of unsupported optional features (240). Sep 19 08:36:31 kernel: [ 7765.121500] EXT3-fs: dm-3: couldn't mount because of unsupported optional features (240). Sep 19 08:36:32 kernel: [ 7765.745557] EXT4-fs (dm-3): mounted filesystem with ordered data mode Sep 19 08:38:45 kernel: [ 7899.089003] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Sep 19 08:38:45 kernel: [ 7899.096842] EXT2-fs: dm-1: couldn't mount because of unsupported optional features (240). Sep 19 08:38:45 kernel: [ 7899.100834] EXT3-fs: dm-1: couldn't mount because of unsupported optional features (240). Sep 19 08:38:46 kernel: [ 7899.447135] EXT4-fs (dm-1): mounted filesystem with ordered data mode Sep 19 08:38:52 main-menu[493]: (process:29083): mount: mounting /dev/mapper/sda3_crypt on /target/mnt failed: Invalid argument Sep 19 08:38:52 main-menu[493]: (process:29083): mount: mounting /dev/mapper/sdb4_crypt on /target/home failed: Invalid argument Sep 19 08:38:52 main-menu[493]: WARNING **: Configuring 'partman-base' failed with error code 2 Sep 19 08:38:52 main-menu[493]: WARNING **: Menu item 'partman-base' failed. Sep 19 08:38:53 main-menu[493]: DEBUG: resolver (libncurses5): package doesn't exist (ignored) Sep 19 08:38:56 main-menu[493]: INFO: Menu item 'bootstrap-base' selected [...] Sep 19 09:04:23 partman: mke2fs 1.41.12 (17-May-2010) Sep 19 09:07:45 kernel: [ 9638.338764] EXT4-fs (sdb3): mounted filesystem with ordered data mode Sep 19 09:07:45 kernel: [ 9638.447888] EXT4-fs (sdb1): mounted filesystem with ordered data mode Sep 19 09:07:45 kernel: [ 9638.848969] EXT4-fs (dm-1): mounted filesystem with ordered data mode Sep 19 09:07:45 main-menu[493]: (process:15976): mount: mounting /dev/mapper/sdb4_crypt on /target/home failed: Invalid argument Sep 19 09:07:45 main-menu[493]: (process:15976): mount: mounting /dev/mapper/sda3_crypt on /target/mnt failed: Invalid argument Sep 19 09:07:45 main-menu[493]: (process:15976): mount: mounting /dev/mapper/sdb4_crypt on /target/home failed: Invalid argument Sep 19 09:07:45 main-menu[493]: (process:15976): mount: mounting /dev/mapper/sdb4_crypt on /target/home failed: Invalid argument Sep 19 09:07:45 main-menu[493]: (process:15976): swapon: /dev/mapper/sda2_crypt: Invalid argument Sep 19 09:07:45 main-menu[493]: (process:15976): mount: mounting /dev/mapper/sdb4_crypt on /target/home failed: Invalid argument -- Douglas A. Augusto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org