Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
well followed the HOWTO on this site and it worked perfectly for my laptop, but not for my gaming box.
both are running the 2.6.x kernels.
here is my dmesg about the usb stick:
Code:
usb 1-2: new high speed USB device using ehci_hcd and address 3
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
Vendor: Model: USB Flash Memory Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdc: 2002944 512-byte hdwr sectors (1026 MB)
sdc: assuming Write Enabled
sdc: assuming drive cache: write through
SCSI device sdc: 2002944 512-byte hdwr sectors (1026 MB)
sdc: assuming Write Enabled
sdc: assuming drive cache: write through
/dev/scsi/host2/bus0/target0/lun0: p1
Attached scsi removable disk sdc at scsi2, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi2, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
so it is detected, and if i read this correctly it is placed on sdc(i am guessing 0) so i made a line in my fstab look like the following:
Code:
/dev/sdc1 /mnt/camera auto defaults,user,noauto 0 0
/dev/sdc2 /mnt/USBdrive auto user,rw,auto 0 0
had to put it on 2 as i already have my USB camera on 1. is this right or wrong? i have tried noauto in the user,rw,auto and still get the same 2 errors:
as user i get the following:
Code:
$ mount /mnt/USBdrive/
mount: I could not determine the filesystem type, and none was specified
ray@p4ssmahome:~$ mount -t vfat /mnt/USBdrive/
mount: only root can do that
so as root i try to mount it and get the following:
Code:
$ su -
Password:
p4ssmahome:~# mount /mnt/USBdrive/
mount: you must specify the filesystem type
p4ssmahome:~# mount -t vfat /mnt/USBdrive/
Usage: mount -V : print version
mount -h : print this help
mount : list mounted filesystems
mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
mount -a [-t|-O] ... : mount all stuff from /etc/fstab
mount device : mount device at the known place
mount directory : mount known device here
mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
mount --bind olddir newdir
or move a subtree:
mount --move olddir newdir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
Well, if you were able to mount ok using vfat as root then replace "auto" with "vfat" in your fstab then user should be able to mount without fs type error...
ok that works, can you explain why when the fstab on both the laptop and game box (basically the same except the sdx part) i do not need a file type on the laptop, but do on the game box?
Good question... If they both have the same distro then its probably a kernel issue with the file system detection... Beyond guessing, I would have to reasearch a little more on that...
ray@p4ssmahome:~$ mount -t vfat /dev/sdc2 /mnt/USBdrive/
mount: only root can do that
ray@p4ssmahome:~$ su -
Password:
p4ssmahome:~# mount -t vfat /dev/sdc2 /mnt/USBdrive/
mount: /dev/sdc2 is not a valid block device
p4ssmahome:~#
Yep. You were defeated by a misunderstanding of the naming convention
sdc means the third SCSI disc detected by the system. sdc1 is the first partition on the disk, sdc2 the second partition on the same disk.
So if you plug in your camera, it'll be sdc, and its first partition sdc1
If you then plug in your flash disk, it'll be sdd with the first partition sdd1, as sdc already exists
But if you unplug your camera and THEN plug in the flash disc, it will then be sdc
It's a logical enough system, but it can be annoying if you always want a piece of hardware to have the same name, rather than it depending on what order you plug things in.
You can set up udev so that hardware will always have the same /dev address no matter when you plug it in, should you feel the need.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.