Bug 98901 - cannot mount cryptofilesystem from SUSE 9.2
Summary: cannot mount cryptofilesystem from SUSE 9.2
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Preview 3
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Dr. Werner Fink
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 97395
  Show dependency tree / graph
 
Reported: 2005-07-27 12:53 UTC by Forgotten User ZhJd0F0L3x
Modified: 2007-06-06 17:16 UTC (History)
0 users

See Also:
Found By: Component Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
/etc/cryptotab (53 bytes, text/plain)
2005-07-27 12:55 UTC, Forgotten User ZhJd0F0L3x 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User ZhJd0F0L3x 2005-07-27 12:53:39 UTC 
i copied the cryptotab from 9.3 back onto preview3, the filesystem was created
on 9.2, but when trying to mount, /etc/init.d/boot.crypto always complains "an
error occured...."
I am pretty sure that i entered the right passphrase.
I did not do the fsck yet to avoid losing all data.

fix:~ # /etc/init.d/boot.crypto start
Activating crypto devices using /etc/cryptotab ... 
Switching to SuSE 9.2 loop_fish2 compatibility mode.
Please enter passphrase for /dev/hda5: 
An error occured.  Maybe the wrong passphrase was
entered or the file system on /dev/hda5 is corrupted.
Do you want to retry entering the passphrase or
do you want to continue with a file system check? ([yes]/no/check/) ndone
fix:~ #
Comment 1 Forgotten User ZhJd0F0L3x 2005-07-27 12:55:00 UTC 
Created attachment 43625 [details]
/etc/cryptotab

just to make sure: this is the cryptotab that was working with 9.3.
It also worked with STABLE until a few days ago
Comment 2 Forgotten User ZhJd0F0L3x 2005-07-27 13:00:05 UTC 
/local did not exist. Sorry for this one.
Maybe boot.crypto should complain about this ;-)