USB external disk stopped showing up on the desktop

rworkman · 11-13-2008, 11:54 AM

Quote:

Originally Posted by LJSBrokken

This solved it for me, as found on http://wiki.archlinux.org/index.php/...ount_correctly

In short:

Quote:

If

# hald --verbose=yes --daemon=no

says something like

18:50:59.028 [i] blockdev.c:502: Probing storage device /dev/sda
Run started hald-probe-storage (10000) (0)
! full path is '/usr/lib/hal/hald-probe-storage', program_dir is '/usr/lib/hal'
/usr/lib/hal/hald-probe-storage: error while loading shared libraries: libvolume_id.so.1: cannot open shared object file: No such file or directory

You'd have to create a symlink to the library:

# ln -s /lib/libvolume_id.so.0 /lib/libvolume_id.so.1

No, No, NO.

You've got something else screwed up. If you have all of the correct packages installed, that will NOT happen.

Either you've installed some -current packages onto a 12.1 installation, or you've not upgraded all of the packages to -current.

The libvolume_id library version was incremented in udev-129 due to the removal of some deprecated functions. HAL was then recompiled against the new udev package (which includes the updated libvolume_id and others). If you have the correct package combinations, then you won't experience this "bug" at all.

Symlinking shared library versions like you did is begging for trouble - don't do it. That's NEVER a proper solution.

Note: I also edited the wiki page so that hopefully nobody else will follow that bad advice.

BroX · 11-13-2008, 12:24 PM

Quote:

Originally Posted by rworkman

No, No, NO.

You've got something else screwed up. If you have all of the correct packages installed, that will NOT happen.

Thanks for that info!
I have indeed only recently found out that I had an outdated udev package. And now there isn't even a libvolume_id.so.0 anymore:

Code:

bash-3.1$ ls -l /lib/|grep volume
lrwxrwxrwx  1 root root      21 2008-11-09 14:20 libvolume_id.so.1 -> libvolume_id.so.1.0.2
-rwxr-xr-x  1 root root   34356 2008-10-10 04:53 libvolume_id.so.1.0.2

So I guess all is well now ;-)

rworkman · 11-13-2008, 12:30 PM

Quote:

Originally Posted by LJSBrokken

Thanks for that info!
I have indeed only recently found out that I had an outdated udev package. And now there isn't even a libvolume_id.so.0 anymore:

Code:

bash-3.1$ ls -l /lib/|grep volume
lrwxrwxrwx  1 root root      21 2008-11-09 14:20 libvolume_id.so.1 -> libvolume_id.so.1.0.2
-rwxr-xr-x  1 root root   34356 2008-10-10 04:53 libvolume_id.so.1.0.2

So I guess all is well now ;-)

If you didn't move the rc.udev.new to rc.udev, your guess is still wrong - but you'll discover that on your next reboot :-)

BroX · 11-13-2008, 12:36 PM

Code:

bash-3.1# find /etc/ -iname "*.new"
bash-3.1#

dchmelik · 11-13-2008, 09:24 PM

Quote:

Originally Posted by T3slider

Floppy drives don't need to be unmounted (but if you eject the disk while it is being written to it could be disatrous. Also, who uses floppies nowadays?) and CDs (though there is really no chance of ruining a read-only CD whether it is unmounted before ejecting or not. Also, KDE automatically unmounts the CD for me through HAL when I press the CD drive's eject button). FUD has no place here.

I am certainly not afraid of KDE, but I do not know almost everything about new versions' usage. I have not pressed CD eject for a read-mounted CD in KDE since 2.x, but you did not say if you mounted the CD somewhere normal, or if you or KDE mounted it somewhere only normal to it. The only reason CDs were even relevant is someone else mentioned them, but would you eject one or a floppy if it/they was/were mounted read-write?

--David

T3slider · 11-13-2008, 09:36 PM

Quote:

Originally Posted by dchmelik

I am certainly not afraid of KDE, but I do not know almost everything about new versions' usage. I have not pressed CD eject for a read-mounted CD in KDE since 2.x, but you did not say if you mounted the CD somewhere normal, or if you or KDE mounted it somewhere only normal to it. The only reason CDs were even relevant is someone else mentioned them, but would you eject one or a floppy if it/they was/were mounted read-write?

--David

The CD eject button only works if you mount the CD using HAL, for example, using KDE or another DE that supports HAL (or using ivman/pmount in the console) -- ie it only works if you automount the CD (I think -- it may work with an fstab entry, but I haven't had the need to try it). I don't use CD-RW, so I can't really comment on mounting a CD read-write. However, I am pretty sure if you automount it through HAL, the eject button will trigger an unmounting of the CD. If it can't unmount, it'll pop up an error on the screen instead of ejecting the CD. Floppies are a different story because, as far as I know, the eject button is purely mechanical, so the eject operation cannot be cancelled using software -- and therefore, if you eject a mounted floppy, you could damage the filesystem. However, there is always risk in other OSes when ejecting floppies if they are being written to. My current PC has no floppy drive, and if I need to transfer anything to my old PCs I use the network (or if I'm installing an OS I use bootable CDs), so I really have no use for floppy disks any more. 1.44 MB (or at most about 2 MB) is not enough for any practical purpose any more, in my opinion; a 2.6 kernel cannot even fit on it without tailoring it to one specific PC.

vbisis · 11-14-2008, 12:38 AM

If you have updated to current, you should install parted since hal depends on it according to changelog.

That was the trick for me at least, I had the same problem a while ago, but thought it was because of kde 4.2 which I updated to at the same time.