Red Hat 9 Mounting

[Gir]

Ok i have had this problem befor but i can't remember what i did. i am trying to mount a 200Gb maxtor drive. It is to be used for file serving and was origionally installed on a win98 computer. You may recall me asking a question about that crashing all the time. well i got it to install RH9. Any way in fstab i have
/dev/hdb1 /mnt/share1 vfat defaults 0 0
/dev/hdb3 /mnt/share2 vfat defaults 0 0
but when i try and mount it i get this error mount: wrong fs type, bad option, bad superblock on /dev/hdb1,
or too many mounted file systems any ideas why? Or how to fix it.

[zENGER]

I'd suggest going into fdisk and listing the partions on the drive and see what FS type it shows are on the drives. What are they currently supposed to be? This isn't the drive you booted off of I venture to guess or did you install RH9 into a FAT partition? Give us some details about how your system is currently setup, i.e. # of drives, types, how they're configured, which one you boot from, and the FSs on those drives.

[Gir]

Its a dual boot booting off hda3 formatted ext3 hda1 formatted fat32 on their own hard drive. the maxtor is for storage its fat32.


This is the fdisk output:
Disk /dev/hda: 13.7 GB, 13707096064 bytes
255 heads, 63 sectors/track, 1666 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 836 6715138+ b Win95 FAT32
/dev/hda2 837 1615 6257317+ 83 Linux
/dev/hda3 1616 1666 409657+ 82 Linux swap

Disk /dev/hdb: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 * 1 12549 100799811 c Win95 FAT32 (LBA)
/dev/hdb2 12550 24792 98341897+ f Win95 Ext'd (LBA)
/dev/hdb5 12550 24792 98341866 b Win95 FAT32

After modifying the fstab file hdb5 mounts but hdb1 still won't.

[zencoder]

I'd say give us the output from df -H as well as the entire /etc/fstab file. That too many mounted file systems statement sounds like something I recall seeing in HP-UX back in the day (PH-UX as we unaffectionately called it). It could also mean that another pointer is mounted to that partition, although I'd think you would get a message more descriptive indicating if that was the case.