Did the limits for RAM on Home edition get changed with SFOS 16.05.2 MR2? I'm only seeing 4GB after update. Still only showing 4GB after rolling back to SFOS 16.05.1 MR-1. I was seeing 6GB usable before upgrade.
console> system diagnostics show memory
MemTotal: 4995628 kB
MemFree: 1689396 kB
MemAvailable: 2617568 kB
SFVH_SO01_SFOS 16.05.2 MR-2# dmidecode -t 17
# dmidecode 2.12
SMBIOS 3.0 present.
# SMBIOS implementations newer than version 2.7 are not
# fully supported by this version of dmidecode.
Handle 0x0043, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0042
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: ChannelA-DIMM0
Bank Locator: BANK 0
Type: <OUT OF SPEC>
Type Detail: Synchronous
Speed: 2133 MHz
Manufacturer: 0467
Serial Number: 19123522
Asset Tag: 9876543210
Part Number: RMUA5110MB78HAF2400
Rank: 1
Configured Clock Speed: 2133 MHz
Minimum voltage: Unknown
Maximum voltage: Unknown
Configured voltage: 1.200 V
I am having the same issue. Sophos was using 8GB prior to the upgrade and after I upgraded (SFOS 16.05.1 MR-1 to 16.05.2 MR-2) I noticed the issue. In the BIOS I see 8GB, when Sophos boots it now is only using 4GB. Not sure what the issue is; I tried to downgrade the firmware and the issue persisted. Then I came to 16.05.2 MR-2 and it still shows 4GB. Running Sophos on a small box, not VMWARE.
I tried swapping out RAM to make sure my two DIMMS were not having issue, after the swap Sophos continues to use 4GB.
This does not appear to be an issue with the system but with the upgrade and noticing that other are having issues I am pointing this at the new firmware 16.05.2.
Has anyone found a solution or are we waiting for another firmware fix?
Just to provide another data point...
I upgraded my VMware based XG appliance from 16.05.1 MR-1 to 16.05.2 MR-2 and did NOT see this issue. Memory reported before and after the upgrade are identical. I notice that everyone reporting the issue is on a hardware appliance. Hopefully that can help point someone in the right direction.
Let's dig in and see if we can find something.
Post output by running two commands in the console.
console> system diagnostics show memory
console> system diagnostics show cpu
I see JD MaC has a point here, are you guys experiencing this on a hardware appliance? The above command will fetch the hardware information for us.
Finally, a memory test. Refer: https://community.sophos.com/kb/en-us/125025. Note: It may take 1-2 hour time to complete a full scan of 6 GB. Post the output.
Thanks
System has 8GB installed (2 x 4GB).
Was using 6GB before upgrade from 16.05.1 MR-1 to 16.05.2 MR-2
===================
console> system diagnostics show memory
MemTotal: 3922720 kB
MemFree: 539512 kB
MemAvailable: 1685256 kB
Buffers: 224608 kB
Cached: 970988 kB
SwapCached: 0 kB
Active: 2861868 kB
Inactive: 347436 kB
Active(anon): 2066852 kB
Inactive(anon): 42972 kB
Active(file): 795016 kB
Inactive(file): 304464 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 3101332 kB
SwapFree: 3101332 kB
Dirty: 512 kB
Writeback: 0 kB
AnonPages: 2013684 kB
Mapped: 130588 kB
Shmem: 96160 kB
Slab: 106720 kB
SReclaimable: 75916 kB
SUnreclaim: 30804 kB
KernelStack: 5016 kB
PageTables: 20040 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 5062692 kB
Committed_AS: 4898588 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 6572 kB
VmallocChunk: 34359702964 kB
DirectMap4k: 7780 kB
DirectMap2M: 4063232 kB
================================
console> system diagnostics show cpu
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Celeron(R) CPU J1900 @ 1.99GHz
stepping : 8
microcode : 0x811
cpu MHz : 1996.800
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 3993.60
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Celeron(R) CPU J1900 @ 1.99GHz
stepping : 8
microcode : 0x811
cpu MHz : 1996.800
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 3993.60
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Celeron(R) CPU J1900 @ 1.99GHz
stepping : 8
microcode : 0x811
cpu MHz : 1996.800
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 3993.60
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Celeron(R) CPU J1900 @ 1.99GHz
stepping : 8
microcode : 0x811
cpu MHz : 1996.800
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 3993.60
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
=====================
Memory diagnostics in Sophos Firewall (SFOS)
Sorry, but that is not going to be possible anytime soon.
Was using 6GB before upgrade from 16.05.1 MR-1 to 16.05.2 MR-2. Nothing wrong with my hardware, unless XG whacked my BIOS!
=====================
Hi David,
The limit is 6GB RAM and not 8 GB. Use a 4GB RAM and another 2GB of RAM instead of 2x4GB and let us know if that makes a difference.
Thanks
sachingurung said:The limit is 6GB RAM and not 8 GB. Use a 4GB RAM and another 2GB of RAM instead of 2x4GB and let us know if that makes a difference.
Wow!!!! Read your own documentation.
"Home Edition is limited to 4 cores and 6 GB of RAM. The computer can have more than this, but XG Firewall Home Edition will not be able to utilize it."
https://www.sophos.com/en-us/products/free-tools/sophos-xg-firewall-home-edition.aspx
After running a over a year with 8GB physical and utilizing 6GB all of a sudden this is not supported!!!
Please clarify.
Hi David,
I just wanted to verify if 2x4GB RAM caused the issue and we are on the same page. Only 6 GB of RAM is supported by the XG home edition.
Patience will be appreciated.
sachingurung said:I just wanted to verify if 2x4GB RAM caused the issue and we are on the same page. Only 6 GB of RAM is supported by the XG home edition.
Ok, thanks. I don't have a 2GB stick laying around, just to test.
Note that another poster has a single 8GB stick and is seeing the same 4GB limitation all of a sudden.
