Description of problem: Version-Release number of selected component (if applicable): FC7T1 DVD Desktop set How reproducible: Always Steps to Reproduce: Here is my harddrive snapshot : [sda1 - NTFS][sda5 (sda6 - ext3)(sda7 - swap)(sda8 - ext3)(sda9 - ext3)] I tried to install FC7 with DVD Desktop spin. I chose a partition on my driver that I deserve to testing (/dev/sda8). Anaconda accepts this partition but right after I validate to launch the installation process, a error box appears instead of the formating progress box. The error is the following : "Error informing the kernel about modifications to partition /dev/sda5 - peripheral busy. This means Linux won't know about changes you made to /dev/sda5 until you reboot - so you shouldn't mount it or use it in any way before rebooting." Then a bugbuddy window appears telling the above message comes from parted. Ths windows also advises reporting a bug against anaconda. Actual results: No installation is possible.
Oh, when I click on 'Debug' from bugbuddy, the tty whell points to /usr/lib/anaconda/partedUtils.py(869)SavePartitions() Hope this helps.
Created attachment 147830 [details] anaconda dump
This is the same error that is preventing my F7T1 install, but in my case I'm not even telling the installer to make ANY changes to the partition table, since I'm simply installing into a pre-existing partition where FC6T3 used to live, and re-using swap.
Also, it looks like it tried (and thankfully failed) to partition the WRONG drive (sdi). I told to installer to leave all my other drives untouched, and to install to sdj2 with swap on sdj5, but it's complaining about a drive that's off by one less. With the new libata, the installer listed my drives as: sda: external sata drive on sata_sil - h/w raid1 with single ntfs part sdb - sde: sata drives on sata_nv sd? - my USB flash drive sdi - my 120GB PATA drive (primary master. previously /dev/hda) sdj - my 80GB PATA drive (secondary slave. /dev/hdd) Maybe this has something to do with usb devices being sandwiched between the scsi/sata drives and the old pata drives? (I'll attempt another install with all my usb devices unplugged.)
I tried with all the usb devices unplugged and had the same error.
Do you need extras info to resolve this bug ? Will it be resolved before F7T3 release ? I really want to test Fedora 7 to report bug, but this one prevents me from installing it. Thanks.
I'm going to get parted-1.8.3 released and merged in. We've got a lot of bug fixes in that release and I'd prefer to get that in rawhide and then go from there.
I've released up through parted-1.8.6 and hopefully that will fix your issue. It will be present in F7T3. Please test F7T3 when it's released and let me know if the issue has been resolved. Thanks.
It still doesn't work in FC7 Test 3.
Can you attach /tmp/anaconda.log to the bug report?
Also, 'ls -lR /proc' might be interesting to see if there's anything holding the partition table open.
Created attachment 151258 [details] anaconda.log
Created attachment 151259 [details] lslRproc
Can you change over to a shell (Ctrl+Alt+F2) and run: parted /dev/sda print > /tmp/parted-sda.txt parted /dev/sdb print > /tmp/parted-sdb.txt And for comparison: fdisk -l > /tmp/fdisk.txt Attach /tmp/parted-sda.txt, /tmp/parted-sdb.txt, and /tmp/fdisk.txt to this bug report. Thanks.
I'm still affected by this bug in test3 on my hardware. I tell anaconda that I ONLY want it to install to my pre-existing sdj2 partition which is on my spare 80GB secondary slave PATA drive, and to reuse swap (sdj5), and yet the "error informing the kernel about modifications..." is for sdi5, which is my 120GB primary master PATA drive (where my windows, extra swap, extra NTFS part, and s/w raid partition lives). I have no idea why it would be complaining about sdi5 (which happens to my extra NTFS partition) since it's not supposed to be touching that drive anyway. off by one bug? Attachments to follow:
Created attachment 151380 [details] anaconda.log
Created attachment 151381 [details] syslog
Created attachment 151382 [details] fdisk -l
Created attachment 151383 [details] parted sd{a..j} print
(In reply to comment #15) > I'm still affected by this bug in test3 on my hardware. I tell anaconda that I > ONLY want it to install to my pre-existing sdj2 partition which is on my spare > 80GB secondary slave PATA drive, and to reuse swap (sdj5), and yet the "error > informing the kernel about modifications..." is for sdi5, which is my 120GB > primary master PATA drive (where my windows, extra swap, extra NTFS part, and > s/w raid partition lives). > > I have no idea why it would be complaining about sdi5 (which happens to my extra > NTFS partition) since it's not supposed to be touching that drive anyway. off by > one bug? > > Attachments to follow: Where are you telling anaconda to write the boot loader? The error messages from the partitioning interface are not always exactly correct. Based on the parted output, I see that two devices report no medium found (sdg and sdh), which are before sdi. Are these actual disks or some sort of flash drive?
(In reply to comment #20) > Where are you telling anaconda to write the boot loader? In this case I told the installer to SKIP installing grub at all (it wanted to install to sdi's MBR by default, btw, even though sdi isn't my first bios boot drive). Usually I'll install it to the ROOT partition for test releases, and to my actual MBR (on sata raid1) for final releases. > The error messages from the partitioning interface are not always exactly > correct. Based on the parted output, I see that two devices report no medium > found (sdg and sdh), which are before sdi. Are these actual disks or some sort > of flash drive? There are no other obvious storage devices connected. sdg and sdh are unknown to me. I did have to manually select the PATA_AMD driver to begin the installation from DVD, so maybe it's related? Though grepping the syslog reveals them to be distinct: <5>sd 9:0:0:0: Attached scsi removable disk sdf <5>sd 8:0:0:0: Attached scsi removable disk sdg <5>sd 8:0:0:1: Attached scsi removable disk sdh <5>scsi 11:0:0:0: CD-ROM _NEC DVD_RW ND-3520A 1.04 PQ: 0 ANSI: 5
Created attachment 151417 [details] anaconda.log (new) I went farther and the og file displays errors this time
Created attachment 151418 [details] fdisk -l command print
Created attachment 151419 [details] lslRproc.txt New file with the diplay of the bug on screen while excuting the command.
Created attachment 151420 [details] parted-sda.txt
Created attachment 151421 [details] parted-sdb.txt
the error is still here, on f7t3, here's my 'original' report from the test mailing list :) i've searched the list but i haven't found somebody else reporting this, so here's the bug i've encountered while tryin' to install f7 t3. the target: one hard disk (pata) with several partitions, including one valid fc6 install splitted on: /boot, /, /home and swap. another partition is supposed to be the f7t3 /, and another is supposed to be the f7t3 /home. install starts just fine and after spending _a lot_ of time (amd barton 1833) while solving dependecies, right before it was supposed to format partiions, it prompts to ignore one error or exit. the error states that (anaconda?) "failed to inform the kernel about changes to /dev/hda5 and (some garbage)" . whether you choose to ignore the error or choos to exit, in both cases will exit. worth mentioning that the partiion table was not suppose to be changed, and /dev/hda5 is not supposed to be used during the install of f7t3, since is part of hte existing fc6 install, and is not even mounted. after reboot, the partiion table is still, there, no partition has been formatted. the error shows up on both livecdinstall, or dvd install. same dvd, used on another machine where all partitions become part of f7t3 (even if one, /home, is not formatted), worked just fine. unfortunately the machine where install failed, is offline so i report from memory :)
This bug is present since Fedora 4 and is present also in CentOS 5: http://bugs.centos.org/view.php?id=1906
Well, I can't reproduce this problem using rawhide as of today. I'm using the same partition layout as indicated in the opening comment for this bug.
Little news from a subscriber of this bug. NOTE: I have never changed my partion table during these tests. While with Fedora 4 up to Fedora 7 after the message: "Error: Error informing the kernel about modifications to partition /dev/hda5 -- Dispositivo o risorsa occupata. This means Linux won't know about any changes you made to /dev/hda5 until you reboot -- so you shouldn't mount it or use it in any way before rebooting." another message appears: "Exception Occurred: An unhandled exception has occurred. This is most likely a bug. Please save a detailed copy of the detailed exception and file a bug report against anaconda at http://bugzilla.redhat.com/" and then the installation stops and the system restarts, with Fedora 8 (both Live and Installer) the first message still appears but the second message appears no more and the installation starts and completes correctly.