FortiAnalyzer
FortiAnalyzer can receive logs and Windows host events directly from endpoints connected to EMS, and you can use FortiAnalyzer to analyze the logs and run reports.
heng
Staff
Staff
Article Id 195264

Description

 

This article discusses when the FortiManager/FortiAnalyzer hardware are being installed with a new RMA replacement disk and the disk does not rebuild by itself and how to fix it.
When the disk does not rebuild by itself, it will show a RAID status 'Degraded' as well as the disk number as 'Unused' even it able to detect the new disk size correctly. Degraded also means the hard drive is no longer being used by the RAID controller.
 
An example of the CLI output from FortiAnalyzer as follows with the RAID status query
Scope
 
FortiAnalyzer.
 
FAZ # diagnose sys raid status
Software RAID:
RAID Level: Raid-10
RAID Status: Degraded
RAID Size: 5589GB
File System: ext4 5501GB
 
Disk 0: Unused 2795GB
Disk 1: OK 2795GB
Disk 2: OK 2795GB
Disk 3: OK 2795GB


Solution

 
Sometimes, the newly installed disk is not properly detected by the system.
 
To fix it:
 
  1. Reboot the system.
  2. Reseat (slot-out/slot-in) the physical disk again to trigger the detection and the rebuild.
  3. Run CLI execute raid add-disk <disk no.> to add the disk manually.
 
For example disk 0 is the disk number that being replaced.
 
FAZ # execute raid add-disk 0
Added disk 0 to RAID.
 
  1. Run # diagnose sys raid status to check whether the rebuilding is started. 
 
For example, disk 0 will start the rebuilding, run the same command over time to check the status and  disk 0 will be visible as 'OK' if the rebuild is completed. 
 
FAZ # diagnose sys raid status
Software RAID:
RAID Level: Raid-10
RAID Status: Background-Rebuilding (0%)
RAID Size: 5589GB
File System: ext4 5501GB
 
Disk 0: Rebuilding 2795GB
Disk 1: OK 2795GB
Disk 2: OK 2795GB
Disk 3: OK 2795GB
 
  1. If the above does not help, contact Fortinet support to further troubleshoot. 
Contributors