I mounted a USB flash card with a reader OK once, but failed the
second time. With two hard disks, an external USB mass storage deveice
and with a USB-key, all mounted using sda-sdd interfaces,

# mount -t vfat /dev/sde1 /media/reader
mount: special device /dev/sde1 does not exist

Indeed, udev has not generated any such interface. I have sdc, sdc1,
sdd, sdd1, sde, sdf, sdf1. The sda and sdb interfaces are for hard
disks.

The flash card reader is seen on the USB bus and the necessary modules
are loaded.

But I get a very odd report from trying to mount sde1: :

$ dmesg | tail
sdf: assuming drive cache: write through
SCSI device sdf: 234441648 512-byte hdwr sectors (120034 MB)
sdf: Write Protect is off
sdf: Mode Sense: 27 00 00 00
sdf: assuming drive cache: write through sdf: sdf1
sd 13:0:0:0: Attached scsi disk sdf
usb-storage: device scan complete
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sdb1.

The message about FAT on sdb1 is correct, for it is ext2. Since udev
had created a sdf1, if I try to mount using it:

# mount -t vfat /dev/sdf1 /media/reader
mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

I get the sense that for some reason udev is not creating sde1, and so
sdf and sdf1 are created, but can't be used. I'm running Etch, and
udev is 0.105-4.

--

Haines Brown, KB1GRM





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Haines Brown wrote:
> I mounted a USB flash card with a reader OK once, but failed the
> second time. With two hard disks, an external USB mass storage deveice
> and with a USB-key, all mounted using sda-sdd interfaces,
>
> # mount -t vfat /dev/sde1 /media/reader
> mount: special device /dev/sde1 does not exist
>
> Indeed, udev has not generated any such interface. I have sdc, sdc1,
> sdd, sdd1, sde, sdf, sdf1. The sda and sdb interfaces are for hard
> disks.
>
> The flash card reader is seen on the USB bus and the necessary modules
> are loaded.
>
> But I get a very odd report from trying to mount sde1: :
>
> $ dmesg | tail
> sdf: assuming drive cache: write through
> SCSI device sdf: 234441648 512-byte hdwr sectors (120034 MB)
> sdf: Write Protect is off
> sdf: Mode Sense: 27 00 00 00
> sdf: assuming drive cache: write through sdf: sdf1
> sd 13:0:0:0: Attached scsi disk sdf
> usb-storage: device scan complete
> FAT: bogus number of reserved sectors
> VFS: Can't find a valid FAT filesystem on dev sdb1.
>
> The message about FAT on sdb1 is correct, for it is ext2. Since udev
> had created a sdf1, if I try to mount using it:
>
> # mount -t vfat /dev/sdf1 /media/reader
> mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
> missing codepage or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
> I get the sense that for some reason udev is not creating sde1, and so
> sdf and sdf1 are created, but can't be used. I'm running Etch, and
> udev is 0.105-4.
>

I've seen this sort of thing happen, when the system, for whatever
reason, thinks the original device is still attached. The detection
event for the second use is then given a new device node.

You may want to try running an 'fdisk' on the device names, to see which
actually has partitions, and what their type(s) is(are). For example:

# fdisk -l /dev/sde

Disk /dev/sde: 65 MB, 65012224 bytes
8 heads, 32 sectors/track, 496 cylinders
Units = cylinders of 256 * 512 = 131072 bytes

Device Boot Start End Blocks Id System
/dev/sde1 * 1 484 61924+ 1 FAT12
Partition 1 has different physical/logical endings:
phys=(499, 7, 32) logical=(483, 7, 32)

which will at least tell you the device name to use with the mount
command, and the file system type.

--
Bob McGowan

Haines Brown wrote:
> I mounted a USB flash card with a reader OK once, but failed the
> second time. With two hard disks, an external USB mass storage deveice
> and with a USB-key, all mounted using sda-sdd interfaces,
>
> # mount -t vfat /dev/sde1 /media/reader
> mount: special device /dev/sde1 does not exist
>
> Indeed, udev has not generated any such interface. I have sdc, sdc1,
> sdd, sdd1, sde, sdf, sdf1. The sda and sdb interfaces are for hard
> disks.
>
> The flash card reader is seen on the USB bus and the necessary modules
> are loaded.
>
> But I get a very odd report from trying to mount sde1: :
>
> $ dmesg | tail
> sdf: assuming drive cache: write through
> SCSI device sdf: 234441648 512-byte hdwr sectors (120034 MB)
> sdf: Write Protect is off
> sdf: Mode Sense: 27 00 00 00
> sdf: assuming drive cache: write through sdf: sdf1
> sd 13:0:0:0: Attached scsi disk sdf
> usb-storage: device scan complete
> FAT: bogus number of reserved sectors
> VFS: Can't find a valid FAT filesystem on dev sdb1.
>
> The message about FAT on sdb1 is correct, for it is ext2. Since udev
> had created a sdf1, if I try to mount using it:
>
> # mount -t vfat /dev/sdf1 /media/reader
> mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
> missing codepage or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
> I get the sense that for some reason udev is not creating sde1, and so
> sdf and sdf1 are created, but can't be used. I'm running Etch, and
> udev is 0.105-4.
>

