Board index Linux Hardware

FAT32 mount broken in even under 2.0.35

FAT32 mount broken in even under 2.0.35

Post by Dennis R. Weiler » Sat, 25 Jul 1998 04:00:00



I installed RedHat-5.1 (kernel 2.0.34), upgraded to 2.0.35, but I still
cannot mount my FAT32 partition.  I checked to see if the patches by Mr.
Chaffee were there.  They were.  I tried

# mount -t vfat -o debug /dev/hda1 /dosc

 and got

mount: wrong fs type, bad option, bad superblock on /dev/hda1,
       or too many mounted file systems

From this the tail from /var/log/messages was

Jul 24 14:19:44 mordor kernel: [MS-DOS FS Rel. 12,FAT
32,check=n,conv=b,uid=0,gid=0,umask=022,bmap]
Jul 24 14:19:44 mordor kernel:
[me=0xf8,cs=8,#f=2,fs=32,fl=12260,ds=24552,de=0,data=24552,se=0,ts=12578832,ls=512,rc=2,fc=1254859]
Jul 24 14:19:44 mordor kernel: Transaction block size = 512
Jul 24 14:19:44 mordor kernel: VFS: Can't find a valid MSDOS filesystem
on dev 03:01.

What gives?

One should know that before installing Linux, I tried to shrink my
Winders partition using a FAT32 (beta) extension of FIPS (1.6b I
believe). Since Winders could no longer find KERNEL386.EXE, I restored
from the rescue floppy made by FIPS.  Being the cheapskate I am, I then
tried using PartitionIt from Quarterdeck.  This also failed.

Maybe one of these programs (PartitionIt) corrupted my superblock, or
MBR, or ???.

Dennis R. Weilert

 
 
 
Top

FAT32 mount broken in even under 2.0.35

Post by Steve Luzynsk » Sun, 26 Jul 1998 04:00:00



> I installed RedHat-5.1 (kernel 2.0.34), upgraded to 2.0.35, but I still
> cannot mount my FAT32 partition.  I checked to see if the patches by Mr.
> Chaffee were there.  They were.  I tried
[snip]
> One should know that before installing Linux, I tried to shrink my
> Winders partition using a FAT32 (beta) extension of FIPS (1.6b I
> believe). Since Winders could no longer find KERNEL386.EXE, I restored
> from the rescue floppy made by FIPS.  Being the cheapskate I am, I then
> tried using PartitionIt from Quarterdeck.  This also failed.

> Maybe one of these programs (PartitionIt) corrupted my superblock, or
> MBR, or ???.

Well, to rule that out, boot off your Windows boot disk that you of
course made and type 'fdisk /mbr'. This will put the original MBR back
on your drive. You will then need to boot Linux from floppy to reinstall
LILO (if that's what you're doing for multiboot.)

I'm running RedHat5.1 with the original out of the box kernel and can
mount FAT32 with no problems.

Personally when I'm in the mood to abuse my partition table, I find that
PartitionMagic is well worth the money.

 
 
 
Top

FAT32 mount broken in even under 2.0.35

Post by mohaw » Sun, 26 Jul 1998 04:00:00


If you rebuilt the kernel version 3.0.35 (It started in 2.0.34) you have to turn on codepages to get
the option of Windows (DOS) and cdrom file systems. You make simply need to run "make config" and make
sure you get the options for fat files systems.

> I installed RedHat-5.1 (kernel 2.0.34), upgraded to 2.0.35, but I still
> cannot mount my FAT32 partition.  I checked to see if the patches by Mr.
> Chaffee were there.  They were.  I tried

> # mount -t vfat -o debug /dev/hda1 /dosc

>  and got

> mount: wrong fs type, bad option, bad superblock on /dev/hda1,
>        or too many mounted file systems

> From this the tail from /var/log/messages was

> Jul 24 14:19:44 mordor kernel: [MS-DOS FS Rel. 12,FAT
> 32,check=n,conv=b,uid=0,gid=0,umask=022,bmap]
> Jul 24 14:19:44 mordor kernel:
> [me=0xf8,cs=8,#f=2,fs=32,fl=12260,ds=24552,de=0,data=24552,se=0,ts=12578832,ls=512,rc=2,fc=1254859]
> Jul 24 14:19:44 mordor kernel: Transaction block size = 512
> Jul 24 14:19:44 mordor kernel: VFS: Can't find a valid MSDOS filesystem
> on dev 03:01.

> What gives?

> One should know that before installing Linux, I tried to shrink my
> Winders partition using a FAT32 (beta) extension of FIPS (1.6b I
> believe). Since Winders could no longer find KERNEL386.EXE, I restored
> from the rescue floppy made by FIPS.  Being the cheapskate I am, I then
> tried using PartitionIt from Quarterdeck.  This also failed.

> Maybe one of these programs (PartitionIt) corrupted my superblock, or
> MBR, or ???.

> Dennis R. Weilert


 
 
 
Top

1. FAT32 and Linux 2.0.35: mounting the FAT32 partition

Hello,

I have just reinstalled win95 on a FAT32 partition and
upgraded my kernel to 2.0.35 so that (hopefully) I will
be able to see my dos partiton even though it uses FAT32
(aka "enable lrge disk support").

I have the following /etc/fstab file:

/dev/hda5               /                       ext2    defaults        1 1
/dev/hda8               /home                   ext2    defaults        1 2
/dev/hda6               /usr/local              ext2    defaults        1 2
/dev/hda7               swap                    swap    defaults        0 0
/dev/fd0                /mnt/floppy             ext2    noauto          0 0
/dev/cdrom              /mnt/cdrom              iso9660 noauto,ro       0 0
none                    /proc                   proc    defaults        0 0

... and my dos partiton is on /dev/hda1 and is supposed to be mounted under the /msdos directory
which is already there (I created it through RedHat's Disk Druid (aka "fdisk with GUI") when I was
installing up Linux).

Here's the output of df:


Filesystem         1024-blocks  Used Available Capacity Mounted on
/dev/hda5             599043  524089    44010     92%   /
/dev/hda8              50717    8856    39242     18%   /home
/dev/hda6             247871   35465   199606     15%   /usr/local

The fat32 filesystem does not show (the /msdos directory doesin't either).
/msdos should be mounted on (? /dev/hda9) and should get mounted at boot time?

Any suggestions?

TIA,

Neil Zanella

2. HELP: pppd connection terminated

3. Apache 2.0.35 rotating logs even though I didn't ask it to

4. Apache permissions, need advice

5. FAT32 in 2.0.34/2.0.35

6. Help configuring Gnome/Ximian

7. FAT32 under 2.0.34/2.0.35?

8. Gnome gremlins

9. RHL 5.1 kernel upgrade to 2.0.35 rpm breaks PC speaker sound ?

10. Apache 2.0.35 rewrite engine broken?

11. 2.0.30 -> 2.0.35 upgrade breaks printer device

12. ipautofw Broken with 2.0.35 Kernel?

13. Newbie-Having a problem mounting joliet with S.u.S.E. 5.3 (kernel 2.0.35)


All times are UTC
Board index