Running a Filesystem Check on Mac OS X

(UP)

Filesystem damage is a common cause of problems in an active Kerio MailServer message store. It can cause bizarre problems with no logical explanation such as read errors on files that root should be able to read, incorrect available disk space, crashes, or odd problems opening files.

All of these symptoms can be caused by really dangerous things such as bad memory, CPU, motherboard, drives, fiber switch, drive shelves, fiber/firewire/usb drive cables.

Check the Filesystem!

A way to check the filesystem not only helps to diagnose such difficult problems, but it can be an early warning for knowing if there is bad hardware corrupting your data. It requires some downtime, so you will need to schedule it.

Try to preserve output from FSCK to show Kerio Technical support. It can be almost impossible to save it to a file. If you have a digital camera handy, try to snap a shot of the errors and send us the snapshot.

What if fsck fixes something?

It could be something simple... such as a dirty shutdown (the system crashed, a blackout caused a loss of power, etc...) First, run fsck again. Does it fix things the second time?

It could be a serious hardware problem. If fsck fixed something, then run fsck again immediately, then schedule another fsck in 7 days. Does it fix something again every time? If so then some piece of hardware is causing filesystem corruption, and possibly data corruption of your files.

Start testing hardware:

Some Related Internet Links