That sounds pretty swell to me. On top of that there are posts I've made pretty far back in this thread complaining about USB boot drives, so it's definitely time to move on.To mirror the operating system device, move to additional devices and press spacebar to select them also. If all of the selected devices are larger than 64 GiB and none are connected through USB, a 16 GiB swap partition is also created.
New alerts:
* Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44!/44!).
Aug 15 01:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44!/44!)
Aug 15 01:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44!/44!)
Aug 15 02:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44/44)
Aug 15 02:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44/44)
Aug 15 03:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44/44)
Aug 15 03:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44/44)
Aug 15 04:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44/44)
Aug 15 04:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44/44)
Aug 15 05:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 46 Celsius reached critical limit of 44 Celsius (Min/Max 44/46!)
Aug 15 05:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 46 Celsius reached critical limit of 44 Celsius (Min/Max 44/46!)
Aug 15 06:20:14 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 46 Celsius reached critical limit of 44 Celsius (Min/Max 44/46)
Aug 15 06:20:14 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 46 Celsius reached critical limit of 44 Celsius (Min/Max 44/46)
Aug 15 07:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44/46)
Aug 15 07:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44/46)
Aug 15 08:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44/46)
Aug 15 08:20:13 bns-citadel smartd[4100]: Device: /dev/da0 [SAT], Temperature 44 Celsius reached critical limit of 44 Celsius (Min/Max 44/46)
You read that right, LOWBATT signal sent while (as far as I can tell) there was no outage, and the battery was at 100% charge... And also the server didn't shut down like it otherwise is supposed to for LOWBATT.NOTIFICATION: 'LOWBATT'
UPS: 'ups'
Statistics recovered:
1) Battery charge (percent)
battery.charge: 100
2) Battery runtime (seconds)
battery.runtime: 3331
So it looks like I'm going to be placing all 6 4-gig DIMMs back with the original CPU, and all of the new 8-gig DIMMs on the riser card. I'm glad I checked, because otherwise I was going to do a split arrangement with 36GB next to each CPU.Dual CPU configurations (6 DIMM slots on MB plus 6 DIMM slots on Riser)
If configuration contains DIMMs of all the same size, populate in the following order: MB_DIMM1, Riser_DIMM1, MB_DIMM2,
Riser_DIMM2, MB_DIMM3, Riser_DIMM3, MB_DIMM4, Riser_DIMM4, MB_DIMM5, Riser_DIMM5, MB_DIMM6, Riser_DIMM6.
If configuration contains DIMMs of mixed sizes, populate the larger DIMMs in the dual-processor riser.
www.dell.com
* Failed to check for alert VolumeStatus:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/middlewared/plugins/alert.py", line 706, in __run_source
alerts = (await alert_source.check()) or []
File "/usr/local/lib/python3.8/site-packages/middlewared/alert/source/volume_status.py", line 31, in check
for vdev in await self.middleware.call("pool.flatten_topology", pool["topology"]):
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1238, in call
return await self._call(
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1206, in _call
return await self.run_in_executor(prepared_call.executor, methodobj, *prepared_call.args)
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1110, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
File "/usr/local/lib/python3.8/site-packages/middlewared/utils/io_thread_pool_executor.py", line 25, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.8/site-packages/middlewared/plugins/pool.py", line 438, in flatten_topology
d = deque(sum(topology.values(), []))
AttributeError: 'NoneType' object has no attribute 'values'
12.0 doesn't match the base system; it's on 12.2.Upgrading jails to 12.0 to match the base system.
You're confusing the old TrueNAS 11 documentation with the TrueNAS 12 CORE documentation... TrueNAS and FreeNAS are only the same product from 12.0 and the older TrueNAS (11 and before) was the Enterprise product (Now TrueNAS 12.0 Enterprise), which carries that limitation.Is that an indication that VMs will be leaving the community version of TrueNAS?
Since the guest VM disk is a ZVOL (block storage) TrueNAS can't see it and won't mount it.I cannot seem to figure out what is going on with the VM disk, it isn't available mounted anywhere I've checked.