Bug 25259

Summary: mounting of vfat during installation throws exception
Product: [Retired] Red Hat Linux Reporter: Clint Larraga <clint>
Component: installerAssignee: Michael Fulbright <msf>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: clint
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-01-30 21:40:49 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 Clint Larraga 2001-01-30 03:57:52 UTC
I have a dual boot system Win98SE and Linux and had initial problems 
installing redhat 7.0 on the linux partition (using lilo as boot loader). 
During the installation (tried for both GUI and text mode) I mounted the 
vfat partition using /mnt/drive_x and this is what i got.


--------------

Traceback (innermost last)
	File "/var/tmp/anaconda-
7.0.1//usr/lib/anaconda/iw/progress_gui.py", line 20 in run
	rc=self.to.do.doInstall()

	File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 
1480, 
	indoInstall
		if self.method.systemMounted 
(self.fstab,self.insPath,self.hdList.selected():
	
	File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/image.py",line 46, 
in systemMounted

		self.loopbackFile=mntPoint+fstab.filesystem Space(mntPoint)
[0][0]+\

	File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/fstab.py", line 
258, in filesystemSpace
	
	File "/usr/lib/anaconda/isys.py", line 16, in fsSpaceAvailable 
return_isys.devSpaceFree(fsystem)

	System Error:(2,'No such file or directory')


--------------

I retried leaving the vfat partition unmounted and proceeded with the 
installation. When everything was finished I just remounted the same vfat 
partition using the mount command and I had no more problem. This bug 
(although there is a workaround) can be discouraging for newbies.

Comment 1 Michael Fulbright 2001-01-30 21:40:44 UTC

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