Richard Fish wrote:
> On 11/27/06, Guido Doornberg <[EMAIL PROTECTED]> wrote:
>> Well, I want to use Gentoo but i don't realy like the idea of spoiling
>> my weekend by installing an OS thats gonna stop working 30 times
>> booting later.
>
> I doubt this is really Gentoo-specific.
Me too, i don't think it's Gentoo making this break.
>
>> So, does anyone know whats wrong here and how i can prevent that it
>> happens again?
See below.
>
> What kernel are you using? Can you post your emerge --info?
>
> My initial guesses are one of:
>
> 1. You are using some experimental kernel that is corrupting the filesystem
He said he was installing 2006.0 so i doubt he was going for ~arch and
testing kernel.
>
> or
>
> 2. That your old power supply is not sufficient for your new
> components, and this is showing up as an occasional IO/DMA error on
> the hard disk.
This could be the reason.
3. another reason: did you actually run a mke2fs with disk checking when
creating the huge partition during installation? Could be your Samsung
spinpoint is just broken somewhere at the 50GB region and the "simple
and fast" mke2fs just creating the inode table is not noticing this for
a weird reason.
from man mke2fs:
-c Check the device for bad blocks before creating the
file system. If this option is specified twice,
then a slower, read-write test is used instead of a fast
read-only test.
Please try this and report back if you found something.
There is also low level test programs of disk vendors where you can
stress test the brick to make sure it's not faulty.
After all: sorry for the inconveniences you had, but this looks like a
real bad hardware issue rather than a notoric software misbehaviour :)
Good luck,
Alex
--
[email protected] mailing list
