Prev: firmware motherboard
Next: Hauppage Nova-T PCI DVB receiver card not working
From: Rob Blomquist on 5 Feb 2006 16:50
I asked this earlier, and several asked for more information about what is
going or not going on on my system. I am trying to figure out if something is
missing, or if something needs manual configuration on my system.

Here's the output from lsmod | grep usb:
usb_storage 69056 0
usbserial 29896 1 visor
usbhid 32224 0
usbcore 118980 8
usb_storage,visor,usbserial,usbhid,ehci_hcd,ohci_hcd
ide_core 139940 5
usb_storage,ide_cd,ide_generic,ide_disk,amd74xx
scsi_mod 125228 3 usb_storage,sd_mod,libata

Here's what happens when my PNY 256Mb flash drive is inserted:
Feb 5 13:16:31 localhost kernel: usb 3-5: new high speed USB device using
address 31
Feb 5 13:16:31 localhost kernel: scsi6 : SCSI emulation for USB Mass Storage
devices
Feb 5 13:16:31 localhost kernel: Vendor: PNY Model: USB 2.0 FD
Rev: 1.13
Feb 5 13:16:31 localhost kernel: Type: Direct-Access
ANSI SCSI revision: 02
Feb 5 13:16:31 localhost kernel: SCSI device sdb: 487424 512-byte hdwr
sectors(250 MB)
Feb 5 13:16:31 localhost kernel: sdb: assuming Write Enabled
Feb 5 13:16:31 localhost kernel: /dev/scsi/host6/bus0/target0/lun0: p1
Feb 5 13:16:31 localhost kernel: Attached scsi removable disk sdb at scsi6,
channel 0, id 0, lun 0

And that's where it ends. I would think that something should now pick it up
and automount it. Let me try to mount it:
# mount -t vfat /dev/sdb /media/flash
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

