Your message dated Mon, 2 Sep 2013 15:53:07 +0200 with message-id <201309021553.23982.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #633306, regarding Install troubles with GPT partions (and other issues) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 633306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633306 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Install troubles with GPT partions (and other issues)
- From: Helge Kreutzmann <debian@helgefjell.de>
- Date: Sat, 9 Jul 2011 13:49:41 +0200
- Message-id: <20110709114941.GA3411@Debian-50-lenny-64-minimal>
Package: installation-reports Severity: important Boot method: netinst CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/ from June 8th Date: June 8th, 2011 / June 9th, 2011 Machine: Custome made AMD Phenom(tm) II X6 1055T Processor Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/sda3 ext3 961192 166388 745976 19% / tmpfs tmpfs 5120 4 5116 1% /lib/init/rw tmpfs tmpfs 7688360 1620968 5676840 23% /var/run/lock tmpfs tmpfs 2882592 71872 2664288 3% /tmp udev tmpfs 4059536 0 4059536 0% /dev df: `/var/run/shm': No such file or directory tmpfs tmpfs 7688360 1620968 5676840 23% /var/run /dev/sda2 ext2 91511 16880 69749 20% /boot /dev/mapper/system_vg-home_vg ext3 5765236 142668 5329704 3% /home /dev/mapper/system_vg-tmp_lv ext3 2882592 71872 2664288 3% /tmp /dev/mapper/system_vg-usr_vg ext3 7688360 3659432 3638376 51% /usr /dev/mapper/system_vg-var_vg ext3 7688360 1620968 5676840 23% /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: [O] 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: [O] Install boot loader: [E] Overall install: [E] The machine has a 2 TB disk and is using GPT / EFI (as far as I understand) I used expert install all the time. The following problems appeared, please clone / reassign appropriately. Comments/Problems: a) LVM tries to use the entire available disk (which is fine!) but then suggests one logical volume to span the entire remaining physical volume (in my case /home). I could not find out how to change volume sizes. Since I wanted to install further logical volumes later (and do not need a 2 TB /home) I had to revert to manual partitioning (see b)) Type: wishlist Description: Make size(s) of logical volumes configurable b) Once guided partitioning is chosen, manual partitioning does no longer work. The menu item is available, but returns to guided partitioning. I had to open a shell, run gparted, delete all partitions and reboot (into the installer) to actually manually partition. Type: normal Description: Either remove "manual partitioning" from the menu when guided partitioning was chosen *or* actually allow for manual partitioning after guided (the latter is preferred) c) The boot partion (more on that in d)) gets the flag "boot". However, both grub installation within the installer *and* on the shell fail (both in MBR and in /dev/sda). Running set 1 bios_grub on within gparted (which cleared the flag "boot" at the same time) enabled the grub install to be completed, both in the installer and on the console. Type: serious Description: For gpt, the flag has to be "bios_grub" *not* "boot" d) Since I did a manual partitioning, I partitioned as I was used from other systems, putting /boot as the first partition. Using (c)) I "sucessfully" installed grub, but then after the reboot (see also e) for that) I could not boot; i.e. only "GRUB." was shown. Type: serious Description: If gpt partitioning is chosen, the first partition (10 MB) must *not* have a file system on it. If a file system is present, grub installation must *not* succeed, neither in the installer nor on the console (probably a bug in grub-pc?). The installer should probably warn if the first partition contains a filesystem and/or is prepared for mounting. e) There is no way to reboot in the installer. Chosing "Finishing install" finally ejects the CD-ROM, but then returns to the main installer screen, where no "reboot" is shown. This is even the case if the other problems listed above are solved and/or partially present. Type: important Description: The installer should either reboot autmatically or offer a menu entry for doing so (the former is preferred, probably after a warning) f) After the system finally rebooted the keyboard is lost after X starts, both for kdm and for gdm. A mouse is currently (not yet) connected. In the grub prompt, the emergeny root shell and if kdm/gdm is stopped (via login via ssh) the keyboard works. I will investigate next how to enable the keyboard. Type: important Description: After X (kdm/gdm3) is installed by the installer, the keyboard does not work (at least within kdm/gdm3). If you need further infos/install logs do not hesitate to ask. -- Dr. Helge Kreutzmann debian@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/Attachment: hardware-summary.gz
Description: Binary dataAttachment: partman.gz
Description: Binary dataAttachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: 704605-done@bugs.debian.org, 705089-done@bugs.debian.org, 706304-done@bugs.debian.org, 623735-done@bugs.debian.org, 633306-done@bugs.debian.org, 645210-done@bugs.debian.org, 667802-done@bugs.debian.org, 673548-done@bugs.debian.org, 688064-done@bugs.debian.org, 700656-done@bugs.debian.org, 700976-done@bugs.debian.org, 702434-done@bugs.debian.org, 702435-done@bugs.debian.org, control@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Mon, 2 Sep 2013 15:53:07 +0200
- Message-id: <201309021553.23982.holger@layer-acht.org>
reassign 619236 debian-installer severity 619236 normal reassign 705484 debian-installer thanks Hi, thank you for submitting installation reports, much appreciated. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they contained user errors and/or - they were caused by broken hardware and/or - they have been from a development phase where things were not stable and/or - they are quite old (and thus likely fixed today) and/or - moreinfo was asked and not given or - they are wishlist but rather special + exotic and not have been acted on for years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to close wishlist bugs.) If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---