Failed to mount

I can no longer use any external drives on my AAO (Linpus). Message I get is "Failed to mount" then what ever I have plugged in, SD cards, external dvd/cd, 3 different usb sticks.
Also when I shut down it no longer shuts down, I have to do this manually.
I had the dependency issues as well but got all the software updates bar 6 to down load.
Have trawled through the list for hours now looking for clues. I did find one topic which added a line to something "killall Thunar" I added this and then when I saved and quit in terminal there was a message something like connection refused. I am buggard if I can find the thread with the killall Thunar in it either.

Can't say I'm a happy camper at the moment with my AAO

At present I can't even change the os even if I wanted to.

Someone please shed some light on my sad little AAO for me.

Cheers Wilky

 

Hi wilky,

You mean this viewtopic.php?f=39&t=4931 thread.
Please post your exact error outputs, otherwise its hard to analyse.

gr33tz,
Tybor

 

I had a similar problem... ...only just got an external DVD player.

This page sorted me out:

http://ohioloco.ubuntuforums.org/showthread.php?t=638194

Might be some help to you.

 

I have exactly the same problem... cards, usb stick, external HD all fail to mount today even though they worked perfectly for the last few months. And I also can't shut down using the power button.. the screen freezes; but I can shut down using the terminal.

Here's the error message from the file manager:
Failed to mount "/org/freedesktop/Hal/devices/volume_uuid_11CF_E097".
Given device "/org/freedesktop/Hal/devices/volume_uuid_11CF_E097" is not a volume or drive.

I also have a dmesg result if anyone's interested.

Another guy also had the same problem:
http://www.aspireoneuser.com/forum/...=0&sk=t&sd=a&hilit=how+to+mount+code&start=20

System: Linpus Lite 8GB SSD, BIOS v. 3109.

 

Ok, let's see if the HAL daemon has crashed first. Try this:

Code:

ps ax | grep hal

Then we'll see what the Policy Kit says:

Code:

cat /etc/PolicyKit/PolicyKit.conf

In each case, please post the output back here and I'll have a look.

 

Here are the results:

[user@localhost ~]$ ps ax | grep hal
1909 ? Ss 0:00 hald
1910 ? S 0:00 hald-runner
6009 pts/0 S+ 0:00 grep hal

[user@localhost ~]$ cat /etc/PolicyKit/PolicyKit.conf
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">



<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-fixed">
<return result="yes"/>
</match>
<match user="500">
<return result="yes"/>
</match>
</config>

I replaced the PolicyKit.conf file with the one posted here because it seemed to help some people with similar problems.
http://www.aspireoneuser.com/forum/viewtopic.php?f=5&t=4469&st=0&sk=t&sd=a&hilit=mount&start=10

Thanks for your help.

 

Hi jellybean,

It seems to me, that somehow it is tried to mount "/org/freedesktop/Hal/devices/volume_uuid_11CF_E097" which is of course not a valid device to mount.
Try the following in a terminal:

• plug in your usb stick and type:
  Code:

  sudo fdisk -l

  your available devices should be listed. The usb stick should be visible as /dev/sdb1 or something like this (your internal SSD is /dev/sda1).[/*:2n5ftoa3]
• now type:
  Code:

  sudo mount -t auto /dev/sdb1 /mnt/usb

  this mounts your usb stick to the directory /mnt/usb (should be available on you AAO)[/*:2n5ftoa3]
• now following:
  Code:

  mount

  and you should see an entry for /dev/sdb1[/*:2n5ftoa3]

greetz,
Tybor

 

I'm not sure what is causing problems like this for some people? But, it might be that things haven't been properly cleared out of /dev for some reason, so there is more than one disk uuid being referenced there. If one looks in:

/dev/disk/by-uuid

you'll see a softlink of the disk's uuid pointing to the actual /dev/sdbX

Possibly those haven't been cleared out on a shutdown or reboot? Not sure when this clearing would take place? I'm not sure how to fix it. Possibly by booting another Linux from a flashkey and then going into that directory and remove those links?

I'm surmising a lot here, but it is looking like this is what is causing problems for some people.

Just checked and when the ext drive is unmounted, the uuid link in that directory is removed. Maybe, if a drive hasn't been properly unmounted the uui device remains there, hence causing future conflicts?

Cheers.