Bon vais donner un truc qu'on m'a indiqu� dans ce genre de cas. Ne pas rire.

Mettre le hd dans un sac isolant.

Mettre le tout une nuit au frigo

Sortir le hd et le mettre rapidement dans la machine

Le ghoster tout aussi rapidement

Avec un peu de bol tu aura une image 'acceptable' de laquelle tu pourra
pomper les datas.

Alain Barth�lemy said:
> Bonjour,
>
> Pour une fois, je ne suis pas le seul � avoir des probl�mes de disque dur.
> Mon
> fils y �cope aussi.
>
> Voila ce que dit dmesg lorsque le disque est mis en slave (hdb).
>
> Ce n'est pas Linux naturellement, juste ce que dit Linux lors du boot.
>
> Le disque est probablement tout-�-fait nase mais un sp�cialiste hardware a
> peut-�tre une suggestion. R�cup�rer les fichiers est probablement
> d�sesp�r�.
>
> #############################################################
>
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> hdb: recal_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: recal_intr: error=0x04 { DriveStatusError }
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> ide0: reset: success
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> end_request: I/O error, dev 03:40 (hdb), sector 2
> lost async page write due to I/O error on 03:40
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> hdb: recal_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: recal_intr: error=0x04 { DriveStatusError }
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> ide0: reset: success
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> hdb: recal_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: recal_intr: error=0x04 { DriveStatusError }
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> ide0: reset: success
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> end_request: I/O error, dev 03:40 (hdb), sector 4
> lost async page write due to I/O error on 03:40
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> hdb: recal_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: recal_intr: error=0x04 { DriveStatusError }
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> ide0: reset: success
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> hdb: recal_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: recal_intr: error=0x04 { DriveStatusError }
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> ide0: reset: success
> hdb: read_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: read_intr: error=0x04 { DriveStatusError }
> end_request: I/O error, dev 03:40 (hdb), sector 6
> lost async page write due to I/O error on 03:40
>
> --
> Alain Barth�lemy
> [EMAIL PROTECTED]
> http://bartydeux.be
> _______________________________________________________
> Linux Mailing List - http://www.unixtech.be
> Subscribe/Unsubscribe: http://www.unixtech.be/mailman/listinfo/linux
> Archives: http://www.mail-archive.com/[EMAIL PROTECTED]
> IRC: chat.unixtech.be:6667 - #unixtech
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> MailScanner thanks transtec Computers for their support.
>


-- 

[Alain Belkadi]

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

_______________________________________________________
Linux Mailing List - http://www.unixtech.be
Subscribe/Unsubscribe: http://www.unixtech.be/mailman/listinfo/linux
Archives: http://www.mail-archive.com/[EMAIL PROTECTED]
IRC: chat.unixtech.be:6667 - #unixtech

Répondre à