-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting Guide
This page provides solutions for common issues that may occur with the TrueNAS server.
Symptoms:
- ZPool shows as DEGRADED in
zpool status - One or more drives show as UNAVAIL or FAULTED
Troubleshooting Steps:
-
Identify the failed drive:
zpool status -
Check if the drive is physically accessible:
smartctl -a /dev/[drive_id] -
Verify the physical location using the Physical Drive Layout document
-
Replace the drive following the Drive Replacement Procedure
Symptoms:
-
zpool statusshows checksum errors - Files may be corrupted
Troubleshooting Steps:
-
Run a scrub to attempt automatic repairs:
zpool scrub [pool_name] -
Check which files are affected:
zpool status -v [pool_name] -
If errors persist after scrub, check drive health:
smartctl -a /dev/[drive_id] -
Consider replacing the drive if SMART tests indicate issues
Symptoms:
- Unable to import ZPool after system restart
- "Pool cannot be imported" error
Troubleshooting Steps:
-
Try forcing the import:
zpool import -f [pool_name] -
If that fails, try recovery mode:
zpool import -F [pool_name] -
Check SAS connections and expander status (see SAS Expander Configuration)
-
Verify all drives are detected:
camcontrol devlist
Symptoms:
- Drive missing from
camcontrol devlist - Drive missing from TrueNAS web interface
Troubleshooting Steps:
-
Check physical connection:
- Verify drive is properly seated in slot
- Check SAS cable connections
- Inspect SAS expander LEDs
-
Verify SAS expander can see the drive:
sas2ircu [adapter_id] DISPLAY -
Try reseating the drive or moving to a different slot
-
Replace SAS cables if necessary
Symptoms:
- Multiple drives suddenly unavailable
- SAS expander error LEDs lit
Troubleshooting Steps:
-
Check SAS expander status:
sas2ircu LIST -
Verify all SAS cables are properly connected
-
Try restarting the system:
shutdown -r now -
If issues persist, try replacing SAS cables or the expander
Symptoms:
- High temperature warnings in system logs
- Fans running at high speed
- System throttling or shutting down
Troubleshooting Steps:
-
Check system temperatures:
ipmitool sdr type "Temperature" -
Verify all fans are operational:
ipmitool sdr type "Fan" -
Check for dust buildup in the system
- Clean air intakes and exhaust vents
- Ensure proper airflow in the server room
-
Verify ambient temperature is within acceptable range (18-27°C)
Symptoms:
- File transfers are slower than expected
- Applications experience lag when accessing data
Troubleshooting Steps:
-
Check ZPool I/O statistics:
zpool iostat -v 5 -
Verify ZFS ARC (cache) usage:
arc_summary -
Check for fragmentation:
zpool list -v -
Consider adding or expanding L2ARC (cache) or SLOG (ZIL) devices
Symptoms:
- System feels sluggish
- High CPU usage shown in top or in TrueNAS dashboard
Troubleshooting Steps:
-
Identify processes using high CPU:
top -o cpu -
Check if deduplication is enabled (can be CPU intensive):
zfs get dedup [pool_name] -
Verify compression settings:
zfs get compression [pool_name] -
Consider adjusting ZFS dataset properties or upgrading CPU if necessary
Symptoms:
- Slow file transfers over network
- Timeouts when accessing shares
Troubleshooting Steps:
-
Check network interface status:
ifconfig -
Test network speed:
iperf3 -c [client_ip] -
Verify jumbo frames if enabled:
ping -s 8972 [gateway_ip] -
Check for network errors:
netstat -i
Symptoms:
- Unable to access SMB shares
- Permission denied errors
Troubleshooting Steps:
-
Check SMB service status:
service samba_server status -
Verify permissions on the dataset:
ls -la /mnt/[pool_name]/[dataset_name] -
Check SMB configuration:
midclt call smb.config -
Restart SMB service:
service samba_server restart
Symptoms:
- System fails to boot
- Boot loop
Troubleshooting Steps:
- Access the boot menu by pressing F8 during startup
- Select a previous boot environment
- If successful, investigate what caused the current boot environment to fail
- Create a new boot environment before making system changes
Recovery Steps:
- Access the TrueNAS web interface
- Navigate to System > General > Upload Config
- Select the previously saved configuration file
- Restore the configuration
- Reboot the system when prompted
Recovery Steps:
- Check all hardware for damage
- Power on the system
- Verify all ZPools import correctly:
zpool import -f [pool_name] - Run a scrub on all pools:
zpool scrub [pool_name] - Check system logs for errors:
cat /var/log/messages
Recovery Steps:
- Do not make any changes to the failed pool
- Try importing the pool in read-only mode:
zpool import -o readonly=on [pool_name] - If successful, copy critical data to another storage
- If unsuccessful, try recovery mode:
zpool import -F [pool_name] - Consider professional data recovery services if critical data cannot be recovered
Note: This is a template. Please replace with your actual troubleshooting procedures.