UPS with TrueNAS

Max90

Explorer
Joined
Nov 21, 2020
Messages
75
Hi, I have an UPS Atlantis land a03-s1501 and I want to configure it with TrueNAS.
I would like the nas to shutdown when the ups battery is almost exhausted, very useful when the current is absent for a long time and therefore to safeguard the disks.

How can I do? can anyone help me?
I have already connected the nas also with the usb cable
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,740
There's a UPS configuration section in the UI. What did you try and what didn't work?
 

Max90

Explorer
Joined
Nov 21, 2020
Messages
75
There's a UPS configuration section in the UI. What did you try and what didn't work?
do you mean in the services menu -> UPS?
If yes, I don't know how to fill. Also I believe that the drivers that it offers me from the drop-down menu are not the same model as my ups.
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,740
Then the first step would be your UPS' documentation. Connection via USB might hint at a usb-hdi interface. If that is the case it is not guaranteed to work. The usb-hdi code in the NUT port for FreeBSD is quite outdated, as far as I know. I could not get it to work.

So steps for you to do:
  • check UPS docs
  • try with usb-hdi if applicable
  • if that works --> great
  • if not, check if the UPS has got a serial interface as an alternative ...
  • ...
Sorry, chances are low anyone has got that precise model, so you will have to experiment.

Open a shell, type dmesg<ENTER> right after you plugged in the USB cable. That should give you another hint at the interface type.
 
Joined
Jun 2, 2019
Messages
591
TrueNAS uses NUT for UPS monitoring

You will likely not find the exact model, but you can try the various drivers listed on the compatibility page.


Screen Shot 2021-07-31 at 10.13.05 AM.png
 

Max90

Explorer
Joined
Nov 21, 2020
Messages
75
Then the first step would be your UPS' documentation. Connection via USB might hint at a usb-hdi interface. If that is the case it is not guaranteed to work. The usb-hdi code in the NUT port for FreeBSD is quite outdated, as far as I know. I could not get it to work.

So steps for you to do:
  • check UPS docs
  • try with usb-hdi if applicable
  • if that works --> great
  • if not, check if the UPS has got a serial interface as an alternative ...
  • ...
Sorry, chances are low anyone has got that precise model, so you will have to experiment.

