Hide Forgot
Description of problem: "Routine" upgrade of FC4 using FC5 DVS crashes at first copy of core to HD; message says disk is probably full (it's far from full, has >100 GB free space). I have a anacdump.txt file that I will attach or include. Installation that allows repartition hangs right after parititioning but before formatting. I allowed it to stay that way overnight in case I was just impatient. Computer does not respond to keyboard or on/off switch; reset button must be used to regain control. Rescue, fdisk works fine. Version-Release number of selected component (if applicable): FC5 DVD for x86_64 How reproducible: Endlessly on one of my machines. No problem on another with identical configuration. One big red flag: HD of problem machine originally had Windows XP 64-Bit Edition on it, and FC4 had trouble partitioning it. Steps to Reproduce: 1. Insert DVD for FC5 x86_64 and boot to it. 2. Select Upgrade Existing Installation. 3. Allow it to write anacdump.txt to floppy when it crashes trying to copy the installation files to the HD. Alternatively, select Delete Partitions and Use Default Configuration and it will hang right after it writes the partition table, but before formatting. Actual results: Re-installed FC4, then upgraded without incident. Expected results: Trouble-free installation without problems or issues; this was seen about a week earlier in a machine with identical hardware (AMD Athalon 64 4400+ X2 (dual core), 2 GB RAM (passes RAM test). Additional info:
Created attachment 127509 [details] Anaconda traceback dump on crash
Looks like there was a problem reading part of stage2.img (part of anaconda) from your DVD drive, as shown by these messages in your exception traceback: <4>hda: media error (bad sector): status=0x51 { DriveReady SeekComplete Error } <4>hda: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 } <4>ide: failed opcode was: unknown <4>end_request: I/O error, dev hda, sector 117832 <3>Buffer I/O error on device hda, logical block 29458 The error message you got about being out of space is just because some of our error messages aren't set up to catch all these cases correctly. We've done a little work along these lines since FC5, so error messages should be more useful now.