[vdr] Re: Maxtor 160 GB

["Ralf Spitzauer" <ralf@spitzauer.de>]

> -----Original Message-----
> From: Carsten.Koch@icem.de [mailto:Carsten.Koch@icem.de]
> Sent: Saturday, March 02, 2002 2:30 PM
> To: vdr@linuxtv.org
> Subject: [vdr] Re: Maxtor 160 GB
>
>
> Ralf Spitzauer wrote:
> ...
> > > A new controller is NOT needed, you only need the 48-bit
> > > LBA kernel patch (or a kerner that has 48-bit LBA already).
> > > Marco, you wasted your 78 EUR. With the patch, the 160GB
> > > disk works full size on most newer controllers.
> > >
> > I īhavenīt install such a patch but I have full capacity (153GB in
> > KdiskFree) with Kernel 2.4.10
> > Do I need the patch or a newer kernel?
>
> I do not know.
> The SuSE 2.4.10 kernel may have the patch in it already.
> SuSE ships a higly-modified kernel with their distribution,
> so I do not know what is in it. The patch is NOT in the
> standard <= 2.4.17 kernels. It first showed up in the -ac
> series. I am not sure if it made it into standard 2.4.18?
>
> If my disk test below completes a full 153GB write and read pass
> on your 153GB disk, you are all set with whatever you have.
>
Disk test competed that night. Hereīs the result:

Writing.
156334 MB.
Write complete - No space left on device.
 163928604672 bytes in 18555.9 seconds = 8.42502 MB/s.
Reading.

Data error: 137438961408 != 7936. Exit.

I think now itīs for shure that I need a newer kernel or a patch when I
whant to use full Capacity.
Unfortunatly Iīm nearly a Linux Newbee. Iīve never build a kernel by myself
and I never patched a kernel. So I need some help or I have to wait for a
SuSe-Update or new Version.

Thank you very much for helping with this stuff.
>
> > > So I strongly recommend to run a disk test that writes
> > > and verifies every byte and uses different contents.
> > > badblocks was not able to find these errors, so I wrote
> > > my own test which did find the problem.
> > >
> > Where I can find such a disk test?
>
> Here:
>
> /*  Disk surface test and benchmark.
>     Carsten Koch, January 2002.
>
>