|
Bugzilla – Full Text Bug Listing |
| Summary: | Installation: The partitioner is broken in SL 10.1 | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Michael Gross <mgross> |
| Component: | Installation | Assignee: | Thomas Fehr <fehr> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | aj, brian.b, Daniel.Ottey, fmfischer, jdouglas, kernel01, kukuk, marcel, michael.raskey, suse-beta, tiwai, trenn, ug, varkoly |
| Version: | Beta 5 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
yast logs for the second installation
Very huge as I turned on debugging info and the installation was a bit progressed... |
||
|
Description
Michael Gross
2006-02-17 20:45:49 UTC
Revisions for the first comment (sorry but there is no preview available ): > This report is a summary of the following reports: bug #181783 ... This means of course bug #151873 *** Bug 150744 has been marked as a duplicate of this bug. *** *** Bug 151808 has been marked as a duplicate of this bug. *** *** Bug 151783 has been marked as a duplicate of this bug. *** *** Bug 151884 has been marked as a duplicate of this bug. *** We decided that 150744 should go independently. This is the result of the first (successful) installation. I did not attach the logs because this time it worked: fstab: /dev/hda3 / ext3 acl,user_xattr 1 1 /dev/hda2 /boot ext2 acl,user_xattr 1 2 /dev/hda1 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 fdisk -l: Disk /dev/hda: 20.0 GB, 20020396032 bytes 255 heads, 63 sectors/track, 2434 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 66 530113+ 82 Linux swap / Solaris /dev/hda2 * 67 75 72292+ 83 Linux /dev/hda3 76 2434 18948667+ 83 Linux everything looks fine. Interesting... This relates to issue (3): after I started a new installation based on the partitioning in comment #8, YaST made another proposal for the partitioning: Basically deleting hda3 (which is was primary partition) and use the rest of the space for its default partition scheme. Conclusion: This problem (3) obviously does only occurr with an existing extended partition (which will usually be the case). I accepted the proposal without a change and after that which resulted in a working system. For this installation `fdisk -l', `fstab' and YaST-logs follow. I'm no longer sure if YaST really proposed to create no extra partiotion for boot - but this can be extracted from the logfiles, they are just a bit to cryptic for me right now. Created attachment 69152 [details]
yast logs for the second installation
The partitioning and fstab after the second installation: Disk /dev/hda: 20.0 GB, 20020396032 bytes 255 heads, 63 sectors/track, 2434 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 66 530113+ 82 Linux swap / Solaris /dev/hda2 * 67 75 72292+ 83 Linux /dev/hda3 76 2434 18948667+ f W95 Ext'd (LBA) /dev/hda5 76 1490 11365956 83 Linux /dev/hda6 1491 2434 7582648+ 83 Linux --- /dev/hda6 / reiserfs acl,user_xattr 1 1 /dev/hda5 /home reiserfs acl,user_xattr 1 2 /dev/hda1 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/hda2 /data1 auto noauto,user 0 0 Still - looks good. It has to be checked if the proposal for /boot is correct, though. OK, now... making an installation based on this partitioning, YaST fails again to make a good proposal exactly as described in (3). Note: hda2 was /boot in the installation before and stayed as primary partition. So this is definetly about the existance of an partitioning scheme with an extended partition. I used the expert partitioning tool and changed exactly the following: + deleted logial partitions hda5 and hda6 + created a logical partition with the whole space in hda3 to be mounted as / with ext3. + All partitions were marked for formatting So the new setup should exactly look like this: /dev/hda1 swap /dev/hda2 /boot (ext2) /dev/hda5 / (ext3) Expectably, it formatted hda5 with the wrong fs again (reiser this time). I will attach the complete logs as well as the fstab and partition table after that. This time, there was no doubled entry for / in the fstab... I'm attaching the logfiles later. Reassigning to Thomas now. *** Bug 151758 has been marked as a duplicate of this bug. *** *** Bug 152257 has been marked as a duplicate of this bug. *** *** Bug 152564 has been marked as a duplicate of this bug. *** *** Bug 152568 has been marked as a duplicate of this bug. *** Michael I've managed to get a system here to show the same behavior. 1. Previous OS - SLES 10 p4 Partitioning /dev/hda1 1GB as swap /dev/hda2 39GB as / (reiser) The first attempt at Beta4, I got the following proposal Delete existing partitions. create: /dev/hda1 39GB as / (reiser) /dev/hda2 1GB as swap I accepted this proposal and ended up with 2 swap partitions. The / filesystem never really mounted (/dev/hda2). I think this is where the error about disk space being exhausted comes from. The install completes but never really copies anything to the partition. Grub fails install. I deleted all partitions manually before starting the install again. I got the same proposal as above with the same results. 2. I used the 'custom' partitioning section of Yast to delete all partitions and manually created the following entries. /dev/hda1 1GB as swap /dev/hda2 39GB as / (reiser) This install completed with no errors and the system is up and running now. If I can get another system to show the same behavior, are there any particular logs etc... that would be most useful to you? Murlin: I suppose your / was formatted with swap or some other (wrong) fs and therefore failed to mount. You are lucky because not even the manual setip (expert partitioner) does work correctly (see this comment). You might attach your logfiles for the failed installation if you still have them. If not, it's not as wild as we have plenty of material by now. In Beta5: This time I used the manual partitioner to delete all existings partitions and create three new ones (/boot as ext3, 512M swap and / as ext3) and the only error this time was that /boot was also created as swap space. Consistent however, as the fstab was created with /dev/hda1 /boot swap (...) I verified that the partition was actually formatted as swap space. Later at the bootloader configuration this would of course fail completely and result in a non-bootable system. For this installation, I will attach the yast-logs. Created attachment 69956 [details]
Very huge as I turned on debugging info and the installation was a bit progressed...
Well now this is strange. I observed the same problem pictured in comment #19 happening even if I deleted the partitions with fdisk before proceeding. The first time I assumed it always works with non-partitioned disks (non-partitioned was ment with an empty partition table here). This is not the case (anymore). I have just fixed the problem that a partition gets formated with a wrong (old) filesystem in libstorage 2.13.30 I needed to revert another fix from Thomas for that but at least we can do partitioning now that differs from the partitiong that is already on the harddisk. I think you had hit that bug too and it should work with the next beta. Please test. I will keep testing this. Thanks so far. *** Bug 153127 has been marked as a duplicate of this bug. *** 153127: Wrongly crated fstab entries, this time (AFAIK yet) with wrong attributes. *** Bug 153352 has been marked as a duplicate of this bug. *** Disk /dev/hda: 60.0 GB, 60011642880 bytes here is my partition table: 255 heads, 63 sectors/track, 7296 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 3648 29302528+ 7 HPFS/NTFS /dev/hda2 3649 7296 29302560 f W95 Ext'd (LBA) /dev/hda5 3649 5062 11357923+ 7 HPFS/NTFS /dev/hda6 5063 5193 1052226 82 Linux swap / Solaris /dev/hda7 5194 6034 6755301 83 Linux /dev/hda8 6035 7296 10136983+ 83 Linux Both hda7 and hda8 carry an ext3 file system. The installation routine suggests reformatting hda7 with reiserfs and mounting it at "/" (I could live with that) and suggests to reformat hda8 with reiserfs, too, and mounting it at "/home". Moreover when trying to mount hda8 by hand I get: "unknown file system type ext3". So clearly the file system type on this partition was not recognized properly. Reformatting a "working" partition beside the root partition is useless and dangerous. *** Bug 153186 has been marked as a duplicate of this bug. *** *** Bug 154006 has been marked as a duplicate of this bug. *** *** Bug 153951 has been marked as a duplicate of this bug. *** *** Bug 152264 has been marked as a duplicate of this bug. *** *** Bug 154259 has been marked as a duplicate of this bug. *** MIchael, can your retest this with Beta6 and check which of these are fixed? The bug #153352 still exists on beta6. The partitioner doesn't use the whole disk space even if "use entire disk" is selected. 20GB remain unused. STATE Beta6: The problem described in #153127 exist still. The /etc/fstab does not contains the options acl,user_xattr but defults for /. (Default settings, nothig changed in the partitioner) Andreas: I've installed Beta6 however this time I went with the proposal, which worked fine (however I'm not sure if there was a partitioning before). I will try changing the partitioning, based on the existing one and do some more specific testing, though. I'll provide a comment as soon as it's done. *** Bug 155904 has been marked as a duplicate of this bug. *** *** Bug 155114 has been marked as a duplicate of this bug. *** The bug #153352 (doesn't use entire disk) still remains on beta7. Good news: I'm installing Beta7, deleted the old partitioning scheme with the expert partitioner, created 3 primary partitions (one for /boot [ext3], one swap and one for / [reiserfs]) and this resulted in a correct installation, correct fstab and the filesystems were formatted correctly. Problems should be gone in beta#9. Thanks Thomas. *** Bug 153941 has been marked as a duplicate of this bug. *** STATE Beta8: The problem described in #153127 exist still. The resulting /etc/fstab does not contains the options acl,user_xattr for /. (Default settings, nothig changed in the partitioner) You are right the issue with wrong default fstab options for xfs should be fixed with beta#9. |