I've seen this sort of thing happen, when the system, for whatever
reason, thinks the original device is still attached. The detection
event for the second use is then given a new device node.

You may want to try running an 'fdisk' on the device names, to see which
actually has partitions, and what their type(s) is(are). For example:

# fdisk -l /dev/sde

Disk /dev/sde: 65 MB, 65012224 bytes
8 heads, 32 sectors/track, 496 cylinders
Units = cylinders of 256 * 512 = 131072 bytes

Device Boot Start End Blocks Id System
/dev/sde1 * 1 484 61924+ 1 FAT12
Partition 1 has different physical/logical endings:
phys=(499, 7, 32) logical=(483, 7, 32)

which will at least tell you the device name to use with the mount
command, and the file system type.

--
Bob McGowan

USB detection has been broken on Debian for years, literally. It works fine
for me with removable drives, but my Testing system will detect my Palm
device once -- and never again, until I reboot. Then I can sync once more.
--
Carl Fink nitpicking@nitpicking.com

Read my blog at nitpickingblog.blogspot.com. Reviews! Observations!
Stupid mistakes you can correct!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jul 30, 2007 at 09:13:03PM -0400, Carl Fink wrote:
> USB detection has been broken on Debian for years, literally. It works fine
> for me with removable drives, but my Testing system will detect my Palm
> device once -- and never again, until I reboot. Then I can sync once more.

Care to give us the relavent sections of your /var/log/syslog and dmesg?

