Bugzilla – Bug 327612
Parted does not recognise partitions during installation
Last modified: 2007-09-25 02:42:16 UTC
I have two hard drives on my primary IDE controller /dev/sda1 is NTFS /dev/sda2 is FAT32 /dev/sda3 is EXT3 /dev/sdb1 is SWAP /dev/sdb2 is EXT3 /dev/sdb3 is EXT3 I was doing a fresh installation of openSUSE 10.3 RC1. When I got to the partitioning stage I received an error message "The partitioning on disk /dev/sda is not readable by the partitioning tool parted. You can use the patitions on disk /dev/sda as they are..." I selected "Custom Setup" and when I got to the screen where the partitions are listed, sda1 sda2 and sda3 were all listed as "Linux". I could not get them to change to NTFS or FAT32 using Edit. When I tried to mount them using Edit, sda1 mounted but trying to mount sda2 and sda3 gave an error message "it is not allowed to assign a mount point to a device with nonexistant or unknown file system". I proceeded to install openSUSE on /dev/sdb, with sdb2 as / and sdb3 as /home. Installation proceeded normally, but whenever I booted the installed system the boot process spent a long time trying to access /dev/sda and complaining that it could not do so. I do not think that this is a hardware problem because I subsequently ran the openSUSE 10.2 installation program which correctly detected all the partitions on the two hard disks.
Created attachment 174098 [details] y2 installation logs
This is again a case where parted complains about partitions outsize of disk for /dev/sda. Tejun, could you have a look of this is a duplicate of the disk size detection problem you reported a fix on suse-kernel these days. /proc/partitions looks 8 0 5544943 sda 8 1 8385898 sda1 8 2 2096482 sda2 8 3 28611765 sda3 8 16 195360984 sdb 8 17 2104483 sdb1 8 18 20972857 sdb2 8 19 172281060 sdb3 which makes sda smaller that even sda1.
Yes, that was bug 325552 and this one looks like a duplicate. Michael, please post /var/log/boot.msg from SL103 after the long boot completes. Thanks.
Unfortunately I've reverted to 10.2 on this box. However, from memory I was getting the same problem as described in bug 325552, viz. "Boot process shows a lot of "attempt to access beyond end of device" lines". As soon as I get time I will reinstall 10.3 and post /var/log/boot.msg as requested. Am I likely to be able to solve the problem by installing kernel 2.22.5-29 from Factory?
Created attachment 174466 [details] /var/log/boot.msg file
OK, I've reinstalled 10.3 RC1, and I attach /var/log/boot.msg as requested. The problem is still occurring with the latest 2.6.22.5-29-default kernel. When I use the YaST partitioning tool I get the same message about parted being unable to read /dev/sda, and it shows /dev/sda as being 5.2GB where /dev/sda1 alone is 7.9GB.
Yeap, that's the same problem. KOTD should have it fixed. ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/i386/kernel-default-2.6.22.5-20070921222900.i586.rpm Marking duplicate. *** This bug has been marked as a duplicate of bug 325552 ***
I can confirm that booting with the KOTD solves the problem. The error messages no longer appear while booting, and the YaST partitioner is able to read /dev/sda and mount the three partitions. Thank you for resolving this so speedily. It's a pleasure to report bugs to you. :-)
Thanks. :-)