Open a shell, type dmesg<ENTER> right after you plugged in the USB cable. That should give you another hint at the interface type.
On the pdf I have it does not speak of usb-hdi but only of usb cable to be connected to the pc.
I ran the dmesg command, this is the result:
root@freenas[~]# dmesg ---<<BOOT>>--- Copyright (c) 1992-2020 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.2-RELEASE-p6 df578562304(HEAD) TRUENAS amd64 FreeBSD clang version 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611aa2) VT(vga): text 80x25 CPU: AMD Turion(tm) II Neo N40L Dual-Core Processor (1497.54-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x100f63 Family=0x10 Model=0x6 Stepping=3 Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> Features2=0x802009<SSE3,MON,CX16,POPCNT> AMD Features=0xee500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!> AMD Features2=0x837ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,NodeId> SVM: NP,NRIP,NAsids=64 TSC: P-state invariant real memory = 17179869184 (16384 MB) avail memory = 16295796736 (15540 MB) Event timer "LAPIC" quality 100 ACPI APIC Table: <HP ProLiant> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) random: unblocking device. Firmware Warning (ACPI): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20200430/tbfadt-748) ioapic0 <Version 2.1> irqs 0-23 on motherboard Launching APs: 1 Timecounter "TSC" frequency 1497541148 Hz quality 800 random: entropy device external interface kbd1 at kbdmux0 mlx5en: Mellanox Ethernet driver 3.5.2 (September 2019) nexus0 vtvga0: <VT VGA driver> on motherboard aesni0: No AES or SHA support. padlock0: No ACE support. cryptosoft0: <software crypto> on motherboard acpi0: <HP ProLiant> on motherboard acpi0: Power Button (fixed) acpi0: _OSC failed: AE_BUFFER_OVERFLOW cpu0: <ACPI CPU> on acpi0 attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.000000s Event timer "RTC" frequency 32768 Hz quality 0 hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 Event timer "HPET1" frequency 14318180 Hz quality 450 apei0: <ACPI Platform Error Interface> on acpi0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0 pci1: <ACPI PCI bus> on pcib1 vgapci0: <VGA-compatible display> port 0xe000-0xe0ff mem 0xf0000000-0xf7ffffff,0xfe8f0000-0xfe8fffff,0xfe700000-0xfe7fffff irq 18 at device 5.0 on pci1 vgapci0: Boot video device pcib2: <ACPI PCI-PCI bridge> irq 18 at device 6.0 on pci0 pci2: <ACPI PCI bus> on pcib2 bge0: <HP NC107i PCIe Gigabit Server Adapter, ASIC rev. 0x5784100> mem 0xfe9f0000-0xfe9fffff irq 18 at device 0.0 on pci2 bge0: CHIP ID 0x05784100; ASIC REV 0x5784; CHIP REV 0x57841; PCI-E miibus0: <MII bus> on bge0 brgphy0: <BCM5784 10/100/1000baseT PHY> PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Using defaults for TSO: 65518/35/2048 bge0: Ethernet address: e8:39:35:f0:8f:74 ahci0: <AMD SB7x0/SB8x0/SB9x0 AHCI SATA controller> port 0xd000-0xd007,0xc000-0xc003,0xb000-0xb007,0xa000-0xa003,0x9000-0x900f mem 0xfe6ffc00-0xfe6fffff irq 19at device 17.0 on pci0 ahci0: AHCI v1.20 with 6 3Gbps ports, Port Multiplier supported ahci0: quirks=0x22000<ATI_PMP_BUG,1MSI> ahcich0: <AHCI channel> at channel 0 on ahci0 ahcich1: <AHCI channel> at channel 1 on ahci0 ahcich2: <AHCI channel> at channel 2 on ahci0 ahcich3: <AHCI channel> at channel 3 on ahci0 ahcich4: <AHCI channel> at channel 4 on ahci0 ahcich5: <AHCI channel> at channel 5 on ahci0 ohci0: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fe000-0xfe6fefff irq 18 at device 18.0 on pci0 usbus0 on ohci0 usbus0: 12Mbps Full Speed USB v1.0 ehci0: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe6ff800-0xfe6ff8ff irq17 at device 18.2 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci0 usbus1: 480Mbps High Speed USB v2.0 ohci1: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fd000-0xfe6fdfff irq 18 at device 19.0 on pci0 usbus2 on ohci1 usbus2: 12Mbps Full Speed USB v1.0 ehci1: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe6ff400-0xfe6ff4ff irq17 at device 19.2 on pci0 usbus3: EHCI version 1.0 usbus3 on ehci1 usbus3: 480Mbps High Speed USB v2.0 isab0: <PCI-ISA bridge> at device 20.3 on pci0 isa0: <ISA bus> on isab0 pcib3: <ACPI PCI-PCI bridge> at device 20.4 on pci0 pci3: <ACPI PCI bus> on pcib3 ohci2: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fc000-0xfe6fcfff irq 18 at device 22.0 on pci0 usbus4 on ohci2 usbus4: 12Mbps Full Speed USB v1.0 ehci2: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe6ff000-0xfe6ff0ff irq17 at device 22.2 on pci0 usbus5: EHCI version 1.0 usbus5 on ehci2 usbus5: 480Mbps High Speed USB v2.0 amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb4 acpi_button0: <Power Button> on acpi0 ipmi0: <IPMI System Interface> on isa0 ipmi0: KCS mode found at mem 0x0 alignment 0x1 on isa ipmi0: couldn't configure I/O resource device_attach: ipmi0 attach returned 6 ipmi0: <IPMI System Interface> at iomem 0-0x1 on isa0 ipmi0: KCS mode found at mem 0x0 alignment 0x1 on isa ipmi0: couldn't configure I/O resource device_attach: ipmi0 attach returned 6 amdsbwd0: <AMD SB8xx/SB9xx/Axx Watchdog Timer> at iomem 0xfec000f0-0xfec000f3,0xfec000f4-0xfec000f7 on isa0 hwpstate0: <Cool`n'Quiet 2.0> on cpu0 Timecounters tick every 1.000 msec ZFS filesystem version: 5 ZFS storage pool version: features support (5000) ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled ugen2.1: <ATI OHCI root HUB> at usbus2 ugen4.1: <ATI OHCI root HUB> at usbus4 uhub0: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2 uhub1: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4 ugen1.1: <ATI EHCI root HUB> at usbus1 ugen0.1: <ATI OHCI root HUB> at usbus0 uhub2: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 uhub3: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0 ugen3.1: <ATI EHCI root HUB> at usbus3 uhub4: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3 ugen5.1: <ATI EHCI root HUB> at usbus5 uhub5: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus5 Trying to mount root from zfs:freenas-boot/ROOT/12.0-U4.1 []... Root mount waiting for: CAM usbus0 usbus1 usbus2 usbus3 usbus4 usbus5 bge0: link state changed to UP ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: <ST1000DM003-1CH162 CC46> ATA8-ACS SATA 3.x device ada0: Serial Number Z1D4C3JK ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 953869MB (1953525168 512 byte sectors) ada0: quirks=0x1<4K> ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: <ST1000DM003-1CH162 CC46> ATA8-ACS SATA 3.x device ada1: Serial Number Z1D4B0TM ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors) ada1: quirks=0x1<4K> ada2 at ahcich2 bus 0 scbus2 target 0 lun 0 ada2: <ST1000DM003-1CH162 CC46> ATA8-ACS SATA 3.x device ada2: Serial Number Z1D4B8KH ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 953869MB (1953525168 512 byte sectors) ada2: quirks=0x1<4K> ada3 at ahcich3 bus 0 scbus3 target 0 lun 0 ada3: <ST1000DM003-1CH162 CC46> ATA8-ACS SATA 3.x device ada3: Serial Number Z1D4B1VD ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada3: Command Queueing enabled ada3: 953869MB (1953525168 512 byte sectors) ada3: quirks=0x1<4K> uhub1: 4 ports with 4 removable, self powered uhub0: 5 ports with 5 removable, self powered uhub3: 5 ports with 5 removable, self powered Root mount waiting for: usbus1 usbus3 usbus5 uhub5: 4 ports with 4 removable, self powered uhub2: 5 ports with 5 removable, self powered uhub4: 5 ports with 5 removable, self powered ugen0.2: <CHICONY USB Keyboard> at usbus0 ukbd0 on uhub3 ukbd0: <CHICONY USB Keyboard, class 0/0, rev 2.00/2.00, addr 2> on usbus0 kbd2 at ukbd0 ugen2.2: <vendor 0xffff 010937> at usbus2 uhid0 on uhub0 uhid0: <vendor 0xffff 010937, class 0/0, rev 1.10/9.37, addr 2> on usbus2 Root mount waiting for: usbus3 ugen3.2: <SanDisk Ultra Fit> at usbus3 umass0 on uhub4 umass0: <SanDisk Ultra Fit, class 0/0, rev 2.10/1.00, addr 2> on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x8100 umass0:7:0: Attached to scbus7 da0 at umass-sim0 bus 0 scbus7 target 0 lun 0 da0: <SanDisk Ultra Fit 1.00> Removable Direct Access SPC-4 SCSI device da0: Serial Number 4C531001440104116552 da0: 40.000MB/s transfers da0: 14663MB (30031250 512 byte sectors) da0: quirks=0x2<NO_6_BYTE> intsmb0: <AMD SB600/7xx/8xx/9xx SMBus Controller> at device 20.0 on pci0 smbus0: <System Management Bus> on intsmb0 lo0: link state changed to UP GEOM_MIRROR: Device mirror/swap0 launched (2/2). GEOM_MIRROR: Device mirror/swap1 launched (2/2). GEOM_ELI: Device mirror/swap0.eli created. GEOM_ELI: Encryption: AES-XTS 128 GEOM_ELI: Crypto: software GEOM_ELI: Device mirror/swap1.eli created. GEOM_ELI: Encryption: AES-XTS 128 GEOM_ELI: Crypto: software hwpmc: SOFT/16/64/0x67<INT,USR,SYS,REA,WRI> TSC/1/64/0x20<REA> K8/16/48/0x1ff<INT,USR,SYS,EDG,THR,REA,WRI,INV,QUA> bge0: link state changed to DOWN bge0: link state changed to UP CPU: AMD Turion(tm) II Neo N40L Dual-Core Processor (1497.54-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x100f63 Family=0x10 Model=0x6 Stepping=3 Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> Features2=0x802009<SSE3,MON,CX16,POPCNT> AMD Features=0xee500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!> AMD Features2=0x837ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,NodeId> SVM: NP,NRIP,NAsids=64 TSC: P-state invariant Security policy loaded: MAC/ntpd (mac_ntpd) bridge0: Ethernet address: 02:b8:bd:87:61:00 epair0a: Ethernet address: 02:a9:a8:2f:70:0a epair0b: Ethernet address: 02:a9:a8:2f:70:0b epair0a: link state changed to UP epair0b: link state changed to UP epair0a: changing name to 'vnet0.1' bge0: promiscuous mode enabled bridge0: link state changed to UP vnet0.1: promiscuous mode enabled lo0: link state changed to UP epair1a: Ethernet address: 02:20:2e:69:90:0a epair1b: Ethernet address: 02:20:2e:69:90:0b epair1a: link state changed to UP epair1b: link state changed to UP epair1a: changing name to 'vnet0.2' epair1b: changing name to 'epair0b' vnet0.2: promiscuous mode enabled lo0: link state changed to UP epair2a: Ethernet address: 02:01:5c:2d:3b:0a epair2b: Ethernet address: 02:01:5c:2d:3b:0b epair2a: link state changed to UP epair2b: link state changed to UP epair2a: changing name to 'vnet0.3' epair2b: changing name to 'epair0b' vnet0.3: promiscuous mode enabled bge0: link state changed to DOWN lo0: link state changed to UP bge0: link state changed to UP vnet0.2: link state changed to DOWN epair0b: link state changed to DOWN epair1a: Ethernet address: 02:26:b7:1d:ef:0a epair1b: Ethernet address: 02:26:b7:1d:ef:0b epair2a: link state changed to UP epair2b: link state changed to UP epair2a: changing name to 'vnet0.3' epair2b: changing name to 'epair0b' vnet0.3: promiscuous mode enabled bge0: link state changed to DOWN lo0: link state changed to UP bge0: link state changed to UP vnet0.2: link state changed to DOWN epair0b: link state changed to DOWN epair1a: Ethernet address: 02:26:b7:1d:ef:0a epair1b: Ethernet address: 02:26:b7:1d:ef:0b epair1a: link state changed to UP[ICODE] I don't know if you can understand something.

