Bug 71217
Summary: | Full disk not visible | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Brian Freeman <linuxboy> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | 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: | 2004-09-30 15:39:50 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: |
Description
Brian Freeman
2002-08-10 05:47:20 UTC
> The boot messages recognize geometry from append, but also show 32.8GB
> capacity.
Are these the messages from the kernel when the system is booting up?
Yes, the messages are from the kernel and happen during boot. Reassigning to kernel. did you jumper the disks? Jumpering IBM disks changes the actual capacity of the drive and when jumpered only 32GB can be used. Setting the capacity reported to BIOS using the drive configuring utility from IBM allows the drivers to set the capacity to the full 40GB. As a test I did try setting full capacity in the configure utility and jumpering the drive, but the results were as expected... The OS could not see more than 32GB, even win98 could not see the full capacity when the drives were jumpered for 32GB. When the test was complete, I restored the jumper to the full capacity setting and used the utility to set 32GB for BIOS compatiblity. Since win98 was installed at that point, I confirmed that it could see the full 40GB. Reinstalling RH7.3 resulted in the same problem. Been a bit, just want to indicate that the resolution is still desired. Thanks. Linuxboy Tested 8.0 and it's identical. Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |