|
Bugzilla – Full Text Bug Listing |
| Summary: | USB storrage not mounted | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Petr Ostadal <postadal> |
| Component: | Basesystem | Assignee: | Danny Kukawka <dkukawka> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Output of lshal
hald log strace of hal Yast Logs |
||
|
Description
Petr Ostadal
2005-08-18 09:46:32 UTC
Please attach output of lshal if the device is attached Created attachment 46463 [details]
Output of lshal
Looks OK. Can you please: * unplug the mass storage device * $ rchal stop * $ hald --daemon=no --verbose=yes --retain-privileges * Wait for hald to settle down * Plug in the usb storage device and send the log messages occured since hald settled. Created attachment 46485 [details]
hald log
There is a error in HAL I think. The volume is detected as a vfat partition with volume label 'M326STN326 DISK' can you please do this as root: * rchal stop * strace -fqrv -s 512 -o /tmp/hal_strace hald --retain-privileges --verbose=yes --daemon=no * whait 30 sec * attach the device * whait 10 sec * stop strace and attach the file /tmp/hal_strace to this bug (please tar -cjf the file) Created attachment 46659 [details]
strace of hal
did you see the partition in the yast partitioner module? Can you change the volume label vor testing to TESTPARTITION ? What is the current volume label? JFYI: Tomorrow our admins will disconnect network to our office from 09:00 to 14:00. Yes I see the partition in the yast partitioner module. I don't know how can I change volume label, if you know, please do it by yourself (I have backuped data on this disk). Hm, I tried to format the device and add a new partition (FAT and Ext2) with the yast2 partitioner. I can remove the existing volume, but I can't add a new. I get always a error message from yast: --------------- Error Storage modification failed System error code was: -1007 Failure occurred during following action: Creating partition /dev/sdb1 --------------- Looks as there is more than only a problem with HAL. No Idea what the problem is. Now I get volume in HAL and can't also not mount directly. There is no sdb1 anymore. I reassign this to the yast guys. They must say, what the reason for this error is. Parted failed to create the partition. YaST2 logs will show you more information. Hm ... this was really strange. I couldn't format the device with ext2 and also problems to format the device with FAT. Need more than 5 trials to overwrite the current partition and create a full new FAT partition. And first as this worked I could format the device with ext2. There must be a problem with something. I think maybe with volumelabel or a bug in Yast. I attach all yast2 logs to the bug and reassign again to the yast guys. Created attachment 46783 [details]
Yast Logs
YaST told parted a cylinder number that is too big. So this should be a duplicate of bug #105441 and fixed in Beta 3. Please try again with Beta 3. *** This bug has been marked as a duplicate of 105441 *** I don't understand how hal dependent on cylinder number, but which rpms I need update to test fix of this bug? The problem with YaST2 in comment #13 should be fixed with the latest yast2-storage. I can't confirm fix, because the previous (original) partition was replaced and now mount point creates on beta1 too. Yes, this is not fixed for the HAL part. I tested a littlebit with the string for the volume lable: 'M\326STN\326 DISK\'. Looks like D-BUS don't accept the string. I get always this error message from dbus: 29973: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "(error) == NULL || !dbus_error_is_set ((error))" failed in file dbus- connection.c line 2764. This is normally a bug in some application using the D-BUS library. We checked this an it happen with character >= 0x80 I reassign this bug to timo as D-BUS Bug to reproduce: hal-set-property --udi /org/freedesktop/Hal/devices/computer --key xxx --string `echo -e '\x80'` hal-set-property --udi /org/freedesktop/Hal/devices/computer --key xxx --string `echo -e '\x79'` This is not a DBUS bug. This is a problem/bug of HAL. DBUS accept only valid utf8 strings. HAL must check (and if needed fix the string) for valid utf8 befor send string to DBUS. added fix for new package close bug now, package submitted |