# dmesg | tail
usb 3-5: new high speed USB device using address 31
scsi6 : SCSI emulation for USB Mass Storage devices
Vendor: PNY Model: USB 2.0 FD Rev: 1.13
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 487424 512-byte hdwr sectors (250 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
/dev/scsi/host6/bus0/target0/lun0: p1
Attached scsi removable disk sdb at scsi6, channel 0, id 0, lun 0
USB Mass Storage device found at 31

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

# dmesg | tail
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 487424 512-byte hdwr sectors (250 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
/dev/scsi/host6/bus0/target0/lun0: p1
Attached scsi removable disk sdb at scsi6, channel 0, id 0, lun 0
USB Mass Storage device found at 31
NTFS-fs error (device sdb): read_ntfs_boot_sector(): Primary boot sector is
invalid.
NTFS-fs error (device sdb): read_ntfs_boot_sector(): Mount option
errors=recover not used. Aborting without trying to recover.
NTFS-fs error (device sdb): ntfs_fill_super(): Not an NTFS volume.

Now, just for yucks I added the following line to /etc/fstab:
/dev/sdb /media/flash auto rw,user,noauto 0 0

#mount /dev/sdb
mount: you must specify the filesystem type

Here's lsmod again just to compare:
# lsmod| grep usb
usb_storage 69056 0
usbserial 29896 1 visor
usbhid 32224 0
usbcore 118980 8
usb_storage,visor,usbserial,usbhid,ehci_hcd,ohci_hcd
ide_core 139940 5
usb_storage,ide_cd,ide_generic,ide_disk,amd74xx
scsi_mod 125228 3 usb_storage,sd_mod,libata


Ok from all this, I wonder if the drive is corrupt. It is connected. Why can't
I manually mount it? I don't know. Why doesn't something try to automount it
for me?

Beyond this, I know not what to do other than to try it on another computer.
Your suggestions would be appreciated.

Rob



--
Mountlake Terrace, WA, USA


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Andrew Sackville-West on 5 Feb 2006 17:00
On Sun, 5 Feb 2006 13:30:01 -0800
Rob Blomquist <rob.blomquist(a)verizon.net> wrote:

> I asked this earlier, and several asked for more information about what is
> going or not going on on my system. I am trying to figure out if something is
> missing, or if something needs manual configuration on my system.
>
> Here's the output from lsmod | grep usb:
> usb_storage 69056 0
> usbserial 29896 1 visor
> usbhid 32224 0
> usbcore 118980 8
> usb_storage,visor,usbserial,usbhid,ehci_hcd,ohci_hcd
> ide_core 139940 5
> usb_storage,ide_cd,ide_generic,ide_disk,amd74xx
> scsi_mod 125228 3 usb_storage,sd_mod,libata
>
> Here's what happens when my PNY 256Mb flash drive is inserted:
> Feb 5 13:16:31 localhost kernel: usb 3-5: new high speed USB device using
> address 31
> Feb 5 13:16:31 localhost kernel: scsi6 : SCSI emulation for USB Mass Storage
> devices
> Feb 5 13:16:31 localhost kernel: Vendor: PNY Model: USB 2.0 FD
> Rev: 1.13
> Feb 5 13:16:31 localhost kernel: Type: Direct-Access
> ANSI SCSI revision: 02
> Feb 5 13:16:31 localhost kernel: SCSI device sdb: 487424 512-byte hdwr
> sectors(250 MB)
> Feb 5 13:16:31 localhost kernel: sdb: assuming Write Enabled
> Feb 5 13:16:31 localhost kernel: /dev/scsi/host6/bus0/target0/lun0: p1
> Feb 5 13:16:31 localhost kernel: Attached scsi removable disk sdb at scsi6,
> channel 0, id 0, lun 0
>
> And that's where it ends. I would think that something should now pick it up
> and automount it. Let me try to mount it:
> # mount -t vfat /dev/sdb /media/flash
> mount: wrong fs type, bad option, bad superblock on /dev/sdb,
> missing codepage or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
> # dmesg | tail
> usb 3-5: new high speed USB device using address 31
> scsi6 : SCSI emulation for USB Mass Storage devices
> Vendor: PNY Model: USB 2.0 FD Rev: 1.13
> Type: Direct-Access ANSI SCSI revision: 02
> SCSI device sdb: 487424 512-byte hdwr sectors (250 MB)
> sdb: assuming Write Enabled
> sdb: assuming drive cache: write through
> /dev/scsi/host6/bus0/target0/lun0: p1
> Attached scsi removable disk sdb at scsi6, channel 0, id 0, lun 0
> USB Mass Storage device found at 31
>
> # mount -t ntfs /dev/sdb /media/flash
> mount: wrong fs type, bad option, bad superblock on /dev/sdb,
> missing codepage or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
> # dmesg | tail
> Type: Direct-Access ANSI SCSI revision: 02
> SCSI device sdb: 487424 512-byte hdwr sectors (250 MB)
> sdb: assuming Write Enabled
> sdb: assuming drive cache: write through
> /dev/scsi/host6/bus0/target0/lun0: p1
> Attached scsi removable disk sdb at scsi6, channel 0, id 0, lun 0
> USB Mass Storage device found at 31
> NTFS-fs error (device sdb): read_ntfs_boot_sector(): Primary boot sector is
> invalid.
> NTFS-fs error (device sdb): read_ntfs_boot_sector(): Mount option
> errors=recover not used. Aborting without trying to recover.
> NTFS-fs error (device sdb): ntfs_fill_super(): Not an NTFS volume.
>
> Now, just for yucks I added the following line to /etc/fstab:
> /dev/sdb /media/flash auto rw,user,noauto 0 0
>
> #mount /dev/sdb
> mount: you must specify the filesystem type
>
> Here's lsmod again just to compare:
> # lsmod| grep usb
> usb_storage 69056 0
> usbserial 29896 1 visor
> usbhid 32224 0
> usbcore 118980 8
> usb_storage,visor,usbserial,usbhid,ehci_hcd,ohci_hcd
> ide_core 139940 5
> usb_storage,ide_cd,ide_generic,ide_disk,amd74xx
> scsi_mod 125228 3 usb_storage,sd_mod,libata
>
>

Ummm... is it formatted?

> Ok from all this, I wonder if the drive is corrupt. It is connected. Why can't
> I manually mount it?

maybe its not formatted?

I don't know. Why doesn't something try to automount it
> for me?

because nothing is configured to automount it for you?

>
> Beyond this, I know not what to do other than to try it on another computer.
> Your suggestions would be appreciated.

well trying another machine would certainly provide so insight as to whether the problem is realted to the media or the machine.

A

>
> Rob
>
>
>
> --
> Mountlake Terrace, WA, USA
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian..org
>
From: Marc Wilson on 5 Feb 2006 18:20
On Sun, Feb 05, 2006 at 01:30:01PM -0800, Rob Blomquist wrote:

<much silliness deleted>

> Ok from all this, I wonder if the drive is corrupt. It is connected. Why can't
> I manually mount it?

Because you're trying to mount the block device, rather than a partition on
it. Example:

rei $ sudo fdisk -l /dev/sdf

Disk /dev/sdf: 519 MB, 519569408 bytes
129 heads, 32 sectors/track, 245 cylinders
Units = cylinders of 4128 * 512 = 2113536 bytes

Device Boot Start End Blocks Id System
/dev/sdf1 1 246 507376 4 FAT16 <32M
Partition 1 has different physical/logical endings:
phys=(249, 128, 32) logical=(245, 106, 32)

rei $ mount | grep sdf
/dev/sdf1 on /mnt/usbstick type vfat (rw,noexec,nosuid,nodev,user=mwilson)


> Why doesn't something try to automount it for me?

What would this "something" be? Have you installed something that would do
that for you? Are you using a recent Gnome or KDE that would do that by
default? No, I don't know in what version Gnome started doing that... I
don't use Gnome. Nor KDE, for that matter.

IMHO automount is an incredibly broken behavior. Gnome users swear that
it's desirable, though. Your mileage may vary.

--
Marc Wilson | Show your affection, which will probably meet with
msw(a)cox.net | pleasant response.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Andrew Sackville-West on 5 Feb 2006 20:00
On Sun, 5 Feb 2006 15:13:46 -0800
Marc Wilson <msw(a)cox.net> wrote:

> On Sun, Feb 05, 2006 at 01:30:01PM -0800, Rob Blomquist wrote:
>
> <much silliness deleted>
>
> > Ok from all this, I wonder if the drive is corrupt. It is connected. Why can't
> > I manually mount it?
>
> Because you're trying to mount the block device, rather than a partition on
> it. Example:
>
> rei $ sudo fdisk -l /dev/sdf
>
> Disk /dev/sdf: 519 MB, 519569408 bytes
> 129 heads, 32 sectors/track, 245 cylinders
> Units = cylinders of 4128 * 512 = 2113536 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdf1 1 246 507376 4 FAT16 <32M
> Partition 1 has different physical/logical endings:
> phys=(249, 128, 32) logical=(245, 106, 32)
>
> rei $ mount | grep sdf
> /dev/sdf1 on /mnt/usbstick type vfat (rw,noexec,nosuid,nodev,user=mwilson)
>
>
> > Why doesn't something try to automount it for me?
>
> What would this "something" be? Have you installed something that would do
> that for you? Are you using a recent Gnome or KDE that would do that by
> default? No, I don't know in what version Gnome started doing that... I
> don't use Gnome. Nor KDE, for that matter.
>
> IMHO automount is an incredibly broken behavior. Gnome users swear that
> it's desirable, though. Your mileage may vary.

d'oh!

A

>
> --
> Marc Wilson | Show your affection, which will probably meet with
> msw(a)cox.net | pleasant response.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian..org
>
From: Rob Blomquist on 5 Feb 2006 21:10
On Sunday 05 February 2006 3:13 pm, Marc Wilson so eloquently stated:
> On Sun, Feb 05, 2006 at 01:30:01PM -0800, Rob Blomquist wrote:
>
> <much silliness deleted>
>
> > Ok from all this, I wonder if the drive is corrupt. It is connected. Why
> > can't I manually mount it?
>
> Because you're trying to mount the block device, rather than a partition on
> it. Example:
>
> rei $ sudo fdisk -l /dev/sdf
>
> Disk /dev/sdf: 519 MB, 519569408 bytes
> 129 heads, 32 sectors/track, 245 cylinders
> Units = cylinders of 4128 * 512 = 2113536 bytes

OK, I know what you mean about mounting the block device, I tried sdb0, 1, and
2, but got no response before I emailed.

timmy:~# dmesg | tail
usb 3-5: new high speed USB device using address 32
scsi7 : SCSI emulation for USB Mass Storage devices
Vendor: PNY Model: USB 2.0 FD Rev: 1.13
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 487424 512-byte hdwr sectors (250 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
/dev/scsi/host7/bus0/target0/lun0: p1
Attached scsi removable disk sdb at scsi7, channel 0, id 0, lun 0
USB Mass Storage device found at 32

So it is still there, and let me find out what it responds to:

timmy:~# fdisk -l /dev/sdb

Disk /dev/sdb: 249 MB, 249561088 bytes
16 heads, 32 sectors/track, 952 cylinders
Units = cylinders of 512 * 512 = 262144 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 952 243696 6 FAT16

Ah, so it is vfat on sdb1! no sweat!

timmy:~# mount -t vfat /dev/sdb1 /media/flash
mount: special device /dev/sdb1 does not exist

Now this is silly!

Is it still there?

timmy:~# fdisk -l /dev/sdb

Disk /dev/sdb: 249 MB, 249561088 bytes
16 heads, 32 sectors/track, 952 cylinders
Units = cylinders of 512 * 512 = 262144 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 952 243696 6 FAT16

I will be darned. Still there, but mount can't find it!



> Device Boot Start End Blocks Id System
> /dev/sdf1 1 246 507376 4 FAT16 <32M
> Partition 1 has different physical/logical endings:
> phys=(249, 128, 32) logical=(245, 106, 32)
>
> rei $ mount | grep sdf
> /dev/sdf1 on /mnt/usbstick type vfat (rw,noexec,nosuid,nodev,user=mwilson)
>
> > Why doesn't something try to automount it for me?
>
> What would this "something" be? Have you installed something that would do
> that for you? Are you using a recent Gnome or KDE that would do that by
> default? No, I don't know in what version Gnome started doing that... I
> don't use Gnome. Nor KDE, for that matter.

Yes, that something is automount. Under Mandriva and Ubuntu, it seems to be
working quite well, especially for flash drives. I find it more of a pain to
deal with for USB drives, to find out what block device it is then mount it
if it could have a static device for each usb drive, well that would be one
thing, and I would be fine mounting and unmounting them like CDROMs.

I have been quite confused with the changes to USB that the 2.6 kernel gives.

Is automount available for Debian?

Rob
--
Mountlake Terrace, WA, USA


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
 |  Next  |  Last
Pages: 1 2 3 4
Prev: firmware motherboard
Next: Hauppage Nova-T PCI DVB receiver card not working