sslug-teknik team mailing list archive

[Björn Lundin <bnl@xxxxxxxxxx>]

Henrik Storner wrote:

> In <25048.212.242.150.24.1078848250.squirrel@inet.riker> "Kristian
> Kallenberg" <kale@xxxxxxxxxxxxx> writes:
> 
>>>> Filesystem            Size  Used Avail Use% Mounted on
>>>> /dev/hda2             152G  132G   21G  87% /
>>>>
>>>> Jeg kører debian woody, kerne 2.4.25 og reiserfs 3.6 på en 160GB disk.
>>> Er du løbet tør for inodes? Hvad skriver "df -i"?
> 
>>Filsystem            Inoder   IBrugt  IFri  IBrug% Monteret på
>>/dev/hda2            4294967295       0 4294967295    0% /
> 
> i-noder er ubegrænsede på reiserfs filsystemer.
> 
> Det lyder mere som et problem med IDE driveren der ikke kan
> håndtere diske større end 132 GB - SVJH er der noget med at det
> er en grænse på IDE diske.
> 
> Er BIOS'en sat til at køre LBA mode ?
> 
> 
> Henrik

På mandrakes 'expert' lista finns en liknande tråd. Jag klipper in ett
inlägg därifrån:

<inlägg>
Hi, have to pop in on this. What you are seeing is DEFINITELY the 48bit
"Big-Disk" LBA bug, ie. your BIOS does not support disks bigger than
137GB

You can either: 
Find out if your MB Manufacturer has an updated BIOS available. I did a
bit of digging and ASUS has a BIOS file dated 13.05.2002 available, it's
marked BETA though. You might want to try this.

Change MB (this costs money)

Sell the new HD to someone else that can use is fully and then buy a
smaller one (ie. 120GB disk) that you can use fully.

On Tue, 2004-03-02 at 10:38, Raffaele Belardi wrote:
>Just to recap, I have data corruption on a Maxtor 160Gb HD on my MDK9.2
>(motherboard Asus P5A-B with AMD K6-2/550 and 128Mb RAM). Disk is 
>partitioned as 5Gb+75Gb+75Gb (approx).
> I came to these conclusions:
> 
> - the hd is ok, I tested it on a different system.
> - it's not a kernel or MDK bug, on another system with 9.2 it's ok.
> - it's not related to memory, I tried with a different 256M DIMM 
> (instead of the current 128M) and got exactly the same result.
> 
> So, for me it's a motherboard bug. But, note that the corruption occurs 
> in the whereabouts of the 130Gb - too near the infamous 137.9Gb BIOS 
> limit not to ring a bell.
> 
> Thanks to all who contributed, now I have the options of either changing 
> mb or leave part of the disk unused.
> 
> raffaele
> 
</inlägg>

/Björn