On 10/26/07, maxim wexler <[EMAIL PROTECTED]> wrote:
>
> > Since you didn't specify how you determined that it
> > has only 131G,
> > perhaps you should check with fdisk to see what the
> > actual capacity
> > is?
> >
>
> The BIOS has 131G for the Samsung in a sub-menu for
> that drive: Maximum Cap
> The BIOS has 131G for the Samsung in a sub-menu for
> that drive: Maximum Capacity [131071MB], fdisk sees
> the whole 160G.
In that case I'd look for a BIOS update. (FWIW 128 x 1024 = 131072).
--
[EMAIL PROTECTED] mailing list
> Since you didn't specify how you determined that it
> has only 131G,
> perhaps you should check with fdisk to see what the
> actual capacity
> is?
>
The BIOS has 131G for the Samsung in a sub-menu for
that drive: Maximum Capacity [131071MB], fdisk sees
the whole 160G.
On my way to check the c
> Anyway, this is where things get even stranger. I've
> quadruple-checked and I still don't believe it. The
> Maxtor drive now PASSES smartctl -H and the "new" one
> FAILS. The Maxtor still gets the dma_intr errors in
> dmesg and the Samsung is said to have it's "DMA
> disabled" which contradicts
Hi group,
A while ago my Maxtor 120G IDE HD started acting up,
smartctl wouldn't pass it and in dmesg were many
ominous dma_intr errors.
So from ebay I got a used Samsung 160g which I just
installed. I was hoping to transfer over my OS and
files etc to the "new" drive.
The drive is recognized i
5 matches
Mail list logo
