Nogami

No issues upgrading either my main server or my backup (both are supermicro platforms).

Canadian here. Most of our banking is electronic in Canada and I just don’t physical currency much. I mostly stuck with using paper currency in Japan this past summer.

I couldn’t find a quick and easy way to easily convert my coins back to paper yen before the flight home so used up some of my baggage weight allowance with a big sack of Japanese coins. Any tips?

I don’t mind paying a percentage to do it but don’t want to count myself. If there’s a shortage of coins in Japan right now it’s because all your yen are in my luggage.

Banks here used to have machines to do it with Canadian coins but with few people using coins now they all got removed.

Plan B was to pour my 2kg sack-o-yen into a temple donation box and reap the good Karma for years to come.

Got some extreme warm weather coming and I'm going to be out of town for a while. Can't trust the inlaws staying here to do anything server related.

Anyone know of a plugin or script to automatically shutdown if the system temp is too high?

Bug fixes

emhttpd: remove "unraid" from reserved names list
emhttpd: properly handle "ERROR" strings in 'btrfs filesystem show' command output
emhttpd: prevent cmdStart if already Started
network: Revised service reload functionality: ensures the services are only reloaded once
network: rc.library: read IP addresses directly from interfaces instead of file
network: NTP: fix listening interfaces
network: NTP: exclude WG tunnels and user defined interfaces
network: NTP: add interface name in config
network: SSH: add interface name in config
webgui: fix PHP8 warning in UPS Settings page
webgui: Dashboard: show ZFS percentage based on c_max value
webgui: Dashboard: suppress coloring of ZFS utilization bar
webgui: Dashboard: olther misc fixes

Linux kernel

version 6.1.34

Base Distro

ttyd: version 1.7.3 (fixes issue of invisible underbar characters with certain FireFox versions)

Security updates

ca-certificates: version 20230506
curl: version 8.1.2 (CVE-2023-28322 CVE-2023-28321 CVE-2023-28320 CVE-2023-28319)
git: version 2.35.8 (CVE-2023-25652 CVE-2023-25815 CVE-2023-29007)
ntp: version 4.2.8p17 (CVE-2023-26551 CVE-2023-26552 CVE-2023-26553 CVE-2023-26554 CVE-2023-26555)
openssl: version 1.1.1u (CVE-2023-2650)
openssh: version 9.3p1
php: version 8.2.7
libX11: version 1.8.6 (CVE-2023-3138)
libssh: version 0.10.5 (CVE-2023-1667 CVE-2023-2283)
zstd: version 1.5.5

So just to get some content going on Lemmy, and get contributing here, thought I'd write a bit about going to 6.12 RC with a ZFS pool and what I've done on my server to try and make use of that newfound ability...

Original configuration (pre 6.12):

• 17 unRAID array drives in XFS format
• dual parity
• 2 NVMEs (cache and appdata are separate) in XFS format
• XFS formatted
• Backed-up daily with rsync to a second unRAID server on my LAN.

New configuration 6.12 (currently RC8)

• 13 unRAID array drives in XFS format
• dual parity
• 4 x 8TB drives in a ZFS raidz1 pool
• 2 NVMEs (cache and appdata are separate) in ZFS format with compression enabled.
• Backed-up hourly with ZFS snapshots

Why the change?

• Going to ZFS for my "important data", which is to say, personal documents, family photos (yay babies!)
• Enables snapshots to help aid in the event of a "soft" data error (file being accidentally deleted, overwritten, or maliciously damaged by software, etc, bitrot, etc). Also enables extremely quick replications to my backup server.
• Faster access to those personal documents with data striped across 4 drives.
• Keeping main array as unRAID array drives for "easily replaceable data" (mostly media files, linux ISOs, etc.) so I can expand it easily by chucking another drive in my server or up-sizing an older drive easily.

Enhanced backups through ZFS:

• ZFS has some rather remarkable options for data backups that are enabled by the snapshot capability of the filesystem. Rather than sending individual files across the network and having to laboriously calculate the differences between each file on the dataset (part of the ZFS volume), you can essentially just send the "difference" between snapshots which can stream between servers in a very short time (usually only a couple of seconds in my case).

This means I have my system continually backed-up on an hourly basis, with saved snapshots every hour, and every day/month for half a year.

Plugins in use

The current unraid RC8 supports ZFS pools, however GUI support for managing ZFS pools is lacking. I'm using the following plugins and tools to accomplish everything (available through App installs):

• ZFS Master for Unraid, makes most ZFS operations a GUI interaction rather than terminal. I've heard rumblings that unRAID may acquire/in-house this plugin to add the functionality to the GUI. It would be worthwhile.
• Sanoid, automatically handles ZFS snapshots, as well as rotating snapshots based on the number of required snapshots per month and/or day. Enables sending ZFS snapshots to a backup server and rotating those snapshots as well to ensure continuity of data. Requires a bit of config file editing by hand to make it work, and setting-up a cron script but nothing difficult (it's well-documented) and was about 5 min to set up successfully.

Backup thoughts

RAID (of any type) is not backup. That said, I have part of the "3-2-1" backup strategy automatically enabled here, with my main server backing up the "important stuff" to a separate backup server also running unRAID. That covers having 2 copies of my data on separate devices, however it does not cover keeping one copy off-site as well.

I do have a removable drive in my backup system (currently in XFS format) that's mounted through unassigned devices that I will insert and sync my ZFS pools to twice a year, then go and put in a safe deposit box off-site to ensure it's reliably protected. I currently use XFS for this as it's easy to just plug into any system and get at my files. ZFS is still not as well supported on Windows and Mac systems, but I may go there in the future.