Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <[🔎] 20211030183054.906cb9aac22395d0f32a6a86@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #292513, regarding debian-installer: After grub software raid installation, machine fails to boot with first drive removed or blanked. 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.) -- 292513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=292513 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: debian-installer: After grub software raid installation, machine fails to boot with first drive removed or blanked.
- From: Tim Small <tim@buttersideup.com>
- Date: Wed, 02 Jul 2008 18:56:51 +0100
- Message-id: <20080702175651.1758.67585.reportbug@zebedee.config>
Package: debian-installer Version: 20070308etch2 Severity: normal I preseeded an Etch installtion with: d-i grub-installer/bootdev string (hd0) (hd1) but it didn't do what I expected with respect to software RAID, and failed drives. The current behaviour seems to be: boot from sda if it is first BIOS drive (0x80) boot from sdb if it is second BIOS drive (0x81) If the first hard drive is completely failed, or missing, it will attempt to boot from the second drive, but fail, because it tries to acces drive 0x81, but the BIOS has now assigned 0x80 to the remaining drive. If I "dd if=/dev/zero of=/dev/sda count=1" (i.e. remove partition table, and beginning of grub code) then the boot still fails, as the BIOS still assigns the second drive 0x80. OTOH, if the first hard drive is present, but unreadable, AND the BIOS attempts to boot from the second hard drive, but still assigns the second drive 0x81, then boot will succeed with the existing code, but not with my post-install commands (however you could still get the machine to boot by disabling or removing the first drive). However, I haven't observed a BIOS which behaves like this. I got better behaviour by executing this as a post-install step: echo '(hd0) /dev/sdb' > /target/boot/grub/device.map in-target /usr/sbin/grub-install hd0 echo '(hd0) /dev/sda' > /target/boot/grub/device.map in-target /usr/sbin/grub-install hd0 Behaviour with the additional post-install steps seems to be: boot from sda if it is first BIOS drive (0x80) boot from sdb if it is first BIOS drive (0x80) It is possible to make sdb the second BIOS drive (0x80) by telling the BIOS to boot from the second drive, and/or physically removing sda. If I "dd if=/dev/zero of=/dev/sda count=1" (i.e. remove partition table, and beginning of grub code) then the boot still succeeds. A better fix, which should work in all situations, would be to change grub so that it attempts to attempt to fall-back to reading from BIOS drive 0x81 if 0x80 doesn't work (is blank / or unwell i.e. reads fail etc.). Without reviewing the grub code in detail, I don't know if this second fix would be possible. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.25-2-amd64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- no debconf information
--- End Message ---
--- Begin Message ---
- To: debian-boot <debian-boot@lists.debian.org>
- Cc: 785149-done@bugs.debian.org, 489005-done@bugs.debian.org, 610116-done@bugs.debian.org, 611713-done@bugs.debian.org, 612420-done@bugs.debian.org, 621923-done@bugs.debian.org, 647267-done@bugs.debian.org, 659116-done@bugs.debian.org, 665856-done@bugs.debian.org, 666552-done@bugs.debian.org, 668923-done@bugs.debian.org, 686955-done@bugs.debian.org, 690515-done@bugs.debian.org, 690592-done@bugs.debian.org, 702731-done@bugs.debian.org, 729411-done@bugs.debian.org, 771467-done@bugs.debian.org, 780115-done@bugs.debian.org, 806164-done@bugs.debian.org, 806849-done@bugs.debian.org, 416986-done@bugs.debian.org, 292513-done@bugs.debian.org, 310798-done@bugs.debian.org, 391489-done@bugs.debian.org, 489006-done@bugs.debian.org, 578338-done@bugs.debian.org, 582367-done@bugs.debian.org, 229128-done@bugs.debian.org, 463842-done@bugs.debian.org, 497168-done@bugs.debian.org, 500079-done@bugs.debian.org, 516392-done@bugs.debian.org, 520361-done@bugs.debian.org, 544949-done@bugs.debian.org, 549703-done@bugs.debian.org, 557242-done@bugs.debian.org, 580461-done@bugs.debian.org, 587699-done@bugs.debian.org, 588670-done@bugs.debian.org, 596877-done@bugs.debian.org, 612025-done@bugs.debian.org, 618498-done@bugs.debian.org, 639713-done@bugs.debian.org, 666559-done@bugs.debian.org, 699456-done@bugs.debian.org, 703901-done@bugs.debian.org, 707604-done@bugs.debian.org, 711330-done@bugs.debian.org, 609939-done@bugs.debian.org, 498831-done@bugs.debian.org
- Subject: Mass-closing old grub-installer bugs
- From: Holger Wansing <hwansing@mailbox.org>
- Date: Sat, 30 Oct 2021 18:30:54 +0200
- Message-id: <[🔎] 20211030183054.906cb9aac22395d0f32a6a86@mailbox.org>
Hi, similar to the installation-reports bugs, I'm closing the grub-installer reports below. These are reports for Debian 4 / 6 / 7 / 9 where grub-installer fails (for various reasons). There have been numerous changes/improvements on this topics in the past, and also because of the age of the reports we should consider these problems as being fixed (or it is even reported in the bugs that they are fixed). They are most likely of no use anymore for recent releases. If you know, that the issue you reported (and gets closed here) is still existing in recent installation images, please file a new report for that with up-to-date details! Thank you for filing these bug reports, they have been very useful at the time they were filed! https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785149 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489005 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610116 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611713 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612420 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621923 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647267 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659116 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665856 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666552 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668923 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686955 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690515 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690592 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702731 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729411 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771467 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780115 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806164 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806849 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416986 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252009 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=292513 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310798 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391489 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489006 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578338 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582367 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=229128 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463842 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497168 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500079 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516392 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520361 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544949 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549703 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557242 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580461 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587699 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588670 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596877 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612025 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618498 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639713 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666559 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699456 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703901 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707604 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711330 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609939 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498831 Cheers Holger -- Holger Wansing <hwansing@mailbox.org> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
--- End Message ---