I got this error now:

mag1strate@linux-o6a5:~> sudo mount /dev/sdf1 /media/Elements
mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

For the record, because it seems now that you may have another problem, if you don't have a storage group I don't know how to add it in the correct manner. So my suggestion is editing the file /etc/dbus-1/system.d/hal.conf and inside (in between them) this tags
add the following,
and probably this too,
Now, because of your latest error try to mount the device respecifying it file system like this if it is FAT32
or like this if is NTFS (note that in this case you must have ntfs-3g installed)

Has an additional note the /media folder should only be controlled by HAL, manual mounts should go to /mnt. If HAL is to mount a device and the folder were it will mount it already exists, no action is taken by HAL.

I looked in my hal.conf file and all those lines were there.

and I get this problem when I put in those commands:

mag1strate@linux-o6a5:~> sudo mount -t vfat /dev/sdf1 /media/Elements
mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

mag1strate@linux-o6a5:~> sudo mount -t ntfs-3g /dev/sdf1 /media/Elements
NTFS signature is missing.
Failed to mount '/dev/sdf1': Invalid argument
The device '/dev/sdf1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?

Ok, by that output is safe to say the file system is FAT32.
I wonder if the disk was incorrectly unmounted...if this is the case I usually connect it to a windows machine and then click "Safe Removal". However I know there's a forcing option on linux, but can't find it...I suspect you can append -o force to the mount command, but not sure though.

No it still fails to mount, The cdrom isn't mounting either. I really don't know what is up with this. This is the first time I have ever run into a problem like this.

cd /media
mkdir usb
fdisk -l
mount -t vfat /dev/whatever /media/usb

Go to directory media. Make folder usb. use fdisk -l to figure out what the USB device file is (find /dev/whatever you think the USB drive is)
mount the usb drive into /media/usb.

I'm out of ideas...

Still get an error:


mag1strate@linux-o6a5:/media> sudo fdisk -|
> sudo mount -t vfat /dev/sdf1 /media/usb
sudo: fdisk: command not found
mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Try sudo /sbin/fdisk -l -- That should give you the partition type on your drive, if its fat sudo mount -t vfat /dev/sdf1 /media/usb should work. If its NTFS then its sudo mount -t ntfs.

Please give the output of sudo /sbin/fdisk -l
If sudo doesn't work, login as root to make things quicker.

When you ran this command, you used a pipe "|" instead of an "l" (a lowercase version of "L"). You don't want to pipe the data, we just want information on the disks you have plugged in

nope still getting the same error:

mag1strate@linux-o6a5:~> /sbin/fdisk -l
mag1strate@linux-o6a5:~> sudo mount -t vfat /dev/sdf1 /media/usb
mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

post the output of:

mag1strate yesterday showed his dmesg after connecting the drive...

DarkVenger:
There is nothing in his dmesg that looks suspicious. All the errors are network related, not pertinent to the usage of his usb disk.

Here you go:


mag1strate@linux-o6a5:~> which fdisk
which: no fdisk in (/home/mag1strate/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib64/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin)