Strange: Can't mount a certain FAT32 partition

[Redwolf]

Okay, before I start I might want to show you the current hard drive structure I have:

/dev/hda <-Linux Hard Drive
->/dev/hda1 <-/boot
->/dev/hda2 <-swap
->/dev/hda3 <-root

/dev/hde <-Windows Hard Drive
->/dev/hde1

/dev/hdf <-80G Misc hard drive
->/dev/hdf1 <-Stuff 1
->/dev/hdf2 <-Extended partition
-->/dev/hdf5 <-Stuff2

Okay, with that knowledge, here is the problem. I cannot mount /dev/hdf5. I can mount /dev/hdf1 and /dev/hde1. Here's the really wierd thing.

I can run fsck.vfat on /dev/hdf5. With no problems.

But when I try to mount, I get this pretty little message:

redwolf@wolf redwolf $ mount /fat-stuff2
mount: wrong fs type, bad option, bad superblock on /dev/hdf5,
       or too many mounted file systems
redwolf@wolf redwolf $

Wonderful, isn't it. Lets eliminate some options.

It's not the wrong fs type. As I mentioned, fsck.vfat runs file on it. All partitions on /dev/hdf are FAT32.

It's not too many mounted filesystems either. Right after I get this message I can mount /dev/hdf1 no problems.

It's definately not a bad superblock. I ran fsck.vfat on full surface scan overnight. No problems detected other than improper free space reported, which still didn't help after fixing that. I can open the drive just fine in Windows too.

So it has to be a bad option somewhere. Hmm...maybe being a logical partition is throwing it off somehow. I've never had a logical partition fail to mount though. Here is my fstab, just in case:

# <fs>          	<mountpoint>    <type>  	<opts>      		<dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1		/boot		ext2		noauto,noatime		1 1
/dev/hda3		/		xfs		noatime			0 0
/dev/hda2		none		swap		sw			0 0
/dev/cdroms/cdrom0	/mnt/cdrom	iso9660		noauto,ro		0 0
/dev/fd0		/mnt/floppy	auto		noauto			0 0
/dev/hde1 		/fat-windwos    vfat		noauto,rw		0 0
/dev/hdf1		/fat-stuff1	vfat		noauto,rw,user,gid=800		0 0
/dev/hdf5		/fat-stuff2     vfat		noauto,rw,user,gid=800		0 0

# NOTE: The next line is critical for boot!
none			/proc		proc		defaults		0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink). 
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:

none			/dev/shm	tmpfs		defaults		0 0

I'm stumped. I'm running Gentoo (switched back cuz I love it ) installed from stage 1. Just in case, options are -02, -march=athlon-xp and -pipe in make.conf.

Can somebody help me? Please

[lynchmob]

Af the end of the hdf5 line, did you type a carriage return?
You'll get that message if not...I think.
lynch

[Redwolf]

Yep. There is a carriage return at the end of that line.

[krohnjw]

What does mtab show?

[Redwolf]

/dev/hda3 / xfs rw,noatime 0 0
/dev/hda3 / ext3 rw,noatime 0 0
none /proc proc rw 0 0
none /sys sysfs rw 0 0
none /dev devfs rw 0 0
none /dev/pts devpts rw 0 0
none /dev/shm tmpfs rw 0 0
none /proc/bus/usb usbfs rw 0 0
/dev/hdf1 /fat-stuff1 vfat rw,noexec,nosuid,nodev,gid=800,user=redwolf 0 0

Hmmm...the mtab looks a little, screwy....

[Redwolf]

-bump-

[krohnjw]

What filesystem is /dev/hda3?

[Redwolf]

All the drives on HDA are ext3 except for the swap (of course).

[nukes]

/dev/hda3		/		xfs		noatime			0 0

That could be a problem if its ext3.
Is there a reason for using an extended partition for /dev/hdf5?
I've had this problem before, but the filesystem was corrupted. What version of baselayout are you using?

[Redwolf]

I'm using extended partitions because I partitioned the drive with Windows FDISK, which forces you to create an extended partition for more than one partition. I don't know about baselayout yet, but I'll be checking it out in a few.

okay, I'm using baselayout 1.8.6.13, the latest on the portage tree (until I resynce probably ).