http://bugzilla.novell.com/show_bug.cgi?id=538855 Summary: Already-created encrypted volumes fail to mount after boot - "unknown" is not a valid entry for the fs field in fstab Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jeffm@novell.com QAContact: jsrain@novell.com Found By: Development When I add my /dev/system/home encrypted volume in the partition tool during installation, it correctly asks me for my password. In the partition tool, I can understand why the file system type isn't available - no action is taken until the configuration is accepted. It appears to use a placeholder value, "unknown" when it can't detect the file system type. fstab already has a keyword for that, "auto". It directs mount and/or the kernel to autodetect which file system is on the device. This difference means that the file system can't be mounted without manually correcting the fstab entry. For me, since it's /home, this eventually causes installation problems. As created by YaST2: /dev/mapper/cr_home /home unknown noauto 0 0 As corrected manually to be usable: /dev/mapper/cr_home /home auto noauto 0 0 I thought I had already filed a bug with this description, but a Bugzilla search came up empty. Apologies if the search is just broken. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.