From: Bill Gradwohl <bill@ycc.com>
To: linux-hotplug@vger.kernel.org
Subject: USB fixed disk
Date: Wed, 16 Feb 2005 16:17:22 +0000 [thread overview]
Message-ID: <42137212.8080301@ycc.com> (raw)
On an FC3 system, a USB fixed disk was being recognized and set up to
mount at /media/usbdisk
I manually commented out the line in /etc/fstab for that device that
fstab-sync had created so I could control mounting and dismounting
myself. However, the /dev entry it used, namely sdd1 isn't created any
longer after I bounced the machine..
I tried to find a mechanism that would tell udev not to create the
entry, but came up empty.
Why isn't udev creating the /dev/ssd1 entry, or am I completely
misunderstanding this?
Anyone know how to get the original functionality back, as at this point
I've got no access at all. When I uncommented the line in fstab and
bounced the box, the line disappeared.
Here's the section of /var/log/messages:
Feb 15 17:00:16 s2 kernel: usb 1-2: new full speed USB device using
ohci_hcd and address 2
Feb 15 17:00:16 s2 kernel: Initializing USB Mass Storage driver...
Feb 15 17:00:16 s2 kernel: scsi3 : SCSI emulation for USB Mass Storage
devices
Feb 15 17:00:16 s2 kernel: usbcore: registered new driver usb-storage
Feb 15 17:00:16 s2 kernel: USB Mass Storage support registered.
...
Feb 15 17:00:16 s2 kernel: Vendor: ST320420 Model: A
Rev: 3.21
Feb 15 17:00:16 s2 kernel: Type: Direct-Access
ANSI SCSI revision: 00
Feb 15 17:00:16 s2 kernel: SCSI device sdd: 39851761 512-byte hdwr
sectors (20404 MB)
Feb 15 17:00:16 s2 kernel: sdd: assuming drive cache: write through
Feb 15 17:00:16 s2 kernel: SCSI device sdd: 39851761 512-byte hdwr
sectors (20404 MB)
Feb 15 17:00:16 s2 kernel: sdd: assuming drive cache: write through
Feb 15 17:00:16 s2 kernel: sdd: sdd1
Feb 15 17:00:16 s2 kernel: Attached scsi disk sdd at scsi3, channel 0,
id 0, lun 0
Yet there is no /dev/sdd*. I'm also curious about the 20 Gig USB drive
being listed twice.
--
Bill Gradwohl
bill@ycc.com
http://www.ycc.com
spamSTOMPER Protected email
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2005-02-16 16:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42137212.8080301@ycc.com \
--to=bill@ycc.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.