| 1 |
Richard Fish wrote: |
| 2 |
> On 11/27/06, Guido Doornberg <guidodoornberg@×××××.com> wrote: |
| 3 |
>> Well, I want to use Gentoo but i don't realy like the idea of spoiling |
| 4 |
>> my weekend by installing an OS thats gonna stop working 30 times |
| 5 |
>> booting later. |
| 6 |
> |
| 7 |
> I doubt this is really Gentoo-specific. |
| 8 |
Me too, i don't think it's Gentoo making this break. |
| 9 |
> |
| 10 |
>> So, does anyone know whats wrong here and how i can prevent that it |
| 11 |
>> happens again? |
| 12 |
See below. |
| 13 |
> |
| 14 |
> What kernel are you using? Can you post your emerge --info? |
| 15 |
> |
| 16 |
> My initial guesses are one of: |
| 17 |
> |
| 18 |
> 1. You are using some experimental kernel that is corrupting the filesystem |
| 19 |
He said he was installing 2006.0 so i doubt he was going for ~arch and |
| 20 |
testing kernel. |
| 21 |
> |
| 22 |
> or |
| 23 |
> |
| 24 |
> 2. That your old power supply is not sufficient for your new |
| 25 |
> components, and this is showing up as an occasional IO/DMA error on |
| 26 |
> the hard disk. |
| 27 |
This could be the reason. |
| 28 |
|
| 29 |
3. another reason: did you actually run a mke2fs with disk checking when |
| 30 |
creating the huge partition during installation? Could be your Samsung |
| 31 |
spinpoint is just broken somewhere at the 50GB region and the "simple |
| 32 |
and fast" mke2fs just creating the inode table is not noticing this for |
| 33 |
a weird reason. |
| 34 |
|
| 35 |
from man mke2fs: |
| 36 |
|
| 37 |
-c Check the device for bad blocks before creating the |
| 38 |
file system. If this option is specified twice, |
| 39 |
then a slower, read-write test is used instead of a fast |
| 40 |
read-only test. |
| 41 |
|
| 42 |
Please try this and report back if you found something. |
| 43 |
There is also low level test programs of disk vendors where you can |
| 44 |
stress test the brick to make sure it's not faulty. |
| 45 |
|
| 46 |
After all: sorry for the inconveniences you had, but this looks like a |
| 47 |
real bad hardware issue rather than a notoric software misbehaviour :) |
| 48 |
|
| 49 |
|
| 50 |
Good luck, |
| 51 |
|
| 52 |
Alex |
| 53 |
-- |
| 54 |
gentoo-amd64@g.o mailing list |
Archives