Message-ID: <4DED42CF.9000008 at verizon.net>

[Nils Kassube]

Douglas Pollard wrote:
> (LBA) douglasdoug at ubuntuDoug:~$ sudo rm -rf /media/sde1

Be careful with that last command. If you have mounted a partition 
there, you would probably remove the entire contents of that partition.

> douglasdoug at ubuntuDoug:~$ sudo fdisk -l

> Disk /dev/sdc: 2000.4 GB, 2000398932992 bytes

>     Device Boot      Start         End      Blocks   Id  System
> /dev/sdc1   *           1      243201  1953512001    c  W95 FAT32
> (LBA) douglasdoug at ubuntuDoug:~$ sudo mkdir /media/sdc1
> mkdir: cannot create directory `/media/sdc1': File exists
> douglasdoug at ubuntuDoug:~$ sudo mount -t vfat /dev/sdc1 /media/sdc1
> mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
>         missing codepage or helper program, or other error
>         In some cases useful info is found in syslog - try
>         dmesg | tail  or so

There seems to be a problem with that 2TB partition. I think you should 
try a file system check with the command

sudo fsck.vfat -a -l -v /dev/sdc1

like Jordon suggested some days ago.

> douglasdoug at ubuntuDoug:~$ sudo dmesg | tail or so

That should have been

dmesg | tail

instead (without the "or so" at the end).

>    OK should dev,sdc1 input be input sudo mount -t vfat/dev.sdc1
> /boot/ sdc1  that partition is a boot partition rather than media
> according to disk utility           Doug

It doesn't matter if the boot flag is set. You can use the partition for 
any kind of data. The mount command was OK like you used it but it 
failed because of some problem with that partition, not because of the 
boot flag.


Nils