Bug 77651 - Seagate 80GB (ST380020ACE) harddrive not usable (Installation)
Seagate 80GB (ST380020ACE) harddrive not usable (Installation)
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i586 Linux
medium Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-11-11 09:58 EST by Carsten Meyer
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-11-19 07:24:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
The kernel patch from James Finnie (2.94 KB, text/plain)
2002-11-19 07:24 EST, Carsten Meyer
no flags Details

  None (edit)
Description Carsten Meyer 2002-11-11 09:58:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
The kernel does not recognize the drive. This problem occours during
installation (partitioning with DiskDruid or fdisk is impossible because the
kernel has nothing to partion). The problem has to do with the kernel version an
the disks firmware (see below).

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

How reproducible:

Steps to Reproduce:
1. try to install RedHat 8.0 on the drive from CD/Floppy
2. Installation aborts when you try to partition the disk
3. -> Kernel sees wrong geometry with 0 cylinders (size of the drive could not
be determined).

Actual Results:  abort of installation (anaconda wants to reboot)

Additional info:

The drives firmware falsely tells the kernel it is capable of LBA 48 adressing.
That is wrong. The kernel tries to send some LBA 48 commands and the drive
errors. Kernel versions <2.4.18 worked ok. Disk geometry is reported with 0
cylinders due to wrong drive size recognition. Specifying geometry at the boot
prompt does not help. "nodma" does not help.

There was a patch posted by James Finnie (jf1@IMERGE.co.uk) on
newsgroup lucky.linux.kernel (17th October 2002)
Comment 1 Arjan van de Ven 2002-11-11 10:00:48 EST
what controller is the disk connected to ?
Comment 2 Carsten Meyer 2002-11-11 10:08:04 EST
The drive is connected to the onboard IDE controler (connected as primary
master). The Board is an ASUS P2B-S with an Intel BX440 chipset.
Comment 3 Carsten Meyer 2002-11-19 07:24:06 EST
Created attachment 85549 [details]
The kernel patch from James Finnie
Comment 4 Alan Cox 2002-11-19 08:04:54 EST
Such a change for an apparently faulty device is much much too risky for a
production grade operating system. If someone takes such a fix properly though
the 2.5 development tree so it gets broad testing then it might be something to
look at but not currently.

Closing as NOTABUG, since the problem seems to be the drive firmware. Perhaps
Seagate have fixed firmware by now?

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