Error Code 3033 when setting up flash drive encrypted

My install of OpenSuse 12.3 wirh UEFI boot and Xfce desktop went like a dream. But when I tried to set up a Sandisk 64GB USB 2 drive with a single encrypted Ext4 partition using Yast, I get a fail with Error Code 3033. No amount of Googling or searching in the Forum sheds any light on what this means, let alone what to do about it.

My own thoughts are that maybe this is happening after work on the hardware, and to do with getting the desktop (Xfce) to handle the access and closing of the device when plugged in.

I’m happy to work with the command line if somebody can point the way.

I do not know what that error means, I tried encrypted ext4 on an old
1GB USB stick and it works (I work with KDE) as it should (asks for
password when I click on it in dolphin and then shows its content).
I suspect your device is really somehow mounted or accessed by something
in your desktop environment.
To rule that out you could do the following simple test.
Log out from your graphical session and unplug the device.
Switch to a virtual console with [ctrl][alt] F1 and login to the console
as root.
plug in the device and start yast (text version). Try to create the
encrypted partition again.
Do you get the same error or does it work now?


PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.0 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500

On 2013-04-21 15:04, Martin Helm wrote:
> I do not know what that error means, I tried encrypted ext4 on an old
> 1GB USB stick and it works (I work with KDE) as it should (asks for
> password when I click on it in dolphin and then shows its content).

I have hit yast errors often when creating encrypted partitions, and the
error message gives a number, not an explanation. There is no published
list of such numbers, which is absurd.

Sometimes I could find what the error was, by looking at the logs.
Sometimes I completed the procedure by hand.

I do have a procedure to created encrypted filesystems by hand, but I do
not know if systemd influences it. Some commands have changed, there is
no longer the rcrypto script.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Am 21.04.2013 16:03, schrieb Carlos E. R.:
> I do have a procedure to created encrypted filesystems by hand, but I do
> not know if systemd influences it. Some commands have changed, there is
> no longer the rcrypto script.
>
From what I understood the media the OP talks about is just a removable
one, no need for rccrypto here which I can see.


PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.0 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500

Thanks Martin and Robin.

I took Martin’s tip of dropping out, removing device and logging in on a term. Then entered Yast in text mode, (wow it seemed like stepping back a century!)

It asked for a Passphrase when I selected the device under partitioner, so clearly it had got far enough last time to flag encryption. But when I gave the correct phrase it responded: “No encrypted volume to unlock” !!

Undaunted, I created the partition again, to be formatted Ext4 and flagged for encryption. There was no problem. I left Yast but could not mount the visible encrypted partition. I had done enough reading to have an inkling os what to do. From the terminal, as root, I used

cryptsetup luksOpen DEVICE NewName

to map the device, which i believe is the correct way to say it. Encouragingly it asked for the PassPhrase and then went away and did it

Success!! Now, when I plug the drive in, it is detected and if I click the icon it prompts for the PassPhrase. Once that is entered the device opens and i see the Lost&Found. Brilliant.

I just needed the nudge in the right direction, though as Robin comments, I would love to be able to look up what 3033 is about.

Thanks again

I almost bet that the 3033 is something like “unable to unmount” or a
“device blocked by a process”.
It is too bad that we have neither a human readable message nor a useful
list of error codes (my google fu failed on that).


PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.0 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500