Your message dated Sat, 20 Jul 2013 17:22:32 +0200 with message-id <201307201723.03308.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #609558, regarding encrypted system on USB drive is unbootable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 609558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609558 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: encrypted system on USB drive is unbootable
- From: toby cabot <toby@caboteria.org>
- Date: Mon, 10 Jan 2011 11:17:02 -0500
- Message-id: <20110110161702.GA5104@caboteria.org>
Package: installation-reports Boot method: CD Image version: debian-507-i386-CD-1.iso (via bittorrent) Date: 2011-01-10 09:00 Machine: Dell Latitude E6400 Processor: Intel Core2 Duo T9900 @3.06GHz Memory: 4GB Partitions: #1 255.0MB ext2 /boot #2 79.8GB crypto (sdb2_crypt) Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card: [O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system: [O] Clock/timezone setup: [O] User/password setup: [O] Install tasks: [O] Install boot loader: [O] maybe E Overall install: [E] Comments/Problems: Attempted to install an encrypted LVM system on a USB-attached hard drive. Tried to do as "vanilla" an install as possible, accepting the defaults where I could. One non-default is that I wrote GRUB to (hd1,0), the USB drive, instead of the default since I didn't want to disturb the primary drive which has an encrypted Windows installation. Everything appeared to go OK but the system can't boot. It reaches the GRUB menu but when GRUB tries to boot the kernel I don't get prompted for a password and I get: Filesystem type unknown, partition type 0xde Kernel /vmlinuz-2.6.26-686 root=/dev/mapper/mm177490--pc-root ro Error 17. Cannot mount the selected partition.
--- End Message ---
--- Begin Message ---
- To: 619692-done@bugs.debian.org, 618010-done@bugs.debian.org, 614504-done@bugs.debian.org, 613835-done@bugs.debian.org, 613093-done@bugs.debian.org, 612763-done@bugs.debian.org, 611357-done@bugs.debian.org, 609801-done@bugs.debian.org, 609558-done@bugs.debian.org, 609339-done@bugs.debian.org, 605453-done@bugs.debian.org, 591069-done@bugs.debian.org, control@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sat, 20 Jul 2013 17:22:32 +0200
- Message-id: <201307201723.03308.holger@layer-acht.org>
reassign 609339 netcfg tags 609339 + wontfix reassign 604150 partman-partitioning thanks Hi, thank you for submitting installation reports, much appreciated. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they contained user errors and/or - they have been from a development phase where things were not stable and/or - they are quite old. If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---