lkml.org 
[lkml]   [2000]   [Sep]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[patch-required!] Recent kernels show problems in handling VERY large HDs
Date
Hi everybody,

my name is Andreas Eibach and it's the first time I'm here.

I'm aware of the fact that posting here requires having read ALL FAQs and
available documents before doing that.
I did this, of course.

But since the problem seems brand-new (due to the fact that these huge-sized
HDs are very new), I could, however, find questions and answers on the ML
archives, but still no solution of this recent problem.

Please apologize this being longer than usual posts, but I feel the need to
go into detail very much so that the problem can be fixed soon.

My setup is: (relevant things only)

AMD K6-266 (oc'ed @300)
Motherboard GA-586 SG w/AWARD BIOS 4.51PG
(no updates available anymore from the manufacturer! 586sg BIOS rev. is
1.15)
SDRAM
Maxtor 60 GB hard drive:
- Capacity Limitation Jumper J46 APPLIED (otherwise BIOS does not
recognize the HD at all!)
(note: this lets the HD look like a 32 GB one, causing total confusion
with the kernel)
- EZDrive (aka MaxBlast) APPLIED (as _prescribed_ by original
documentation for older BIOSes)

---

Linux SuSE 6.2, Kernels 2.2.10, 2.2.15, 2.4.0 test4
NOT TESTED YET: 2.2.17 (should I give it a try?)
Util-Linux 2.9f (from the distribution)
(Note: I've got latest 2.10o tarball here now, one of my suspects causing
the errors below was Fdisk at first)

Now my outputs: (slightly shortened)


Linux version 2.4.0-test4 (root@janus) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #2 Wed Sep 6 16:38:45 MEST 2000
[...]
Kernel command line: root=/dev/hdc11 ro single BOOT_IMAGE=bzi_240
Initializing CPU#0
Detected 300681014 Hz processor.
[...]
CPU: AMD-K6tm w/ multimedia extensions stepping 00
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
[...] (pci stuff)
[...] (net4 stuff)
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SIS5513: IDE controller on PCI bus 00 dev 01
SIS5513: chipset revision 208
SIS5513: not 100% native mode: will probe irqs later
SiS5591
ide0: BM-DMA at 0x4000-0x4007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x4008-0x400f, BIOS settings: hdc:pio, hdd:pio
--------------------------------------------^^
hda: Maxtor 96147U8, ATA DISK drive
--------------------------------------------^^
hdb: CD-532E-A, ATAPI CDROM drive
hdc: IBM-DTTA-350840, ATA DISK drive
hdd: ST33232A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 120060864 sectors (61471 MB) w/2048KiB Cache, CHS=7473/255/63, UDMA(33)
[...] (hdc: / hdd: / hdb:)
Uniform CD-ROM driver Revision: 3.11
Partition check:
hda:hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: status timeout: status=0xd8 { Busy }

OUCH...

hda: DMA disabled
hdb: DMA disabled
hda: drive not ready for command

OUCHIE...

ide0: reset: success
[EZD] [remap 0->1] [7473/255/63] hda1 hda2 hda3 < hda5 hda6 hda7 hda8 hda9
hda10 hda11 hda12hda: read_intr: status=0x59 { DriveReady SeekComplete
DataRequest Error }
hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=71987265, sector=0
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=71987265, sector=0
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=71987265, sector=0
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=71987265, sector=0
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=71987265, sector=0
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=71987265, sector=0
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=71987265, sector=0
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=71987265, sector=0
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=71987265, sector=0
end_request: I/O error, dev 03:0d (hda), sector 0

AYEEE .... OH MY GOD...

> hda4
hdc: [PTBL] [1027/255/63] hdc3 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 hdc11 hdc12
>
hdd: [PTBL] [781/128/63] hdd3 < hdd5 hdd6 hdd7 hdd8 >
[...]
[EXT II FS 0.5b, 95/08/09, bs=1024, fs=1024, gc=11, bpg=8192, ipg=4016,
mo=160b]

Well this doesn't look _that_ nice... :)

So what did I do?

Since my Maxtor HD contains already 8 Windows partitions and is supposed to
"get Linux" on the 3rd third, I deleted everything except those Windows
partitions. Then I used MS-DOS FDISK to build two _very big_ new partitions
in order to fill the thing up entirely to get rid of these

"Warning: Logical drive chain points to sector without partition table"
"Warning: EPBR partition starting at 71987265 is without logical partition"
(messages from PartitionInfo while testing HD - Partition Magic 5.0)

Back to Linux:
With CFdisk, I DELETED those two partitions again and wanted to start with
a, say, 300 MB / root partition.

Same error message again! (read_intr stuff....)

What I need is a kernel patch capable of handling this capacity limiter
correctly, because my suspicion is that everything BEHIND 32 GB (like in my
case, for 2/3 is used for Windows stuff) doesn't exist for the kernel, so to
say, an "Input past end" error.

Odd thing is, though, that the 2.4.0 test-x kernels do report the SIZE of
the hard disk all correctly.

Thanks for listening,

Andreas Eibach







-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:38    [W:0.043 / U:11.952 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site