Bug 150255

Summary: Installation mount points missing for Windows FAT and NTFS file systems
Product: [openSUSE] SUSE Linux 10.1 Reporter: Terje J. Hanssen <terjejhanssen>
Component: InstallationAssignee: Thomas Fehr <fehr>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: suse-beta
Version: Beta 2   
Target Milestone: ---   
Hardware: x86   
OS: SuSE Linux 10.1   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: 10.1 beta2 /var/log/YaST2/ files.zip
10.1 beta2 /etc/fstab (incomplete installation)
10.0 /etc/fstab (just to compare with correct mount points from that installation)

Description Terje J. Hanssen 2006-02-12 19:46:03 UTC
On my multiboot configured installation, previous Suse distros and versions included OpenSuse 10.0, automatically set mount points during Installation Partitioning for existing FAT and NTFS filesystem. OpenSuse 10.1 beta2 Installation finds these partitions and file systems, but the mount points are missing.

Example:
/dev/hda2  /windows/C (FAT)
/dev/hda5  /windows/D (NTFS)
/dev/hda6  /windows/E (FAT)
/dev/hda7  /windows/F (NTFS)
Comment 1 Michael Gross 2006-02-13 11:13:36 UTC
Attach the yast logfiles (/var/log/YaST2) and the resulting /etc/fstab, please.
Note: It's still SUSE Linux, openSUSE is just the project, not the product.
Comment 2 Terje J. Hanssen 2006-02-13 13:00:53 UTC
Created attachment 67989 [details]
10.1 beta2 /var/log/YaST2/ files.zip

See also Bug #150251 Kernel Panic during installation boot.
Remember this is an incomplete 10.1 beta2 installation that doesn't install properly.
However, the initial Partitioning is true enough regarding mount points.
However, it happened that the boot and installation process continued after the CD#1 and asked for CD#2 and CD#3 (for a standard KDE installation selected initially).

However, the installation hung again on
Saving Network Configuration
-> Write drivers information (/etc/modprobe.conf) ..... 0%
while the time stamp surrounded

This has also happened during a previous installation attempt, or later on Font config.
Also this time I had to reset the PC. Booted again, sluggish. The KDE login box had very small fonts, but I was able to login as root.

From there, starting Yast2 network card, I set the correct hostname "dhcppc3", because the default "linux" isn't able to connect to Internet!? At the same time I created a normal user.

Trying to reboot again, again the kernel panic occures and the PC hang.

Mounting the 10.1 file system from another distro, I'm able to attach zipped Yast2 log files and fstab from both 10.1 and 10.2 on the same multiboot PC to compare.
I haven't tried 10.1 beta3.
Comment 3 Terje J. Hanssen 2006-02-13 13:05:09 UTC
Created attachment 67994 [details]
10.1 beta2 /etc/fstab (incomplete installation)

see previous comment
Comment 4 Terje J. Hanssen 2006-02-13 13:08:24 UTC
Created attachment 67995 [details]
10.0 /etc/fstab (just to compare with correct mount points from that installation)
Comment 5 Terje J. Hanssen 2006-02-13 17:28:01 UTC
See also the somewhat related
Bug 150253 - Partitioning - tries to delete and split the last partition and installed system
https://bugzilla.novell.com/show_bug.cgi?id=150253
Comment 6 Terje J. Hanssen 2006-02-18 15:59:17 UTC
FAT and NTFS mount points worked now installing beta 3
Comment 7 Hendrik Vogelsang 2006-02-28 15:22:22 UTC
so this is "fixed"