Red Hat Bugzilla – Bug 82989
Installer fails while attempting to partition IDE drive
Last modified: 2007-04-18 12:50:26 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030121
Description of problem:
Am booting off a normal RH8 CD1 for either manual or kickstart installation.
"The kernel was unable to re-read the partition table on /tmp/hda (device or
resource busy). This means that Linux knows nothing about any modifications you
made. You should reboot your computer before doing anything with /tmp/hda"
Installation pretty much ends here no matter what I do. ;-)
I'm able to reproduce this both manually and via kickstart. No weird errors are
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RH8 on a clean system
2. Follow prompts, wait for partitioning
3. Attempt to partition
Expected Results: Partition should be written and installation should continue.
Motherboard is a Intel SE7500CW2 (Clearwater) and the IDE drive is connected to
the Primary IDE bus.
There's really nothing wrong with the IDE drives since WinXP installs fine,
Win2K installs fine and FreeBSD seems to install fine.
Also if going through "linux rescue" and doing "fdisk /dev/hda" one is able to
write a new partition table without any problems.
I'll try to get the lspci -v and dmesg off the server somehow, if needed.
This seems to be similar to a problem reported in bug #64788, #82269 seems to be
Failed on drive type Maxtor DiamondMax Plus 8 (40 GB), shows up as 6E040L0510211
(or 6E040L05), tried with several.
Changed to an IBM IC35L040AVVN07-0 (40 GB) and it started working.
what kind of IDE hard drive did you have?
*** Bug 82269 has been marked as a duplicate of this bug. ***
We have the same Problem here. We've already exchaged an 80GB IBM Drive
(can't remember exact model) for a 80 GB Matror Drive (Maxtor 6Y080L0
ATA-133) but still no success.
Mainboard is a MSI-9211 and the drive is currently connected as master on
the primary ide bus.
I can create partitions with fdisk when anaconda creashed and the kernel
sees them on the next boot but even if I hardwire partitions in the
kickstart installation (e.g. part / --fstype=ext3 -onpart=hda1) , the installer aborts this error message.
Do you get the "device or resource busy" message?
Can you attach your ks.cfg?
Created attachment 90725 [details]
some unimportant parts omitted
And it falls over every time?
Somehow I got one of these back (surprise, surprise!) on my table exhibiting the
problem described earlier on.. Is there anything special you want me to run on
it because now is the time if ever ;-)
Please feel free to close this issue, it doesn't seem to be reproducible with
the RH9 or Severn installer... lots of other fun things with the CW2
motherboards as well.
Resolving as CURRENTRELEASE, not happening with the FC1 installer either.