Red Hat Bugzilla – Bug 167855
Error informing the kernel about modifications to partition /dev/sda5 - Device or resource
Last modified: 2007-11-30 17:11:13 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Description of problem:
I recieved the following error "Error informing the kernel about modifications to partition /dev/sda5 - Device or resource" while installing fedora 4 on a new Dell Deminsion 9100 (DIM 9100 630 3.0GHz, 512MB Dual Channel DDR2 400MHz (2x256) Memory, 160GB 7200rpm SATA Hard Drive, 256MB nVidia Ge Force 6800)with the request that I copy the anacdump to bugzilla (will attach).
It occured during a text install - graphic install froze as soon as graphics loaded and when installed with the boot line 'linux nofb' I recieved the error along the lines of 'unsupported video mode' at the same stage in the process - I don't know if that had anything to do with the error.
The command line I finally installed from was:
linux jfs nofb ide=nodma
hope this helps.
Version-Release number of selected component (if applicable):
* had unresolved dependencies, resolved.
* moving (1) to step confirminstall
* discNums is 
* don't have 2
* moving (1) to step install
* id.methodstr = cdrom://hda:/mnt/source 0
* moving (1) to step enablefilesystems
* parted exception: Error: Error informing the kernel about modifications to partition /dev/sda5 - Device or resource busy. This means Linux won't know about any changes you made to /dev/sda5 until you reboot - so you shouldn't mount it or use it in any way before rebooting.
No volume groups found
Wiping internal VG cache
Finding all volume groups
No volume groups found
Reading all physical volumes. This may take a while...
cal volumes. This may take a while...
Created attachment 118612 [details]
This the anacdump created by the error message with a request that it be
submitted to bugzilla.
I have reinstalled using ext3 instead of jfs on /dev/sda5 and this seems to have
solved the problem.
small correction to the info above - the boot line should have read
linux jfs nofb ide=nodma text
It probably should have worked regardless of what filesystem you used on the
second attempt as long as you provided the same partitioning information.
*** This bug has been marked as a duplicate of 160693 ***