I have met a strange problem. When I installed Redhat 9.0 on VMWARE 4.0, all went fine until it told me that some packages on the second CD could not be read, and probably the CD was corrupted. However, it is a good CD, 'coz I installed these packages in other machines using it. Assuming that this CD was damaged, I downloaded the second ISO from redhat and made a new CD, but I still failed with the same problem. So I decided not to install these packages. It took me a lot of time (starting over and over) to decide and remove the "bad" packages (xsane, xpdf, yelp, xsri, xscreensaver etc) and packages which need them from the installing list and finally I got redhat 9.0 installed. -- I only installed 507 packages with a total size of 1616 MB. Pretty compact, huh? On the other hand, I successfully installed redhat 8.0 on vmware with packages freely chosen.

Though I guess I can install these packages later, I still wonder what happened. Any opinions? Thanks a lot.

Dani AI

Generated

Short summary and practical follow-ups for the Disk 2 read errors: ’s symptom (installer failing reading packages on the second CD) is a common VM/optical-media interaction problem, and ’s ISO-mount workaround (confirmed by and ) often fixes it. Below are reliable checks and alternatives that go beyond “swap the ISO mid-install” so the install completes cleanly and you can add the skipped packages later.

First, verify the media/ISO before blaming VMware or the guest. On the machine where you have the ISO:

md5sum disk2.iso

or on Windows:

certutil -hashfile disk2.iso MD5

Compare against the official checksum. If the ISO is good, avoid burned-disc variables (burn at lowest speed, different burner) and attach the Disk 2 ISO to the VM from the VM settings before booting the installer — this prevents host/guest CD hot-swap and drive caching issues.

If you already have a minimal install (like ) and want the missing packages installed afterward, mount the Disk 2 ISO inside the guest and install from the RPM directory:

mkdir /mnt/cdrom
mount -o loop /path/to/disk2.iso /mnt/cdrom
cd /mnt/cdrom/RedHat/RPMS
rpm -Uvh *.rpm

Or copy the RPMS to a data disk and install from there, or set up a simple local repository for yum if available.

If a specific package keeps failing (for example the db4-4.0.14-20 mentioned by ), try fetching that single RPM from a mirror or Red Hat archive and install it first — a corrupted RPM on the media will always break the installer. Final notes: if you hit stubborn I/O errors, try text-mode install or a network/FTP install to bypass CD/DVD I/O entirely.

Recommended Answers

All 4 Replies

I had the same problem. After searching around I found the following work-a-round:

Install Red Hat as usual. When it fails, click on Edit->Removable Devices-><yours CDROM>->Edit. From there choose "Use ISO Image" and browse to your Disk 2 ISO. Once Disk 2 is done, change it back to the CDROM and continue.

Hope this helps, it did for me.

This worked great thanks

I had the same problem. After searching around I found the following work-a-round:

Install Red Hat as usual. When it fails, click on Edit->Removable Devices-><yours CDROM>->Edit. From there choose "Use ISO Image" and browse to your Disk 2 ISO. Once Disk 2 is done, change it back to the CDROM and continue.

Hope this helps, it did for me.

:o i spent 2 days on vmware and then i saw this. thanks a million

Hum... That should solve my problem.

I am installing RedHat 9, and the installation process is suspended when the error occurrs, leaving me only with the Reboot option. Perhaps if I run the setup in Text mode?

TIA

PS: The error occurs with the file "db4-4.0.14-20": "The Berkeley DB database library (version 4) for C."

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.