Bug 52034

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010725

Description of problem:
Adding and mounting FAT32 drives (as vfat) data is accessable as usual,
however upon a reboot at external drive mount time a warning is given that
FAT32 is in ALPHA code, and then hangs.  Nothing past a one line warning is
given.

The drives are:
/dev/hda6      /mnt/dos/e      vfat     exec,dev,suid,rw 1 1
/dev/hda5      /mnt/dos/d      vfat     exec,dev,suid,rw 1 1
/dev/hda2      /mnt/dos/c      vfat     exec,dev,suid,rw 1 1
In order to regain access to my system I needed to use a CD and boot to
rescue mode, and comment out those 3 drives from the /etc/fstab

For some reason after a forced hard reset my windows partitions would not
boot from lilo anymore, although according to norton disk doctor all data
is intact.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Installed linuxconf via Redhat Network

2. Added the 3 dos partitions listed previously under the Filesystems/Add
Local Drive, mount & accept.  Quit linux conf.

3. Check systems loaded under /mnt/dos/X and copied some files from them to
another computer on the network (my redhat 7.1 gateway)

4. Rebooted the pc.

Actual Results:  After entering the section of boot with the [ ok ]
confirmations, daemon loading etc (sorry I dont know the term for that
part) it comes to the loading of the VFAT drives from fstab, gives a breif
warning of FAT32 being in ALPHA, and hangs immediatly. This has happend
every boot untill I commented out the drives in rescue mode, at least 6
attempts.

I have not tryed again since commenting out, sorry for this but so far I
cant boot my windows drives anymore, and although they are not critical, I
would prefur not to loose any data from them.  So far I have not managed to
force windows to boot again but am still trying.


Expected Results:  As per Redhat 7.0/7.1/SuSE 7.2/Slackware 7.0/Progeny
Debian RC1 of wich all have existed on the same disk previously and where
Roswell is now, have mounted these drives on boot with not a single problem.

Infact mounting the drives AFTER boot manualy or thru linuxconf works
perfeclty.

Additional info:

I belive, although cannot be certen, the system atempted to "check" my
FAT32 disks as if they were EXT2/EXT3 (I run EXT3 on all my linux
partitions under Roswell).  Unfortunatly I cannot verify this untill I can
recreate the issue.

I have marked this as high on the basis my Windows disk no longer boots,
and so far does not want to be fixed.  (perhaps thats a blessing tho? ;)