Bugzilla – Bug 151818
yast2 creates home as swap partition
Last modified: 2006-02-17 17:38:29 UTC
Selecting the whole disk to assign partitions resulted in a home partition to be formated as a swap. There were 3 partitions in the old system. In the partition dialog, I selected the "use whole disk" button. Then yast tries to create /dev/sda1 as /home (80GB), /dev/sda2 as swap, and /dev/sda3 as / (20GB) -- at least it shows so. However in the real installation, it formats /dev/sda1 as swap. As a result, no /home exists in the booted system. Also, "use whole disk" doesn't really use the whole disk space. Yast doesn't assign the whole disk blocks to partitions but leave unused.
As the second try (with "Use whole disk"), yast made the system unbootable. /dev/sda3 is detected as FAT by GRUB, and can't boot. Raised to BLOCKER.
Takashi, please attach the yast logs.
There is no y2log since yast made the system completely broken. I can neither boot nor mount the partition any more. Trying the same procedure now...
It seems the stuff regarding partitioning is pretty broken now. I select the partitions manually. After removing the whole remaining partitions on the disk, assigned like below: /dev/sda1 -> / 20G (reiserfs) /dev/sda2 -> swap 1G /dev/sda3 -> /home 90G (reiserfs) The installation starts, but the root partition is NOT mounted but yast continues to install to ramdisk and shows "no enough disk space" dialog. (/dev/sda3 is mounted to /home, though.)
Also, I cannot abort the installation. Even after pushing "abort installation", yast continues installing packages further... Sigh.
Takashi: Obviously the packager tends to `mix up' the filesystem types of the partitions sometimes. I will mark this bug as a duplicate of #151808 - this all seems to be related. I noticed that the fstab is written correctly nontheless (correct means with the filesystem that is actually used), can you confirm that? *** This bug has been marked as a duplicate of 151808 ***