Reference Information › CA AppLogic Support Knowledge Base › Overview of Support Knowledge Base › Read Only File System on Application - VDS - .boot Device

Read Only File System on Application - VDS - .boot Device

Usually reported on <application name>.boot

1. Stop the failed application
2. Mount the volume as a md device: 3tctl mount sv dev-tuxedomedia.class.VDS64_CENTOS50.boot

   mount_id = /dev/md1
   APPLOGIC RESTRICTED AREA
   

   (customer shouldn't use 3tctl, they would need to attach it to an appliance and run a fsck from it instead)

3. Run a manual fsck on the device: fsck -y -f /dev/md1 -C 0

   -y = answer yes to all questions, -f = force check even if marked clean, -C 0 (zero) = provides progress indicator
   

   This process found many journal inode issues and fixed them. Run it multiple times until no further errors are reported.

4. Unmount the volume from the md device: 3tctl unmount sv dev-tuxedomedia.class.VDS64_CENTOS50.boot
5. Start the application: 3t app start dev-tuxedomedia

   Building application...
   Configuring application...Done
   Loading application...
   Scheduling application...
   Starting application dev-tuxedomedia
   main.vds64_centos50 started
   

   Application dev-tuxedomedia started successfully

   Took about 30 - 45 seconds to fully start.