I wanted to install CentOS 5.3 as my new development platform (upgrading from 5.2) and I thought I’d take the lazy route and use the net-install ISO. Although the 5.2 net-install worked flawlessly, the 5.3 failed at the same point time everytime (while downloading “minstg2.img”).
If you get the following error after having entered your mirror details:
Traceback (most recent call first):
File "/usr/lib/python2.4/subprocess.py", line 975, in _execute_child
File "/usr/lib/python2.4/subprocess.py", line 542, in __init__
File "/usr/lib/anaconda/iutil.py", line 488, in inVmware
proc = subprocess.Popen(lspci, stdout = subprocess.PIPE)
File "/usr/lib/anaconda/yuminstall.py", line 860, in doGroupSetup
if iutil.inXen() or iutil.inVmware() or
File "/usr/lib/anaconda/yuminstall.py", line 942, in doRepoSetup
File "/usr/lib/anaconda/backend.py", line 172, in doRepoSetup
File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext
File "/usr/lib/anaconda/text.py", line 721, in run
File "/usr/bin/anaconda", line 1006, in ?
OSError: [Errno 2] No such file or directory
Then the fix is to increase the amount of memory available to your VM. 256MB is not enough for a CentOS 5.3 install – 384MB does the trick. I assume the same applies to any physical, real machine.