Re: Strange HD behavior

2006-03-29 Thread Gautham Ganapathy
On Sat, 2006-03-25 at 19:06 -0300, Luiz Eduardo Guida Valmont wrote: > Hi, > > its dependancies) overnight. But I woke up the next day to find the login > prompt and a few (2, i guess) messages of bad blocks somewhere in the /usr > filesystem > > The HD is a Seagate one. > I used to have the

Re: Strange HD behavior

2006-03-26 Thread Andrew Pantyukhin
On 3/26/06, Luiz Eduardo Guida Valmont <[EMAIL PROTECTED]> wrote: > I just tried the seagate tools (seatools). While it did not find any bad > block, it nevertheless hung after completing the process, just before > showing any report. So I think my HD is okay. BTW, it's a ST380022A. > > I thought t

Re: Strange HD behavior

2006-03-26 Thread Luiz Eduardo Guida Valmont
I just tried the seagate tools (seatools). While it did not find any bad block, it nevertheless hung after completing the process, just before showing any report. So I think my HD is okay. BTW, it's a ST380022A. I thought that maybe there could be issues related to temperature. Is there any sort o

Re: Strange HD behavior

2006-03-25 Thread Matthias Fechner
Hello Luiz, * Luiz Eduardo Guida Valmont <[EMAIL PROTECTED]> [25-03-06 19:06]: > Is there an OS agnostic HD diagnose tool that's reliable? > > The HD is a Seagate one. You can try /usr/ports/sysutils/smartmontools and the tool from seagate itself. Best regards, Matthias ___

Re: Strange HD behavior

2006-03-25 Thread Andrew Pantyukhin
On 3/26/06, Luiz Eduardo Guida Valmont <[EMAIL PROTECTED]> wrote: > Hi, > > I've recently (2 or 3 days ago) installed 6.1-BETA4 (from bootonly CD). The > installation process went on flawlessly. Then I left kdebase3 compiling (and > its dependancies) overnight. But I woke up the next day to find th

Strange HD behavior

2006-03-25 Thread Luiz Eduardo Guida Valmont
Hi, I've recently (2 or 3 days ago) installed 6.1-BETA4 (from bootonly CD). The installation process went on flawlessly. Then I left kdebase3 compiling (and its dependancies) overnight. But I woke up the next day to find the login prompt and a few (2, i guess) messages of bad blocks somewhere in t