Se connecter
Inscription
Mot de passe perdu
Supprimer un message
P'tain leur disque est bel et bien mort, fsck est sans appel 
Le prob c'est que si c'est si grave que ça (c'est plus que quelques clusters défectueux on dirait), je ne vais même pas pouvoir le wiper si ça se trouve...
Quoiqu'ils ont l'air de dire qu'il y a moyen d'outrepasser de gérer les clusters défect mais je ne pige pas bien
###########
reiserfsck --check started at Fri Jan 11 16:40:05 2008
###########
Replaying journal..
Reiserfs journal '/dev/md0' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..
The problem has occurred looks like a hardware problem. If you have
bad blocks, we advise you to get a new hard drive, because once you
get one bad block that the disk drive internals cannot hide from
your sight,the chances of getting more are generally said to become
much higher (precise statistics are unknown to us), and this disk
drive is probably not expensive enough for you to you to risk your
time and data on it. If you don't want to follow that follow that
advice then if you have just a few bad blocks, try writing to the
bad blocks and see if the drive remaps the bad blocks (that means
it takes a block it has in reserve and allocates it for use for
of that block number). If it cannot remap the block, use badblock
option (-B) with reiserfs utils to handle this block correctly.
bread: Cannot read the block (43384833): (Input/output error).
Abandon (core dumped)
reiserfsck --check started at Fri Jan 11 16:40:05 2008
###########
Replaying journal..
Reiserfs journal '/dev/md0' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..
The problem has occurred looks like a hardware problem. If you have
bad blocks, we advise you to get a new hard drive, because once you
get one bad block that the disk drive internals cannot hide from
your sight,the chances of getting more are generally said to become
much higher (precise statistics are unknown to us), and this disk
drive is probably not expensive enough for you to you to risk your
time and data on it. If you don't want to follow that follow that
advice then if you have just a few bad blocks, try writing to the
bad blocks and see if the drive remaps the bad blocks (that means
it takes a block it has in reserve and allocates it for use for
of that block number). If it cannot remap the block, use badblock
option (-B) with reiserfs utils to handle this block correctly.
bread: Cannot read the block (43384833): (Input/output error).
Abandon (core dumped)
Le prob c'est que si c'est si grave que ça (c'est plus que quelques clusters défectueux on dirait), je ne vais même pas pouvoir le wiper si ça se trouve...
Quoiqu'ils ont l'air de dire qu'il y a moyen d'outrepasser de gérer les clusters défect mais je ne pige pas bien