@elvisimprsntr
how do i see if one of those drivers works after selecting it?
 
Last edited:

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,740
Nothing from your UPS at the bottom. Boot system without USB to UPS connected. Once it's up, connect UPS, then type dmesg ...
 

Max90

Explorer
Joined
Nov 21, 2020
Messages
75
Nothing from your UPS at the bottom. Boot system without USB to UPS connected. Once it's up, connect UPS, then type dmesg ...
if you want to know the port, I had already tested it some time ago when I tried to configure it. When I insert the cable it is the ugen 2.2
 

Attachments

  • screen.JPG
    screen.JPG
    63.5 KB · Views: 121

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,740
So it is this device:
Code:
uhid0 on uhub0
uhid0: <vendor 0xffff 010937, class 0/0, rev 1.10/9.37, addr 2> on usbus2

Which means you can try usb-hid or one of the devices from the NUT documentation that @elvisimprsntr linked. Like the A03-P551 model ...
 

Max90

Explorer
Joined
Nov 21, 2020
Messages
75
So it is this device:
Code:
uhid0 on uhub0
uhid0: <vendor 0xffff 010937, class 0/0, rev 1.10/9.37, addr 2> on usbus2

Which means you can try usb-hid or one of the devices from the NUT documentation that @elvisimprsntr linked. Like the A03-P551 model ...
how do i see if one of those drivers is okay after i select it from the drop down menu and save it?
There are 4 Atlantis drivers. After saving I get email notifications that the connection has been lost.
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,740
If it works then upsc will return the current status:
Code:
root@freenas[~]# upsc ups
battery.runtime: 90000.00
battery.runtime.elapsed: 0.00
battery.voltage: 27.10
device.mfr: CYBERPOWER
device.model: PR750ELCD
device.serial: ************
device.type: ups
driver.name: snmp-ups
driver.parameter.mibs: cyberpower
driver.parameter.pollinterval: 2
driver.parameter.port: 192.168.1.8
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: cyberpower MIB 0.1
driver.version.internal: 0.97
ups.firmware: CR01201EAD1
ups.mfr: CYBERPOWER
ups.model: PR750ELCD
ups.serial: ************
ups.status: OL
 

