Grub 2
Hi, I try to compile a 64bits kernel on my debian 12 32bits (with a luks2 partition on all the disk) and it not going well. My computer had a boot problem first (when i was booting on the 64bit kernel) : 1) problem on the screen 2) problem for the luks 2 (password recognise) 3) swap not good So touch my fstab, and then my computer refuse to boot at all (grub rescue and all) : 1) Try to actived the normal mod (not such file) 2) Try to reinstall the grub in 32 and 64 bit (change but no recognised password) 3) Try to actived the os prober (same issue, see the 2)) Now im stock the bootrepair, say that to me : "Please enable a repository containing the [linux-generic] packages in the software sources of Debian GNU/Linux 12 (bookworm) (/dev/mapper/Albert--vg-root). Then try again" and that too : "Please enable a repository containing the [grub2] packages in the software sources of Debian GNU/Linux 12 (bookworm) (/dev/mapper/Albert--vg-root). Then try again." Im stuck here for now, how do i actived this repository on boot repair - Linuxmint 21.2 Victoria? Thank you
Bug#1028049: lvm2 is not available in the initramfs, causing the installation media be unmountable on systems using lvm2 when the ISO is booted using grub 2 loopback module
Package: rootskel Version: 1.134 Severity: important grub 2 has a feature of mounting iso images. It allows to boot the installation media without involving CDs and flash drives. The installer relies on mountability of installation media. But when the installation media is on the fs within lvm2 it is problematic to make it to mount it. Currently one has to extract the initramfs, add the needed packages into it, and repack it back, and it has to be done on a working linux machine. It’d be nice if the initramfs had all the needed components inside of it.
Bug#587699: marked as done (installation-reports: can't (install) update grub(2), grub-probe can' find /)
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #587699, regarding installation-reports: can't (install) update grub(2), grub-probe can' find / 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 ow...@bugs.debian.org immediately.) -- 587699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Before installing Squeeze there was Ubuntu 9.10 and Windows 7 on the Laptop. So I can't say if the bootsektor comes from Ubuntu or Squeeze. I want to install Squeeze on a crypt disk. I want to delete Ubuntu. After installation I want to use Windows 7 and Debian Squeeze with the grub bootloader. /boot is on /dev/sda5 /dev/sda6 is the crypt partition lvm is installed in the crypt partition / (root-filesystem) is installed in lvm (lv named root) grub-probe -t device / fails with grub-probe: error: cannot find a device for / (is /dev monted?). Yes /dev is mounted by udev. I don't use chroot. All grub commands that use the grub-probe command fail. So I can't update grub. Installing an other kernel fails too. That is not my first installation with crypt disk and lvm. I tried to install grub-legacy but I can't install, because the installation breaks with the same error. It seems that grub-legacy used the same grub-probe. After installation I miss window 7 in /boot/grub/grub.cfg. -- Package-specific info: Boot method: CD Image version: Squeeze, build 26.06.2010 netinstall i386 Date: Machine: Asus laptop X5DAD AMD64x2 ATI Partitions: root@laptop02:/etc/gdm3# df -Tl Dateisystem Typ1K‐Blöcke Benutzt Verfügbar Ben% Eingehängt auf /dev/mapper/lvm--crypt-root ext3 959512135044775728 15% / tmpfstmpfs 1687372 0 1687372 0% /lib/init/rw udev tmpfs 1682272 244 1682028 1% /dev tmpfstmpfs 168737288 1687284 1% /dev/shm /dev/sda5 ext3 472036 27131420534 7% /boot /dev/mapper/lvm--crypt-home jfs 195270636180660 195089976 1% /home /dev/mapper/lvm--crypt-tmp ext314417392167136 13517892 2% /tmp /dev/mapper/lvm--crypt-usr--squeeze ext3 4805760 4156872404768 92% /usr /dev/mapper/lvm--crypt-var--squeeze ext3 2882592 1794552941608 66% /var Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [E] Install boot loader:[E] Overall install:[O] Comments/Problems: Network: can't configure WLAN with wpa, firmware for module r8169 is missing but eth0 works Partion hard drives: can't delete/rename logical volumen (so I used the prompt) Install tasks: console-data is missing after installation, so I have the wrong keyboard-layout at the textconsole Install boot loader: look at the top The installer wants to use 5 GByte for /usr so I use 5 GByte when I manual partition. /usr is filled by 92%. I thing /usr should be larger. I miss the automatic installation with crypt disk by using free space. The only option is to use the whole disk with crypt partition. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="6.0 (squeeze) - installer build 20100626-15:52" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux laptop02 2.6.32-5-486 #1 Tue Jun 1 04:27:25 UTC 2010 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS780 Host Bridge [1022:9600] lspci -knn: Subsystem: Advanced Micro Devices [AMD] RS780 Host Bridge [1022:9600] lspci -knn
Bug#520361: marked as done (Wrong configuration for GRUB 2 chain-loading Windows)
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #520361, regarding Wrong configuration for GRUB 2 chain-loading Windows 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 ow...@bugs.debian.org immediately.) -- 520361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal -- Package-specific info: Boot method: CD Image version: debian-500-i386-CD-1.iso Date: 2009-03-17 Machine: IBM Thinkpad T61 Partitions: 0x000: EB 4C 90 D0 BC 00 7C FB 50 07 50 1F FC BE 1B 7C 0x010: BF 1B 06 50 57 B9 E5 01 F3 A4 CB BD BE 07 B1 04 0x020: 38 6E 00 7C 09 75 13 83 C5 10 E2 F4 CD 18 8B F5 0x030: 83 C6 10 49 74 19 38 2C 74 F6 A0 B5 07 B4 04 00 0x040: 00 80 00 08 01 00 00 00 00 00 00 00 FF FF FA EB 0x050: 07 F6 C2 80 75 02 B2 80 EA 5D 7C 00 00 31 C0 8E 0x060: D8 8E D0 BC 00 20 FB A1 4C 7C 88 E6 3C FF 74 02 0x070: 88 C2 52 BE 76 7D E8 25 01 BE 05 7C F6 C2 80 74 0x080: 48 B4 41 BB AA 55 CD 13 5A 52 72 3D 81 FB 55 AA 0x090: 75 37 83 E1 01 74 32 31 C0 89 44 04 40 88 44 FF 0x0A0: 89 44 02 C7 04 10 00 66 8B 1E 44 7C 66 89 5C 08 0x0B0: 66 8B 1E 48 7C 66 89 5C 0C C7 44 06 00 70 B4 42 0x0C0: CD 13 72 05 BB 00 70 EB 74 B4 08 CD 13 73 0A F6 0x0D0: C2 80 0F 84 ED 00 E9 85 00 66 0F B6 C6 88 64 FF 0x0E0: 40 66 89 44 04 0F B6 D1 C1 E2 02 88 E8 88 F4 40 0x0F0: 89 44 08 0F B6 C2 C0 E8 02 66 89 04 66 A1 48 7C 0x100: 66 09 C0 75 51 66 A1 44 7C 66 31 D2 66 F7 34 88 0x110: D1 31 D2 66 F7 74 04 3B 44 08 7D 3A FE C1 88 C5 0x120: 30 C0 C1 E8 02 08 C1 88 D0 5A 52 88 C6 BB 00 70 0x130: 8E C3 31 DB B8 01 02 CD 13 72 2B 8C C3 8E 06 42 0x140: 7C 60 1E B9 00 01 8E DB 31 F6 31 FF FC F3 A5 1F 0x150: 61 5A FF 26 40 7C BE 7C 7D E8 42 00 EB 0E BE 81 0x160: 7D E8 3A 00 EB 06 BE 8B 7D E8 32 00 BE 90 7D E8 0x170: 2C 00 CD 18 EB FE 47 52 55 42 20 00 47 65 6F 6D 0x180: 00 48 61 72 64 20 44 69 73 6B 00 52 65 61 64 00 0x190: 20 45 72 72 6F 72 00 BB 01 00 B4 0E CD 10 AC 3C 0x1A0: 00 75 F4 C3 00 00 00 00 00 00 00 00 00 00 00 00 0x1B0: 00 00 00 00 00 00 00 00 4B 7B A5 CC AA AA 80 01 0x1C0: 01 00 07 FE FF CC 3F 00 00 00 4E 83 EE 00 00 00 0x1D0: C1 CD 83 FE FF FF 8D 83 EE 00 FD F3 0E 00 00 FE 0x1E0: FF FF 05 FE FF FF 8A 77 FD 00 B7 96 A7 0A 00 00 0x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA 0x000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 0x1C0: FF FF 82 FE FF FF 3F 00 00 00 F4 90 3B 00 00 FE 0x1D0: FF FF 05 FE FF FF 33 91 3B 00 84 05 6C 0A 00 00 0x1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA 0x000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x070: 00 00 00 00 00 00 00
Grub (2) doesnt find 2nd debian installation
Hello, during the installaton of a kali and buster system onto the same hard discs I ended with only one entry for either kali or buster in the grub boot menu, depending on what was last installed. The problem is, that the grub installer scripts look for the specific file "os-release" which is located under /lib to find/identify other installations. Unfortunately, /lib is now just a link to /usr/lib in the "root (/)" partition. Before it was the directory ON the root partition. Therfore grub is not able to find other linux installations. One way out is to read the fstab file on each root parttion, mount the usr partition and read each os-release file. My partitioning of the HDs to /boot(Common for kali and buster) the /( sda2 for Kali sda3 for buster) /usr ( sda(x) sda(y) /var dito /tmp dito /home dito Regards /Ralf Schneider
Bug#579970: marked as done (installation-reports: GRUB 2 failed with RAID1/LVM it does not support UUID, plus two other remarks.)
Your message dated Sun, 21 Jul 2013 13:23:19 +0200 with message-id 201307211323.57027.hol...@layer-acht.org and subject line dealing with old installation-reports has caused the Debian Bug report #579970, regarding installation-reports: GRUB 2 failed with RAID1/LVM it does not support UUID, plus two other remarks. 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 ow...@bugs.debian.org immediately.) -- 579970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: important -- Package-specific info: Boot method: CD Image version: Netinst - 6.0 (squeeze) - installer build 20100322-00:00 Date: 23 March 2010 Machine: Dell PowerEdge 860 Partitions: df -Tl will do; the raw partition table is preferred FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/VG0-root ext4 238287496977192 225206012 1% / tmpfstmpfs 51340440513364 1% /dev /dev/md0 ext3 93299 33244 55238 38% /boot 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:[E] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Hi, On a new machine, I wanted to test the daily-build of Squeeze installer for amd64. I have three comments on the installation. 1) The machine has 2 SATA hard drives, are mounted in RAID1 soft by Linux. I have a RAID1 partition md0 to /boot, the root is mounted on a logical volume, it uses the same partition RAID1 md1. The installation is successfully completed, except for installing the boot loader grub2 (version 1.98-1). Through the console, I have this: # grub-install --recheck --no-floppy --modules=mdraid raid /dev/md0 /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-setup: error: no mapping exists for `md0'. # grub-install --recheck --no-floppy /dev/sda /usr/sbin/grub-probe: error: no mapping exists for `md0'. Auto-detection of a filesystem module failed. Please specify the module with the option `--modules' explicitly. # grub-install --recheck --no-floppy --modules=mdraid raid /dev/sda /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-probe: error: no mapping exists for `md0'. You attempted a cross-disk install, but the filesystem containing /boot/grub does not support UUIDs. # grub-install --recheck --no-floppy --modules=mdraid raid search_fs_uuid /dev/sda /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-probe: error: no mapping exists for `md0'. You attempted a cross-disk install, but the filesystem containing /boot/grub does not support UUIDs. There is this in the file /boot/grub/device.map: (hd0) /dev/sda (hd1) /dev/sdb The matching of UUID and devices is good: # blkid /dev/sdb1: UUID=248d7222-1d79-dd61-2766-b0f63e142f70 LABEL=eole2:0 TYPE=linux_raid_member /dev/sdb2: UUID=76644d49-c5f7-9ab6-fe74-81c94fa9616e LABEL=eole2:1 TYPE=linux_raid_member /dev/mapper/VG0-swap: UUID=88469241-b7d3-4e85-97b5-d33a56bfd2fd TYPE=swap /dev/sda1: UUID=248d7222-1d79-dd61-2766-b0f63e142f70 LABEL=eole2:0 TYPE=linux_raid_member /dev/sda2: UUID=76644d49-c5f7-9ab6-fe74-81c94fa9616e LABEL=eole2:1 TYPE=linux_raid_member /dev/md0: UUID=157deef1-ea8f-4611-9021-5e2fabcd84cf TYPE=ext3 /dev/md1: UUID=rNyfNa-5mXA-Ne77-Z15k-KpWA-kFzL-nZbp3h TYPE=LVM2_member /dev/mapper/VG0-root: UUID=6e5c349c-d880-4329-a15c-e192aee4954a TYPE=ext4 The file /etc/fstab (created by installer) contains: /dev/mapper/VG0-root/ext4errors=remount-ro01 UUID=157deef1-ea8f-4611-9021-5e2fabcd84cf/bootext302 The command grub-probe is no more reassuring: # grub-probe -d /dev/md0 -tabstraction grub-probe: error: no mapping exists for `md0'. I read the bug report #554790 on Grub2 and UUID, but it is February. Does Grub2 (version 1.98-1) manages UUIDs? I was not able to set Grub2 with the /dev/disk/by-id. It seems that this bug
want some advice on grub 2 chaining issues
Want to figure out whether to file a bug on this or not, and maybe how many.
Three drives, four installs of Linux at this time.
80G drive hung off the motherboard's controller, 16OG and 320G hung
off the expansion card's controller in the master positions of the
primary and secondary channels:
00:0f.0 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
ata-Maxtor_4R080L0_R2T745PE
00:07.0 Mass storage controller: Integrated Technology Express, Inc.
IT/ITE8212 Dual channel ATA RAID controller (rev 13)
ata-Maxtor_6B160P0_B41H5J7H
ata-WDC_WD3200AAJB-00J3A0_WD-WCAV2Z842365
Debian is in the 1st partition of the 80G drive on the motherboard's
controller, single partition.
Fedora 14 is in the 1st and 3rd partition of the 160G drive on the
primary channel of the expansion card. Also, a liveCD install of F14
on the 4th partition of the 320G drive.
Fedora 15 is on the 1st and 2nd partitions of the 320G drive.
With only one drive connected (at the same points as above), I can
boot each of the OSses.
With all three connected as above, I can only boot Debian and the F14
on the 160G drive. But I can't chain boot anything.
Trying to boot the 320G drive or chain boot the 160G or 320G drive,
there is no response after the selector screen.
Trying to chain boot the 80G drive to itself gives the message,
invalid signature.
/etc/grub.d/40_custom:
---
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
# chainload the first three disks blindly
menuentry chain first drive (self) {
# set root=(hd0,1)
insmod part_msdos
insmod ext2
set root=(hd2,msdos1)
search --no-floppy --fs-uuid --set=root 32e25b11-5b7b-4686-b6bd-e36159a3162b
chainloader +1
}
menuentry chain second {
# set root=(hd1,1)
insmod part_msdos
insmod ext2
set root=(hd0,msdos1)
search --no-floppy --fs-uuid --set root=6f56e069-9379-4552-91d9-e30920bbd173
chainloader +1
}
menuentry chain third {
# set root=(hd3,1)
insmod part_msdos
insmod ext2
set root=(hd1,msdos1)
search --no-floppy --fs-uuid --set=root bfb92d48-0cd1-4eb0-8e33-ea54e93936dd
chainloader +1
}
menuentry chain third part 4 {
# set root=(hd3,4)
insmod part_msdos
insmod ext2
set root=(hd1,msdos4)
search --no-floppy --fs-uuid --set=root da739f32-f4b4-4632-bc74-4e908ea02d2c
chainloader +1
}
-- /boot/grub/device.map--
(hd0) /dev/disk/by-id/ata-Maxtor_6B160P0_B41H5J7H
(hd1) /dev/disk/by-id/ata-WDC_WD3200AAJB-00J3A0_WD-WCAV2Z842365
(hd2) /dev/disk/by-id/ata-Maxtor_4R080L0_R2T745PE
--/boot/grub/grub.cfg after update-grub:
-
rover@deb:~$ cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 32e25b11-5b7b-4686-b6bd-e36159a3162b
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 32e25b11-5b7b-4686-b6bd-e36159a3162b
set locale_dir=($root)/boot/grub/locale
set lang=ja
insmod gettext
set timeout=5
play 480 440 1
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 32e25b11-5b7b-4686-b6bd-e36159a3162b
insmod png
if background_image /usr/share/images/desktop-base/spacefun-grub.png; then
set color_normal=light-gray/black
set color_highlight=white/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/08_os-prober ###
menuentry Fedora (2.6.35.13-91.fc14.i686.PAE) (on /dev/sdb1) {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 6f56e069-9379-4552-91d9-e30920bbd173
linux /boot/vmlinuz-2.6.35.13-91.fc14.i686.PAE ro
root=UUID=6f56e069-9379-4552-91d9-e30920bbd173 rd_LVM_LV=f15/f15_swap
rd_LVM_LV=vg_f11/f11swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=ja_JP.UTF-8
KEYTABLE=jp106 rhgb quiet
initrd
Bug#613899: marked as done (Prober does not add Grub 2 boot entries for OS's on SW RAID1 filesystems)
Your message dated Fri, 18 Feb 2011 09:44:30 -0500 with message-id 20110218094430.34ebb...@mail.gmail.com and subject line Re: Bug#613899: Prober does not add Grub 2 boot entries for OS's on SW RAID1 filesystems has caused the Debian Bug report #613899, regarding Prober does not add Grub 2 boot entries for OS's on SW RAID1 filesystems 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 ow...@bugs.debian.org immediately.) -- 613899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: Physical CD and Virtual CD (see below) Image version: http://mirrors.secution.com/linuxmint.com/stable/9/linuxmint-9-lxde-cd-i386.iso Date: c. 2/10/2011 to 2/17/2011 Machine: MSI 870-G45 Processor: AM3 Athon II dual core Memory: 4 GB Partitions: See below. Output of lspci -knn (or lspci -nn): 00:00.0 0600: 1002:5957 00:02.0 0604: 1002:5978 00:0a.0 0604: 1002:597f 00:11.0 0106: 1002:4390 00:12.0 0c03: 1002:4397 00:12.1 0c03: 1002:4398 00:12.2 0c03: 1002:4396 00:13.0 0c03: 1002:4397 00:13.1 0c03: 1002:4398 00:13.2 0c03: 1002:4396 00:14.0 0c05: 1002:4385 (rev 3c) 00:14.1 0101: 1002:439c 00:14.2 0403: 1002:4383 00:14.3 0601: 1002:439d 00:14.4 0604: 1002:4384 00:14.5 0c03: 1002:4399 00:18.0 0600: 1022:1200 00:18.1 0600: 1022:1201 00:18.2 0600: 1022:1202 00:18.3 0600: 1022:1203 00:18.4 0600: 1022:1204 01:00.0 0300: 10de:10c3 (rev a2) 01:00.1 0403: 10de:0be3 (rev a1) 02:00.0 0200: 1969:1063 (rev c0) 03:05.0 0180: 105a:4d69 (rev 02) 03:06.0 0200: 168c:0013 (rev 01) 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: [E] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] OVERVIEW When installing LinuxMint 9, which uses Grub 2 1.98, it failed to generate a grub boot entry for the CentOS 5.5 installation already present on the disk. I attempted this twice in real hardware, and as I explain below, further attempts in virtual machines under VirtualBox. It is reasonable to expect existing OS's on RAID'd partitions to be detected and included in the grub boot menu. This problem persists even after installation is complete. Further runs of grub-install and update-grub do not generate the missing OS. Ultimately, I manually added entries for CentOS in 11centos, a script I added. Now CentOS appears on the grub menu. This will not be up to date after future kernel upgrades to CentOS of course. DETAILS I had the following real-world hardware configuration: 2 320 GB Hard Disks, with identical partition layouts and no hard errors as per smartmontools: Partition 1: swap Partition 2: linuxmint 9 Partition 3: CentOS 5.5 i386 (32bit) Partition 4: LVM, mainly intended for CentOS, but for various purposes (irrelevant, but included for completeness) Partitions 3 4 are RAID 1, but 1 2 are non-RAID. Also, all 4 partitions are primary type, not extended/logical. I had CentOS 5.5 installed, up and running without any issues. The problem was that when I installed LM9, it did not add the CentOS partition to the grub 2 menu. I went through many fits trying to get CentOS to boot again. I was able to use rescuebootcd to restore the CentOS boot. PROOF I've duplicated 2 scenarios under a VirtualBox dualboot VM (very sweet, saved me a lot of headaches trying to get back to my CentOS partition in real hardware), replicating the partitioning more or less in proportion to the real-world hardware, laying out the virtual disk partitions in the same order as above. The first scenario, I didn't bother with RAID. I installed CentOS 5.5 + VBox guest additions, no problems. CentOS boots. Then I installed VM9 and guest additions, no problems either. CentOS shows up in the grub 2 boot menu that LinuxMint 9 installed. All boot entries in the menu worked. In the second scenario, I tried the same thing, but this time simulating RAID 1 for CentOS to model what I have in the real hardware world. RAID 1 under VM is rather slow, even on my brand-new AM3 system. With patience, the CentOS 5.5 install completed and I installed the guest additions for VBox with no issues. CentOS booted. Then I installed VM9 with guest additions, no problems. But this time, CentOS did not show up in the grub 2 boot menu
Bug#613899: Prober does not add Grub 2 boot entries for OS's on SW RAID1 filesystems
Package: installation-reports
Boot method: Physical CD and Virtual CD (see below)
Image version:
http://mirrors.secution.com/linuxmint.com/stable/9/linuxmint-9-lxde-cd-i386.iso
Date: c. 2/10/2011 to 2/17/2011
Machine: MSI 870-G45
Processor: AM3 Athon II dual core
Memory: 4 GB
Partitions: See below.
Output of lspci -knn (or lspci -nn):
00:00.0 0600: 1002:5957
00:02.0 0604: 1002:5978
00:0a.0 0604: 1002:597f
00:11.0 0106: 1002:4390
00:12.0 0c03: 1002:4397
00:12.1 0c03: 1002:4398
00:12.2 0c03: 1002:4396
00:13.0 0c03: 1002:4397
00:13.1 0c03: 1002:4398
00:13.2 0c03: 1002:4396
00:14.0 0c05: 1002:4385 (rev 3c)
00:14.1 0101: 1002:439c
00:14.2 0403: 1002:4383
00:14.3 0601: 1002:439d
00:14.4 0604: 1002:4384
00:14.5 0c03: 1002:4399
00:18.0 0600: 1022:1200
00:18.1 0600: 1022:1201
00:18.2 0600: 1022:1202
00:18.3 0600: 1022:1203
00:18.4 0600: 1022:1204
01:00.0 0300: 10de:10c3 (rev a2)
01:00.1 0403: 10de:0be3 (rev a1)
02:00.0 0200: 1969:1063 (rev c0)
03:05.0 0180: 105a:4d69 (rev 02)
03:06.0 0200: 168c:0013 (rev 01)
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: [E]
Detect hard drives: [O]
Partition hard drives: [E]
Install base system:[O]
Clock/timezone setup: [O]
User/password setup:[O]
Install tasks: [O]
Install boot loader:[E]
Overall install:[E]
OVERVIEW
When installing LinuxMint 9, which uses Grub 2 1.98, it failed to
generate a grub boot entry for the CentOS 5.5 installation already
present on the disk. I attempted this twice in real hardware, and as I
explain below, further attempts in virtual machines under VirtualBox.
It is reasonable to expect existing OS's on RAID'd partitions to be
detected and included in the grub boot menu. This problem persists even
after installation is complete. Further runs of grub-install and
update-grub do not generate the missing OS.
Ultimately, I manually added entries for CentOS in 11centos, a script I
added. Now CentOS appears on the grub menu. This will not be up to date
after future kernel upgrades to CentOS of course.
DETAILS
I had the following real-world hardware configuration:
2 320 GB Hard Disks, with identical partition layouts and no hard errors
as per smartmontools:
Partition 1: swap
Partition 2: linuxmint 9
Partition 3: CentOS 5.5 i386 (32bit)
Partition 4: LVM, mainly intended for CentOS, but for various purposes
(irrelevant, but included for completeness)
Partitions 3 4 are RAID 1, but 1 2 are non-RAID. Also, all 4
partitions are primary type, not extended/logical.
I had CentOS 5.5 installed, up and running without any issues. The
problem was that when I installed LM9, it did not add the CentOS
partition to the grub 2 menu. I went through many fits trying to get
CentOS to boot again. I was able to use rescuebootcd to restore the
CentOS boot.
PROOF
I've duplicated 2 scenarios under a VirtualBox dualboot VM (very sweet,
saved me a lot of headaches trying to get back to my CentOS partition in
real hardware), replicating the partitioning more or less in proportion
to the real-world hardware, laying out the virtual disk partitions in
the same order as above.
The first scenario, I didn't bother with RAID. I installed CentOS 5.5 +
VBox guest additions, no problems. CentOS boots. Then I installed VM9
and guest additions, no problems either. CentOS shows up in the grub 2
boot menu that LinuxMint 9 installed. All boot entries in the menu worked.
In the second scenario, I tried the same thing, but this time simulating
RAID 1 for CentOS to model what I have in the real hardware world. RAID
1 under VM is rather slow, even on my brand-new AM3 system. With
patience, the CentOS 5.5 install completed and I installed the guest
additions for VBox with no issues. CentOS booted. Then I installed VM9
with guest additions, no problems. But this time, CentOS did not show up
in the grub 2 boot menu.
CONCLUSION
It seems grub 2 WILL not detect other OS's on RAID 1 drives.
SOLUTION/WORKAROUND
Manually created /etc/grub.d/11centos:
8-
#! /bin/sh -e
echo Adding CentOS RAID partition entries 2
cat EOF
menuentry CentOS (2.6.18-194.32.1.el5.centos.plusPAE) {
insmod mdraid
insmod ext2
set root=(md0)
linux /boot/vmlinuz-2.6.18-194.32.1.el5 root=/dev/md0 ro rhgb quiet
crashkernel=128M@16M
initrd /boot/initrd-2.6.18-194.32.1.el5.img
}
menuentry CentOS (2.6.18-194.el5) {
insmod mdraid
insmod ext2
set root=(md0)
linux /boot/vmlinuz-2.6.18-194.el5 ro root=/dev/md0 rhgb quiet
initrd /boot/initrd-2.6.18-194.el5.img
}
EOF
8-
I could not seem to locate instructions on the details of working with
the modules, which
Bug#600671: marked as done (installation-reports: (daily-image 20101017) GRUB-2 failed to install on Intel X-25M 80GB)
Your message dated Sat, 27 Nov 2010 11:50:31 + with message-id 201011271150.32027.el...@debianpt.org and subject line Re: Bug#600671: installation-reports: (daily-image 20101017) GRUB-2 failed to install on Intel X-25M 80GB has caused the Debian Bug report #600671, regarding installation-reports: (daily-image 20101017) GRUB-2 failed to install on Intel X-25M 80GB 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 ow...@bugs.debian.org immediately.) -- 600671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: important Hi there! I recently bought an SSD (Intel X-25M 80GB SSDSA2MH080G2C1) and after having read around the web about the different tipstricks for SSD, I was ready to install Debian GNU/Linux on it. Unfortunately, the result was quite far from my expectations (read below). Please note that this is a new report for the same machine at: http://bugs.debian.org/406026 Thx, bye, Gismo / Luca -- Package-specific info: Boot method: multi-arch hd-media Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/multi-arch/iso-cd/ http://d-i.debian.org/daily-images/amd64/daily/hd-media/ Date: from 20101016 to 20101018 Machine: IBM/Lenovo ThinkPad X60 (model 1706-GMG with 2x1GB RAM) Partitions: [upon request] Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] - point 1 Configure network: [O] Detect CD: [ ] Load installer modules: [E] - point 1 Detect hard drives: [O] Partition hard drives: [E] - point 2 Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] - point 3 Overall install:[E] - point 3 Comments/Problems: 1) the amd64-i386-powerpc-netinst multi-arch image built on 20101016-08:59 (d-i 20101016-03:54) is useless, given that on both amd64 (my laptop) and i386 (a Compaq Deskpro EN SFF PIII-650) after the country/language selection there is an error: [!!] Load installer components from CD No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. If you're installing from a mirror, you can work around this problem by choosing to install a different version of Debian. The install will probably fail to work if you continue without kernel modules. Continue the install without loading kernel modules? On i386, continuing causes the installer to fail when looking for drivers for the network card. I thus tested two older multi-arch images I had around: a) the image built on 20100912-03:39 (d-i 20100911-21:57) similarly fails b) the image built on 20100717-15:25 (d-i 20100717-09:54) works OK Today I did two more tests: c) i386 netinst image built on 20101018-09:15 (d-i 20101018-03:54) works OK d) multi-arch image built on 20101018-09:25 (d-i 20101018-03:54) fails again with the No kernel modules were found message on QEMU (both amd64 and i386) In the end, for my laptop (amd64) I downloaded the hd-media image built on 20101017-00:17 and used that for the next steps, together with the amd64-businesscard image built on 20101017-08:45 (d-i 20101017-00:08) and the firmware tarball extracted on the hd-media. 2) first, two things which IMHO are sub-optimized: a) my HD was a fresh new one (never used, not even partitioned before) and thus it does not require any erasing when creating the LUKS volume. I know that I can *manually* switch the erasing off (and everything is explained in the installation guide, thank you!), the major problem is that there is no indication that erasing a disk can last quite a lot of time... b) given that the installation did not completely finish, I have not checked the final result, but it would be a good thing for partman to recognize an SSD and add some default options (e.g. noatime). *NB*, this is only an idea, not a complaint, so please do not start flaming on that... Then, the real problem: I decided to follow the default Debian guided partitioning scheme for LUKS+LVM with a separate /home. However, once I discovered that the filesystem used was ext3 (and not ext4, which AFAIK gives better performances with SSDs), I simply went
Bug#600671: installation-reports: (daily-image 20101017) GRUB-2 failed to install on Intel X-25M 80GB
Hi there! On Tue, 19 Oct 2010 02:41:49 +0200, Luca Capello wrote: Boot method: multi-arch hd-media Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/multi-arch/iso-cd/ http://d-i.debian.org/daily-images/amd64/daily/hd-media/ Date: from 20101016 to 20101018 New test with and hd-media of d-i_squeeze_beta1 :-) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Everything was [O], hurrah! 3) the installation went smoothly (base installation plus tasksel's laptop and standard tasks) until the boot loader installation, i.e. GRUB-2. Here the corresponding output from d-i's syslog: --8---cut here---start-8--- Oct 17 16:36:30 main-menu[387]: INFO: Menu item 'grub-installer' selected Oct 17 16:36:30 grub-installer: info: architecture: amd64/generic Oct 17 16:36:30 grub-installer: info: Identified partition label for /dev/mapper/gismo-root: loop OK, this was the problem. Given that gismo-root is on LVM, I have a separate /boot partition, which was not correctly recognized. Oct 17 16:36:41 grub-installer: info: Installing grub on '/dev/sda' Oct 17 16:36:41 grub-installer: info: grub-install supports --no-floppy Oct 17 16:36:41 grub-installer: info: Running chroot /target grub-install --no-floppy --force /dev/sda Oct 17 16:36:41 grub-installer: /usr/sbin/grub-probe: error: no such disk. Oct 17 16:36:41 grub-installer: Auto-detection of a filesystem module failed. Oct 17 16:36:41 grub-installer: Please specify the module with the option `--modules' explicitly. Oct 17 16:36:41 grub-installer: error: Running 'grub-install --no-floppy --force /dev/sda' failed. This was the same output I got this evening while booting in rescue-mode and starting `grub-install --no-floppy --force /dev/sda`. Then I realized that rescue-mode does not automatically mount all the partitions in /etc/fstab, thus my separate /boot partition (/dev/sda1) was not mounted. Doing that and re-running `grub-install [...]` was now fine. Then, I tried a new full installation with d-i_squeeze_beta1, after having wiped the SSD's MBR and indeed the new grub-installer output is different (and correct): --8---cut here---start-8--- Nov 16 20:52:42 main-menu[374]: INFO: Menu item 'grub-installer' selected Nov 16 20:52:42 grub-installer: info: architecture: amd64/generic Nov 16 20:52:42 grub-installer: info: Identified partition label for /dev/sda1: msdos --8---cut here---end---8--- All logs, at least the one you can save from within d-i, are also available, upon request. Still true, included below a full copy of the reportbug's output. I consider this bug fixed, feel free to close it. And thank you for your work on d-i! Thx, bye, Gismo / Luca == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20101020 X_INSTALLATION_MEDIUM=hd-media == Installer hardware-summary: == uname -a: Linux gismo 2.6.32-5-amd64 #1 SMP Fri Oct 15 00:56:30 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:2017] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:201a] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:201a] lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 02) lspci -knn: Subsystem: Lenovo Device [17aa:2010] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 02) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 02) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 3 [8086:27d4] (rev 02) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 4 [8086:27d6] (rev 02) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB
Bug#600671: installation-reports: (daily-image 20101017) GRUB-2 failed to install on Intel X-25M 80GB
* Luca Capello l...@pca.it, 2010-10-19, 02:41: 1) the amd64-i386-powerpc-netinst multi-arch image built on 20101016-08:59 (d-i 20101016-03:54) is useless, given that on both amd64 (my laptop) and i386 (a Compaq Deskpro EN SFF PIII-650) after the country/language selection there is an error: [!!] Load installer components from CD No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. If you're installing from a mirror, you can work around this problem by choosing to install a different version of Debian. The install will probably fail to work if you continue without kernel modules. Continue the install without loading kernel modules? Same here with debian-testing-amd64-i386-powerpc-netinst 20101025-15:34, both on amd64 and i386. -- Jakub Wilk signature.asc Description: Digital signature
Bug#600671: installation-reports: (daily-image 20101017) GRUB-2 failed to install on Intel X-25M 80GB
Hi there! On Tue, 19 Oct 2010 02:41:49 +0200, Luca Capello wrote: 1) the amd64-i386-powerpc-netinst multi-arch image built on 20101016-08:59 (d-i 20101016-03:54) is useless, given that on both amd64 (my laptop) and i386 (a Compaq Deskpro EN SFF PIII-650) after the country/language selection there is an error: [!!] Load installer components from CD No kernel modules were found. [...] On i386, continuing causes the installer to fail when looking for drivers for the network card. I thus tested two older multi-arch images I had around: a) the image built on 20100912-03:39 (d-i 20100911-21:57) similarly fails b) the image built on 20100717-15:25 (d-i 20100717-09:54) works OK FYI, there is no problem on powerpc with the same images. Thx, bye, Gismo / Luca pgphd2fIdzHda.pgp Description: PGP signature
Bug#600671: installation-reports: (daily-image 20101017) GRUB-2 failed to install on Intel X-25M 80GB
Package: installation-reports Severity: important Hi there! I recently bought an SSD (Intel X-25M 80GB SSDSA2MH080G2C1) and after having read around the web about the different tipstricks for SSD, I was ready to install Debian GNU/Linux on it. Unfortunately, the result was quite far from my expectations (read below). Please note that this is a new report for the same machine at: http://bugs.debian.org/406026 Thx, bye, Gismo / Luca -- Package-specific info: Boot method: multi-arch hd-media Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/multi-arch/iso-cd/ http://d-i.debian.org/daily-images/amd64/daily/hd-media/ Date: from 20101016 to 20101018 Machine: IBM/Lenovo ThinkPad X60 (model 1706-GMG with 2x1GB RAM) Partitions: [upon request] Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] - point 1 Configure network: [O] Detect CD: [ ] Load installer modules: [E] - point 1 Detect hard drives: [O] Partition hard drives: [E] - point 2 Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] - point 3 Overall install:[E] - point 3 Comments/Problems: 1) the amd64-i386-powerpc-netinst multi-arch image built on 20101016-08:59 (d-i 20101016-03:54) is useless, given that on both amd64 (my laptop) and i386 (a Compaq Deskpro EN SFF PIII-650) after the country/language selection there is an error: [!!] Load installer components from CD No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. If you're installing from a mirror, you can work around this problem by choosing to install a different version of Debian. The install will probably fail to work if you continue without kernel modules. Continue the install without loading kernel modules? On i386, continuing causes the installer to fail when looking for drivers for the network card. I thus tested two older multi-arch images I had around: a) the image built on 20100912-03:39 (d-i 20100911-21:57) similarly fails b) the image built on 20100717-15:25 (d-i 20100717-09:54) works OK Today I did two more tests: c) i386 netinst image built on 20101018-09:15 (d-i 20101018-03:54) works OK d) multi-arch image built on 20101018-09:25 (d-i 20101018-03:54) fails again with the No kernel modules were found message on QEMU (both amd64 and i386) In the end, for my laptop (amd64) I downloaded the hd-media image built on 20101017-00:17 and used that for the next steps, together with the amd64-businesscard image built on 20101017-08:45 (d-i 20101017-00:08) and the firmware tarball extracted on the hd-media. 2) first, two things which IMHO are sub-optimized: a) my HD was a fresh new one (never used, not even partitioned before) and thus it does not require any erasing when creating the LUKS volume. I know that I can *manually* switch the erasing off (and everything is explained in the installation guide, thank you!), the major problem is that there is no indication that erasing a disk can last quite a lot of time... b) given that the installation did not completely finish, I have not checked the final result, but it would be a good thing for partman to recognize an SSD and add some default options (e.g. noatime). *NB*, this is only an idea, not a complaint, so please do not start flaming on that... Then, the real problem: I decided to follow the default Debian guided partitioning scheme for LUKS+LVM with a separate /home. However, once I discovered that the filesystem used was ext3 (and not ext4, which AFAIK gives better performances with SSDs), I simply went back to the partitioning step. At the same time, I decided that having a separate /home was useless, so I removed every automatically-created partition. Finally, following Iustin Pop's advice and also because AFAIK dm-crypt can not use TRIM, I decided to leave 5GB of space free for the SSD, i.e. not used and not partitioned at all. And here the surprise: without rebooting, there is no way to delete LUKS+LVM once you have passed the partition step. Instead, I was always answered that the partition (real or encrypted) was in use by the LVM subsystem. As I said, rebooting was the solution and I could then continue on. 3) the installation went smoothly (base installation plus tasksel's laptop and standard tasks) until the boot loader installation, i.e. GRUB-2. Here the corresponding output from d-i's syslog: --8---cut here---start-8--- Oct 17 16:36:30 main-menu[387
Bug#587388: d-i: fails to install grub-2
Subject: d-i: fails to install grub-2 Package: d-i Version: debian-504-i386-businesscard.iso Severity: grave Justification: renders package unusable Installer used on 27/06/2010 to install squeeze, which failed to install grub-2, then failed to revert to grub-legacy, so I used dd to copy /dev/zero to the disc and started again, attempting to install grub-legacy. The installer informed me that it was doing an automatic update to grub-2, which failed. The syslog showed Jun 28 05:49:48 grub-installer: Unrecognized option `-y' Jun 28 05:49:48 grub-installer: error: Running 'update-grub -y' failed. Full logs available if required. -- Chris Bell www.chrisbell.org.uk (was www.overview.demon.co.uk) Microsoft sells you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/marcel-1.53-0628081258-927h...@riscpc.main
Processed: Re: Bug#587388: d-i: fails to install grub-2
Processing commands for cont...@bugs.debian.org: reassign 587388 grub-installer Bug #587388 [d-i] d-i: fails to install grub-2 Warning: Unknown package 'd-i' Bug reassigned from package 'd-i' to 'grub-installer'. Bug No longer marked as found in versions debian-504-i386-businesscard.iso. -- Stopping processing here. Please contact me if you need assistance. -- 587388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127771309231252.transcr...@bugs.debian.org
Bug#587388: d-i: fails to install grub-2
On Mon, Jun 28, 2010 at 08:12:58AM +, Chris Bell wrote: Installer used on 27/06/2010 to install squeeze, which failed to install grub-2, then failed to revert to grub-legacy, so I used dd to copy /dev/zero to the disc and started again, attempting to install grub-legacy. The installer informed me that it was doing an automatic update to grub-2, which failed. The syslog showed Jun 28 05:49:48 grub-installer: Unrecognized option `-y' Jun 28 05:49:48 grub-installer: error: Running 'update-grub -y' failed. I fixed this bug over a year ago in the squeeze installer; see the changelog for grub-installer 1.38, uploaded on 12 June 2009. Are you attempting to use a lenny installer to install squeeze? This won't work well. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100628085951.gb12...@riva.ucam.org
Bug#587388: d-i: fails to install grub-2
On Mon 28 Jun, Colin Watson wrote: On Mon, Jun 28, 2010 at 08:12:58AM +, Chris Bell wrote: Installer used on 27/06/2010 to install squeeze, which failed to install grub-2, then failed to revert to grub-legacy, so I used dd to copy /dev/zero to the disc and started again, attempting to install grub-legacy. The installer informed me that it was doing an automatic update to grub-2, which failed. The syslog showed Jun 28 05:49:48 grub-installer: Unrecognized option `-y' Jun 28 05:49:48 grub-installer: error: Running 'update-grub -y' failed. I fixed this bug over a year ago in the squeeze installer; see the changelog for grub-installer 1.38, uploaded on 12 June 2009. Are you attempting to use a lenny installer to install squeeze? This won't work well. As stated, I was using the 5.04 businesscard ISO which I thought downloaded the correct installer components. I will try the weekly image unless you recommend the daily image. Please close the bug report. -- Chris Bell www.chrisbell.org.uk (was www.overview.demon.co.uk) Microsoft sells you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/marcel-1.53-0628092541-480h...@riscpc.main
Bug#587388: marked as done (d-i: fails to install grub-2)
Your message dated Mon, 28 Jun 2010 12:44:18 +0100 with message-id 20100628114418.gc12...@riva.ucam.org and subject line Re: Bug#587388: d-i: fails to install grub-2 has caused the Debian Bug report #587388, regarding d-i: fails to install grub-2 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 ow...@bugs.debian.org immediately.) -- 587388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: d-i: fails to install grub-2 Package: d-i Version: debian-504-i386-businesscard.iso Severity: grave Justification: renders package unusable Installer used on 27/06/2010 to install squeeze, which failed to install grub-2, then failed to revert to grub-legacy, so I used dd to copy /dev/zero to the disc and started again, attempting to install grub-legacy. The installer informed me that it was doing an automatic update to grub-2, which failed. The syslog showed Jun 28 05:49:48 grub-installer: Unrecognized option `-y' Jun 28 05:49:48 grub-installer: error: Running 'update-grub -y' failed. Full logs available if required. -- Chris Bell www.chrisbell.org.uk (was www.overview.demon.co.uk) Microsoft sells you Windows ... Linux gives you the whole house. ---End Message--- ---BeginMessage--- On Mon, Jun 28, 2010 at 09:25:41AM +, Chris Bell wrote: On Mon 28 Jun, Colin Watson wrote: On Mon, Jun 28, 2010 at 08:12:58AM +, Chris Bell wrote: Installer used on 27/06/2010 to install squeeze, which failed to install grub-2, then failed to revert to grub-legacy, so I used dd to copy /dev/zero to the disc and started again, attempting to install grub-legacy. The installer informed me that it was doing an automatic update to grub-2, which failed. The syslog showed Jun 28 05:49:48 grub-installer: Unrecognized option `-y' Jun 28 05:49:48 grub-installer: error: Running 'update-grub -y' failed. I fixed this bug over a year ago in the squeeze installer; see the changelog for grub-installer 1.38, uploaded on 12 June 2009. Are you attempting to use a lenny installer to install squeeze? This won't work well. As stated, I was using the 5.04 businesscard ISO which I thought downloaded the correct installer components. Ah, no, in general you need to use an installer from at least as new a release as what you're trying to install. I will try the weekly image unless you recommend the daily image. I don't know which is better right now, I'm afraid. Please close the bug report. Done. Thanks, -- Colin Watson [cjwat...@debian.org] ---End Message---
Bug#579970: installation-reports: GRUB 2 failed with RAID1/LVM it does not support UUID, plus two other remarks.
Package: installation-reports Severity: important -- Package-specific info: Boot method: CD Image version: Netinst - 6.0 (squeeze) - installer build 20100322-00:00 Date: 23 March 2010 Machine: Dell PowerEdge 860 Partitions: df -Tl will do; the raw partition table is preferred FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/VG0-root ext4 238287496977192 225206012 1% / tmpfstmpfs 51340440513364 1% /dev /dev/md0 ext3 93299 33244 55238 38% /boot 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:[E] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Hi, On a new machine, I wanted to test the daily-build of Squeeze installer for amd64. I have three comments on the installation. 1) The machine has 2 SATA hard drives, are mounted in RAID1 soft by Linux. I have a RAID1 partition md0 to /boot, the root is mounted on a logical volume, it uses the same partition RAID1 md1. The installation is successfully completed, except for installing the boot loader grub2 (version 1.98-1). Through the console, I have this: # grub-install --recheck --no-floppy --modules=mdraid raid /dev/md0 /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-setup: error: no mapping exists for `md0'. # grub-install --recheck --no-floppy /dev/sda /usr/sbin/grub-probe: error: no mapping exists for `md0'. Auto-detection of a filesystem module failed. Please specify the module with the option `--modules' explicitly. # grub-install --recheck --no-floppy --modules=mdraid raid /dev/sda /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-probe: error: no mapping exists for `md0'. You attempted a cross-disk install, but the filesystem containing /boot/grub does not support UUIDs. # grub-install --recheck --no-floppy --modules=mdraid raid search_fs_uuid /dev/sda /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-probe: error: no mapping exists for `md0'. /usr/sbin/grub-probe: error: no mapping exists for `md0'. You attempted a cross-disk install, but the filesystem containing /boot/grub does not support UUIDs. There is this in the file /boot/grub/device.map: (hd0) /dev/sda (hd1) /dev/sdb The matching of UUID and devices is good: # blkid /dev/sdb1: UUID=248d7222-1d79-dd61-2766-b0f63e142f70 LABEL=eole2:0 TYPE=linux_raid_member /dev/sdb2: UUID=76644d49-c5f7-9ab6-fe74-81c94fa9616e LABEL=eole2:1 TYPE=linux_raid_member /dev/mapper/VG0-swap: UUID=88469241-b7d3-4e85-97b5-d33a56bfd2fd TYPE=swap /dev/sda1: UUID=248d7222-1d79-dd61-2766-b0f63e142f70 LABEL=eole2:0 TYPE=linux_raid_member /dev/sda2: UUID=76644d49-c5f7-9ab6-fe74-81c94fa9616e LABEL=eole2:1 TYPE=linux_raid_member /dev/md0: UUID=157deef1-ea8f-4611-9021-5e2fabcd84cf TYPE=ext3 /dev/md1: UUID=rNyfNa-5mXA-Ne77-Z15k-KpWA-kFzL-nZbp3h TYPE=LVM2_member /dev/mapper/VG0-root: UUID=6e5c349c-d880-4329-a15c-e192aee4954a TYPE=ext4 The file /etc/fstab (created by installer) contains: /dev/mapper/VG0-root/ext4errors=remount-ro01 UUID=157deef1-ea8f-4611-9021-5e2fabcd84cf/bootext302 The command grub-probe is no more reassuring: # grub-probe -d /dev/md0 -tabstraction grub-probe: error: no mapping exists for `md0'. I read the bug report #554790 on Grub2 and UUID, but it is February. Does Grub2 (version 1.98-1) manages UUIDs? I was not able to set Grub2 with the /dev/disk/by-id. It seems that this bug is fixed in Ubuntu in version 1.98-1ubuntu2. https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/527401 2) Currently the server is running by booting on the installation CD, it can not boot from hard drives. But it is difficult to run it by bootin on the installation CD in rescue mode. A telinit 3 does not work, a mknod /dev/initctl does not work, then it must mount the pseudo FS by hand. Can you add an option in rescue mode which would: boot from the CD, boot with the CD kernel, mount the root partition of the PC and run the init process of the PC? This allow to use the installation CD when the bootloader or the kernel of the PC is faulty. 3) I have done several tests for partitioning, MD RAID and LVM. Partman find the old MD / LVM parameters, and it is virtually impossible to remove if the partitioning is identical. Can you add to partman the possibility to delete the
Bug#477092: [PATCH] add support for setting a username + password in grub-installer for GRUB 2
(CC'ing dle for templates review) Quoting Felix Zielcke (fziel...@z-51.de): Index: debian/grub-installer.templates === --- debian/grub-installer.templates (revision 60631) +++ debian/grub-installer.templates (working copy) @@ -87,6 +87,32 @@ _Description: Device for boot loader ins your third drive (SCSI here); - (fd0) or /dev/fd0 will install GRUB to a floppy. +Template: grub-installer/superuser +Type: string +# :sl2: +_Description: GRUB superuser: + The GRUB boot loader offers many powerful interactive features, which could + be used to compromise your system if unauthorized users have access to the + machine when it is starting up. To defend against this, you may choose a + username and password which will be required before editing menu entries or + entering the GRUB command-line interface. By default, any user will still be + able to start any menu entry without entering a username and password. + . + If you do not wish to set a GRUB username, leave this field blank. + s/your system/the system maybe s/starting up/booting up I'm not sure about To defend against this username or user name? +Template: grub-installer/grub2-password +Type: password +# :sl2: +_Description: GRUB password: + Please enter the password you want to use for GRUB 2. I'd suggest something else than you want to use. Maybe Please enter the GRUB 2 password. We need to choose between GRUB 2 and GRUB. Probably drop the 2. After all, this might be used in an hypothetical GRUB3, right? :-) Another option is somethign similar to the root password prompt: _Description: GRUB password: You need to set a password for GRUB. A malicious or unqualified user with GRUB access can have disastrous results, so you should take care to choose a GRUB password that is not easy to guess. It should not be a word found in dictionaries, or a word that could be easily associated with you. (that will help translators as fuzzy matching will prefill translations) + +Template: grub-installer/empty-password +Type: error +# :sl2: +_Description: Empty password + You have given a username but no password. If you don't want authorization + please don't specify an username, else you have to give a password. + You may want to use the same wording than the similar template in user-setup: _Description: Empty password You entered an empty password, which is not allowed. Please choose a non-empty password. signature.asc Description: Digital signature
Bug#477092: [PATCH] add support for setting a username + password in grub-installer for GRUB 2
Christian Perrier wrote: Quoting Felix Zielcke (fziel...@z-51.de): [...] +Template: grub-installer/superuser +Type: string +# :sl2: +_Description: GRUB superuser: + The GRUB boot loader offers many powerful interactive features, which could + be used to compromise your system if unauthorized users have access to the + machine when it is starting up. To defend against this, you may choose a + username and password which will be required before editing menu entries or + entering the GRUB command-line interface. By default, any user will still be + able to start any menu entry without entering a username and password. + . + If you do not wish to set a GRUB username, leave this field blank. + s/your system/the system maybe s/starting up/booting up I'm not sure about To defend against this No strong opinion on any of these (even the you might not be the owner quibble is weak here). username or user name? One word. Christian Perrier and Justin B Rye are user names, but not their usernames. +Template: grub-installer/grub2-password [...] Another option is somethign similar to the root password prompt: _Description: GRUB password: You need to set a password for GRUB. A malicious or unqualified user with GRUB access can have disastrous results, so you should take care to choose a GRUB password that is not easy to guess. It should not be a word found in dictionaries, or a word that could be easily associated with you. Looks good to me. +Template: grub-installer/empty-password +Type: error +# :sl2: +_Description: Empty password + You have given a username but no password. If you don't want authorization + please don't specify an username, else you have to give a password. Looks bad to me: s/an username/a username/; s/, else/; otherwise/; and you don't want (to get) authorization, you want there to be authentication. You may want to use the same wording than the similar template in user-setup: _Description: Empty password You entered an empty password, which is not allowed. Please choose a non-empty password. This loses the advice on what to do if you're not trying to set up a password. On the other hand, how would I apply that advice if I didn't already know about dpkg-reconfigure? Is there a back button? -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#477092: [PATCH] add support for setting a username + password in grub-installer for GRUB 2
tag 477092 + patch thanks Here's now a patch which adds support to set a username and password for GRUB 2 The debconf templates probable need to be changed. I'm not that perfect in writing them. And I wasn't sure what to do if people enter a username but no password. Now I just don't set anything if no password has been given just like with grub-legacy. -- Felix Zielcke Proud Debian Maintainer Index: debian/grub-installer.templates === --- debian/grub-installer.templates (revision 60631) +++ debian/grub-installer.templates (working copy) @@ -87,6 +87,32 @@ _Description: Device for boot loader ins your third drive (SCSI here); - (fd0) or /dev/fd0 will install GRUB to a floppy. +Template: grub-installer/superuser +Type: string +# :sl2: +_Description: GRUB superuser: + The GRUB boot loader offers many powerful interactive features, which could + be used to compromise your system if unauthorized users have access to the + machine when it is starting up. To defend against this, you may choose a + username and password which will be required before editing menu entries or + entering the GRUB command-line interface. By default, any user will still be + able to start any menu entry without entering a username and password. + . + If you do not wish to set a GRUB username, leave this field blank. + +Template: grub-installer/grub2-password +Type: password +# :sl2: +_Description: GRUB password: + Please enter the password you want to use for GRUB 2. + +Template: grub-installer/empty-password +Type: error +# :sl2: +_Description: Empty password + You have given a username but no password. If you don't want authorization + please don't specify an username, else you have to give a password. + Template: grub-installer/password Type: password # :sl2: Index: grub-installer === --- grub-installer (revision 60631) +++ grub-installer (working copy) @@ -750,6 +750,78 @@ if [ $grub_version = grub ] ; then chmod o-r $ROOT/boot/grub/$menu_file rm -f /tmp/menu.lst.password fi +else + # Set up a username and password if asked or preseeded. + superuser= + password= + db_get grub-installer/password-crypted + if [ $RET ] ; then + error encrypted passwords are not yet supported with GRUB 2. + exit 1 + else + PW_PRIO=low + db_input $PW_PRIO grub-installer/superuser || true + if ! db_go; then + # back up to menu + db_progress STOP + exit 10 + fi + db_get grub-installer/superuser + if [ $RET ]; then + superuser=$RET + while :; do +password= + +db_input $PW_PRIO grub-installer/grub2-password || true +if ! db_go; then + # back up to menu + db_progress STOP + exit 10 +fi + +db_get grub-installer/grub2-password +if [ $RET ]; then + password=$RET + db_input $PW_PRIO grub-installer/password-again || true + if ! db_go; then + db_progress STOP + exit 10 + fi + + db_get grub-installer/password-again + if [ $password = $RET ]; then + break + else + db_input critical grub-installer/password-mismatch || true + if ! db_go; then + db_progress STOP + exit 10 + fi + fi +else + # The user doesn't want a password + break +fi +# We only get here if passwords don't match +PW_PRIO=critical +db_set grub-installer/superuser +db_set grub-installer/password +db_set grub-installer/password-again +db_fset grub-installer/superuser seen false +db_fset grub-installer/password seen false +db_fset grub-installer/password-again seen false + done + fi + fi + if [ $superuser ] [ $password ] ; then + cat $ROOT/etc/grub.d/05_password EOF +#!/bin/sh +exec tail -n +3 $0 +set superusers=$superuser +password $superuser $password +EOF + chmod o-r $ROOT/etc/grub.d/05_password + fi fi if [ $grub_version = grub ]; then
Processed: [PATCH] add support for setting a username + password in grub-installer for GRUB 2
Processing commands for cont...@bugs.debian.org: tag 477092 + patch Bug #477092 [grub-installer] grub-installer: does not support setting password for grub2 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#477092: [PATCH] add support for setting a username + password in grub-installer for GRUB 2
On Fri, Sep 04, 2009 at 09:11:23PM +0200, Felix Zielcke wrote: Here's now a patch which adds support to set a username and password for GRUB 2 The debconf templates probable need to be changed. I'm not that perfect in writing them. And I wasn't sure what to do if people enter a username but no password. Best behaviour is probably to fail displaying that the password can't be empty, like it is currently done in user-setup. Cheers, -- Jérémy Bobbio.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#520361: Wrong configuration for GRUB 2 chain-loading Windows
00 00 00 00 00 00 00 00 00 00 00
0x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE
0x1C0: FF FF 8E FE FF FF 3F 00 00 00 45 05 6C 0A 00 00
0x1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA
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:[E]
Overall install:[O]
Comments/Problems:
This computer came with Windows XP installed, so I resized its
partition and chose to include it in the boot menu. I also chose to
use GRUB 2, not GRUB legacy. The resulting menu entry did not work;
the error message was no such partition (if I remember correctly).
The entry was defined in /etc/grub.d/30_otheros as:
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
menuentry Microsoft Windows XP Professional {
set root=(hd0,0)
chainloader +1
}
However, GRUB 2 uses 1-based partition numbers (unlike GRUB legacy, but
like everyone else in the world!) so the root setting should be (hd0,1)
not (hd0,0).
Other than this, the installation went smoothly.
Ben.
--
Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.
Once you have filled out this report, mail it to sub...@bugs.debian.org.
==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=5.0 (lenny) - installer build 20090123
X_INSTALLATION_MEDIUM=cdrom
==
Installer hardware-summary:
==
umame -a: Linux deadeye 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686
unknown
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile
PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c)
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile
GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile
GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c)
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM
Gigabit Network Connection [8086:1049] (rev 03)
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8
Family) USB UHCI Controller #4 [8086:2834] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8
Family) USB UHCI Controller #5 [8086:2835] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8
Family) USB2 EHCI Controller #2 [8086:283a] (rev 03)
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: Kernel modules: ehci-hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family)
HD Audio Controller [8086:284b] (rev 03)
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family)
PCI Express Port 1 [8086:283f] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family)
PCI Express Port 2 [8086:2841] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family)
PCI Express Port 3 [8086:2843] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family)
PCI Express Port 4 [8086:2845] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family)
PCI Express Port 5 [8086:2847] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8
Family) USB UHCI Controller #1 [8086:2830] (rev 03)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8
Family) USB UHCI Controller #2 [8086
daily netinst image: problems with installing grub(2)
Hello, I just tried the daily built netinst image (for i386) from http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/ in qemu, and they worked well. I setup several test systems with encrypted root with and without lvm. I used the debian-testing-i386-netinst.iso image from Feb. 16 2008. The only thing that always failed, was installing grub/grub2 at the end of the installation process. Only way to fix that, was to change to a console, chroot into /target, and run apt-get update manually. After that, grub2 installed without problems. So I guess that somewhere in the installation process an apt-get update is missing. greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: daily netinst image: problems with installing grub(2)
Jonas Meurer [EMAIL PROTECTED] writes: So I guess that somewhere in the installation process an apt-get update is missing. A new apt has been uploaded and is suppose to fix that issue. This is still on sid and won't be used on dailies until it hits testing[1]. As soon as it has the missing architectures built it will migrate and this issue will be fixed. 1. http://release.debian.org/migration/testing.pl?package=apt -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - Microsoft sells you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
GRUB 2 missing from daily netinst images
Hi, I downloaded todays netinst CD image for i386 to test the new GRUB 2, but the installation of the package fails. On the third console there is an error message saying the package could not be downloaded (I have no Internet connection on the testing machine). Would it be possible to add the GRUB 2 package on the netinst CD? Frank
Re: GRUB 2 missing from daily netinst images
On Tue, Aug 07, 2007 at 10:29:48AM -0700, Frank Bauer wrote: Hi, I downloaded todays netinst CD image for i386 to test the new GRUB 2, but the installation of the package fails. On the third console there is an error message saying the package could not be downloaded (I have no Internet connection on the testing machine). Would it be possible to add the GRUB 2 package on the netinst CD? Hi Frank, Not yet. It's still in experimental stage. It should at least migrate to testing and get OF/powerpc and LVM issues sorted out before it can be considered as an option. -- Robert Millan GPLv2 I know my rights; I want my phone call! DRM What use is a phone call, if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385180: marked as done (GRUB 2 support)
Your message dated Thu, 31 Aug 2006 15:32:12 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#385180: fixed in grub-installer 1.18
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: grub-installer
Severity: wishlist
Tags: patch
Attached patch allows grub-installer to optionaly install GRUB 2.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-amd64-k8
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Index: debian/grub-installer.templates
===
--- debian/grub-installer.templates (revision 40258)
+++ debian/grub-installer.templates (working copy)
@@ -89,6 +89,16 @@
.
This is a fatal error.
+Template: grub-installer/grub2_instead_of_grub_legacy
+Type: boolean
+Default: false
+_Description: Install GRUB 2 instead of GRUB Legacy?
+ GRUB 2 is the next generation of GNU GRUB. It has interesting new features
but
+ is yet in experimental stage. If you choose to install it, you should be
+ prepared for breakage, and have an idea on how to recover your system if it
+ becomes unbootable. You're advised not to do try this on production
+ environments.
+
Template: grub-installer/progress/title
Type: text
_Description: Installing GRUB boot loader
Index: grub-installer
===
--- grub-installer (revision 40258)
+++ grub-installer (working copy)
@@ -188,6 +188,22 @@
bootfstype=$(findfstype /boot)
[ -n $bootfstype ] || bootfstype=$(findfstype /)
+
+# GRUB Legacy defaults
+grub_version=grub
+menu_file=menu.lst
+
+# reiserfs is the only filesystem that d-i supports and grub2 doesn't yet
+if [ $bootfstype != reiserfs ]; then
+ db_input critical grub-installer/grub2_instead_of_grub_legacy || [ $? -eq 30
]
+ db_go || true
+ db_get grub-installer/grub2_instead_of_grub_legacy
+ if [ $RET = true ]; then
+grub_version=grub2
+menu_file=grub.cfg
+ fi
+fi
+
if [ $bootfstype = xfs ]; then
# warn user that grub on xfs is not safe and let them back out to
# main menu.
@@ -203,8 +219,13 @@
db_progress INFO grub-installer/progress/step_install
-if ! apt-install grub ; then
- info Calling 'apt-install grub' failed
+# apt-install passes --no-remove to apt, but grub{,2} conflict each other, so
+# we need to purge them first to support users who try grub2 and then switch
+# to grub legacy, or vice-versa.
+log-output -t grub-installer $chroot $ROOT dpkg -P grub grub2
+
+if ! apt-install ${grub_version} ; then
+ info Calling 'apt-install ${grub_version}' failed
# Hm, unable to install grub into $ROOT/, what should we do?
db_input critical grub-installer/apt-install-failed || [ $? -eq 30 ]
if ! db_go; then
@@ -366,7 +387,7 @@
db_progress INFO grub-installer/progress/step_config_loader
# Delete for idempotency.
-rm -f $ROOT/boot/grub/menu.lst
+rm -f $ROOT/boot/grub/${menu_file}
update_grub
# Set up a password if asked.
@@ -389,11 +410,11 @@
# Add a line to menu.lst to use the given password
# The line is appended after the commented example
sed '/^# password/r /tmp/menu.lst.password' \
-$ROOT/boot/grub/menu.lst $ROOT/boot/grub/menu.lst.new
- mv $ROOT/boot/grub/menu.lst.new $ROOT/boot/grub/menu.lst
+$ROOT/boot/grub/${menu_file}
$ROOT/boot/grub/${menu_file}.new
+ mv $ROOT/boot/grub/${menu_file}.new $ROOT/boot/grub/${menu_file}
# By default, menu.lst is world-readable, which is not so good if it
# contains a password.
- chmod o-r $ROOT/boot/grub/menu.lst
+ chmod o-r $ROOT/boot/grub/${menu_file}
rm -f /tmp/menu.lst.password
fi
@@ -401,8 +422,8 @@
if [ -n $user_params ]; then
# Modify menu.lst to include user parameters.
sed s!^\(# kopt=.*\)!\1 $user_params! \
-$ROOT/boot/grub/menu.lst $ROOT/boot/grub/menu.lst.new
- mv $ROOT/boot/grub/menu.lst.new $ROOT/boot/grub/menu.lst
+$ROOT/boot/grub/${menu_file}
$ROOT/boot/grub/${menu_file}.new
+ mv $ROOT/boot/grub/${menu_file}.new $ROOT/boot/grub/${menu_file}
update_grub # again, to add new options to all the Debian kernel entries
fi
@@ -424,37 +445,48 @@
# This entry automatically added
Re: Bug#385180: GRUB 2 support
Christian Perrier [EMAIL PROTECTED] writes: Asking at low priority would also be ok, if enough people would actually use it to justify all the traslator work and added space of such a user-visible question. Well, in that case I'll then apply the patch and manage to have it in. Please make the question *not* translatable by removing the leading _. I actually don't want translators invest their time in translating experimental stuff. If Grub2 stuff ever comes stable enough, we will anyway make it the default so the question will disappear. My own opinion with regards to this is that experimental stuff does not belong to the released D-I. It has never been done this way. But the final word belongs to the D-I RM. Well, it's not exactly an experimental package. It's releases and usable for a lot of people. I just don't think it's suitable to Etch since it's receiving too many modification and redesigns from upstream side. I'll make it not translatable, no problem. But I have no problem to disable it for releasing. I just wish to have some time with it enabled to catch how many bugs we can. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - Microsoft gives you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385180: GRUB 2 support
Well, it's not exactly an experimental package. It's releases and usable for a lot of people. I just don't think it's suitable to Etch since it's receiving too many modification and redesigns from upstream side. I'll make it not translatable, no problem. But I have no problem to disable it for releasing. I just wish to have some time with it enabled to catch how many bugs we can. If the change is easy to revert, I agree that activating it now would give it more exposure (and in the case of udebs we have nothing that can act as experimental does for unstable for regular packages). The final word should belong to Joey, as Frans is currently not available. signature.asc Description: Digital signature
Bug#385180: GRUB 2 support
Christian Perrier [EMAIL PROTECTED] writes: Well, it's not exactly an experimental package. It's releases and usable for a lot of people. I just don't think it's suitable to Etch since it's receiving too many modification and redesigns from upstream side. I'll make it not translatable, no problem. But I have no problem to disable it for releasing. I just wish to have some time with it enabled to catch how many bugs we can. If the change is easy to revert, I agree that activating it now would give it more exposure (and in the case of udebs we have nothing that can act as experimental does for unstable for regular packages). I applied it. Now to disable it we just need to comment an if block. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - Microsoft gives you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385180: GRUB 2 support
Package: grub-installer
Severity: wishlist
Tags: patch
Attached patch allows grub-installer to optionaly install GRUB 2.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-amd64-k8
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Index: debian/grub-installer.templates
===
--- debian/grub-installer.templates (revision 40258)
+++ debian/grub-installer.templates (working copy)
@@ -89,6 +89,16 @@
.
This is a fatal error.
+Template: grub-installer/grub2_instead_of_grub_legacy
+Type: boolean
+Default: false
+_Description: Install GRUB 2 instead of GRUB Legacy?
+ GRUB 2 is the next generation of GNU GRUB. It has interesting new features
but
+ is yet in experimental stage. If you choose to install it, you should be
+ prepared for breakage, and have an idea on how to recover your system if it
+ becomes unbootable. You're advised not to do try this on production
+ environments.
+
Template: grub-installer/progress/title
Type: text
_Description: Installing GRUB boot loader
Index: grub-installer
===
--- grub-installer (revision 40258)
+++ grub-installer (working copy)
@@ -188,6 +188,22 @@
bootfstype=$(findfstype /boot)
[ -n $bootfstype ] || bootfstype=$(findfstype /)
+
+# GRUB Legacy defaults
+grub_version=grub
+menu_file=menu.lst
+
+# reiserfs is the only filesystem that d-i supports and grub2 doesn't yet
+if [ $bootfstype != reiserfs ]; then
+ db_input critical grub-installer/grub2_instead_of_grub_legacy || [ $? -eq 30
]
+ db_go || true
+ db_get grub-installer/grub2_instead_of_grub_legacy
+ if [ $RET = true ]; then
+grub_version=grub2
+menu_file=grub.cfg
+ fi
+fi
+
if [ $bootfstype = xfs ]; then
# warn user that grub on xfs is not safe and let them back out to
# main menu.
@@ -203,8 +219,13 @@
db_progress INFO grub-installer/progress/step_install
-if ! apt-install grub ; then
- info Calling 'apt-install grub' failed
+# apt-install passes --no-remove to apt, but grub{,2} conflict each other, so
+# we need to purge them first to support users who try grub2 and then switch
+# to grub legacy, or vice-versa.
+log-output -t grub-installer $chroot $ROOT dpkg -P grub grub2
+
+if ! apt-install ${grub_version} ; then
+ info Calling 'apt-install ${grub_version}' failed
# Hm, unable to install grub into $ROOT/, what should we do?
db_input critical grub-installer/apt-install-failed || [ $? -eq 30 ]
if ! db_go; then
@@ -366,7 +387,7 @@
db_progress INFO grub-installer/progress/step_config_loader
# Delete for idempotency.
-rm -f $ROOT/boot/grub/menu.lst
+rm -f $ROOT/boot/grub/${menu_file}
update_grub
# Set up a password if asked.
@@ -389,11 +410,11 @@
# Add a line to menu.lst to use the given password
# The line is appended after the commented example
sed '/^# password/r /tmp/menu.lst.password' \
-$ROOT/boot/grub/menu.lst $ROOT/boot/grub/menu.lst.new
- mv $ROOT/boot/grub/menu.lst.new $ROOT/boot/grub/menu.lst
+$ROOT/boot/grub/${menu_file}
$ROOT/boot/grub/${menu_file}.new
+ mv $ROOT/boot/grub/${menu_file}.new $ROOT/boot/grub/${menu_file}
# By default, menu.lst is world-readable, which is not so good if it
# contains a password.
- chmod o-r $ROOT/boot/grub/menu.lst
+ chmod o-r $ROOT/boot/grub/${menu_file}
rm -f /tmp/menu.lst.password
fi
@@ -401,8 +422,8 @@
if [ -n $user_params ]; then
# Modify menu.lst to include user parameters.
sed s!^\(# kopt=.*\)!\1 $user_params! \
-$ROOT/boot/grub/menu.lst $ROOT/boot/grub/menu.lst.new
- mv $ROOT/boot/grub/menu.lst.new $ROOT/boot/grub/menu.lst
+$ROOT/boot/grub/${menu_file}
$ROOT/boot/grub/${menu_file}.new
+ mv $ROOT/boot/grub/${menu_file}.new $ROOT/boot/grub/${menu_file}
update_grub # again, to add new options to all the Debian kernel entries
fi
@@ -424,37 +445,48 @@
# This entry automatically added by the Debian installer for a non-linux OS
# on $partition
+EOF
+ if [ ${grub_version} = grub ] ; then
+ cat $tmpfile EOF
title $title
root $grubdrive
savedefault
EOF
- # Only set makeactive if grub is installed
- # in the mbr.
- if [ $bootdev = (hd0) ]; then
- cat $tmpfile EOF
+ # Only set makeactive if grub is
installed
+ # in the mbr
Bug#385180: GRUB 2 support
I would love to have GRUB2 to being use on installer but I doubt it's stable enough for Etch. I propose that we use this patch but change it to avoid to use grub2 except if we preseed a grub-installer/test-grub2. That would allow us to test it on other arches too and would allow us to use dilab for it too. What you all think about it? -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - Microsoft gives you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385180: GRUB 2 support
Otavio Salvador wrote: I would love to have GRUB2 to being use on installer but I doubt it's stable enough for Etch. In any case, a critical priority question to the main installation path in d-i, for the user to choose between grub 1 and grub 2 is certianly not something we can release with. I propose that we use this patch but change it to avoid to use grub2 except if we preseed a grub-installer/test-grub2. That would allow us to test it on other arches too and would allow us to use dilab for it too. What you all think about it? Asking at low priority would also be ok, if enough people would actually use it to justify all the traslator work and added space of such a user-visible question. -- see shy jo signature.asc Description: Digital signature
Bug#385180: GRUB 2 support
On Tue, Aug 29, 2006 at 03:05:14PM -0400, Joey Hess wrote: Otavio Salvador wrote: I would love to have GRUB2 to being use on installer but I doubt it's stable enough for Etch. In any case, a critical priority question to the main installation path in d-i, for the user to choose between grub 1 and grub 2 is certianly not something we can release with. Oops!! I'm sorry. I set priority to critical to ease my own tests. I intended to reset it to low when submitting but I forgot. -- Robert Millan My spam trap is [EMAIL PROTECTED] Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385180: GRUB 2 support
Joey Hess [EMAIL PROTECTED] writes: What you all think about it? Asking at low priority would also be ok, if enough people would actually use it to justify all the traslator work and added space of such a user-visible question. Well, in that case I'll then apply the patch and manage to have it in. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - Microsoft gives you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#385180: GRUB 2 support
Asking at low priority would also be ok, if enough people would actually use it to justify all the traslator work and added space of such a user-visible question. Well, in that case I'll then apply the patch and manage to have it in. Please make the question *not* translatable by removing the leading _. I actually don't want translators invest their time in translating experimental stuff. If Grub2 stuff ever comes stable enough, we will anyway make it the default so the question will disappear. My own opinion with regards to this is that experimental stuff does not belong to the released D-I. It has never been done this way. But the final word belongs to the D-I RM. signature.asc Description: Digital signature
