Prev: firmware motherboard
Next: Hauppage Nova-T PCI DVB receiver card not working
From: John W. M. Stevens on 5 Feb 2006 22:50
On Sun, 2006-02-05 at 17:47 -0800, Rob Blomquist wrote:
> 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

OK, just in case: Do you actually have a device
special file /dev/sdb1?

Just askin' . . .

> 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!

Maybe because the error message from mount is correct? That
"special device /dev/sdb1 does not exist?"

John S.


--
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 23:00
On Sun, 05 Feb 2006 20:42:09 -0700
"John W. M. Stevens" <john(a)betelgeuse.us> wrote:

> On Sun, 2006-02-05 at 17:47 -0800, Rob Blomquist wrote:
> > 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
>
> OK, just in case: Do you actually have a device
> special file /dev/sdb1?
>
> Just askin' . . .
>
> > 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!
>
> Maybe because the error message from mount is correct? That
> "special device /dev/sdb1 does not exist?"

do you have udev rules to create the device?

A
>
> John S.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian..org
>
From: Brendan on 6 Feb 2006 00:10
On Sunday 05 February 2006 18:13, Marc Wilson wrote:
> IMHO automount is an incredibly broken behavior. Gnome users swear that
> it's desirable, though. Your mileage may vary.

Why do you think that?


--
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 6 Feb 2006 00:20
On Sunday 05 February 2006 7:50 pm, Andrew Sackville-West so eloquently
stated:
On Sun, 05 Feb 2006 20:42:09 -0700


> > 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
>
> OK, just in case: Do you actually have a device
> special file /dev/sdb1?
>
> Just askin' . . .
>
> > 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!
>
> Maybe because the error message from mount is correct? That
> "special device /dev/sdb1 does not exist?"

>do you have udev rules to create the device?

Good question.

This is what is in my udev.rules:

# USB devices
BUS="usb", KERNEL="hiddev*", NAME="usb/%k"
BUS="usb", KERNEL="auer[0-9]*", NAME="usb/%k"
BUS="usb", KERNEL="legousbtower*", NAME="usb/%k"
BUS="usb", KERNEL="dabusb*", NAME="usb/%k"
BUS="usb", KERNEL="cpad[0-9]*", NAME="usb/%k"
BUS="usb", KERNEL="lp[0-9]*", NAME="usb/%k"
BUS="usb", KERNEL="ttyUSB*", SYSFS{product}="Palm Handheld*", SYMLINK="pilot"

Now, I am not sure which of these would be used for a flash drive, but I can
tell that a few won't be....

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 Shapiro on 6 Feb 2006 00:40
Brendan wrote:
> On Sunday 05 February 2006 18:13, Marc Wilson wrote:
>
>>IMHO automount is an incredibly broken behavior. Gnome users swear that
>>it's desirable, though. Your mileage may vary.
>
>
> Why do you think that?

I have a system with a fresh Debian install with KDE. It wants to
automount things. I'm hoping I can correct this behaviour. Here are
the problems that I am having:

Data CDs will automount, but sometimes take so long to do so that I
click on the icon again. I then end up with about a dozen konqueror
windows open on the CD's directory. Then, the CD WILL NOT unmount. If
I try to manually unmount it I get an error saying only root can do
that. OK, I su to root and try again. Then it insists that the CD is
busy. There is nothing using the CD and I HAVE NOT cd'd to /cdrom. The
only way to unmount and eject the CD is to 'killall kdeinit'.

I can read floppies, OK, but kfloppy does not appear to want to format a
floppy. It just sits there, locked up, for a minute, or more, saying
that 0% is done. Then it just ungrays itself, but does nothing. I
formatted a floppy manually weith the default msdos fs and KDE would not
mount it. I reformatted with ext2 and KDE mounted it with no problems.

Is it possible to tell KDE NOT to automount anything? I am quite happy
with commandline mount and umount commands. They just work and I know
the state of my filesystems. I use fvwm on my own box, but this one
will be for my 5 year old daughter, and since it came with KDE, I
thought that it would be easier for her if I just left it that way and
put icons on the desktop for those programs that I want her to have easy
access to. There will be no need for removable devices on a regular
basis, and if there is I can mount it myself, as needed.

--
Marc Shapiro



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