Max90

Explorer
Joined
Nov 21, 2020
Messages
75
If it works then upsc will return the current status:
Code:
root@freenas[~]# upsc ups
battery.runtime: 90000.00
battery.runtime.elapsed: 0.00
battery.voltage: 27.10
device.mfr: CYBERPOWER
device.model: PR750ELCD
device.serial: ************
device.type: ups
driver.name: snmp-ups
driver.parameter.mibs: cyberpower
driver.parameter.pollinterval: 2
driver.parameter.port: 192.168.1.8
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: cyberpower MIB 0.1
driver.version.internal: 0.97
ups.firmware: CR01201EAD1
ups.mfr: CYBERPOWER
ups.model: PR750ELCD
ups.serial: ************
ups.status: OL
your command is wrong..
if i try to use upsc ups@localhost instead:
- with the first driver: error ups unknown
- with the other three dirver: connection error refused
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,740
It uses the identifier you set in the UI. So probably upsc Atlantis or upsc Atlantis@localhost for you. The @localhost part is optional and it works for me exactly as I wrote. I have one UPS so I named it "ups" :wink:
 

Max90

Explorer
Joined
Nov 21, 2020
Messages
75
It uses the identifier you set in the UI. So probably upsc Atlantis or upsc Atlantis@localhost for you. The @localhost part is optional and it works for me exactly as I wrote. I have one UPS so I named it "ups" :wink:
if i try to use upsc Altantis or upsc Atlantis@localhost instead:
- with the first driver: error driver not connected
- with the other three dirver: connection error refused
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,740
Looks like your model is not supported, then. Does the manufacturer offer a network/SNMP add-on card? I don't buy $equipment that does not come with Ethernet, anymore.
 

