* the system did not start; I think the button was stuck and what I
could hear (very gentle noise; I had to put my ears close to the box)
that the power supply and CD-rom got power for a second at every few second
* than I took a hammer :-) joke; applied some force on the power-on
button and the system was turned off; then I could turn the system on
* at the startup I got some massage that the file system check failed,
press something to enter a shell to correct (run the fschk manually?);
but I pressed the other something (cntr-d?) and the system booted up
normally
* I backed up my data
* This morning I tried to figure out what was the problem, but I could
not find anything via dmesg - everything seems to be normal; sda was
brought up normally w journaling - based on dmesg.
How could I figure out the problem, how can I be relaxed about my data
and using that hard disk? I think the hd should be ok, not very old (max
2 year old)... I did not dare to restart my system yet :-)
smartctl -t long -d sat /dev/sda -T permissive
smartctl -d sat /dev/sda --all -T permissive
Hugo
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
10-28-2008, 06:25 PM
Shams fantar
sda failure - no log
Tamas Hegedus wrote:
> Hi,
>
> Last night, very late :-) I did the following:
>
> * press the power-on button
>
> * the system did not start; I think the button was stuck and what I
> could hear (very gentle noise; I had to put my ears close to the box)
> that the power supply and CD-rom got power for a second at every few
> second
>
> * than I took a hammer :-) joke; applied some force on the power-on
> button and the system was turned off; then I could turn the system on
>
> * at the startup I got some massage that the file system check failed,
> press something to enter a shell to correct (run the fschk manually?);
> but I pressed the other something (cntr-d?) and the system booted up
> normally
>
> * I backed up my data
> * This morning I tried to figure out what was the problem, but I could
> not find anything via dmesg - everything seems to be normal; sda was
> brought up normally w journaling - based on dmesg.
>
> How could I figure out the problem, how can I be relaxed about my data
> and using that hard disk? I think the hd should be ok, not very old
> (max 2 year old)... I did not dare to restart my system yet :-)
>
> Thanks for your suggestions in advance,
> tamas
>
>
Use smartcl. (the package to install is smartmontools)
For an IDE hard disk :
smartctl --smart=on --offlineauto=on --saveauto=on /dev/hda
smartctl --test=long /dev/hda
[You wait for time that has been indicated with the previous command)
smartctl --attributes --log=selftest --quietmode=errorsonly /dev/hda
For a SATA hard disk, you just have to add the "-d ata" option to each
command.
Regards,
--
http://snurf.info
"Civil Engineering section" project : http://civil-e-section.org
« A book is like a garden carried in the pocket. »
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
10-28-2008, 08:29 PM
Tamas Hegedus
sda failure - no log
Thanks for the smartctl suggestions - self-test performed - no error was
logged :-)
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
10-29-2008, 04:48 AM
"Douglas A. Tutty"
sda failure - no log
On Tue, Oct 28, 2008 at 10:36:17AM -0400, Tamas Hegedus wrote:
> * I backed up my data
> * This morning I tried to figure out what was the problem, but I could
> not find anything via dmesg - everything seems to be normal; sda was
> brought up normally w journaling - based on dmesg.
>
> How could I figure out the problem, how can I be relaxed about my data
> and using that hard disk? I think the hd should be ok, not very old (max
> 2 year old)... I did not dare to restart my system yet :-)
I'd stress-test the drive. I use a lot of old hardware so have this
down pat: boot with a live CD (I use grml) on boxes that boot CD, and a
custom boot set (based on Woody) for older boxes that only boot floppy.
on one VT, run e2fsck -c -c (the double -c causes it to do a slow read
write verify bad-block test so that each sector gets read and written).
Do this for each filesystem you have.
On another VT, run tail -f /var/log/syslog and watch for drive errors.
If all goes well, reboot the system and do a long smartclt test and see
if the drive has recorded inordinate errors. Also check the drive temp
after all that activity.
Remember, a SMART error is a good indication of a problem, but the lack
of a SMART error is not necessarily a good inidcation of a lack of a
problem.
Doug.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
sda failure - no log
