Bug 39149 – Installation crashed after formatting disk

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 39149 - Installation crashed after formatting disk

Summary:	Installation crashed after formatting disk

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i586 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Brent Fox
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-05-04 18:46 EDT by Otakar Michl
Modified:	2007-04-18 12:33 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-05-15 14:19:25 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Otakar Michl 2001-05-04 18:46:18 EDT

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)

Description of problem:
After formatting disk

How reproducible:
Always

Steps to Reproduce:
1.Installation crashes after formatting disk
2.Sometimes black screen, need to restart computer
3.Must install as "expert"
	

Actual Results:  There is a message that "exception was found" and that I 
should inform you. Installation doesn't continue.

Expected Results:  Will you advise?

Additional info:

It's the legally bought package in Prague, Czech Republic

Comment 1 Brent Fox 2001-05-05 19:54:25 EDT

Can you attach the complete debug error message?  That will help us a great deal
in figuring out what went wrong.

Comment 2 Brent Fox 2001-05-15 14:19:20 EDT

Closing due to inactivity. Please reopen if the problem persists.

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