Max90

Explorer
Joined
Nov 21, 2020
Messages
75
Looks like your model is not supported, then. Does the manufacturer offer a network/SNMP add-on card? I don't buy $equipment that does not come with Ethernet, anymore.
I do not know..
Fortunately, I only had to buy the spare battery because the ups was given to me by a friend. Otherwise I would have bought a better one.
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,740
Possibly you will have better luck with the NUT community:

They are quite Linux centric, though. If a patch & recompile is necessary, that means no luck with TrueNAS. But you could always use a Raspberry or similar running Linux, connect that to the UPS and configure TrueNAS as a slave.
 

Max90

Explorer
Joined
Nov 21, 2020
Messages
75
Possibly you will have better luck with the NUT community:

They are quite Linux centric, though. If a patch & recompile is necessary, that means no luck with TrueNAS. But you could always use a Raspberry or similar running Linux, connect that to the UPS and configure TrueNAS as a slave.
Possibly you will have better luck with the NUT community:

They are quite Linux centric, though. If a patch & recompile is necessary, that means no luck with TrueNAS. But you could always use a Raspberry or similar running Linux, connect that to the UPS and configure TrueNAS as a slave.
in what way? should i pair another machine with linux and connect the usb to this machine to make it work as a slave?
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,740
Yes. If the UPS works with Linux, that is. Get a cheap embedded system like a RasPi, connect to UPS, configure NUT software, configure TrueNAS as slave. If it works with Linux. 30-40 €/$/£ ...
 

Max90

Explorer
Joined
Nov 21, 2020
Messages
75
Yes. If the UPS works with Linux, that is. Get a cheap embedded system like a RasPi, connect to UPS, configure NUT software, configure TrueNAS as slave. If it works with Linux. 30-40 €/$/£ ...
ok but I should always leave another machine running. Please note that I use truenas as the operating system of my nas, on a USB stick connected. I could not connect another key with a linux distro always to the nas in your opinion?
 
Top