Re: Strange HD behavior
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 same problem with a Seagate SATA drive. When I installed Windows on the same drive, it would work fine. I even got the drive replaced by Seagate, but it did not solve the problem. After three drives, I found a page on the net which said that the sata driver in fbsd had some problems with smartmon. I disabled it in the bios and haven't had any problem since for the past 5 months. Haven't tried this smartmontools though Regards Gautham ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange HD behavior
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 that maybe there could be issues related to temperature. Is there > any sort of watchdog in FreeBSD that gets installed by default? =/ Has > anyone ever had a problem like this? > > Thanks for the answers / tips / help, but now I've got more questions. :) Smartmontools can show the temperature of a smart-enabled HDD. Healthd might be able to do that, too, but I'm not sure. Check the smart error-logs anyway. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange HD behavior
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 of watchdog in FreeBSD that gets installed by default? =/ Has anyone ever had a problem like this? Thanks for the answers / tips / help, but now I've got more questions. :) On 3/26/06, Matthias Fechner <[EMAIL PROTECTED]> wrote: > > 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 > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > [EMAIL PROTECTED]" > -- []'s, Luiz Eduardo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange HD behavior
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange HD behavior
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 the login > prompt and a few (2, i guess) messages of bad blocks somewhere in the /usr > filesystem (just as a side note: I chose the automatic partitioning scheme > after alocating some 15GB). > > So what bugs me is that my HD may be "dying" (or expiring, for that matter). > However, I never got any sort of bad block message while running Linux for > more than 6 months, though I've certainly experienced some weird behaviour > not noticed by a friend o' mine who has the same distro (note: I used to run > KDE 3.5.1 and he still run KDE 3.5.0). Besides, I installed 6.0 and I used > to get this very same behaviour a month or so ago. And even before that, I > used run 5.3 (I got no error messages whatsoever). > > Is there an OS agnostic HD diagnose tool that's reliable? > > The HD is a Seagate one. > > -- > []'s, > Luiz Eduardo > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > Google for seatools and mhdd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Strange HD behavior
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 the /usr filesystem (just as a side note: I chose the automatic partitioning scheme after alocating some 15GB). So what bugs me is that my HD may be "dying" (or expiring, for that matter). However, I never got any sort of bad block message while running Linux for more than 6 months, though I've certainly experienced some weird behaviour not noticed by a friend o' mine who has the same distro (note: I used to run KDE 3.5.1 and he still run KDE 3.5.0). Besides, I installed 6.0 and I used to get this very same behaviour a month or so ago. And even before that, I used run 5.3 (I got no error messages whatsoever). Is there an OS agnostic HD diagnose tool that's reliable? The HD is a Seagate one. -- []'s, Luiz Eduardo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
