| View previous topic :: View next topic |
| Author |
Message |
capkin
Tux's lil' helper
Joined: 16 Jul 2005
Posts: 90
|
 Posted: Thu Sep 08, 2005 3:57 am Post subject: udev update USB mass storage not recognized anymore |
 |
|
| I have just merged udev 069 from 058 on a AMD64 machine. I had a Seagate external USB 2.0 drive working perfectly. /media/SEAGATE was automatically created. I don't see this anymore. Should I revert back to 058? Any workarounds for 069? |
|
| Back to top |
|
 |
knirscher
n00b
Joined: 25 Aug 2005
Posts: 16
Location: Darmstadt, Germany
|
| Posted: Fri Sep 09, 2005 6:01 pm Post subject: |
|
|
What exactly is your setup? Please post your /etc/fstab. /media/SEAGATE looks like a directory to me. If it is one, I doubt you are having a udev prolem. Are you using ivman? Have you had a rule for your USB drive in /etc/udev/rules.d/50-udev.rules?
Might take some time for me to answer, since we are suffering from connection problems here :-( |
|
| Back to top |
|
|
capkin
Tux's lil' helper
Joined: 16 Jul 2005
Posts: 90
|
| Posted: Thu Sep 22, 2005 4:45 am Post subject: |
|
|
| Sorry for not replying to this one. When I use udev 058, a folder called /media/seagate is automatically created. When I use latest udev it is not there. I don't have any special rules for my drive. How do you create rules? |
|
| Back to top |
|
|
knirscher
n00b
Joined: 25 Aug 2005
Posts: 16
Location: Darmstadt, Germany
|
| Posted: Thu Sep 22, 2005 7:20 am Post subject: |
|
|
| capkin wrote: | | How do you create rules? |
www.reactivated.net/udevrules.php
But I really wonder if you are probably using ivman?
Be sure to check /etc/udev/rules.d/ for any ._cfg00* files. If you can, compare the /etc/udev/rules.d/50-rules.udev files of the udev versions in question. I suspect this is an ivman related problem or some other automounting mechanism. Maybe the default udev rules were changed and the program - or whatever it is - that creates /media/SEAGATE expects a device node that is no longer created. This reminds me that I would like to take a look at your /etc/fstab. |
|
| Back to top |
|
|
capkin
Tux's lil' helper
Joined: 16 Jul 2005
Posts: 90
|
| Posted: Sat Sep 24, 2005 7:24 pm Post subject: |
|
|
Here is my fstab
| Code: | capkin@tux ~ $ more /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
# /etc/fstab: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.14 2003/10/13 20:03:38 azarah Exp $
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail and tail freely.
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hdc2 /boot reiserfs defaults,noatime,notail 1 2
/dev/hdc8 / reiserfs noatime 0 1
/dev/hdc3 none swap sw 0 0
/dev/hdc5 /home reiserfs noatime 0 0
/dev/hdc6 /usr reiserfs noatime 0 0
/dev/hdc7 /var reiserfs noatime 0 0
/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
/dev/ipod /mnt/ipod vfat sync,nodev,nosuid,user,rw,noauto 0 0
# NOTE: The next line is critical for boot!
none /proc proc defaults 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:
none /dev/shm tmpfs defaults 0 0
/dev/hda /media/cdrecorder auto user,exec,noauto,managed 0 0
|
|
|
| Back to top |
|
|
knirscher
n00b
Joined: 25 Aug 2005
Posts: 16
Location: Darmstadt, Germany
|
| Posted: Sat Sep 24, 2005 7:48 pm Post subject: |
|
|
| Ok, no hint for /media/SEAGATE here. You say this dir was automatically created and the drive was mounted there upon connection? This really looks like some automounting magic. Please tell me if you are using ivman or the Gnome Volume Manager or something similar. If you are looking for a simple and clean solution I would suggest you use submount. |
|
| Back to top |
|
|
capkin
Tux's lil' helper
Joined: 16 Jul 2005
Posts: 90
|
| Posted: Sat Sep 24, 2005 8:05 pm Post subject: |
|
|
| I am using ivman. Howcome with the previous version of udev /media/Seagate was automatically created but not with the latest version? I really need user level access to my storage device. Do I need to create any ivman or udev rule? |
|
| Back to top |
|
|
capkin
Tux's lil' helper
Joined: 16 Jul 2005
Posts: 90
|
| Posted: Sat Sep 24, 2005 8:09 pm Post subject: |
|
|
| How can I figure out to which device file my seagate is mapped, so that I can manually put a fstab entry. |
|
| Back to top |
|
|
knirscher
n00b
Joined: 25 Aug 2005
Posts: 16
Location: Darmstadt, Germany
|
| Posted: Sat Sep 24, 2005 9:00 pm Post subject: |
|
|
You have to find out... plug your drive in and observe ther logs (cat -f /var/log/everything/current). You should get some hints. The device might be /dev/sda1 or /dev/sdb1 or something similar. If you have a pure udev system, you could also just ls /dev, then connect your drive and then ls /dev again to see if any new sd* have shown up.
An entry that would allow manual mount/umount would then look like
| Code: | | /dev/sda1 /media/SEAGATE auto rw,noatime,... 0 0 |
It is, however, generally a good idea to make use of the udev features and follow the directions on e.g. http://www.reactivated.net/writing_udev_rules.html. There should be plenty of examples.
Basically you just put a rule like the following in /etc/udev/rules.d/10-udev.rules
| Code: | | BUS="scsi", KERNEL="sd?1", SYSFS{model}=" i.Beat rock", NAME="ibeat" |
and this should allow you to put /dev/ibeat instead of /dev/sd?1 in your fstab. I suggest you read the udev guide on http://www.gentoo.org/doc/en/udev-guide.xml and the url above, if you want to find out more. |
|
| Back to top |
|
|
capkin
Tux's lil' helper
Joined: 16 Jul 2005
Posts: 90
|
| Posted: Sat Sep 24, 2005 9:08 pm Post subject: |
|
|
| Got it. Thanks a lot for all your help. |
|
| Back to top |
|
|
|
Kernel & Hardware
