netboot.xyz VS nut

I learned about https://netboot.xyz/ the other day. Worked fantastic when I didn't have a big enough thumb drive. Not exactly the same though.

I replied to a reply of yours with this same info, but since you’re both sorta asking the same thing, I’ll post it here for you also.

https://netboot.xyz/

https://github.com/netbootxyz/netboot.xyz

Knew about http://netboot.xyz, but had no idea iVentoy existed. Good to know.

Set the computer to PXE boot, or use a boot image with iPXE (such as netboot.xyz). That would quickly rule out a problem with Debian or the Linux kernel (at least until you download and boot one). I don't know anything about your network setup, but making sure DHCP is enabled on your router and there are enough unreserved IP addresses would probably help.

Hey thanks for the detailed response. You're saying you boot FCOS on bare metal over PXE, correct? I've thought about trying that approach, but have little experience with PXE and TFTP. I just checked out netboot.xyz and it looks surprisingly easy to get going. Last time I played around with PXE I used Synology's TFTP server and, while I got it working, I was more confused by the end than when I started. I think actually learning PXE end-to-end and understanding what I am doing there would be a solid foundation for building my environment the right way.

For netbooting we rely on a netboot.xyz inspired ipxe based setup.

[[UPDATE]]: The fix was as 'simple' as going into the 'bios', and selecting 'add a boot option', which automatically came up with the correct EFI file/path, then putting it at the top of the boot order. 'Simple' it wasn't, many new and temporary instances brought online while digging my way through it all, and finally just going with a brand new Debian Bookworm and migrating my data over from the old disk file. At least I learned a lot about recovering from this weird circumstance. The incorrect EFI file/path must be an artifact of using netboot.xyz to install Deb Bookworm over a previously provisioned Ubuntu instance. Makes sense I guess. Still loving netboot.xyz as a super fast way to spin up an unsupported OS.

I learned about GRML only a few years ago. Absolutely love the mixture of power and minimalism. Here is the only ISO which increases my mileage even more: https://netboot.xyz

> what software do you recommend for gnu/linux to take input from the UPS to tell the laptop to shutdown?

https://networkupstools.org/

The Synology software is based on N.U.T. https://networkupstools.org and the Plus 1100 (listed on NUT as the Easy Power 1200) is supported in the native package with the 'blazer' driver. If you have the skills, I would SSH into the NAS and see if the device is 'noticed' or better yet recognised by the USB sub-system when you plug it it. (Normal Linux would use the lsusb command to see devices but I have no NAS handy to see if this is valid on the Synology)

Others have answered the hardware part of your question. I have not seen much mention about the software to control graceful shutdowns. For this I suggest you look at the ”Network UPS Tool” (NUT for short) project (https://networkupstools.org/). It is mostly manufacturer agnostic with clients for a vast array of hardware components.

You're looking for NUT.

Network UPS Tools is one option: https://networkupstools.org/

APC is giving me pre-nut clarity.

So no, the NAS does not monitor the battery level. The UPS does that. The NAS just acts on the messages it receives from the UPS via Synology's version of NUT - Network UPS Tools (https://networkupstools.org/). The NAS will first receive the ON_BATTERY/POWERFAIL signal. Then, eventually the BATTERY_LOW signal at which time the UPS will shutdown. So you really need to set a time for it to shut down *BEFORE* you get BATTERY_LOW.