Bug 64846 - 7.3 Installer crashes when anaconda starts and encounters a reiserfs filesystem
Summary: 7.3 Installer crashes when anaconda starts and encounters a reiserfs filesystem
Status: CLOSED DUPLICATE of bug 75008
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i686
OS: Linux
high
high
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-13 15:49 UTC by Joe Simmons
Modified: 2005-10-31 22:00 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2002-06-23 05:59:21 UTC


Attachments (Terms of Use)

Description Joe Simmons 2002-05-13 15:49:20 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461)

Description of problem:
When attempting to boot off of the RedHat 7.3 install CD, the system boots and 
starts anaconda.  When it reaches this point, it crashes with the following 
error:

Running anaconda - please wait...
Traceback (innermost last):
 File "/usr/lib/anaconfa", line 67, in ?
   import dispatch
 File "/usr/lib/anaconda/dispatch.py", line 19 in ?
   from packages import readPackages, checkDependenceies, doInstall
 File "/usr/lib/anaconda/packages.py", line 25, in ?
   import fsset
 File "/usr/lib/anaconda/fsset.py", line 355, in ?
   fileSystemTypeRegister(reiserfsFileSystem())
 File "/usr/lib/anaconfa/fsset.py", line 316 in __init__
   seld.partedFileSystemType = parted.file_system_type_get("reiserfs")
parted.error: unknown file system type
install exited abnormally -- received signal 11
(and proceeds to shut down)

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


How reproducible:
Always

Steps to Reproduce:
1.  Boot system off of install CD
2.  Start Installer
3.  Watch Crash
	

Actual Results:  See description

Expected Results:  The installer should have started.

Additional info:

Comment 1 Joe Simmons 2002-05-13 16:02:16 UTC
Also, FWIW there are no current Reiser filesystems on this box.  There were at 
one time but they aren't present any longer.

Comment 2 Michael Fulbright 2002-05-13 18:50:12 UTC
Please boot the installer, and when you reach the welcome screen hit cntl-alt-f2
and goto a shell prompt.  

Then type:

mknod /tmp/hdx

where hdx is the actual name of the drive which used to have reiserfs on it.

Then run:

parted /tmp/hdx

substituting the correct drive device again for hdx.

Then say 'print' and attach the output please. I think parted is seeing the
signature of the old reiserfs filesystem and getting confused.




Comment 3 Joe Simmons 2002-05-13 19:10:18 UTC
The output is as follows:

Using /tmp/hdb
Information: The operating system thinks the geometry on /tmp/hdb is
9729/255/63.  Therefore, cylinder 1024 ends at 8032.499M.
(parted) print
Disk geometry for /tmp/hdb: 0.000-76319.085 megabytes
Minor    Start     End        Type     Filesystem     Flags
1        0.031     76316.594  primary  ext2

This also happens when you attempt to boot into Rescue mode, since Anaconda
still runs then.  The exact same error occurs.

Comment 4 Michael Fulbright 2002-05-13 20:22:04 UTC
Matt any ideas?

Comment 5 Matt Wilson 2002-05-20 20:15:26 UTC
any strange errors on Ctrl+Alt+F3 or Ctrl+Alt+F4?  Did this media pass media check?


Comment 6 Michael Fulbright 2002-06-12 17:04:17 UTC
Closing due to inactivity - please reopen if you have additional information to add.

Comment 7 Joe Simmons 2002-06-23 05:58:55 UTC
I finally discovered the problem.  It seems that the CDROM drive was the root 
of the issue.  On your suggestion, I looked at the CTL-ALT-F3/F4 consoles, and 
it was actually the CDROM which was generating the error, not the previous hard 
drives.  Replacing the drive fixed the issue.  Thanks for the help! 

Joe/Oracle

Comment 8 Michael Fulbright 2002-10-03 19:06:41 UTC
Thanks - marking as a dupe of bugs of this nature.

*** This bug has been marked as a duplicate of 75008 ***

Comment 9 Michael Fulbright 2002-12-20 17:38:25 UTC
Time tracking values updated


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