The system does not function properly due to file system errors. This article explains the method to fix file system errors specifically on the /store partition in STRM/JSA when rebooting the appliance does not resolve the issue.

fsck (file system check) is the system utility/tool used to check the consistency of a file system in Unix/Linux. fsck is automatically run by the system at boot time, so rebooting the system should be the first step in attempting a resolution.

This article explains the method to fix file system errors specifically on the /store partition in STRM/JSA when rebooting the appliance does not resolve the issue.

File system errors are usually caused by faulty hardware (bad disks), electrical problems, but most commonly we see the cause as nongraceful shutdowns in such cases as a crash, power loss (brownouts), or abruptly power-cycling the appliance.

To fix file system errors:

1. Stop STRM services using the following command:

# service tomcat stop
# service hostcontext stop
# service imq stop
# service postgresql stop

2. Unmount both /store and /store/tmp :

# umount /store/tmp
# umount /store


• Run fsck on specific partition (the df -kh command shows the partition table, run fsck to partition in which /store was mounted). In this case, /store was mounted to sda 7 and /store/tmp was mount to sda5, hence:

# fsck -fy /dev/sda7
# fsck -fy /dev/sda5

Note: Do not interrupt this process. It will take several hours to complete.

Options:
-f : Force checking even if filesystem is marked clean
-y : Assume "yes" to all questions

• Once the above command is successful, mount the partitions:

# mount /store
# mount /store/tmp

• Start STRM services:

# service postgresql start
# service imq start
# service tomcat start
# service hostcontext start

19-11-2025: Minor, non-technical edit