Bug#597799: installation-report: GPT related issues
On Thu, Sep 23, 2010 at 12:28:45PM -0400, Lennart Sorensen wrote: On Thu, Sep 23, 2010 at 03:39:08PM +0200, Mike Hommey wrote: The disk is a new one, though I didn't check if there was a pre-existing partitioning (but I really doubt it). OTOH, the disk is 2000GB, which is not quite over 2TB, but close enough that it may have mattered. Certainly MBR partitions do not work when you pass 2TB (2^32 512byte sectors). After all if it had a partition table already, it would have just used it. Well, 2000GB should still work with MBR partitions. Now so far I have been running a few machines with GPT partitions on a 2.5TB raid for a few years and with grub2 it works just fine, even with a machine that just uses a plain old BIOS. The point is, grub just works, if I don't forget to create a small boot partition, which I didn't know I had to create until grub-setup failed because of the lack of it. Mike -- 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/20100924062633.ga3...@glandium.org
Bug#597799: installation-report: GPT related issues
On Fri, Sep 24, 2010 at 08:26:33AM +0200, Mike Hommey wrote: On Thu, Sep 23, 2010 at 12:28:45PM -0400, Lennart Sorensen wrote: On Thu, Sep 23, 2010 at 03:39:08PM +0200, Mike Hommey wrote: The disk is a new one, though I didn't check if there was a pre-existing partitioning (but I really doubt it). OTOH, the disk is 2000GB, which is not quite over 2TB, but close enough that it may have mattered. Certainly MBR partitions do not work when you pass 2TB (2^32 512byte sectors). After all if it had a partition table already, it would have just used it. Well, 2000GB should still work with MBR partitions. Now so far I have been running a few machines with GPT partitions on a 2.5TB raid for a few years and with grub2 it works just fine, even with a machine that just uses a plain old BIOS. The point is, grub just works, if I don't forget to create a small boot partition, which I didn't know I had to create until grub-setup failed because of the lack of it. Well I have a machine that has been running for a few years now with: 50GB / 2200GB LVM Grub2 has no problem with that, and it has a GPT partition table. debian:~# parted GNU Parted 1.8.8 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: ServeRA MAIN (scsi) Disk /dev/sda: 2250GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End SizeFile system Name Flags 1 17.4kB 50.0GB 50.0GB ext3 Root boot 2 50.0GB 2250GB 2200GB LVM lvm (parted) quit debian:~# fdisk -l WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 2250.1 GB, 2250128752640 bytes 255 heads, 63 sectors/track, 273562 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/sda1 1 267350 2147483647+ ee EFI GPT So I would say there is no requirement for a /boot partition. There might be a requirement for /boot to not be on LVM. Not sure. -- Len Sorensen -- 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/20100924153809.gi8...@caffeine.csclub.uwaterloo.ca
Bug#597799: installation-report: GPT related issues
On Fri, Sep 24, 2010 at 11:38:09AM -0400, Lennart Sorensen wrote: Disk /dev/sda: 2250.1 GB, 2250128752640 bytes 255 heads, 63 sectors/track, 273562 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/sda1 1 267350 2147483647+ ee EFI GPT So I would say there is no requirement for a /boot partition. There might be a requirement for /boot to not be on LVM. Not sure. I probably haven't made myself clear enough. I was not talking about a /boot partition, but about a GPT grub boot partition, or whatever grub called it in its grub-setup failure message. One you give a bios_grub flag. But then, maybe your core.img is small enough to fit in the 17.4kB before the first partition. Here it doesn't. I made the boot partition 128kB big because I didn't have a clue and found that to be enough in most cases through a google search, though seeing the size of my current core.img, 32 or 64kB would have been enough. Mike -- 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/20100924163127.ga9...@glandium.org
Bug#597799: installation-report: GPT related issues
On Fri, Sep 24, 2010 at 06:31:27PM +0200, Mike Hommey wrote: On Fri, Sep 24, 2010 at 11:38:09AM -0400, Lennart Sorensen wrote: Disk /dev/sda: 2250.1 GB, 2250128752640 bytes 255 heads, 63 sectors/track, 273562 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/sda1 1 267350 2147483647+ ee EFI GPT So I would say there is no requirement for a /boot partition. There might be a requirement for /boot to not be on LVM. Not sure. I probably haven't made myself clear enough. I was not talking about a /boot partition, but about a GPT grub boot partition, or whatever grub called it in its grub-setup failure message. One you give a bios_grub flag. But then, maybe your core.img is small enough to fit in the 17.4kB before the first partition. Here it doesn't. I made the boot partition 128kB big because I didn't have a clue and found that to be enough in most cases through a google search, though seeing the size of my current core.img, 32 or 64kB would have been enough. My core.img is 27KB. That's less than 63 sectors, so yes it would fit. Of course given the GPT uses space there too, I am not sure where it has put it. Hmm. Maybe it just used blocklist automatically when I installed it. -- Len Sorensen -- 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/20100924184624.gk8...@caffeine.csclub.uwaterloo.ca
Bug#597799: installation-report: GPT related issues
Package: installation-reports Version: 2.42 Severity: important Tags: squeeze -- Package-specific info: Boot method: network Image version: http://ftp.nl.debian.org/debian/dists/lenny/main/installer-amd64/current/images/netboot/gtk/netboot.tar.gz 17:58 26-06-10 Date: 22-09-2010 Machine: Custom-made i7 machine Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [O] Detect CD: [ ] 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: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: First, a little digression about the network card. The on-board network controller is a Realtek controller for which the installer told me I needed a non-free firmware. It happens that answering No left the network... working. It would have been helpful if the installer told me the network may still work without the firmware. Back to the core of my issues. I went through a manual partitionning, and didn't create a boot partition for the grub core image, assuming I was creating an MBR partition. It turned out, in the end, that GRUB failed because of that, because the partition table was GPT. I didn't see anything about GPT being used (or maybe wasn't paying too much attention), and surely the partitioner could issue a warning that no such partition was created and that the risk is that GRUB can't be installed. Other than that, everything went fine. Awesome installer. Thanks Mike -- 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 20100912 X_INSTALLATION_MEDIUM=netboot-gtk == Installer hardware-summary: == uname -a: Linux goemon 2.6.32-5-amd64 #1 SMP Thu Aug 12 13:01:50 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DMI [8086:d131] (rev 11) lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:7588] lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express Root Port 1 [8086:d138] (rev 11) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:08.0 System peripheral [0880]: Intel Corporation Core Processor System Management Registers [8086:d155] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:08.1 System peripheral [0880]: Intel Corporation Core Processor Semaphore and Scratchpad Registers [8086:d156] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:08.2 System peripheral [0880]: Intel Corporation Core Processor System Control and Status Registers [8086:d157] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:08.3 System peripheral [0880]: Intel Corporation Core Processor Miscellaneous Registers [8086:d158] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:10.0 System peripheral [0880]: Intel Corporation Core Processor QPI Link [8086:d150] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:10.1 System peripheral [0880]: Intel Corporation Core Processor QPI Routing and Protocol Registers [8086:d151] (rev 11) lspci -knn: Subsystem: Device [0062:0088] lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05) lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:7588] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05) lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:7588] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 [8086:3b4c] (rev 05) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.6 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 [8086:3b4e] (rev 05) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.7 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 8 [8086:3b50]
Bug#597799: installation-report: GPT related issues
On Thu, Sep 23, 2010 at 08:13:26AM +0200, Mike Hommey wrote: Back to the core of my issues. I went through a manual partitionning, and didn't create a boot partition for the grub core image, assuming I was creating an MBR partition. It turned out, in the end, that GRUB failed because of that, because the partition table was GPT. I didn't see anything about GPT being used (or maybe wasn't paying too much attention), and surely the partitioner could issue a warning that no such partition was created and that the risk is that GRUB can't be installed. Oh I forgot to add this: the installed fdisk is pointless as the only thing it can do is tell you to use parted, which supports GPT... except parted is not installed. If the install is done on GPT, shouldn't parted be installed (or any other fdisk equivalent supporting GPT) Mike -- 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/20100923101237.ga24...@glandium.org
Bug#597799: installation-report: GPT related issues
On Thu, Sep 23, 2010 at 12:12:37PM +0200, Mike Hommey wrote: On Thu, Sep 23, 2010 at 08:13:26AM +0200, Mike Hommey wrote: Back to the core of my issues. I went through a manual partitionning, and didn't create a boot partition for the grub core image, assuming I was creating an MBR partition. It turned out, in the end, that GRUB failed because of that, because the partition table was GPT. I didn't see anything about GPT being used (or maybe wasn't paying too much attention), and surely the partitioner could issue a warning that no such partition was created and that the risk is that GRUB can't be installed. Oh I forgot to add this: the installed fdisk is pointless as the only thing it can do is tell you to use parted, which supports GPT... except parted is not installed. If the install is done on GPT, shouldn't parted be installed (or any other fdisk equivalent supporting GPT) Was this a blank unused HD or had something else already been installed before? How big is the HD? I have not seen Debian efault to GPT unless the disk was over 2TB before, or unless windows 7 had already chosen to make it GPT. -- Len Sorensen -- 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/20100923132955.gb8...@caffeine.csclub.uwaterloo.ca
Bug#597799: installation-report: GPT related issues
On Thu, Sep 23, 2010 at 09:29:55AM -0400, Lennart Sorensen wrote: On Thu, Sep 23, 2010 at 12:12:37PM +0200, Mike Hommey wrote: On Thu, Sep 23, 2010 at 08:13:26AM +0200, Mike Hommey wrote: Back to the core of my issues. I went through a manual partitionning, and didn't create a boot partition for the grub core image, assuming I was creating an MBR partition. It turned out, in the end, that GRUB failed because of that, because the partition table was GPT. I didn't see anything about GPT being used (or maybe wasn't paying too much attention), and surely the partitioner could issue a warning that no such partition was created and that the risk is that GRUB can't be installed. Oh I forgot to add this: the installed fdisk is pointless as the only thing it can do is tell you to use parted, which supports GPT... except parted is not installed. If the install is done on GPT, shouldn't parted be installed (or any other fdisk equivalent supporting GPT) Was this a blank unused HD or had something else already been installed before? How big is the HD? I have not seen Debian efault to GPT unless the disk was over 2TB before, or unless windows 7 had already chosen to make it GPT. The disk is a new one, though I didn't check if there was a pre-existing partitioning (but I really doubt it). OTOH, the disk is 2000GB, which is not quite over 2TB, but close enough that it may have mattered. Mike -- 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/20100923133908.ga6...@glandium.org
Bug#597799: installation-report: GPT related issues
On Thu, Sep 23, 2010 at 03:39:08PM +0200, Mike Hommey wrote: The disk is a new one, though I didn't check if there was a pre-existing partitioning (but I really doubt it). OTOH, the disk is 2000GB, which is not quite over 2TB, but close enough that it may have mattered. Certainly MBR partitions do not work when you pass 2TB (2^32 512byte sectors). After all if it had a partition table already, it would have just used it. Now so far I have been running a few machines with GPT partitions on a 2.5TB raid for a few years and with grub2 it works just fine, even with a machine that just uses a plain old BIOS. -- Len Sorensen -- 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/20100923162845.gc8...@caffeine.csclub.uwaterloo.ca
