Am Montag, 1. August 2005 22:23 schrieb Danny Kukawka: Hallo Danny,
Versuche doch mal erst hal zu stoppen (rchal stop) und dann von Hand mit fstab zu mounten.
das funktioniert. Aug 3 04:51:56 lotus kernel: Unable to identify CD-ROM format. Aug 3 04:51:56 lotus hal.hotplug[10773]: DEVPATH is not set Aug 3 04:51:56 lotus kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'LinuxUDF', timestamp 2005/08/01 04:41 (1078) ich habe dann den hald nochmal im Vordergrund laufen lassen und folgendes log erzeugt: 05:01:25.619 [I] linux/block_class_device.c:839: Forcing check for media check on device /dev/hdg 05:01:25.625 [I] linux/block_class_device.c:636: volume.num_blocks = 8946816 05:01:25.648 [I] linux/block_class_device.c:651: volume.block_size = 2048 05:01:25.648 [I] linux/block_class_device.c:655: volume.size = 4580769792 05:01:25.668 [I] linux/block_class_device.c:706: Disc in /dev/hdg has data 05:01:25.670 [I] linux/block_class_device.c:723: get_disc_type returned 0x12 05:01:25.675 [I] linux/block_class_device.c:1056: Detecting if /dev/hdg contains a fs 05:01:25.699 [I] linux/volume_id/volume_id.c:2103: called with size=0x0 05:01:25.699 [I] linux/volume_id/volume_id.c:202: get buffer off 0x400, len 0x800 05:01:25.699 [I] linux/volume_id/volume_id.c:213: read sbbuf len:0xc00 05:01:25.859 [I] linux/volume_id/volume_id.c:216: got 0xc00 (3072) bytes 05:01:25.859 [I] linux/volume_id/volume_id.c:202: get buffer off 0x0, len 0x800 05:01:25.859 [I] linux/volume_id/volume_id.c:202: get buffer off 0x1200, len 0x200 05:01:25.859 [I] linux/volume_id/volume_id.c:213: read sbbuf len:0x1400 05:01:25.859 [I] linux/volume_id/volume_id.c:216: got 0x1400 (5120) bytes 05:01:25.859 [I] linux/volume_id/volume_id.c:202: get buffer off 0x0, len 0x200 05:01:25.859 [I] linux/volume_id/volume_id.c:202: get buffer off 0x0, len 0x200 05:01:25.859 [I] linux/volume_id/volume_id.c:202: get buffer off 0x0, len 0x200 05:01:25.859 [I] linux/volume_id/volume_id.c:202: get buffer off 0x0, len 0x11000 05:01:25.859 [I] linux/volume_id/volume_id.c:213: read sbbuf len:0x11000 05:01:25.882 [I] linux/volume_id/volume_id.c:216: got 0x11000 (69632) bytes 05:01:25.882 [I] linux/volume_id/volume_id.c:202: get buffer off 0xff6, len 0xa 05:01:25.882 [I] linux/volume_id/volume_id.c:202: get buffer off 0x1ff6, len 0xa 05:01:25.882 [I] linux/volume_id/volume_id.c:202: get buffer off 0x3ff6, len 0xa 05:01:25.882 [I] linux/volume_id/volume_id.c:202: get buffer off 0x400, len 0x200 05:01:25.882 [I] linux/volume_id/volume_id.c:202: get buffer off 0x10000, len 0x200 05:01:25.882 [I] linux/block_class_device.c:1093: Media in no_partitions device /dev/hdg 05:01:25.882 [I] linux/block_class_device.c:108: volume.fsusage = 'filesystem' 05:01:25.882 [I] linux/block_class_device.c:111: volume.fstype = 'reiserfs' 05:01:25.882 [I] linux/block_class_device.c:114: volume.fsversion = '3.6' 05:01:25.882 [I] linux/block_class_device.c:117: volume.uuid = '0a61de60-d8a4-475a-ba34-64f59c0d2833' 05:01:25.882 [I] linux/block_class_device.c:119: volume.label = '' tja, da ist der Check wohl wirklich daneben gegangen.
ich denke nicht, das es dir was bringt. Es kann durchaus sein, das HAL das Medium falsch erkennt. Der HAL aus der 9.3 ist auch nicht mehr ganz so frisch.
ich werde mal einen Bugreport an die hal Maintainer schreiben. Mfg Jörg