Red Hat Bugzilla – Bug 64846
7.3 Installer crashes when anaconda starts and encounters a reiserfs filesystem
Last modified: 2005-10-31 17:00:50 EST
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
Running anaconda - please wait...
Traceback (innermost last):
File "/usr/lib/anaconfa", line 67, in ?
File "/usr/lib/anaconda/dispatch.py", line 19 in ?
from packages import readPackages, checkDependenceies, doInstall
File "/usr/lib/anaconda/packages.py", line 25, in ?
File "/usr/lib/anaconda/fsset.py", line 355, in ?
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):
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.
Also, FWIW there are no current Reiser filesystems on this box. There were at
one time but they aren't present any longer.
Please boot the installer, and when you reach the welcome screen hit cntl-alt-f2
and goto a shell prompt.
where hdx is the actual name of the drive which used to have reiserfs on it.
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.
The output is as follows:
Information: The operating system thinks the geometry on /tmp/hdb is
9729/255/63. Therefore, cylinder 1024 ends at 8032.499M.
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.
Matt any ideas?
any strange errors on Ctrl+Alt+F3 or Ctrl+Alt+F4? Did this media pass media check?
Closing due to inactivity - please reopen if you have additional information to add.
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!
Thanks - marking as a dupe of bugs of this nature.
*** This bug has been marked as a duplicate of 75008 ***
Time tracking values updated