Bug 163225 – anaconda crashed while after partitioning with error "kernel was unable to read partition table"

Bug 163225 - anaconda crashed while after partitioning with error "kernel was unable to read partition table"

Summary:	anaconda crashed while after partitioning with error "kernel was unable to re...

Status:	CLOSED DUPLICATE of bug 160693

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	anaconda (Show other bugs)
Sub Component:
Version:	4
Hardware:	athlon Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Anaconda Maintenance Team
QA Contact:	Mike McLean
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-07-14 04:15 EDT by alessandro brovelli
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-07-15 07:36:47 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
error log (16.00 KB, text/plain) 2005-07-14 04:20 EDT, alessandro brovelli	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description alessandro brovelli 2005-07-14 04:15:13 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
After some file system problem I decided to upgrade from FC2 to FC4. I started a fresh installation, partitioned the HD, and while anaconda was gathering the informations required to start the installation, I got the error:
"error: Warning: The kernel was unable to re-read the partition table on /dev/hda (Device or resource busy).  This means Linux won't know anything nothing about
the modifications you made until you reboot.  You should reboot your computer before doing anything with /dev/hda." After this error I can dump a log file and the installation aborted.

If I start the installation using non-graphical mode, I got the same error, but I can ignore it; the processes finishes without trouble, but at the first boot the system is unable to start (kernel panic, try to use init=, etc.).

It's very annoying because I can install and run MS-Win instead...

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.'Standard' installation
2. Maybe you should need and HD with some problems?
3.
  

Additional info:

Comment 1 alessandro brovelli 2005-07-14 04:20:24 EDT

Created attachment 116733 [details]
error log

Comment 2 Jeremy Katz 2005-07-15 07:36:47 EDT


*** This bug has been marked as a duplicate of 160693 ***

Note You need to log in before you can comment on or make changes to this bug.