Bug#548156: grub-installer: No grub2 when using gpt partition schema
Am Donnerstag, den 24.09.2009, 20:44 +0200 schrieb Marcel Koopmans: > Hello Felix, > > I tried the version you suggested. > > Booting it into "expert install" makes it hang during boot... > Final message = "(process:1161): INFO: kbd-mode: setting console mode to > Unicode (UTF-8)" > I'll see this as a good start ;-) You have to add `nopat' to the boot options. This will be hopefully fixed soon in the dailys. The fix is now in the stock Debian sid kernel but d-i's is a bit special. > But "Graphical expert install" works. > > Partition issues that I see is that I only did create 1 partition for > LVM but when I create a VG I can but it anywhere. > This does not happen in the current text version. > > Also, in text mode I am allowed to make a LV with the size "max" but in > graphical this fails. > ( I could be wrong here... as far as I recall in the text version the > max number is just filled in and I most likely just press enter ) Maybe Colin can tell something there. I'm not familiar with partman. > After the installation I see GRUB version 1.97~beta3 > And it seems I did end with squeeze/sid not Lenny 5.0.3 > Only with the businesscards in expert mode you can choose between stable/testing/unstable By default (and so always with netinst) testing gets choosen. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#548156: grub-installer: No grub2 when using gpt partition schema
Am Donnerstag, den 24.09.2009, 14:34 +0200 schrieb Marcel Koopmans: > Hello Felix, > > I use the current stable version of Debian ( debian-503-amd64-CD-1.iso ) > > As you can see in my screen shots... > > 2 disks GPT partition scheme. > 3 Partitions each ( same layout on both ) > 1x 4Mb space for `Reserved BIOS boot area` just a few MiBs as > you suggested. > 1x 128Mb for MD0 ( RAID-1 ) > MD0 will hold /boot ( ext3 ) > 1x rest of space for MD1 ( RAID-1 ) > MD1 for LVM ( VG = vg_os01 ) > VG vg_os01 will hold > LV lv_swap ( 512Mb ) > swap > LV lv_root ( rest of space ) > / ( ext3 ) > > I will look into the current daily installer. > It would be nice if you could try exactly the same from the failed lenny installation with current daily. With the businesscard you can choose between stable/testing/unstable For grub-installer itself it doestn't matter which you install. It isn't yet checked if you have a bios_grub partition and RAID/LVM on /boot, but then you at least should get an error from grub-install in VT4 or syslog. It shouldn't choose GRUB Legacy if you use GPT on all disks belonging to /root Oh and by the way /boot over LVM over RAID should work now with squeeze's GRUB 2 but it hasn't been yet that much tested. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#548156: grub-installer: No grub2 when using gpt partition schema
Am Donnerstag, den 24.09.2009, 13:32 +0200 schrieb Marcel Koopmans: > Hello Felix, > > I do not get that option. > Screen shots for proof > > with kind regards, > Marcel What CD are you actually using? Seems like you didn't tell yet or I totally missed it. ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy version) ii grub-common 1.96+20080724-16 GRand Unified Bootloader, version 2 (common files) That at least tells me that you install stable and not testing or unstable. AFAIK lenny d-i hasn't that option. It shouldn't matter if you're using a few days old daily image. AFAICS there were no partman and parted uploads recently. But even with lenny d-i you shouldn't get GRUB Legacy with GPT Or did you actually create the RAID over /dev/sd[ab] instead of partitions? In that case there might be a bug that GPT isn't detected, because then there's actually no point at all in having a partition table inside the MBR So it would be good if you could try with current daily: http://www.debian.org/devel/debian-installer -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#548156: grub-installer: No grub2 when using gpt partition schema
Am Donnerstag, den 24.09.2009, 13:05 +0200 schrieb Felix Zielcke: > Am Donnerstag, den 24.09.2009, 12:49 +0200 schrieb Marcel Koopmans: > > Hello Felix, > > > > I need some help here... > > How did you change the partition type in the debian installation? > > > > I don't see the option in Parted and fdisk / sfdisk does not support GPT. > > > > with kind regards, > > Marcel > > > > > > Select the partition, press return, select `Use as' and there you find > the `Reserved BIOS boot area', just like also RAID and LVM. > > With parted I only know this, from the GRUB wiki: > sudo parted /dev/sda set bios_grub on Oh maybe it wasn't clear enough, it has to be outside of the RAID. Else you don't see that option and it wouldn't work anyway. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#548156: grub-installer: No grub2 when using gpt partition schema
Am Donnerstag, den 24.09.2009, 12:49 +0200 schrieb Marcel Koopmans: > Hello Felix, > > I need some help here... > How did you change the partition type in the debian installation? > > I don't see the option in Parted and fdisk / sfdisk does not support GPT. > > with kind regards, > Marcel > > Select the partition, press return, select `Use as' and there you find the `Reserved BIOS boot area', just like also RAID and LVM. With parted I only know this, from the GRUB wiki: sudo parted /dev/sda set bios_grub on -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#548156: grub-installer: No grub2 when using gpt partition schema
Hello Felix, Thanks for the quick reply. --- Why I think GRUB Legacy was chossen... # dpkg -l | grep grub ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy version) ii grub-common 1.96+20080724-16 GRand Unified Bootloader, version 2 (common files) part from /var/log/apt/term.log Log started: 2009-09-24 11:23:26 Selecting previously deselected package grub-common. (Reading database ... 12091 files and directories currently installed.) Unpacking grub-common (from .../grub-common_1.96+20080724-16_amd64.deb) ... Selecting previously deselected package grub. Unpacking grub (from .../grub_0.97-47lenny2_amd64.deb) ... Processing triggers for man-db ... Setting up grub-common (1.96+20080724-16) ... Setting up grub (0.97-47lenny2) ... Log ended: 2009-09-24 11:23:27 --- You are right about the disk size 2 TiB, we passed the 2 GiB a little while ago. --- I'll try again creating the "Reserved BIOS boot area". With kind regards, Marcel Felix Zielcke wrote: Am Donnerstag, den 24.09.2009, 10:05 +0200 schrieb Marcel D.A. Koopmans: Package: grub-installer Severity: important I use 2 disks with GPT partition schemes On those I create 2 RAID-1 partitions RAID #1 ( mirror ) contains /boot RAID #2 ( mirror ) contains LVM with other partitions Using these settings no longer gives me the option of selecting GRUB2 <- this is the real bug If your /boot is on GPT you got never asked that question, because GRUB Legacy just doestn't support it. So this isn't at all a bug. By the way GRUB 2 is now the default for everyone, though that question should still be asked in expert mode and if GRUB Legacy can handle /boot. And GRUB Legacy fails as it cannot handle /boot on mdadm with gpt partition schemes. Why do you think GRUB Legacy was choosen by grub-installer? The syslog would be useful, escpecially the grub-installer part. I thing this is an important bug as we soon have 2 gibibyte disks and the default msdos partition scheme cannot address those! You mean 2 TiB, not 2 GiB. If you use GPT you must create on all disks where your /boot is, a `Reserved BIOS boot area', then shown as biosgrub. A few MiBs are enough. They don't need to be all exactly the same size and they don't need to be at the same sectors on the disks. And you must create the RAID over a partition not over the whole disk, even with msdos partition scheme. I just tried it myself with todays amd64 businesscard. 100 MiB for biosgrub, rest for RAID 1 for an ext4 / It installed fine, though grub-installer still used `grub-install (hd0)' instead of (md0) <>
Bug#548156: grub-installer: No grub2 when using gpt partition schema
Am Donnerstag, den 24.09.2009, 10:05 +0200 schrieb Marcel D.A. Koopmans: > Package: grub-installer > Severity: important > > I use 2 disks with GPT partition schemes > On those I create 2 RAID-1 partitions > RAID #1 ( mirror ) contains /boot > RAID #2 ( mirror ) contains LVM with other partitions > > Using these settings no longer gives me the option of selecting GRUB2 <- this > is the real bug If your /boot is on GPT you got never asked that question, because GRUB Legacy just doestn't support it. So this isn't at all a bug. By the way GRUB 2 is now the default for everyone, though that question should still be asked in expert mode and if GRUB Legacy can handle /boot. > And GRUB Legacy fails as it cannot handle /boot on mdadm with gpt partition > schemes. Why do you think GRUB Legacy was choosen by grub-installer? The syslog would be useful, escpecially the grub-installer part. > > I thing this is an important bug as we soon have 2 gibibyte disks and the > default msdos partition scheme cannot address those! You mean 2 TiB, not 2 GiB. If you use GPT you must create on all disks where your /boot is, a `Reserved BIOS boot area', then shown as biosgrub. A few MiBs are enough. They don't need to be all exactly the same size and they don't need to be at the same sectors on the disks. And you must create the RAID over a partition not over the whole disk, even with msdos partition scheme. I just tried it myself with todays amd64 businesscard. 100 MiB for biosgrub, rest for RAID 1 for an ext4 / It installed fine, though grub-installer still used `grub-install (hd0)' instead of (md0) -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#548156: grub-installer: No grub2 when using gpt partition schema
Package: grub-installer Severity: important I use 2 disks with GPT partition schemes On those I create 2 RAID-1 partitions RAID #1 ( mirror ) contains /boot RAID #2 ( mirror ) contains LVM with other partitions Using these settings no longer gives me the option of selecting GRUB2 <- this is the real bug And GRUB Legacy fails as it cannot handle /boot on mdadm with gpt partition schemes. I thing this is an important bug as we soon have 2 gibibyte disks and the default msdos partition scheme cannot address those! With kind regrads, Marcel -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org