Filesystem corrupts after power failure 2363

Unruh

They are *mainly* firewalls, but some do other small things as well, (eg hylafax, small mail server, small amount of proxy caching etc) so not sure if a read only system would work.

FSCK doesn't seem to help. When the last box died, booting from a live CD fsck wouldn't check the drive, but I forget what the error was. Something about not being able to find the label. I've also used fsck on test software raid systems and managed to toast the parbreastions without it warning me, so I'm a bit wary of it! Also as these are all ext3 I thought that didn't need fsck because of the journalling?

re grub, that box hung straight after the bios post, booting from a live disk and following the instructions on reinstalling grub fixed it which would imply that the grub was toasted to me :) Once grub was reinstalled the box was OK.

Is it not worthing sync'ing the boot and parbreastions then, from what I've read elsewhere it would help, but someone earlier seemed to think it wouldn't make any difference. The parbreastion's always seem to be intact and can be mounted from Live disks, just won't mount when you boot. And making theboot parition read-only would help by the sound of it?

cheers

mark