Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 66568

Summary: expected read-only character buffer, int found
Product: [Retired] Red Hat Linux Reporter: Christopher Cox <chrisc>
Component: installerAssignee: Michael Fulbright <msf>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-06-19 16:13:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Dump the installer provided none

Description Christopher Cox 2002-06-12 11:28:04 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011128
Netscape6/6.2.1

Description of problem:
Intall died right after disk error check.
PII 350, 64M Ram, ATI 3D AGP
Two drives root and /u on hda, /backup and swap on hdc.

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


How reproducible:
Always

Steps to Reproduce:
1.Install->Custom->Everything
2.
3.
	

Additional info:
Comment 1 Christopher Cox 2002-06-12 11:30:09 UTC 
Created attachment 60646 [details]
Dump the installer provided
Comment 2 Christopher Cox 2002-06-12 15:31:30 UTC 
Moved swap to hda2, problem still occured.
Comment 3 Christopher Cox 2002-06-12 15:31:54 UTC 
Moved swap to hda2, problem still occured.
Comment 4 Michael Fulbright 2002-06-12 16:06:26 UTC 
Could you try this case w/o turning on bad blocks checking?
Comment 5 Christopher Cox 2002-06-17 15:29:12 UTC 
Sorry for the belated response. There was difficulty with the test platform that
was causing lockups during the installation, therefore clouding the issue.

On the new stable platform, the problem persisted and was replicable.
Turning off Bad Block checking did allow the install to proceed without error.
Comment 6 Michael Fulbright 2002-06-17 21:28:26 UTC 
This error occurs when the badblocks command detects bad blocks on the system. 
The traceback occurred because the output from the badblocks command has
changed, fooling our parser.

If you get this traceback it means you have bad blocks on the drive it was testing.

In the future an error dialog will be presented saying bad blocks have been
detected.
Comment 7 Michael Fulbright 2002-06-17 21:31:52 UTC 

*** This bug has been marked as a duplicate of 66181 ***
Comment 8 Christopher Cox 2002-06-18 11:27:27 UTC 
I disagree. The changing of platforms also involved changing hard drives from a
10Gig Maxtor to a new Western Digital 40 Gig WD400BB. 

I doubt very much that both drives have bad blocks. Checkit OK'ed the WD400BB.
Comment 9 Christopher Cox 2002-06-19 16:13:40 UTC 
OK close it.

Murphy's law prevails. Purchased yet a third drive and Bad Block Checking did
not crash the install.

Of course there is a problem with your bad block reporting mechanism. 

Thanks and Regards.