[Answered]System panic

[dwhite]

Occasionally a cosmic particle will fly though you hard drive and your system will fail. If you're like me you'll try and fix it. Depending on the track this charged particle leaves various things could happen. Many years ago I added a line to my autoexec.bat that tried to fix any damage these random events caused it occurs to me that Linux tools are more potent a few weeks ago I had to run fsck as root to even get my system to boot. It occurs to me that if I ran fsck routinely before that partition mounted system crashes would occur less.

[isadora]

Dwhite, are you trying to share an experience? If yes, please be more informative.
Or should it be acknowledged as an attempt, to start a query, for getting information, leading to an answer, for a question not clear to me, yet.

You understand? Please be explicit!!!

[wintpe]

dwhite

all unix based OS's used to run fsck on boot up.

tunefs can be used to set how many mounts you partitions will get before forsing a fsck on boot up.

the reason that fsck on boot up is no longer done everytime

journaling filesystems.

fsck or file system consistency check only needs to be done where the journal last time of update is before the last write to the disk indicating that there is something done to the disk not stored in the journal.

a cosmic partical theory, yes occationaly these cause electronics to do something unexpected.

to make you need an fsck even when the journal is OK, no.

as for harddisk errors that can cause a crash, well thats more bad blocks, nothing to do directly with file system consistency
although the two can sometimes reflect on each other.

ie a bad block can cause the file system to consistenly fail consistency checks, and will continue to do so up until the bad block
is mapped.

for this you use the badblocks program, but thats not something you want to run on boot up as you average boot time would be about 7 hours. Just my point of view.

regards peter