Comment 22 for bug 584052

Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

> I changed the topic back.

Ok, for me.

> I felt like my original report was hijacked into a different issue.

Sorry, no hijacking intended.

My mounting issues have been solved by udisks version 1.0.1-1ubuntu1, which is currently available from lucid-proposed ( https://wiki.ubuntu.com/Testing/EnableProposed ). I have not checked whether that includes availability for PowerPC, but I'd assume so. Even if it doesn't sound that likely that it solves your problem, it's probably better to investigate with the newest version of udisks.

To my understanding udisks is the new component between udev and nautilus (which does the automount). New as in Lucid but not in Karmic.

Does "udisks --dump" show anything interesting about your drive in question?

If you do

1.) "sudo killall udisks-daemon"
2.) "udisks --dump"

Will the udisks --dump succeed immediately? (it will restart the daemons you just killed if everything works fine and there is no delay that a human could recognize)

> I think this is now worse. Now I can't even mount the drive from the command line:

Actually I had the same issue with a certain CD-ROM recently (in i386). To my surprise the following trick worked:

1. use dvdisaster application (needs to be installed manually) to read the ISO-image. Just read it, don't do anything with dvdisaster's checksum stuff.
2. loop mount the ISO image "mount -o loop image.iso /media/tricky"

It seems that the kernel or mount or whatever does not retry on I/O errors as hard as dvdisaster does. That was at least my guess.