Bug 19844

Summary: install crashes when disks blank but not re-formatted from another linux (?!)
Product: [Retired] Red Hat Linux Reporter: Need Real Name <pictorm>
Component: installerAssignee: Michael Fulbright <msf>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-10-30 21:33:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2000-10-26 05:22:32 UTC
I repartitioned and formatted with a competing (older) linux version, waiting for rh7.  I chose not to re-format, since the partitions (2 ext2 and 1 
swap) should have been empty.  After the screen saying that it was my last chance to exit - it was going to over-write everything by installing, it 
crashed.  I tried again, formatting all 3 linux partitions, and had NO problems.

Machine: 
Cyrix M2-300, 128MB, i439TX/371AB chipset
hard disks: 8.4GB IDE primary master, hda, partitions: 2G hda1 type ext2; remainder, hda2, type FAT32
                 520MB pri slave, hdb, partitions: 130M swap, remainder is ext
boot method: CDROM
linux started with mem=128M

Here is the text it said to post:
=================

Traceback (innermost last:)
  File "/var/temp/anaconda-7.0.1//usr/lib/anaconda/iw/Progress_gui.py", line 20, in run
    rc=self.todo.doinstall()
  File "/var/temp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1472, in doInstall()
    self.fstab.mountFilesystems (self.instPath)
  File "/var/temp/anaconda-7.0.1//usr/lib/anaconda/fstab.py", line 713, in mountFilesystems
    raise SystemError, (errno, msg)
   System Error: (22,'invalid argument')

Comment 1 Michael Fulbright 2000-10-30 21:33:02 UTC
This appears to be a dupe of  bug16686.

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