Your message dated Fri, 30 Aug 2013 12:45:13 +0200 with message-id <201308301245.50219.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #685886, regarding installation-reports: installing on the second hard disk fails: grub error after reboot 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.) -- 685886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685886 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: installation-reports: installing on the second hard disk fails: grub error after reboot
- From: "Eugene V. Lyubimkin" <jackyf@debian.org>
- Date: Sun, 26 Aug 2012 03:00:12 +0300
- Message-id: <20120826000012.17355.12119.reportbug@Host-001.Elisa>
Package: installation-reports Severity: important Dear Maintainer, [ I'm reporting the problem on behalf of my friend. ] Tried 6.0.5 CD1 and the current testing snapshot (August 20). There were two hard drives (/dev/sda and /dev/sdb), Debian was installed to the logical partition of the second drive (something like /dev/sdb6), everything (except swap) was installed to a single partition. Everything was fine on the installation stage, but after the reboot the user was greeted with the Grub command line, i.e. boot failed. Apparently because the Grub was installed to the /dev/sda unconditionally. After we managed to install (manually, using the rescue disk) Grub to the MBR of second hard drive (i.e. 'grub-install /dev/sdb'), boot succeeded. This is unfortunate. I wonder if we did something wrong or installer should have some more code for handling multi-disk installations. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: control@bugs.debian.org, 664142-done@bugs.debian.org, 621919-done@bugs.debian.org, 618432-done@bugs.debian.org, 673910-done@bugs.debian.org, 699293-done@bugs.debian.org, 697692-done@bugs.debian.org, 696877-done@bugs.debian.org, 694570-done@bugs.debian.org, 694388-done@bugs.debian.org, 689512-done@bugs.debian.org, 687811-done@bugs.debian.org, 686665-done@bugs.debian.org, 686032-done@bugs.debian.org, 685886-done@bugs.debian.org, 685414-done@bugs.debian.org, 680631-done@bugs.debian.org, 680631-done@bugs.debian.org, 677476-done@bugs.debian.org, 671751-done@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Fri, 30 Aug 2013 12:45:13 +0200
- Message-id: <201308301245.50219.holger@layer-acht.org>
reassign 604033 debian-installer severity 604033 wishlist forcemerge 604033 699430 retitle 699430 debian-installer: support for Intel Matrix Raid (RST, imsm) reassign 699293 pcmciautils-udeb 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 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. 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 ---