The unknown partition is one of my NTFS partitions, I dont know why :-s Text installer works fine for me. version is release var/log/installer.log.failed GLI: September 06 2006 21:33:03 - Gentoo Linux Installer version 0.4.2 GLI: September 06 2006 21:33:03 - Setting root password. GLI: September 06 2006 21:33:03 - Livecd root password set. GLI: September 06 2006 21:33:05 - Portmap started. GLI: September 06 2006 21:33:05 - Completed pre_install steps GLI: September 06 2006 21:37:40 - partition(): Processing /dev/sda... GLI: September 06 2006 21:37:40 - Exception received during 'Partition': UnknownPartitionTypeError :FATAL: partition: Refusing to partition this drive due to the presence of an unknown type of partition GLI: September 06 2006 21:37:40 - Traceback (most recent call last): GLI: September 06 2006 21:37:40 - File "/opt/installer/GLIClientController.py", line 197, in run self._install_steps[self._install_step]['function']() GLI: September 06 2006 21:37:40 - File "/opt/installer/templates/x86ArchitectureTemplate.py", line 409, in partition raise GLIException("UnknownPartitionTypeError", 'fatal', 'partition', "Refusing to partition this drive due to the presence of an unknown type of partition") GLI: September 06 2006 21:37:40 - GLIException: UnknownPartitionTypeError :FATAL: partition: Refusing to partition this drive due to the presence of an unknown type of partition /tmp/installprofile.xml <?xml version=" 1.0" ?> <gli-profile> <kernel-build-method> genkernel </kernel-build-method> <cron-daemon> none </cron-daemon> <domainname> localdomain </domainname> <portage-snapshot> file:///mnt/cdrom/snapshots/portage-2006.1.tar.bz2 </portage-snapshot> <kernel-source> livecd-kernel </kernel-source> <install-pcmcia-cs> False </install-pcmcia-cs> <time-zone> Europe/Warsaw </time-zone> <install-distcc> False </install-distcc> <boot-device> /dev/sda </boot-device> <dynamic-stage3> True </dynamic-stage3> <kernel-bootsplash> False </kernel-bootsplash> <bootloader-mbr> True </bootloader-mbr> <hostname> localhost </hostname> <bootloader-kernel-args> doscsi </bootloader-kernel-args> <post-install-script-uri/> <nisdomainname/> <install-stage> 3 </install-stage> <ftp-proxy/> <rsync-proxy/> <stage-tarball/> <bootloader> grub </bootloader> <root-pass-hash> $1$6a2ikz9s$wSFnTFGAXnc5xgWxxQGwv. </root-pass-hash> <http-proxy/> <mta/> <grp-install> False </grp-install> <logging-daemon> sysklogd </logging-daemon> <kernel-config/> <portage-tree-sync> snapshot </portage-tree-sync> <kernel-initrd> True </kernel-initrd> <install-rp-pppoe> False </install-rp-pppoe> <install-packages> gnome xorg-x11 openoffice-bin mozilla-firefox mplayer k3b </install-packages> <network-interfaces> <device ip="dhcp" options=""> eth0 </device> </network-interfaces> <network-mounts/> <partitions> <device devnode="/dev/sda" disklabel="msdos"> <partition format="False" mb="71202" minor="1.0" mkfsopts="" mountopts="" mountpoint="" origminor="1" resized="False" type="ntfs"/> <partition format="False" mb="167270" minor="2.0" mkfsopts="" mountopts="" mountpoint="" origminor="2" resized="False" type="extended"/> <partition format="False" mb="33094" minor="5.0" mkfsopts="" mountopts="" mountpoint="" origminor="5" resized="False" type="ntfs"/> <partition format="True" mb="109" minor="6.0" mkfsopts="" mountopts="defaults" mountpoint="/boot" origminor="6" resized="False" type="ext3"/> <partition format="True" mb="10001" minor="7.0" mkfsopts="" mountopts="defaults" mountpoint="/" origminor="7" resized="False" type="unknown"/> <partition format="False" mb="10001" minor="8.0" mkfsopts="" mountopts="" mountpoint="" origminor="8" resized="False" type="reiserfs"/> <partition format="True" mb="2055" minor="9.0" mkfsopts="" mountopts="" mountpoint="" origminor="9" resized="False" type="linux-swap"/> <partition format="False" mb="12001" minor="10.0" mkfsopts="" mountopts="" mountpoint="" origminor="10" resized="False" type="reiserfs"/> <partition format="False" mb="60000" minor="11.0" mkfsopts="" mountopts="" mountpoint="" origminor="11" resized="False" type="ntfs"/> <partition format="False" mb="40005" minor="12.0" mkfsopts="" mountopts="" mountpoint="" origminor="12" resized="False" type="ntfs"/> </device> </partitions> <services> alsasound,xfs,xdm </services> <etc-files> <file name="rc.conf"> <entry name="DISPLAYMANAGER"> gdm </entry> <entry name="XSESSION"> Gnome </entry> <entry name="EDITOR"> /bin/nano </entry> </file> <file name="conf.d/clock"> <entry name="CLOCK"> UTC </entry> </file> <file name="conf.d/keymaps"> <entry name="KEYMAP"> pl </entry> <entry name="SET_WINDOWSKEYS"> Yes </entry> </file> <file name="conf.d/consolefont"> <entry name="CONSOLEFONT"> 8859-2.a0-ff.16 </entry> </file> <file name="make.conf"> <entry name="MAKEOPTS"/> <entry name="USE"> X alsa amd64 arts avi berkdb bitmap-fonts cairo cdr cli crypt cups dbus dlloader dri dvd dvdr eds elibc_glibc emboss encode esd fam firefox fortran gdbm gif gnome gpm gstreamer gtk gtk2 hal input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog jpeg kde kernel_linux ldap libg++ mad mikmod mp3 mpeg ncurses nls nptl nptlonly ogg opengl oss pam pcre pdflib perl png ppds pppd python qt3 qt4 quicktime readline reflection sdl session spell spl ssl tcpd truetype truetype-fonts type1-fonts udev unicode userland_GNU vorbis xml xorg xv zlib </entry> <entry name="FEATURES"/> <entry name="ACCEPT_KEYWORDS"/> <entry name="CFLAGS"> -march=athlon64 -O2 -pipe </entry> </file> </etc-files> </gli-profile>
var/log/installer.log.failed GLI: September 06 2006 21:33:03 - Gentoo Linux Installer version 0.4.2 GLI: September 06 2006 21:33:03 - Setting root password. GLI: September 06 2006 21:33:03 - Livecd root password set. GLI: September 06 2006 21:33:05 - Portmap started. GLI: September 06 2006 21:33:05 - Completed pre_install steps GLI: September 06 2006 21:37:40 - partition(): Processing /dev/sda... GLI: September 06 2006 21:37:40 - Exception received during 'Partition': UnknownPartitionTypeError :FATAL: partition: Refusing to partition this drive due to the presence of an unknown type of partition GLI: September 06 2006 21:37:40 - Traceback (most recent call last): GLI: September 06 2006 21:37:40 - File "/opt/installer/GLIClientController.py", line 197, in run self._install_steps[self._install_step]['function']() GLI: September 06 2006 21:37:40 - File "/opt/installer/templates/x86ArchitectureTemplate.py", line 409, in partition raise GLIException("UnknownPartitionTypeError", 'fatal', 'partition', "Refusing to partition this drive due to the presence of an unknown type of partition") GLI: September 06 2006 21:37:40 - GLIException: UnknownPartitionTypeError :FATAL: partition: Refusing to partition this drive due to the presence of an unknown type of partition
Don't restrict bugs without any reason. Just leave the checkboxes alone. And, this is intentional, not a bug.
I dont understand, why this is intentional. I have good partitions, fedora core works fine. After manual recreating linux partition installer dont see my one buggy NTFS partition and works fine (crash with root password later :-s). This 'buggy' NTFS partition is good, and is working in windows. Any reason why it is buggy for gentoo installer? Better is to warn about unknown partition and do installer job (other partition for linux are super healthy).
Reopen bugs, because I dont understand reason for breaking installation.
(In reply to comment #4) > Reopen bugs, because I dont understand reason for breaking installation. Because it's very much saner than killing partitions that it doesn't understand. It's by design, not a bug. Read the message.
This is normal error, because installer crash. If partition is unknonwn, installer should exit with nice message for user about problem with partitions. Usability and error reporting is very important. Looking in logs for information (message) is very bad solutions. In text mode installer screen is unreadable, user need to open logs manually.
This is not a bug. You ignored the warning on the partitioning screen about their being an unknown partition. The "crash" you see here is a last ditch effort to stop people from screwing up their partition table because they can't read.
*** Bug 149703 has been marked as a duplicate of this bug. ***
I dont know nothing about OS or good application, who is crashing under start and this is _not error_. Can you give me any example? For me crash is crash, good app should display error message and explanation, DONT CRASH! I think, gentoo developers should think in more userfriendly way ;)
*** Bug 149711 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > This is normal error, because installer crash. If partition is unknonwn, > installer should exit with nice message for user about problem with partitions. > Usability and error reporting is very important. Looking in logs for > information (message) is very bad solutions. In text mode installer screen is > unreadable, user need to open logs manually. > No, that's just crazy talk. If the partition is unknown, it should LEAVE IT ALONE, and perhaps report it to the user, but then allow him to proceed! I have a perfectly valid 35GB LVM2 partition (for another version of linux) on my /dev/hda that now I have to find room to copy over to another drive, so I can flag it as something LIVECD's partitioner will "recognize," (which probably includes letting it format it -- so I either have to use dd | bzip2 to take a snapshot of it or recreate all the logical volumes by hand). I tried reflagging it as several different partition types as well as just deleting it (figuring I'd just doctor it back by hand later). It can't even deal with any of that! It's not satisfied with just looking at the type flag of the partition, it has to look into the partition itself for magic numbers and see if that's what's really there. Now that I've deleted it, it won't let me recreate it without formatting it. This logic is akin to allowing Microsoft windows to refuse to install if there is any other operating system concurrently installed on the system. Unless someone can show some further compelling reason why it HAS to operate in this fashion, I say it is BUNK! I've used just about every partitioner available in the linux community and NONE OF THEM BEHAVED THIS WAY! THIS PARTITIONER IS A TYRANT! -- the avoidance of which is many of our purposes to use linux in the first instance. THIS IS A BUG! FINAL ANSWER! (sorry for all the CAPS but this program just cost me an extra hour or two finding room for, and copying this partion out and back, FOR NOTHING!)
(In reply to comment #11) > (In reply to comment #6) > > This is normal error, because installer crash. If partition is unknonwn, > > installer should exit with nice message for user about problem with partitions. > No, that's just crazy talk. If the partition is unknown, it should LEAVE IT > ALONE, and perhaps report it to the user, but then allow him to proceed! > Yes, maybe should allow him to proceed (and now user can make progress), but Im talking not about this. Im talking about crash screen for end user, when I ignore warning message about partitions. If fdisk (or other tool) crash or something, then gentoo installer should display nice screen with message for user. Now gentoo crash, and user need to look in logs for message. Previously displayed warning is ok, but crash is crash... nothing more.
(In reply to comment #12) > (In reply to comment #11) > > No, that's just crazy talk. If the partition is unknown, it should LEAVE IT > > ALONE, and perhaps report it to the user, but then allow him to proceed! > > > > Yes, maybe should allow him to proceed (and now user can make progress), but Im > talking not about this. Im talking about crash screen for end user, when I > ignore warning message about partitions. > > If fdisk (or other tool) crash or something, then gentoo installer should > display nice screen with message for user. Now gentoo crash, and user need to > look in logs for message. Previously displayed warning is ok, but crash is > crash... nothing more. > Sorry, someone flagged *MY* bug (149703) saying it was resolved by this one. Your english is a little choppy so I'm not totally understanding what your saying, but if I read it right, you are only complaining that you have to dig through the log files rather than have the cause of the error displayed in a popup dialog. I don't think that is that big of a problem because my log file was displayed right there and the error was pretty close to the bottom. If I am correct about your complaint, perhaps someone flagging my bug as resolved by this one was another error. I'm complaining about the behavior of the partitioner to not just ignore a partition that it doesn't recognize the type of, just like EVERY OTHER PARTITIONER OUT THERE! (sorry, not yelling at you :-D )
(In reply to comment #13) > Sorry, someone flagged *MY* bug (149703) saying it was resolved by this one. No, your bug as marked as a duplicate of this one. There was nothing saying your bug was resolved by this one. > resolved by this one was another error. I'm complaining about the behavior of > the partitioner to not just ignore a partition that it doesn't recognize the > type of, just like EVERY OTHER PARTITIONER OUT THERE! If you don't like the way the partitioner works, feel free to write your own code and submit a patch. I am *one* person working on the partitioning code. The way it works with regard to identifying partitions is a function of libparted, which I have absolutely *zero* control over.
(In reply to comment #14) > (In reply to comment #13) > > Sorry, someone flagged *MY* bug (149703) saying it was resolved by this one. > > No, your bug as marked as a duplicate of this one. There was nothing saying > your bug was resolved by this one. > Actually, this one and mine are both flagged as 'resolved' (until I just unflagged it). > > resolved by this one was another error. I'm complaining about the behavior of > > the partitioner to not just ignore a partition that it doesn't recognize the > > type of, just like EVERY OTHER PARTITIONER OUT THERE! > > If you don't like the way the partitioner works, feel free to write your own > code and submit a patch. I am *one* person working on the partitioning code. > The way it works with regard to identifying partitions is a function of > libparted, which I have absolutely *zero* control over. > And I can appreciate that. I am not a python guy or I would (although I might take a look at libparted though). I guess it was not clear that installer's only option was to warn the user about a bug/shortcoming in the underlying library, thereby in effect, institutionalizing the situation! Perhaps until the library is upgraded we should make the popup that appears when you first enter the partitioner state more clearly that "due to a BIG, NASTY, UGLY BUG in the underlying partition library...", etc...?
This is dumb: the program gives a warning and then allowes the user to proceed when the program KNOWS it will later fail? Why not fail immediately? At least stop the user from pressing the "next" button when the installer can see immediately that the user has made a fatal error that will bite him fifteen minutes later!
For me, you are right.
