Hi all... I have seen a very strange thing. I was trying hdparm -tT on a SATA disk, it did the buffered part OK, and hanged my box in the non-buffered measure. After waiting some minutes, I did a SysRQ-s-u-b, and the the disk began to give many read errors on sectors and could not boot because journal was not present and many other errors. After some warm and cold boots, finally the box came up correctly. I suspect that something that hdparm did left my disk dumb. But what ? I will keep away from hdparm for some time... Any idea ? TIA -- J.A. Magallon <jamagallon()able!es> \ Software is like sex: werewolf!able!es \ It's better when it's free Mandriva Linux release 2006.1 (Cooker) for i586 Linux 2.6.13-jam8 (gcc 4.0.1 (4.0.1-5mdk for Mandriva Linux release 2006.0))
Attachment:
pgpzAL3gytMEi.pgp
Description: PGP signature
- Follow-Ups:
- Re: hdparm almost burned my SATA disk
- From: Mark Lord <[email protected]>
- Re: hdparm almost burned my SATA disk
- From: "J.A. Magallon" <[email protected]>
- Re: hdparm almost burned my SATA disk
- Prev by Date: Re: uinput crash and fix
- Next by Date: Re: hdparm almost burned my SATA disk
- Previous by thread: [BUG] PDC20268 crashing during DMA setup on stock Debian 2.6.12-1-powerpc
- Next by thread: Re: hdparm almost burned my SATA disk
- Index(es):
 |