Bug 52825 - Boot up hang
Boot up hang
Status: CLOSED NOTABUG
Product: Red Hat Public Beta
Classification: Retired
Component: filesystem (Show other bugs)
roswell
i586 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-29 14:29 EDT by T
Modified: 2014-03-16 22:23 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-29 15:37:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description T 2001-08-29 14:29:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.1)
Gecko/20010607 Netscape6/6.1b1

Description of problem:
During the boot up process the system will hang leaving me only able to
type onto the window(and thats is, no Ctrl alt del).
This happens just after it goes to check the filesystems and prints a
messege similar to: "Fat32 support is alpha" in the status column.

The system started up fine before I upgraded it.  Could it have somthing to
do with the conversion of my Linux partions to ext3 during the upgrade?

System info:
Primary OS: Windows XP(2K based)
PIII 800 384 mb ram

30 GB hd allocated as follows:
Primary: 5.77 GB (FAT32)
Logical: 5.03 GB(FAT32) ; 7.43GB(FAT32) ; *GB (Linux)
Linux Section allocated as follows:
768mb swap drive
Boot partion 5mb or so mb (EXT3)
Main partion *(around 7 GB) GB (EXT3)

I appologize that I can't get exact information as I can't work around this
crash to access my system.

If any other information that I didn't include is needed I can provide.

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


How reproducible:
Always

Steps to Reproduce:
1. Turn on the computer and boot linux with MY system


Actual Results:  "Fat32 support is ALPHA"
[Explosion]

Expected Results:  System booting up as normal

Additional info:

Could it have somthing to do with the conversion of my Linux partions to
ext3 during the upgrade?

System info:
Primary OS: Windows XP(2K based)
PIII 800 384 mb ram

30 GB hd allocated as follows:
Primary: 5.77 GB (FAT32)
Logical: 5.03 GB(FAT32) ; 7.43GB(FAT32) ; *GB (Linux)
Linux Section allocated as follows:
768mb swap drive
Boot partion 5mb or so mb (EXT3)
Main partion *(around 7 GB) GB (EXT3)
Comment 1 Bill Nottingham 2001-08-29 14:45:04 EDT
Boot with 'linux init=/bin/bash'.

What does your /etc/fstab look like?
Comment 2 T 2001-08-29 15:37:37 EDT
I was able too boot with your params so I mounted a windows drive and redirected the contents of the fstab into a file on it.

Heres what it gave me:
LABEL=/                 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
/dev/cdrom              /mnt/cdrom     
         iso9660 noauto,owner,ro 0 0
/dev/cdrom1             /mnt/cdrom1             iso9660 noauto,owner,ro 0 0
/dev/fd0                /mnt/floppy             auto    
noauto,owner    0 0
none                    /proc                   proc    defaults        0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                 
   /dev/pts                devpts  gid=5,mode=620  0 0
/dev/hda9               swap                    swap    defaults        0 0
/dev/hda1	/mnt/vFatC	vfat	
 exec,dev,suid,rw 1 1
/dev/hda5	/mnt/vFatD	vfat	 exec,dev,suid,rw 1 1
/dev/hda6	/mnt/vFatE	vfat	 
exec,dev,suid,rw 1 1
/SWAP                   swap                    swap    defaults        0 0
Comment 3 Bill Nottingham 2001-08-29 16:00:03 EDT
Change the last bits for all your vfat partitions to '0 0', not '1 1'.
MS-DOS/vfat/etc. partitions should *not* be set to check at boot.
Comment 4 T 2001-08-29 17:28:33 EDT
Yes that would do it.  Should this bug be passed on to the intaller guys as a upgrade bug?  
>fsck ran fine on the old fstab, is this a backwards compatibility issue or is the upgrade changing things it shouldn't be?


Can someone give me instructions on how to get my drive writtable when booted up like this so I can either modify the fstab manually or use 
fsconfig?  Thanks.

Note You need to log in before you can comment on or make changes to this bug.