LinHES

One of the packages upgraded was hal. try reverting to an older hal from your cache to see if it fixes your issue and report back.

It's udev-135-5.
Rolling back hal to hal-0.5.11-4 had no effect so I rolled udev back to udev-135-4 and it worked.
Updated hal back to hal-0.5.11-5 and it is still working

Unfortunatly the way automount was implemented it had some nasty side effects.
For installs with new harddrives it caused the install to fail, and post install it was causing data corruption.
Because of this it was disabled.

If it was working fine for you, then I suggest making your own udev rules file and placing the rules in it.

Probably related to the problems I had with my 2nd hard drive getting mounted automatically in /media and then reverting to it randomly on reboot. I'll do some research on the udev rules and see about making my own and bring the package back up to current and use them.

I can confirm that there's no auto-mounting of USB mass storage in the latest ISO built from git sources.

I created a udev rule culled from several sources on the net and placed it in /etc/udev/rules.d. I posted it on the Knoppmyth General forum this morning. Here's a copy of it:

KERNEL=="sd[c-z]", SUBSYSTEMS=="usb", NAME="%k", SYMLINK+="usb%m", GROUP="users"
ACTION=="add", KERNEL=="sd[c-z][0-9]", SYMLINK+="usb%n", GROUP="users", NAME="%k"
ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mkdir -p /media/$env{ID_FS_LABEL}"
ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,sync,noatime /dev/%k /media/$env{ID_FS_LABEL}"
ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/$env{ID_FS_LABEL}"
ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/rmdir /media/$env{ID_FS_LABEL}"

The idea is it will only target usb devices and I deliberately started with sdc to skip my 2nd hard drive. It seems to mount properly by disk label and umounts and removes the directory properly but it needs testing and I'm sure could be tweaked and cleaned up.

I wanted to add that when I booted the installation CD, the installer mounted the USB Mass Storage device (thumb drive) I had attached and offered it as an option for the installation target. So it looks as if automounting works in the installer but fails post-install. Jams, if you had to disable it due to side-effects, should it also be disabled in the installer?

It's disabled in both spots.
The USB flash drive being offered as an installation target is intended behaviour. The drive was available when udev started so the drive was mounted.
It's the automounting after the system boots that causes problems.

Re-classified as a feature request and re-opened. It would be very nice if users could attach USB Mass Storage devices and automount them for copying media to/from them.

I found a lightweight volume manager in AUR. Initial testing is going well with the following exception:

• Doesn't seem to mount on boot (with a USB device plugged in).
• Must restarted (although it does start on boot) in order for it to work...

Removed your usb rule (move it to /home/mythtv).

After a 'pacman -Syu'

Found and modified a udev rule and script to take care of this bug. You can remove skvm as it isn't needed.

Worked w/o issue here, so please test and let me know. If your thumb drive has a label then it will mount /media/$label else /media/usb-$dev.

Worked great for me post-reboot. I haven't tried unplugging and plugging back in yet, though.

I'm out of the loop for a couple weeks. Will try this on my box ASAP and get back to you.

I removed my USB thumb drive, and now I get this behavior:

Looks like it's not unmounting automatically. Even if yanking it without unmounting is potentially bad for the filesystem on the USB stick, the OS should at least unmount it once it's gone, right?

I've modified the rule to cleanly unmount. Works fine in testing here!