In the past days i could test an Asrock E350 mainboard, the Asrock
(almost) equivalent of the Sapphire board reported in this bug.
The problem mounting the initial drive is still present *but* if i
change hard disk everything is fine.
In my initial post i've written that i was not able to mount any disk
drive. At that time i had tested two hard disk: a 2.5" (main) and a 3.5"
(the alternative one).
But now with the new board i've troubles only with the 2.5" drive and
not with the 3.5". And the same happens if i remount both on the
Sapphire: the 2.5" one is the only that fails.
Mmh, i cannot remember why in the past i couldn't boot with the 3.5"
drive too...
Now i'm going to close this bug as failing drive but there are still two
strange things:
* the alleged failing drive works ok with Win7 (but could be that
Windows is more tolerant to some kind of troubles);
* the 3.5" disk, the one that works ok, shows an high amount on
Raw_Read_Error_Rate (170126688), Seek_Error_Rate (5409416) and
Hardware_ECC_Recovered (233395922) under smartctl.
I still think that could be a failing drive: if something will prove
that i'm wrong and that the problem is something that could be related
to the kernel, i'll reopen the bug.
Cesare.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e9b82d2.8000...@gmail.com
