Your message dated Sun, 1 Sep 2013 19:23:42 +0200 with message-id <201309011924.00219.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #701862, regarding Fails to boot, no cryptsetup in initramfs 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.) -- 701862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701862 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Fails to boot, no cryptsetup in initramfs
- From: John Talbut <jt@dpets.co.uk>
- Date: Thu, 28 Feb 2013 07:09:12 +0000
- Message-id: <512F0298.7020000@dpets.co.uk>
Package: installation-reports Boot method: USB Image version: http://cdimage.debian.org/cdimage/wheezy_di_rc1/amd64/iso-cd/debian-wheezy-DI-rc1-amd64-netinst.iso Date: 27th February 2013 Machine: Samsung NC110P Processor: Atom N2600 Memory: 2GB RAM, 320GB disk Partitions: #1 primary 254.8 MB B f ext4 / #2 primary 319.8 GB K crypto (sda2_crypt) - Provides logical volume: da 290820MB #1 290.8 GB F ext4 /data - Provides logical volume: ho 9999MB #1 10 GB F ext4 /home - Provides logical volume: rt 499MB #1 499.1 MB F ext4 / - Provides logical volume: sw 3997MB #1 4 GB F swap swap - Provides logical volume: tm 499MB #1 499.1 MB F ext4 /tmp - Provides logical volume: us 9999MB #1 10 GB F ext4 /usr - Provides logical volume: va 3997MB> #1 4 GB F ext4 /var Comments/Problems: Everything installed apparently correctly. When I then boot the system Grub starts OK, then the system stops with the "ALERT! /dev/mapper/dk-rt does not exist Dropping to a shell!" message. On my other machine with a similar installation (installed some months ago) it asks me for the cryptsetup password instead just before this point. Once in the shell, cryptsetup is unavailable.
--- End Message ---
--- Begin Message ---
- To: 692338-done@bugs.debian.org, 703176-done@bugs.debian.org, 702959-done@bugs.debian.org, 702774-done@bugs.debian.org, 702098-done@bugs.debian.org, 701862-done@bugs.debian.org, 701676-done@bugs.debian.org, 701493-done@bugs.debian.org, 701493-done@bugs.debian.org, 701149-done@bugs.debian.org, 700974-done@bugs.debian.org, 700688-done@bugs.debian.org, 700637-done@bugs.debian.org, 700598-done@bugs.debian.org, 703648-done@bugs.debian.org, 701545-done@bugs.debian.org, 703626-done@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sun, 1 Sep 2013 19:23:42 +0200
- Message-id: <201309011924.00219.holger@layer-acht.org>
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 were caused by broken hardware and/or - they have been from a development phase where things were not stable and/or - they are quite old (and thus likely fixed today) and/or - moreinfo was asked and not given or - they are wishlist but rather special + exotic and not have been acted on for years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to close wishlist bugs.) 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 ---