Bugzilla – Bug 119940
Custom partitioning does not work
Last modified: 2008-06-25 09:52:53 UTC
I have the following partitions: 1) 15 GB FAT32 2) 1 GB SWAP 3) 80 GB SUSE 9.3 (which I want to keep) 4) 18 GB Linux test partition (for installation of beta OS) All are primary partitions. During new installation, I select custom partitioning, and the 1 disk I have. YAST asks me which partition do I want to delete to make space. I select 4. It says: "The current selection is invalid. Start with highest numbered list entry." Why? OK, I don't have Windows, so I give you FAT32 as well. I select 1 and 4. Same message. Only if I select all partitions, wiping out all my data, it is happy and allows me to move on. BUT, if I go back, and say to use the old partitioning as the base, it will still want to wipe my 80 GB partition, but I can modify partitioning suggestions, and succesfully install the OS in the 19 GB partition, where I want it.
Please provide the y2logs of this scenario as well as the output of `fdisk -l'.
This is the output of "fdisk -l" (sorry, in Italian) Disk /dev/sda: 122.9 GB, 122941242880 bytes 255 heads, 63 sectors/track, 14946 cylinders Units = cilindri of 16065 * 512 = 8225280 bytes Dispositivo Boot Start End Blocks Id System /dev/sda1 1 1959 15735636 c W95 FAT32 (LBA) /dev/sda2 1960 2090 1052257+ 82 Linux swap / Solaris /dev/sda3 2091 12533 83883397+ 83 Linux /dev/sda4 * 12534 14945 19374390 83 Linux I did find the blurb in y2logs during installation, but am unable to copy it to any media, since I am in the middle of the installation without write access to any disks.
you can switch to console and mount one of your linux partitions to copy the file on it. don't forget to umount before go on with the installation or reboot.
Please reopen this bug if the information asked for (y2logs) can be provided.
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(