Description
This article describes how to handle an issue where 'get system status' output shows 'Log hard disk: Not available' when the physical hard disk is present in the Unit
This could cause issue while introducing the RMA unit or introducing the unit back in cluster after factory reset or flash format as the Hardware is same between both the units
Scope
All FortiGates with HDD.
Solution
If the FortiGate has one hard disk, it can be used for either disk logging or WAN optimization, but not both.
By default, the hard disk is used for disk logging.
When the hard disk is being used for WAN optimization, it displays 'Log hard disk: Not available' in the get system output.
# get sys status
Version: FortiGate-3000D v6.0.10,build0365,200617 (GA)
Virus-DB: 1.00000(2018-04-09 18:07)
Extended DB: 1.00000(2018-04-09 18:07)
Extreme DB: 1.00000(2018-04-09 18:07)
IPS-DB: 6.00741(2015-12-01 02:30)
IPS-ETDB: 6.00741(2015-12-01 02:30)
APP-DB: 6.00741(2015-12-01 02:30)
INDUSTRIAL-DB: 6.00741(2015-12-01 02:30)
Serial-Number: FGT3KD3Z16800075
IPS Malicious URL Database: 1.00001(2015-01-01 01:01)
Botnet DB: 1.00000(2012-05-28 22:51)
BIOS version: 05000004
System Part-Number: P17065-02
Log hard disk: Not available
Hostname: FGT3KD-1
Operation Mode: NAT
Current virtual domain: root
Max number of virtual domains: 10
Virtual domains status: 1 in NAT mode, 0 in TP mode
Virtual domain configuration: disable
FIPS-CC mode: disable
Current HA mode: standalone
Branch point: 0365
Release Version Information: GA
FortiOS x86-64: Yes
System time: Wed Sep 23 09:31:42 2020
# get hardware status
Model name: FortiGate-3000D
ASIC version: CP8
ASIC SRAM: 64M
CPU: Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
Number of CPUs: 40
RAM: 64469 MB
Compact Flash: 15331 MB /dev/sdb
Hard disk: not available
USB Flash: not available
Network Card chipset: Intel(R) Gigabit Ethernet Network Driver (rev.0003)
Network Card chipset: FortiASIC NP6 Adapter (rev.)
This prevents the units in forming HA cluster as the hardware is not same in this case.
The existing unit in the cluster would have 'Log hard disk: Not available' and the factory reset or RMA unit will have 'Log hard disk: Available'.
To confirm if the HDD is being used for WAN optimization, check using the following command.
diagnose hardware deviceinfo disk
Disk HDD1 ref: 255 447.1GiB type: SSD [ATA ADATA SX1000L] dev: /dev/sda
partition ref: 1 125.4GiB, 124.9GiB free mounted: Y label: WANOPTXX02F8ADD2 dev: /dev/sda1 start: 2048
partition ref: 2 127.4GiB, 127.4GiB free mounted: N label: dev: /dev/sda2 start: 267245568
partition ref: 3 169.9GiB, 169.9GiB free mounted: N label: dev: /dev/sda3 start: 534489088
To form HA between the peers, configure the HDD for WAN optimization on the RMA or factory reset unit.
config system storage
edit "HDD1"
set usage wanopt
end
The command above will make the HDD dedicated for WAN optimization and the disk memory will no longer be available for the logging.
Now the hardware will be similar and the HA shall be formed between the peers and allows to sync the configuration from the Master unit.
The output below provides an example of what should be expect from a unit with a working storage disk, when not using WAN optimization:
get sys status
Log hard disk: Available
diagnose hardware deviceinfo disk
Disk SYSTEM(boot) 14.9GiB type: SSD [ATA 16GB SATA Flash] dev: /dev/sda
partition 247.0MiB, 154.0MiB free mounted: N label: dev: /dev/sda1(boot) start: 1
partition 247.0MiB, 153.0MiB free mounted: Y label: dev: /dev/sda2(boot) start: 524289
partition ref: 3 14.2GiB, 13.8GiB free mounted: Y label: dev: /dev/sda3 start: 1048577
Disk SSD ref: 16 447.1GiB type: SSD [ATA INTEL SSDSC2KB48] dev: /dev/sdb
partition ref: 17 440.1GiB, 439.0GiB free mounted: Y label: LOGUSEDXF4DD35B9 dev: /dev/sdb1 start: 2048
diag hardware test disk
DISK
HDD Single Block Write/Read/Verify Test....................... PASS
File Test (data).............................................. PASS
File Test (data2)............................................. PASS
Logdisk File Test............................................. PASS
config system storage
edit "SSD"
set status enable
set media-status enable
set order 1
set partition "LOGUSEDXF4DD35B9"
set device "/dev/sdb1"
set size 450673
set usage log
next
end
The output below provides an example of when the disk is not being detected, and WAN optimization not being used, by the device and points out the output differences:
get sys status
Log hard disk: Not available <-----------------
diagnose hardware deviceinfo disk
Disk SYSTEM(boot) 14.9GiB type: SSD [ATA 16GB SATA Flash] dev: /dev/sda
partition 247.0MiB, 139.0MiB free mounted: N label: dev: /dev/sda1(boot) start: 1
partition 247.0MiB, 134.0MiB free mounted: Y label: dev: /dev/sda2(boot) start: 524289
partition ref: 3 14.2GiB, 13.9GiB free mounted: Y label: dev: /dev/sda3 start: 1048577
Total available disks: 1 <-----------------
Max SSD disks: 1 Available storage disks: 0 <-----------------
diag hardware test disk
DISK
File Test (data).............................................. PASS
File Test (data2)............................................. PASS
HDD Single Block Write/Read/Verify Test....................... PASS
Logdisk File Test............................................. N/A <-----------------
config system storage
edit "SSD"
set status enable
set media-status disable <-----------------
set order 1
set partition "LOGUSEDXBE2470AB"
set device ''" <-----------------
set size 450673
set usage log
next
end
Related document:
System storage - FortiGate CLI reference
