https://bugzilla.novell.com/show_bug.cgi?id=411447 User AxelKoellhofer@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=411447#c7 --- Comment #7 from Axel Köllhofer <AxelKoellhofer@web.de> 2008-07-27 22:01:57 MDT --- I ran several tests in the last few days. - reformatted the internal LUKS-partiton (tried reiserfs and also ext2/ext3) - updated hal to latest available gif-snapshot from http://download.opensuse.org/repositories/home:/dkukawka/openSUSE_Factory/sr... (rebuilt from src.rpm) - updated udev to 125 (OBS Packages, all rebuilt from src.rpms) but the problem remained the same (in order to give comparable results in further investigating this problem, I then went back to the versions provided via the official Repositories, of course). Mounting an encrypted external USB-Pendrive works "nearly" without problems, in about one of 5 or 6 cases, also the same misrecognition of a partition with size 0 occurs. This happens very often on "first try" after plugging in the USB-Stick. (USB-Stick) lshal -m Start monitoring devicelist: ------------------------------------------------- 05:46:30.880: volume_part_1_size_64000 added 05:46:31.018: volume_part_1_size_64000 removed 05:46:31.036: volume_part_1_size_0 added 05:46:31.105: volume_uuid_ab78772e_3cfb_4709_8956_e106d8d3c4f0 property info.callouts.remove = {'hal-luks-remove'} (new) 05:46:46.205: volume_part_1_size_0 removed Error Message occured Locked and unlocked again 05:46:46.210: volume_uuid_ab78772e_3cfb_4709_8956_e106d8d3c4f0 property info.callouts.remove = {} 05:46:52.193: volume_part_1_size_64000 added 05:46:52.281: volume_part_1_size_64000 removed 05:46:52.343: volume_uuid_dd86c53c_587c_42da_8b02_9c69fb0c1c68 added 05:46:52.407: volume_uuid_ab78772e_3cfb_4709_8956_e106d8d3c4f0 property info.callouts.remove = {'hal-luks-remove'} 05:46:56.696: volume_uuid_dd86c53c_587c_42da_8b02_9c69fb0c1c68 property volume.mount_point = '/media/disk' 05:46:56.698: volume_uuid_dd86c53c_587c_42da_8b02_9c69fb0c1c68 property volume.is_mounted = true 05:47:00.863: volume_uuid_dd86c53c_587c_42da_8b02_9c69fb0c1c68 property volume.mount_point = '' 05:47:00.875: volume_uuid_dd86c53c_587c_42da_8b02_9c69fb0c1c68 property volume.is_mounted = false 05:47:00.998: volume_uuid_dd86c53c_587c_42da_8b02_9c69fb0c1c68 removed 05:47:01.031: volume_uuid_ab78772e_3cfb_4709_8956_e106d8d3c4f0 property info.callouts.remove = {} 05:47:08.691: volume_part_1_size_64000 added 05:47:08.779: volume_part_1_size_64000 removed 05:47:08.834: volume_uuid_dd86c53c_587c_42da_8b02_9c69fb0c1c68 added 05:47:08.897: volume_uuid_ab78772e_3cfb_4709_8956_e106d8d3c4f0 property info.callouts.remove = {'hal-luks-remove'} And everything Works fine. Interestingly, on very first decrypting, primarily the internal partition is _not_ recognized as size 0, but then removed and added again as a "size_0" device. (First decryption of internal partition) 05:21:10.089: volume_part_1_size_64000 added 05:21:10.140: volume_part_1_size_64000 removed 05:21:10.155: volume_part_1_size_0 added 05:21:10.224: volume_uuid_e33ef778_5200_407e_8617_e0f7fb040474 property info.callouts.remove = {'hal-luks-remove'} All other consecutive encryting/decrypting cycles show the device as "volume_part_1_size_0". When deleting the file /etc/udev/rules.d/64-device-mapper.rules, the internal partition seems to be recognized correctly with its uuid-string but mounting vial hal fails with the same error. I would appreciate any ideas about further tests or other information I could provide. Greetings, Axel Köllhofer -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.