(auto)mount (in KDE) not working after update from 12.1 to 12.2

seancrawford · 01-12-2009, 01:23 PM

I worked with slackware 12.1 for almost a year and whenever I plugged in a usb device I was greeted with a konqueror-window. Since I updated to 12.2 nothing happens anymore.

This is my fstab:
/dev/sda1 /mnt/sda1 ntfs-3g umask=000 0 0
/dev/sdb1 /mnt/sdb1 auto noauto,users 0 0
/dev/sdc1 /mnt/sdc1 auto noauto,users 0 0
/dev/sdd1 /mnt/sdd1 auto noauto,users 0 0
/dev/sde1 /mnt/sde1 auto noauto,users 0 0
/dev/hdc /mnt/dvd auto noauto,users 0 0
/dev/hdd /mnt/dvdrec auto noauto,users 0 0

The first device is a hard disc which is mounted at boot - no problems here. But new usb-stick or flash cards can't be found even if I mount in command line:
I type: mount /mnt/sde1/
answer: mount: special device /dev/sde1 does not exist
Yes, the directories do exist in /mnt/
By the way, even as su the answer remains the same.

HELP!!!!!!!!!!!

----------------------------------------------------
Thanks a lot for all your quick answers. My "/etc/group" entry for plugdev looks like this:
plugdev:x:83:root,wagner (of course "wagner" is my user name. So the problem shouldn't be there.

I also tried the "dmesg | tail" command and got this:

sd 9:0:0:0: [sdf] Mode Sense: 00 00 00 00
sd 9:0:0:0: [sdf] Assuming drive cache: write through
sd 9:0:0:0: [sdf] 15794176 512-byte hardware sectors (8087 MB)
sd 9:0:0:0: [sdf] Write Protect is off
sd 9:0:0:0: [sdf] Mode Sense: 00 00 00 00
sd 9:0:0:0: [sdf] Assuming drive cache: write through
sdf:
sd 9:0:0:0: [sdf] Attached SCSI removable disk
sd 9:0:0:0: Attached scsi generic sg5 type 0
usb-storage: device scan complete

Which I think is totally weird. Why does the system put a new usb-device into sdf if it's the second device I ever plugged in? Shouldn't it at least be "sdb"? And what's more, why is not "sdf1". I never before saw that a formatted device didn't have a number. This is exactly the same usb-stick that showed up as "sdb1" in slackware 12.1. I commented out the removable devices in fstab although those have never been a problem with slackware 12.1. On the contrary hal usually uses fstab, so I can find my device easier when I am working in a terminal. However it didn't change anything at all.

More HELP!!!!!!!!!!!!!!!!!!!! please

Alien_Hominid · 01-12-2009, 01:45 PM

Why sde1? Is your USB multipartitioned?

junpa · 01-12-2009, 01:49 PM

Code:

HAL is not new anymore, but here are a few notes related to it:
  1. User accounts with permission to mount removable devices must be in at
     least the plugdev group, and the power group is also recommended to 
     allow shutdown and reboot via HAL methods.

...from 12.2 changes_and_hint.txt

Didier Spaier · 01-12-2009, 01:51 PM

It doesn't say that /mnt/sde1 does not exist but that /dev/sde1 does not exist.
You should mount your device, wait for ten seconds, then type in a terminal

Code:

dmesg | tail

It will tel you the name given by the kernel to your device, and you should use that one.

For instance:

Code:

ash-3.1$ dmesg|tail
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 252928 512-byte hardware sectors (129 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
usb-storage: device scan complete
sd 0:0:0:0: Attached scsi generic sg0 type 0
bash-3.1$

In his case I know that my device is known as /dev/sda1

Furthermore if you use HAL (and you should if you want to use the auto-mounting with KDE), remove all the lines in /etc/fstab for the removable devices, they are useless as the system will take care of creating a device node for you when you plug-in the device. this stand for USB devices and for your CD/DVD readers and writers.

Last thing, don't forget to check that all users who need to mount removable device should belong to the 'plugdev' and 'cdrom' groups. You can use kuser (as root) for that.

Woodsman · 01-12-2009, 03:18 PM

If the devices are listed in fstab then HAL will not poll for those devices. The devices then must be mounted manually. If this is what you want then consider autostarting KwikDisk to provide an easy way to mount devices.

If you want automatic mounting, then comment out the related mount points in fstab and ensure udev and hal are running. You should see hal polling in ps ax.

The lsusb command will inform you when a USB device is detected.

In KDE you also must have the KDED Media Manager and Media Notifier Daemon services enabled to start.

If after doing all this you do not see any automatic prompts when inserting a USB device, exit KDE, delete or edit ~/.kde/share/config/medianotifierrc and ~/.kde/share/config/mediamanagerrc.

seancrawford · 01-13-2009, 10:36 AM

Thanks a lot for all your quick answers. My "/etc/group" entry for plugdev looks like this:
plugdev:x:83:root,wagner (of course "wagner" is my user name. So the problem shouldn't be there.

I also tried the "dmesg | tail" command and got this:

sd 9:0:0:0: [sdf] Mode Sense: 00 00 00 00
sd 9:0:0:0: [sdf] Assuming drive cache: write through
sd 9:0:0:0: [sdf] 15794176 512-byte hardware sectors (8087 MB)
sd 9:0:0:0: [sdf] Write Protect is off
sd 9:0:0:0: [sdf] Mode Sense: 00 00 00 00
sd 9:0:0:0: [sdf] Assuming drive cache: write through
sdf:
sd 9:0:0:0: [sdf] Attached SCSI removable disk
sd 9:0:0:0: Attached scsi generic sg5 type 0
usb-storage: device scan complete

Which I think is totally weird. Why does the system put a new usb-device into sdf if it's the second device I ever plugged in? Shouldn't it at least be "sdb"? And what's more, why is not "sdf1". I never before saw that a formatted device didn't have a number. This is exactly the same usb-stick that showed up as "sdb1" in slackware 12.1. I commented out the removable devices in fstab although those have never been a problem with slackware 12.1. On the contrary hal usually uses fstab, so I can find my device easier when I am working in a terminal. However it didn't change anything at all.

More HELP!!!!!!!!!!!!!!!!!!! please

gegechris99 · 01-13-2009, 02:07 PM

Quote:

Originally Posted by seancrawford

This is my fstab:
/dev/sda1 /mnt/sda1 ntfs-3g umask=000 0 0
/dev/sdb1 /mnt/sdb1 auto noauto,users 0 0
/dev/sdc1 /mnt/sdc1 auto noauto,users 0 0
/dev/sdd1 /mnt/sdd1 auto noauto,users 0 0
/dev/sde1 /mnt/sde1 auto noauto,users 0 0
/dev/hdc /mnt/dvd auto noauto,users 0 0
/dev/hdd /mnt/dvdrec auto noauto,users 0 0

Your entries for /dev/sd* devices in your fstab have the option noauto (the same applies to your dvd drives). As Woodman said, you should remove those entries from /etc/fstab.

By the way, there is a change in how udev is configured between 12.1 and 12.2. Please refer to CHANGES_AND_HINTS.TXT:

Quote:

As usual, there are changes in udev packaging that need mentioning...
First, be sure to move the /etc/rc.d/rc.udev.new over - the old
/etc/rc.d/rc.udev will not work with the new udev package (and the new
one won't work with the old udev package).
The system udev rules now reside in /lib/udev/rules.d/ instead of
/etc/udev/rules.d/ in older versions. There should never be a reason
to edit anything in /lib/udev/rules.d/, so if you think you have a case
where this is required, either you're wrong or it needs to be addressed
in the upstream source. However, you can override default rules by
placing one with an identical name inside /etc/udev/rules.d/
The rules files in /etc/udev/rules.d/ are still intended to (maybe) be
edited as needed by local system administrators, and as such, the rules
for optical and network devices will still be placed there.

Also pay attention to upgrade instructions in UPGRADE.TXT and in particular step 6 about configuration files.

Did you perform those steps about .new config files (udev in particular)?

Woodsman · 01-13-2009, 02:11 PM

Quote:

Why does the system put a new usb-device into sdf if it's the second device I ever plugged in?

Because in fstab you manually reserved sda through sde.

Quote:

I commented out the removable devices in fstab although those have never been a problem with slackware 12.1.

I'm no expert with HAL, but HAL did go through some changes between 12.1 and 12.2. With respect to hald, udev, etc., I would not place complete emphasis on comparing how things worked between 12.1 and 12.2.

Make sure rc.udev, rc.hald, and rc.messagebus all are executable. Reboot without the external device.

Start X/KDE. Open a terminal session. Verify hald is polling (ps ax | grep poll).

Type lsusb.

Insert the device. Wait two seconds. Type lsusb.

You should see the device get assigned to the next available sdx sequence number, which might not be sdb.

If lsusb shows the device being added but no pop-up dialog boxes appear in KDE, then please refer to my previous post.

seancrawford · 01-14-2009, 12:18 PM

Quote:

Originally Posted by gegechris99

Your entries for /dev/sd* devices in your fstab have the option noauto (the same applies to your dvd drives). As Woodman said, you should remove those entries from /etc/fstab.

By the way, there is a change in how udev is configured between 12.1 and 12.2. Please refer to CHANGES_AND_HINTS.TXT:

Also pay attention to upgrade instructions in UPGRADE.TXT and in particular step 6 about configuration files.

Did you perform those steps about .new config files (udev in particular)?

...this could be the problem...after installation of the udev-package there was no /etc/rc.d/rc.udev.new And the /etc/rc.d/rc.udev was old with all the old paths in it. Any idea where I can get a new /etc/rc.d/rc.udev ?

gegechris99 · 01-14-2009, 01:35 PM

Quote:

Originally Posted by seancrawford

Any idea where I can get a new /etc/rc.d/rc.udev ?

Just look for file rc.udev.new in the udev package (it's just a tarball)

EDIT: However I would rather suggest that you reinstall the udev package. You will see the rc.udev.new file because you have an existing one.

seancrawford · 01-15-2009, 01:08 PM

Quote:

Originally Posted by gegechris99

Just look for file rc.udev.new in the udev package (it's just a tarball)

EDIT: However I would rather suggest that you reinstall the udev package. You will see the rc.udev.new file because you have an existing one.

I did precisely that: reinstall, bit there was no rc.udev.new. I checked the package but there is none. I seem to have a corrupt udev.tgz...

gegechris99 · 01-15-2009, 02:12 PM

Quote:

Originally Posted by seancrawford

I did precisely that: reinstall, bit there was no rc.udev.new. I checked the package but there is none. I seem to have a corrupt udev.tgz...

Did you delete /etc/rc.d/rc.udev before re-installing the package. If yes, then it's normal that there is no rc.udev.new because the post-installation script moved rc.udev.new to rc.udev.

If you had an existing /etc/rc.d/rc.udev before re-installing the package, then you used a corrupted udev-135-i486-2.tgz package.

dive · 01-15-2009, 02:58 PM

Have you got the parted package installed? This one caught me out too until I was pointed at the changelog. Parted is now a dependency of HAL.

seancrawford · 02-20-2009, 03:07 AM

Quote:

Originally Posted by dive

Have you got the parted package installed? This one caught me out too until I was pointed at the changelog. Parted is now a dependency of HAL.

That's it!! You did it!!! You saved me!!! You made my day!!! thankyouthankyouthankyouthankyouthankyou
Now it finally works. and it was so easy.

Thanks again

Bjoern

P.S.: And it has absolutely no consequence to change the fstab. Quite contrary - hal uses the fstab and mounts to where it points. So you always know where hal monts your usb devices ;-)