Summary: | Upgrade fails | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | dhughes |
Component: | installer | Assignee: | Matt Wilson <msw> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | ||
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: | 2000-02-10 20:03:50 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: |
Description
dhughes
1999-06-11 01:53:17 UTC
Are you using a CdRom to upgrade? Booting from the Cd or from a floppy? Is this by any chance a hard drive install, ie the RPMs are located on the hard drive you are upgrading? ------- Email Received From "Don Hughes" <dhughes> 06/12/99 13:03 ------- Try booting the upgrade process from cdrom rather than booting from the boot disks that you downloaded. There is a possibility that the boot disks are corrupt and that is leading to the problem that you are seeing. ------- Email Received From "Don Hughes" <dhughes> 06/14/99 22:09 ------- ------- Additional Comments From 06/15/99 03:34 ------- I had exactly the same problem when I tried to upgrade from RH 5.2 (heavily updated already by hand, including the kernel to the latest 2.2 available at the moment). I tried the following (all combinations): - booting either from floppy or from a bootable CD I have created, using both the boot.img file provided in the RHL 6.0 RPMS and the one provided as update - installing from a HDD partition (/dev/hdc11, 1 GB, only used to store install kits, usually unmounted!) or from the above mentioned CD The solution was to manually umount /mnt, after the first 'device busy' message, hit 'retry' and afterwards all worked fine. Looks to me like the bug already mentioned on bugzilla (#2499/2504/2505 and so on) Manuel Wolfshant (wolfy67) ------- Email Received From "Don Hughes" <dhughes> 06/16/99 20:45 ------- This issue has been forwarded to a developer for further action. |