Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
Mounting a USB Mass Storage DeviceOn Sat, 2007-12-01 at 16:26 +0100, Samuel Bächler wrote: Hi Sam, what other stuff do you expect to see? Is the listing given actually on the stick or do you know it is not? With the stick unmounted what does ls /mnt/usb give you? More information is needed. Regards, Bob -- -- Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
Mounting a USB Mass Storage Device
Samuel Bächler wrote:
>> Is the vfat module loaded? You might want to check the filesystem
>> type with "file -s /dev/sdb1". Also are you able to access the files
>> on any other system? If the data on the usb drive is not important,
>> then try formatting it. "mkdosfs /dev/sdb1" will create a fat16
>> filesystem while mke2fs will create an ext2 partition.
>
> Thanks a lot! I learned quite a lot this weekend, :-).
>
> Summary of mistakes:
> (1) I wanted to mount a wrong device (sda1 instead of sdb1).
So it was a Windows partition you were seeing. Sorry about the error, but I
still advise deleting and reformatting it.
> (2) Did not have the vfat module and the usb_storage module loaded.
>
> Cheers
>
> Sam
>
>
--
Mounting a USB Mass Storage Device
Hi Everyone
Does anyone know what is going wrong on my system or
what I am doing wrong or else?
To mount a memory stick I do:
# mount -t auto /dev/sda1 /mnt/usb
...
# ls /mnt/usb
boot
bootmgr
MFGSTAT
preboot
recovery
SCRREC.VER
swwork
System Volume Information
tvtos
windows
So, I can't see what's on the stick but some other stuff.
Thank's for your inputs.
Sam
--
Mounting a USB Mass Storage Device
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/01/07 09:26, Samuel Bächler wrote:
> Hi Everyone
>
> Does anyone know what is going wrong on my system or
> what I am doing wrong or else?
>
> To mount a memory stick I do:
>
> # mount -t auto /dev/sda1 /mnt/usb
> ...
> # ls /mnt/usb
> boot
> bootmgr
> MFGSTAT
> preboot
> recovery
> SCRREC.VER
> swwork
> System Volume Information
> tvtos
> windows
>
> So, I can't see what's on the stick but some other stuff.
>
>
> Thank's for your inputs.
Is kernel module usb_storage loaded (or built into the kernel)?
What version of Debian are you running?
The real console, or a GUI?
What happens to syslog when you insert the memory stick?
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHUY3qS9HxQb37XmcRApeLAJ4ktUkau0JtRPjhum9TOnIgVM89OACcD1z2
kiJ5l7wxCjDX1N4odINsHYI=
=1wbJ
-----END PGP SIGNATURE-----
--
Mounting a USB Mass Storage Device
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/01/07 19:49, Raj Kiran Grandhi wrote:
> Ron Johnson wrote:
>
>> Since the "drive letter" of removable devices is subject to change,
>> I now use UUID values in /etc/fstab instead of /dev/sd??. (Except
>> for /boot and /.)
>>
>> # blkid /dev/sdXY
>> # vi /etc/fstab (Replace /dev/sdXY with UUID="")
>>
>> Also, if you have hal installed, GNOME & KDE should automagically
>> handle removable devices for you.
>
> UUIDs are helpful if you have a known set of devices you wish to use.
Like devices that you want to be seen at boot up, or when you are
not logged in.
> I
> just let gnome handle the mounting (I think it uses hal to do it) and
> unmount it with pumount. Once I have disabled nautilus from opening a
> window whenever a removable device is mounted, the process becomes
> terminal friendly. Plugin, cd, do_stuff, pumount, without ever having to
> reach out for the mouse.
GNOME+hal is definitely a valid tool for "user oriented", dynamic
devices like thumb drives.
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHUhgeS9HxQb37XmcRAhCeAJ9JolLELl+fUe/DjrpGhExwJ+bPLQCfZEbJ
XK/dWvb4Sqh+eoRnn9WUywU=
=eed8
-----END PGP SIGNATURE-----
--
Mounting a USB Mass Storage Device
On Sun, 02 Dec 2007 12:35:04 +0100
Samuel Bächler wrote:
> Thanks for your many inputs so far!
>
> > Are you sure /dev/sda1 is your usb stick and not your primary hard
> > disk? Do a tail -f /var/log/syslog and then plugin your memory
> > stick. That will give you some info as to what the actual device
> > is.
>
> Your are right, Raj, sda* is my harddisk. Shame on me...
>
> > Is kernel module usb_storage loaded (or built into the kernel)?
> > What version of Debian are you running? The real console, or a GUI?
> > What happens to syslog when you insert the memory stick?
>
> Thanks, Ron, I did not 'modprobe usb_storage'. I am using etch and
> work on the console.
>
> Hitherto I learned a lot. But it still does not work. On the 'Konsole
> Terminal
> Programm' of KDE I did the folling things:
>
> # tail -f /var/log/syslog
> Then I inserted the stick...
> Dec 2 12:28:29 ataraxia kernel: usb 2-2: new full speed USB device
> using uhci_hcd and address 7
> Dec 2 12:28:30 ataraxia kernel: usb 2-2: configuration #1 chosen
> from 1 choice
> Dec 2 12:28:30 ataraxia kernel: scsi5 : SCSI emulation for USB Mass
> Storage devices
> Dec 2 12:28:30 ataraxia kernel: usb-storage: device found at 7
> Dec 2 12:28:30 ataraxia kernel: usb-storage: waiting for device to
> settle before scanning
> Dec 2 12:28:35 ataraxia kernel: Vendor: USB 2.0 Model: Flash
> Disk Rev: 2.00
> Dec 2 12:28:35 ataraxia kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> Dec 2 12:28:35 ataraxia kernel: SCSI device sdb: 249120 512-byte
> hdwr sectors (128 MB)
> Dec 2 12:28:35 ataraxia kernel: sdb: Write Protect is off
> Dec 2 12:28:35 ataraxia kernel: sdb: Mode Sense: 0b 00 00 08
> Dec 2 12:28:35 ataraxia kernel: sdb: assuming drive cache: write
> through Dec 2 12:28:35 ataraxia kernel: SCSI device sdb: 249120
> 512-byte hdwr sectors (128 MB)
> Dec 2 12:28:35 ataraxia kernel: sdb: Write Protect is off
> Dec 2 12:28:35 ataraxia kernel: sdb: Mode Sense: 0b 00 00 08
> Dec 2 12:28:35 ataraxia kernel: sdb: assuming drive cache: write
> through Dec 2 12:28:35 ataraxia kernel: sdb: sdb1
> Dec 2 12:28:35 ataraxia kernel: sd 5:0:0:0: Attached scsi removable
> disk sdb
> Dec 2 12:28:35 ataraxia kernel: usb-storage: device scan complete
>
> # mount /dev/sdb1 /mnt/usb
> mount: you must specify the filesystem type
>
> I tried also 'mount -t [ vfat | usbfs | ntfs ] /dev/sdb1 /mnt/usb'
> but only with poor results.
>
> S.
>
You may try -t auto, or, even better, check it with disktype! USB
storage devices are usually formatted to FAT16.
--
Szia:
Nyizsa.
----------------------------------------------------------------------
Get a free email address with REAL anti-spam protection.
http://www.bluebottle.com/tag/1
Mounting a USB Mass Storage Device
Thanks for your many inputs so far!
> Are you sure /dev/sda1 is your usb stick and not your primary hard
> disk? Do a tail -f /var/log/syslog and then plugin your memory
> stick. That will give you some info as to what the actual device is.
Your are right, Raj, sda* is my harddisk. Shame on me...
> Is kernel module usb_storage loaded (or built into the kernel)? What
> version of Debian are you running? The real console, or a GUI? What
> happens to syslog when you insert the memory stick?
Thanks, Ron, I did not 'modprobe usb_storage'. I am using etch and work
on the console.
Hitherto I learned a lot. But it still does not work. On the 'Konsole
Terminal
Programm' of KDE I did the folling things:
# tail -f /var/log/syslog
Then I inserted the stick...
Dec 2 12:28:29 ataraxia kernel: usb 2-2: new full speed USB device
using uhci_hcd and address 7
Dec 2 12:28:30 ataraxia kernel: usb 2-2: configuration #1 chosen from 1
choice
Dec 2 12:28:30 ataraxia kernel: scsi5 : SCSI emulation for USB Mass
Storage devices
Dec 2 12:28:30 ataraxia kernel: usb-storage: device found at 7
Dec 2 12:28:30 ataraxia kernel: usb-storage: waiting for device to
settle before scanning
Dec 2 12:28:35 ataraxia kernel: Vendor: USB 2.0 Model: Flash
Disk Rev: 2.00
Dec 2 12:28:35 ataraxia kernel: Type:
Direct-Access ANSI SCSI revision: 02
Dec 2 12:28:35 ataraxia kernel: SCSI device sdb: 249120 512-byte hdwr
sectors (128 MB)
Dec 2 12:28:35 ataraxia kernel: sdb: Write Protect is off
Dec 2 12:28:35 ataraxia kernel: sdb: Mode Sense: 0b 00 00 08
Dec 2 12:28:35 ataraxia kernel: sdb: assuming drive cache: write through
Dec 2 12:28:35 ataraxia kernel: SCSI device sdb: 249120 512-byte hdwr
sectors (128 MB)
Dec 2 12:28:35 ataraxia kernel: sdb: Write Protect is off
Dec 2 12:28:35 ataraxia kernel: sdb: Mode Sense: 0b 00 00 08
Dec 2 12:28:35 ataraxia kernel: sdb: assuming drive cache: write through
Dec 2 12:28:35 ataraxia kernel: sdb: sdb1
Dec 2 12:28:35 ataraxia kernel: sd 5:0:0:0: Attached scsi removable
disk sdb
Dec 2 12:28:35 ataraxia kernel: usb-storage: device scan complete
# mount /dev/sdb1 /mnt/usb
mount: you must specify the filesystem type
I tried also 'mount -t [ vfat | usbfs | ntfs ] /dev/sdb1 /mnt/usb' but
only with poor results.
S.
--
Mounting a USB Mass Storage Device
Samuel Bächler wrote:
> Hi Everyone
>
> Does anyone know what is going wrong on my system or
> what I am doing wrong or else?
>
> To mount a memory stick I do:
>
> # mount -t auto /dev/sda1 /mnt/usb
> ...
> # ls /mnt/usb
> boot
> bootmgr
> MFGSTAT
> preboot
> recovery
> SCRREC.VER
> swwork
> System Volume Information
> tvtos
> windows
>
> So, I can't see what's on the stick but some other stuff.
Typical contents of a new USB flash drive. Just delete it or reformat.
>
>
> Thank's for your inputs.
>
> Sam
>
>
--
Mounting a USB Mass Storage Device
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/01/07 10:53, Raj Kiran Grandhi wrote:
> Samuel Bächler wrote:
>> Hi Everyone
>>
>> Does anyone know what is going wrong on my system or
>> what I am doing wrong or else?
>>
>> To mount a memory stick I do:
>>
>> # mount -t auto /dev/sda1 /mnt/usb
>
> Are you sure /dev/sda1 is your usb stick and not your primary hard disk?
> Do a tail -f /var/log/syslog and then plugin your memory stick. That
> will give you some info as to what the actual device is.
Since the "drive letter" of removable devices is subject to change,
I now use UUID values in /etc/fstab instead of /dev/sd??. (Except
for /boot and /.)
# blkid /dev/sdXY
# vi /etc/fstab (Replace /dev/sdXY with UUID="")
Also, if you have hal installed, GNOME & KDE should automagically
handle removable devices for you.
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHUZh/S9HxQb37XmcRAtIPAJ4yZ+qF5Sgz+QoJZsEfAFSiC81cfwCgrHiF
caZisr9qPn6jv5QKrTNtXiU=
=UUBC
-----END PGP SIGNATURE-----
--
Mounting a USB Mass Storage Device
> Is the vfat module loaded? You might want to check the filesystem
> type with "file -s /dev/sdb1". Also are you able to access the files
> on any other system? If the data on the usb drive is not important,
> then try formatting it. "mkdosfs /dev/sdb1" will create a fat16
> filesystem while mke2fs will create an ext2 partition.
Thanks a lot! I learned quite a lot this weekend, :-).
Summary of mistakes:
(1) I wanted to mount a wrong device (sda1 instead of sdb1).
(2) Did not have the vfat module and the usb_storage module loaded.
Cheers
Sam
--