Prev: Possible OpenDNS problem ?
Next: INIT_WORK
From: none on 31 Mar 2007 15:21
Thanks to yet another failed Maxstor disk, yesterday I did a fresh FC6
install from CD onto the new disk (not a Maxstor, natch) followed by
full upgrade to kernel 2.6.20 build 2933. After getting everything
reinstalled and my usual daemon set up and working everything was
looking good, with automount working just fine for a USD hard disk.

Then I had a rip round, shutting down unwanted daemons, such as the NFS
collection. This caused amd to crash, so I've now turned enough of them
on to keep amd happy, but:

- when I plug in a USB disk of memory stick the icon appears in the
"My computer" window, followed immediately by an error popup
"Cannot mount volume".
Details show "Cannot obtain lock on/media/.hal-mtab"

- when I tried manually making a directory in /media and mounting the
disk I get told that I don't have the permissions to make the
directory, yet I was logged in as root. Presumably this is related
to the mount failure, because I had no problem running mkdir on /mnt
and mounting the drive.

Obviously, I haven't restarted a vital daemon, but I can't work out
which one. I've looked at the HAL website, but its a developer site, not
intended to help with troubleshooting and I couldn't find anything
useful there.

I'd be grateful if anybody who has met this problem can describe how
they overcame it or point me at documentation that will help me solve
the problem.


--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |
From: andrew on 5 Apr 2007 01:48
On Sat, 31 Mar 2007 20:21:51 +0100
none <""martin\"@(none)"> wrote:

[...]
> Obviously, I haven't restarted a vital daemon, but I can't work out
> which one. I've looked at the HAL website, but its a developer site,
> not intended to help with troubleshooting and I couldn't find
> anything useful there.
>

[...]

Have you tried the following command:

'Open the Pod Bay Doors, Please, HAL'

Just a thought :-)

Andrew


--
Andrew's Corner
http://people.aapt.net.au/~adjlstrong/
From: Anders on 12 Apr 2007 17:50
none skrev:
> Thanks to yet another failed Maxstor disk, yesterday I did a fresh FC6
> install from CD onto the new disk (not a Maxstor, natch) followed by
> full upgrade to kernel 2.6.20 build 2933. After getting everything
> reinstalled and my usual daemon set up and working everything was
> looking good, with automount working just fine for a USD hard disk.
>
> Then I had a rip round, shutting down unwanted daemons, such as the NFS
> collection. This caused amd to crash, so I've now turned enough of them
> on to keep amd happy, but:
>
> - when I plug in a USB disk of memory stick the icon appears in the
> "My computer" window, followed immediately by an error popup
> "Cannot mount volume".
> Details show "Cannot obtain lock on/media/.hal-mtab"
>
> - when I tried manually making a directory in /media and mounting the
> disk I get told that I don't have the permissions to make the
> directory, yet I was logged in as root. Presumably this is related
> to the mount failure, because I had no problem running mkdir on /mnt
> and mounting the drive.
>
> Obviously, I haven't restarted a vital daemon, but I can't work out
> which one. I've looked at the HAL website, but its a developer site, not
> intended to help with troubleshooting and I couldn't find anything
> useful there.
>
> I'd be grateful if anybody who has met this problem can describe how
> they overcame it or point me at documentation that will help me solve
> the problem.
>
>
The system communication buss (dbus) must be running as an
service on the system for HAL to work properly.
http://www.linuxcnc.org/docs/HAL_Documentation.pdf
/Anders
 | 
Pages: 1
Prev: Possible OpenDNS problem ?
Next: INIT_WORK