Troubleshooting Configuration

After the system boots, a message appears stating that the configuration file is missing.

The node boots, but storage is not available on the node.

A hard drive in a node does not appear as available storage.

After adding a new hard drive to a node, some of the volumes do not mount.

After moving a volume between nodes, some volumes in the new node do not mount.

Verify each node has a node.cfg file on the USB stick and that disk.volumes is properly specified.

See Configuring the Nodes.

The volume must be greater than the minimum value specified by the disk.minGB parameter (64 GB by default) or it does not boot. Small disks can be booted by lowering the size value in disk.minGB.

If the vols specification is correct and the volume is greater than disk.minGB, this may be an issue with the amount of RAM in the node. Check the available RAM and verify it is sufficiently provisioned.

The node boots from the USB device but Swarm fails to start.

The node begins to boot but reports a "kernel panic" error and stops.

If using a CSN or custom PXE boot server, update the ramdisk size as mentioned at the bottom of this page:Swarm Storage 15.3.1 Release
These symptoms could indicate a compatibility issue with the hardware. Contact Swarm Support with the details of your hardware setup.

Some changes to the node.cfg file disappear after editing.

If a USB flash drive is removed from a computer without unmounting, changes can be lost. Use the method for your OS to stop and unmount the USB media before removing it.

The following alert displays in the Swarm Admin Console:
Local clock is out of sync with node ip-address

The following indicator displays for each node where the error occurs:

A clock synchronization issue exists between the cluster nodes.

The clock icon displays next to any node that sends a data packet that is more than three minutes offset from the reporting node's local clock. The local node logs a critical error.

Verify the Network Time Protocol (NTP) settings are correct and the cluster nodes can access the configured NTP server.

See Configuring an External Time Server.

A node hangs during boot while initializing ACPI services.

System hardware is conflicting with the Advanced Configuration and Power Interface (ACPI) interface.

To resolve this issue, add the argument acpi=off to the syslinux.cfg file on the USB flash drive (for local booting) or to the PXE configuration file (for network booting).

The Swarm node boots as having an unregistered license.

The license file is not in the Caringo directory on the USB drive, or the licenseFileURL option in the node or cluster configuration file is not set properly.

Inconsistent performance when using virtualized disks.

There may be timeout issues. Add the disk.deviceTimeout configuration parameter and increase the value as needed for your virtualization environment.