What software are you useing to connect to your Palm? What device name
have you told the software to use? Its been a while since I hooked up
my palm (the data hasn't changed in 6 months), and I've reinstalled
Debian since so don't have it set up. However, I remember that in
gnome-pilot there was some confusion over the actual device to tell it.
If I was too specific, and the kernel alternated between two device
names, it couldn't find it the second time.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

I would suggest reading the USB docs in these links:
http://www.kernel.org/pub/linux/util...plug/udev.html

It is convenient to use persistence to ensure that all removable USB devices retain their name regardless of how many times you plug them in and remove them. This also allows you to make fstab entries so that any user can, for example, mount your digital camera to download the pictures. You will run into naming problems if the previous device is still in use even if the device node had been removed, but in that case you should be asking yourself what's keeping the device open. Without using the persistent naming mechanism, your 'sd?' assignments will be based solely on the order in which you happened to plug things in - like USB stick or camera first.



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/30/07 20:13, Carl Fink wrote:
> USB detection has been broken on Debian for years, literally. It works fine
> for me with removable drives, but my Testing system will detect my Palm
> device once -- and never again, until I reboot. Then I can sync once more.

It always works perfectly for me plugging thumb drives and a digital
camera.

I've taken to using UUIDs for permanent mount points, since pmount
seems to bypass udev. And udev is (was?) in such flux and the rules
changed on me.

http://www.debian-administration.org...522#comment_15

Here's a snippet from my /etc/fstab:

UUID="c207a86c-91ac-4733-9760-93b0389e193d" /media/backup \
ext3,ext2 defaults,noauto 0 2

- --
Ron Johnson, Jr.
Jefferson LA USA

Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGrrygS9HxQb37XmcRAhU6AJ4zKgngaJmLnnbnzYvF34 dOcYUPBwCeOpoi
wmD+wHDeJV+5Zs0O8tiDHHQ=
=Z7f2
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jul 30, 2007 at 11:37:52PM -0500, Ron Johnson wrote:
> On 07/30/07 20:13, Carl Fink wrote:
> > USB detection has been broken on Debian for years, literally. It works fine
> > for me with removable drives, but my Testing system will detect my Palm
> > device once -- and never again, until I reboot. Then I can sync once more.
>
> It always works perfectly for me plugging thumb drives and a digital
> camera.
>
> I've taken to using UUIDs for permanent mount points, since pmount
> seems to bypass udev. And udev is (was?) in such flux and the rules
> changed on me.
>
> Here's a snippet from my /etc/fstab:
>
> UUID="c207a86c-91ac-4733-9760-93b0389e193d" /media/backup \
> ext3,ext2 defaults,noauto 0 2

For a shorter fstab entry, can you label a digital camera and then use
LABEL="camera" instead?

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jul 30, 2007 at 11:37:52PM -0500, Ron Johnson wrote:
> On 07/30/07 20:13, Carl Fink wrote:
> > USB detection has been broken on Debian for years, literally. It works fine
> > for me with removable drives, but my Testing system will detect my Palm
> > device once -- and never again, until I reboot. Then I can sync once more.
>
> It always works perfectly for me plugging thumb drives and a digital
> camera.
>
> I've taken to using UUIDs for permanent mount points, since pmount
> seems to bypass udev. And udev is (was?) in such flux and the rules
> changed on me.
>
> Here's a snippet from my /etc/fstab:
>
> UUID="c207a86c-91ac-4733-9760-93b0389e193d" /media/backup \
> ext3,ext2 defaults,noauto 0 2

For a shorter fstab entry, can you label a digital camera and then use
LABEL="camera" instead?

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/01/07 08:05, Douglas Allan Tutty wrote:
> On Mon, Jul 30, 2007 at 11:37:52PM -0500, Ron Johnson wrote:
>> On 07/30/07 20:13, Carl Fink wrote:
>>> USB detection has been broken on Debian for years, literally. It works fine
>>> for me with removable drives, but my Testing system will detect my Palm
>>> device once -- and never again, until I reboot. Then I can sync once more.
>> It always works perfectly for me plugging thumb drives and a digital
>> camera.
>>
>> I've taken to using UUIDs for permanent mount points, since pmount
>> seems to bypass udev. And udev is (was?) in such flux and the rules
>> changed on me.
>>
>> Here's a snippet from my /etc/fstab:
>>
>> UUID="c207a86c-91ac-4733-9760-93b0389e193d" /media/backup \
>> ext3,ext2 defaults,noauto 0 2
>
> For a shorter fstab entry, can you label a digital camera and then use
> LABEL="camera" instead?

You can do it with fixed disks that have decent filesystems, but I
doubt that anything partitioned with vfat would work.

Can't hurt to try, though...

- --
Ron Johnson, Jr.
Jefferson LA USA

Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGsL9YS9HxQb37XmcRAuHxAJ9t3G3xDXcUzx8tnHTQEp VWXy+jFACfTKvb
spzHj9pHqPuOaXU4+Hc6fKs=
=WAv9
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, Aug 01, 2007 at 12:14:01PM -0500, Ron Johnson wrote:
> On 08/01/07 08:05, Douglas Allan Tutty wrote:
>
> > For a shorter fstab entry, can you label a digital camera and then use
> > LABEL="camera" instead?
>
> You can do it with fixed disks that have decent filesystems, but I
> doubt that anything partitioned with vfat would work.

Can't you use mlabel? Or mkfs.vfat with the -n parameter?

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Douglas Allan Tutty wrote:
> On Wed, Aug 01, 2007 at 12:14:01PM -0500, Ron Johnson wrote:
>> On 08/01/07 08:05, Douglas Allan Tutty wrote:
> >
>>> For a shorter fstab entry, can you label a digital camera and then use
>>> LABEL="camera" instead?
>> You can do it with fixed disks that have decent filesystems, but I
>> doubt that anything partitioned with vfat would work.
>
> Can't you use mlabel? Or mkfs.vfat with the -n parameter?
>
> Doug.
>
>

Yes. I have used mlabel to label my XD memory cards (all of them) as
FUJIXDCARD, and set up fstab for them with "LABEL=FUJIXDCARD..." and it
works fine.

I also have an old Muvo MP player (64MB) I'm using as portable storage
now, also labeled the same way (MUSICDISK), it also works fine.

--
Bob McGowan

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/01/07 15:40, Bob McGowan wrote:
> Douglas Allan Tutty wrote:
>> On Wed, Aug 01, 2007 at 12:14:01PM -0500, Ron Johnson wrote:
>>> On 08/01/07 08:05, Douglas Allan Tutty wrote:
>> >
>>>> For a shorter fstab entry, can you label a digital camera and then use
>>>> LABEL="camera" instead?
>>> You can do it with fixed disks that have decent filesystems, but I
>>> doubt that anything partitioned with vfat would work.
>>
>> Can't you use mlabel? Or mkfs.vfat with the -n parameter?
>> Doug.
>>
>>
>
> Yes. I have used mlabel to label my XD memory cards (all of them) as
> FUJIXDCARD, and set up fstab for them with "LABEL=FUJIXDCARD..." and it
> works fine.
>
> I also have an old Muvo MP player (64MB) I'm using as portable storage
> now, also labeled the same way (MUSICDISK), it also works fine.

Well, I'm glad I'm wrong.

- --
Ron Johnson, Jr.
Jefferson LA USA

Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGsT2xS9HxQb37XmcRArJuAJ9nTEWZpXn9yHQOgWyO1x eN6PDdUQCfScX7
qxCL4SdkQpE/Zkdj94PIjcY=
=YOKj
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org