Bugzilla – Bug 525282
Cannot install due to nonexistent filesystems during partitioning
Last modified: 2009-08-08 18:43:31 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090714 SUSE/3.5.1-1.1 Firefox/3.5.1 Bugs have not allowed RC2,3 and now 4 to install. RC1 was the best! During install and at the point where I create all mount points manually. For any volume I notice if you click on a volume the filesystem show up blank. If I proceed to edit and select "mount" and type a mount point I get "It's not allowed to assign a mount point to a device with a nonexistent or unknown file system". I am using boot on non-lvm as EXT2 and all other partitions are on lvm and formatted xfs. I also have a two disk system. I have about 10 mount points, none of them work. So far the last 3 11.2 RCs barely start to install. There is nothing unusual with my setup. I has 10.1, 10.3 and 11.1 install and working fine on this machine. I hope by the time 11.2 install works I have enough time to test things before GA. Reproducible: Always Steps to Reproduce: 1.Start installation 2.Select create own partition 3.Edit a partition and try to add a mount point for it. Actual Results: No mount points can be added Expected Results: All paritions should be mounted and installation continues.
Forgot to mention, RC2 and RC3 problems were due to bug 505670. But in RC4 I can't get that far to test that bug. Partition setup was not a problem in RC1/2/3.
linux:/home/mario # fdisk -l Disk /dev/sda: 150.0 GB, 150039945216 bytes 255 heads, 63 sectors/track, 18241 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00033669 Device Boot Start End Blocks Id System /dev/sda1 * 1 9 72261 83 Linux /dev/sda2 10 18241 146448540 8e Linux LVM Disk /dev/sdb: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xc3e8bdc3 Device Boot Start End Blocks Id System /dev/sdb1 1 13 104391 83 Linux /dev/sdb2 14 9729 78043770 8e Linux LVM Disk /dev/dm-0: 17.1 GB, 17179869184 bytes 255 heads, 63 sectors/track, 2088 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 36.0 GB, 36079403008 bytes 255 heads, 63 sectors/track, 4386 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-2 doesn't contain a valid partition table Disk /dev/dm-3: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-3 doesn't contain a valid partition table Disk /dev/dm-4: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-4 doesn't contain a valid partition table Disk /dev/dm-5: 20.4 GB, 20401094656 bytes 255 heads, 63 sectors/track, 2480 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-5 doesn't contain a valid partition table Disk /dev/dm-6: 17.1 GB, 17179869184 bytes 255 heads, 63 sectors/track, 2088 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-6 doesn't contain a valid partition table Disk /dev/dm-7: 20.4 GB, 20401094656 bytes 255 heads, 63 sectors/track, 2480 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-7 doesn't contain a valid partition table Disk /dev/dm-8: 20.4 GB, 20401094656 bytes 255 heads, 63 sectors/track, 2480 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-8 doesn't contain a valid partition table
provide yast2 log files please
How is that possible if there is nothing mounted? BTW, I tried different scenarios, selecting different options at different times. Nothing works. I also verified the DVD.
Could this be related to 505670 since both are lvm/partition related and both are occurring on the same machine?
bug 505670 has been fixed. I also have root partition on an LVM and had no problems at all creating any partitions on the LVM since M1 (though after M1 and some factory updates i could not boot because of bug 505670). You must be doing something unusual with your setup. Do you create them manually or do you create them without formatting them? If the latter is the case then it is natural that you can't assign any mount points to unformatted partitions. If i invoke fdisk -l i also have many logs that /dev/dm-x doesn't containg valid partition table but in my case everything is completely fine.
See bug #525390 comment #1.
Sorry, bug #525290 comment #1.
Why was this marked resolved? This is not resolved here. I have spent a lot of time on this to obtain info to report. Unfortunately, since nothing is mounted I have no way of getting yast logs. I installed the same way from RC1 and up until RC4 setting partitioning/mount points worked. RC2 and RC3 failed later due to lvm bugs. Prior to RC4, any partition showed the correct file system when I edit, now they show ext4. 1. I do not format the boot partition, it has other things on it. 2. I format the root partition since I always do a clean install. 3. I add mount points for all other partitions in LVM that are all xfs. Now, in RC4, none of the above work. I don't know what is unusual, 11.1 installs fine. As mentioned, since I do not see anyone else with this issue (at least in this form) I checked the checksum of the DVD and all is ok.
Ok, looks like you mean this is bug 525290 so may be this should be a duplicate? I will have to wait until RC5, lot's of time wasted on trying to install RC2/3/4 so far, I think if RC5 failed I may skip 11.2 this time.Thanks.
This is M4 not RC4. Milestone 4 is more like Alpha 4, there is still lots to do till the GM.
Look like someone fixed the problem in M5, I was finally able to complete the install with no problems. First time since M1.