Modifying backup before starting a new ABS container on a new NAS

Hi,

I have the following issue: I am migrating from my old Synology NAS to a new NAS running TrueNAS. I ran ABS in Docker on the old and plan to run it the same way, with one major difference: old ABS had two libraries (both with audiobooks; for ebooks I use other software) and in my new NAS I united these two libraries. I can easily start a new ABS container, but I want to keep my reading stats, gathering of books into series, etc. So, I am thinking about taking backup from my old ABS and changing the SQLite database inside (backup file has the extension .audiobookshelf but it is just .zip file). I asked AI how to change to receive my goals and it suggested the following:

-- Update paths in the library settings themselves

UPDATE libraries SET folderPaths = replace(folderPaths, '/books1', '/audiobooks');

UPDATE libraries SET folderPaths = replace(folderPaths, '/books2', '/audiobooks');

-- Update paths for each specific book in the database

UPDATE libraryItems SET path = replace(path, '/books1', '/audiobooks');

UPDATE libraryItems SET path = replace(path, '/books2', '/audiobooks');

-- Update paths for individual audio files inside the books

UPDATE libraryFiles SET path = replace(path, '/books1', '/audiobooks');

UPDATE libraryFiles SET path = replace(path, '/books2', '/audiobooks');

This assumes that old libraries had paths '/books1' and '/books2' and the new will be '/audiobooks'. The suggested change seems logical, but AI often gives total bullshit that seems logical. Therefore, if anyone had a similar experience, please share!

Thanks!

reddit.com
u/TemplarB — 6 days ago
▲ 5 r/UgreenNASync+1 crossposts

I'm abvout to setup TrueNAS on my UGREEN DXP4800 Pro and have questions about scripts – LED and fan control

Hi everyone,

I’m setting up TrueNAS SCALE on a UGREEN DXP4800 Pro and would like to properly configure the hardware-specific functions that TrueNAS doesn’t handle out of the box. From what I read here on Reddit and elsewhere, there are at least two issues:

- front LED control – HDD/SSD activity and status LEDs, which are too bright. Here is one of the scripts for modifying it: https://github.com/miskcoo/ugreen_leds_controller (it has not been tested yet on my specific model)

- fan control – preferably temperature-based fan curves, taking HDD temperatures into account. The used chipset is it87, but different for different NAS models. Script here: https://github.com/IT-Kuny/UGREEN-DXP-FAN-NAS-Driver

- any other useful DXP4800 Pro-specific hardware-control scripts, because maybe I missed something.

I’m particularly interested in hearing from people who have actually done this on a DXP4800 Pro, rather than generic TrueNAS fan-control solutions.

Could someone please provide a detailed step-by-step explanation of:

  1. Which scripts are you using and where did you get them?

  2. Where and how the scripts should be installed in TrueNAS SCALE (I don't afraid to experiment but I need instructions).

  3. What precautions should be taken so that a failed script cannot leave the fans stopped or the drives overheating or something similar?

Thanks!

u/TemplarB — 10 days ago

Please suggest optimal RAM and SSD for my new NAS.

Hi all,

I just purchased UGREEN NASync DXP4800 Pro. I plan to replace their OS with TrueNAS. I plan to buy 4x 6 TB Seagate IronWolf HDDs (ST6000VN006, 5400 RPM, CMR) and run them as in a ZFS RAIDZ1 array. I already have a NAS with 4x4Tb BTRFS RAID5 and size-with the upgrade is enough.

What I really care about is what to do with RAM and SSD – my current NAS was limited in them, so I only now checking what and how I can install to have fast and not too expensive home NAS and family media server. The model I purchased comes with 8Gb RAM. I checked Reddit, TrueNAS forums and asked three different AI what to buy – they suggest from 16G (+8Gb already installed) and quite enough to suggesting 64Gb to feel free. Given current RAM prices I guess that 32+8 will be my choice – a bit over my expected current needs (TrueNAS + NextCloud + Docker running Jellyfin, Navidome, HomeAssist, etc).

With SSD it is harder. Their prices are making me cry 😊 so I guess getting 2x 1Tb as a mirror is an overkill. I thought taking one 1Tb for apps and another for read-only cache, but from what I read about cache is ZFS for my need my larger RAM an be enough – I do not edit video or other large files, have only a few BD Remuxes – so I ended up with 1Tb SSD for now.

Because all this stuff is costly, I need an advice before I buy – I do not want to pay in excess but I want my my NAS surprise me with speed of its work.

So,

1.       Are 16Gb (+8) RAM enough or go 32+8 (I currently prefer this vasiant)

2.       1 Tb (where I live currently 500G and 1T differ in price by mere 25% or so) SSD

Thoughts?

reddit.com
u/TemplarB — 1 month ago

Please suggest optimal RAM and SSD for my new NAS.

Hi all,

I just purchased UGREEN NASync DXP4800 Pro. I plan to replace their OS with TrueNAS. I plan to buy 4x 6 TB Seagate IronWolf HDDs (ST6000VN006, 5400 RPM, CMR) and run them as in a ZFS RAIDZ1 array. I already have a NAS with 4x4Tb BTRFS RAID5 and size-with the upgrade is enough.

What I really care about is what to do with RAM and SSD – my current NAS was limited in them, so I only now checking what and how I can install to have fast and not too expensive home NAS and family media server. The model I purchased comes with 8Gb RAM. I checked Reddit, TrueNAS forums and asked three different AI what to buy – they suggest from 16G (+8Gb already installed) and quite enough to suggesting 64Gb to feel free. Given current RAM prices I guess that 32+8 will be my choice – a bit over my expected current needs (TrueNAS + NextCloud + Docker running Jellyfin, Navidome, HomeAssist, etc).

With SSD it is harder. Their prices are making me cry 😊 so I guess getting 2x 1Tb as a mirror is an overkill. I thought taking one 1Tb for apps and another for read-only cache, but from what I read about cache is ZFS for my need my larger RAM an be enough – I do not edit video or other large files, have only a few BD Remuxes – so I ended up with 1Tb SSD for now.

Because all this stuff is costly, I need an advice before I buy – I do not want to pay in excess but I want my my NAS surprise me with speed of its work.

So,

  1. Are 16Gb (+8) RAM enough or go 32+8 (I currently prefer this vasiant)

  2. 1 Tb (where I live currently 500G and 1T differ in price by mere 25% or so) SSD

Thoughts?

reddit.com
u/TemplarB — 1 month ago

Please suggest optimal RAM and SSD for my new NAS.

Hi all,

I just purchased UGREEN NASync DXP4800 Pro. I plan to replace their OS with TrueNAS. I plan to buy 4x 6 TB Seagate IronWolf HDDs (ST6000VN006, 5400 RPM, CMR) and run them as in a ZFS RAIDZ1 array. I already have a NAS with 4x4Tb BTRFS RAID5 and size-with the upgrade is enough.

What I really care about is what to do with RAM and SSD – my current NAS was limited in them, so I only now checking what and how I can install to have fast and not too expensive home NAS and family media server. The model I purchased comes with 8Gb RAM. I checked Reddit, TrueNAS forums and asked three different AI what to buy – they suggest from 16G (+8Gb already installed) and quite enough to suggesting 64Gb to feel free. Given current RAM prices I guess that 32+8 will be my choice – a bit over my expected current needs (TrueNAS + NextCloud + Docker running Jellyfin, Navidome, HomeAssist, etc).

With SSD it is harder. Their prices are making me cry 😊 so I guess getting 2x 1Tb as a mirror is an overkill. I thought taking one 1Tb for apps and another for read-only cache, but from what I read about cache is ZFS for my need my larger RAM an be enough – I do not edit video or other large files, have only a few BD Remuxes – so I ended up with 1Tb SSD for now.

Because all this stuff is costly, I need an advice before I buy – I do not want to pay in excess but I want my my NAS surprise me with speed of its work.

So,

1.       Are 16Gb (+8) RAM enough or go 32+8 (I currently prefer this vasiant)

2.       1 Tb (where I live currently 500G and 1T differ in price by mere 25% or so) SSD

Thoughts?

reddit.com
u/TemplarB — 1 month ago

Please advise on the optimal hardware (and software) setup for DXP4800 Pro with TrueNAS

I purchased the UGREEN NASync DXP4800 Pro to replace my HP ProLiant Microserver Gen 8 (released in 2013), which I have been using with Xpenology since 2017. I hope the newer model will serve me well for another 6-10 years. Therefore, I selected a model that is slightly above my current requirements, allowing for adequate NAS when I update the rest of my system. I plan to use TrueNAS as its OS, because I'm a bit suspicious that UGreen software lags behind their hardware. Note, that the following post was partially structured by AI, but I did read forums on the different aspects.

Project: Setting up UGREEN NASync DXP4800 Pro with TrueNAS

1. Project Goal

To build a highly responsive, power-efficient, and resilient 24/7 Network Attached Storage (NAS) system. The setup is designed for heavy containerized workloads (Docker), automated media management, and continuous torrent operations over (at least currently) a 300 Mbps internet connection.

2. Hardware Architecture & Choice Rationales

Main Chassis: UGREEN NASync DXP4800 Pro

Memory: 40 GB RAM Configuration

  • Hardware1x32 GB Samsung DDR5 4800MHz SO-DIMM (M425R4GA3BB0-CQK) added to the stock 8 GB module.
  • Why: ZFS is highly dependent on system memory. A single 32 GB stick provides the lowest cost-per-gigabyte while maximizing capacity. Running an asymmetric setup (8GB + 32GB) yields 40 GB total RAM. In a NAS environment, total capacity for the ZFS ARC (Adaptive Replacement Cache) and Docker containers is vastly more critical than dual-channel bandwidth. It also leaves room for a future upgrade to 64 GB. I initially planned 2x16GB, but it seems that the current option is both cheaper and gives more RAM, plus simplifies update (if ever needed) to 2x32GB.

Core Storage (Data Pool): 24 TB Raw / ~16.3 TiB Usable

  • Hardware4x 6 TB Seagate IronWolf HDDs (ST6000VN006, 5400 RPM, CMR).
  • Layout: Configured in a ZFS RAIDZ1 array.
  • Why: The low-speed HDDs will give less noise and less heat. I have been using 4x 4TB BRFS RAID5 for the last 4 years and I guess I won't need much larger disks or better data protection (currently running at 80% of my 10TB volume), therefore Z1, not Z2 or mirror. I initially planned to use Toshiba HDDs, but they are only 7200 RPM, with more heat and noise. I decided that with SSDs (see below) lower speeds won't be a factor. Choosing between Seagate and WD (I now use WD), I chose the former because it is slightly newer and cheaper, but maybe I'll end up with WD Red Plus 6 TB (WD60EFPX)

High-Speed Storage (Apps & Ingest Pool): 1 TB Usable (Mirror)

  • Hardware2x 1 TB NVMe SSDs with DRAM Cache (probably, Kingston KC3000).
  • Layout: Configured in a ZFS RAID 1 (Mirror).
  • Why: Chiefly a dedicated fast storage pool. SSDs with onboard DRAM are chosen to handle high IOPS workloads without stuttering.

The optimal setup of this part (SSD) is the most undecided part of the NAS

3. Software & Storage Strategy (TrueNAS Scale)

The entire ecosystem will run on TrueNAS Scale, optimizing the hardware through precise data dataset separation:

The Docker & App Environment (fast-ssd pool)

  • Usage: The TrueNAS App service (ix-applications), all Docker containers, and active databases will live here.
  • ZFS Optimization: The dataset will be configured with a 16 KiB or 32 KiB recordsize and atime=off. This aligns perfectly with container file systems (Overlay2) and database structures, preventing write amplification and dramatically extending the lifespan of the NVMe SSDs.

The Torrent Ingest Workflow (300 Mbps Internet Connection)

  • The Problem: Downloading torrents directly to a 5400 RPM HDD array causes massive file fragmentation, high disk latency, and physical drive thrashing.
  • The Solution:
  1. Temporary Downloads: Torrents will download onto a dedicated dataset on the NVMe pool (fast-ssd/torrent-temp) with a 256 KiB or 512 KiB recordsize. The SSDs will easily handle the chaotic, random writes of torrent peers.
  2. Finished Media: Once 100% complete, the torrent client will automatically move the completed file to the HDD pool. It writes to the HDDs in one massive, sequential block, which is the easiest and fastest workload for 5400 RPM mechanical drives.
  3. Seeding: Active torrent seeding will occur from the HDD pool.
  4. Torrent Client RAM Cache: The torrent client (e.g., qBittorrent) will be allocated 512 MB to 1 GB of internal RAM cache to buffer incoming data chunks before committing them to the SSD.

The Long-Term Media Vault (tank-hdd pool)

  • Usage: Stores completed movies, series, personal backups, and cold archives.
  • ZFS Optimization: This dataset will use a 1 MiB recordsize with LZ4 or ZSTD-1 compression enabled. Large records ensure maximum sequential read/write performance from the slower 5400 RPM drives and prevent file fragmentation over time.

System Memory Management

  • ZFS ARC Limit: To prevent ZFS from consuming all 40 GB of RAM and triggering Out-Of-Memory (OOM) crashes in Docker, a post-init command script will lock the ZFS cache size: echo 17179869184 > /sys/module/zfs/parameters/zfs_arc_max.
  • The Split: This cleanly reserves 16 GB for the ZFS ARC (plenty for indexing a 16 TiB pool) and leaves ~24 GB completely free for TrueNAS core OS operations, Docker apps, and the torrent client cache.

 

reddit.com
u/TemplarB — 2 months ago

I bought DXP4800 Pro. While it is on its way to me, I want to discuss the setup.

I purchased the UGREEN NASync DXP4800 Pro to replace my HP ProLiant Microserver Gen 8 (released in 2013), which I have been using with Xpenology since 2017. I hope the newer model will serve me well for another 6-10 years. Therefore, I selected a model that is slightly above my current requirements, allowing for adequate NAS when I update the rest of my system. I plan to use TrueNAS as its OS, because I'm a bit suspicious that UGreen software lags behind their hardware. Note, that the following post was partially structured by AI, but I did read forums on the different aspects.

Project: Setting up UGREEN NASync DXP4800 Pro with TrueNAS

1. Project Goal

To build a highly responsive, power-efficient, and resilient 24/7 Network Attached Storage (NAS) system. The setup is designed for heavy containerized workloads (Docker), automated media management, and continuous torrent operations over (at least currently) a 300 Mbps internet connection.

2. Hardware Architecture & Choice Rationales

Main Chassis: UGREEN NASync DXP4800 Pro

Memory: 40 GB RAM Configuration

  • Hardware1x32 GB Samsung DDR5 4800MHz SO-DIMM (M425R4GA3BB0-CQK) added to the stock 8 GB module.
  • Why: ZFS is highly dependent on system memory. A single 32 GB stick provides the lowest cost-per-gigabyte while maximizing capacity. Running an asymmetric setup (8GB + 32GB) yields 40 GB total RAM. In a NAS environment, total capacity for the ZFS ARC (Adaptive Replacement Cache) and Docker containers is vastly more critical than dual-channel bandwidth. It also leaves room for a future upgrade to 64 GB. I initially planned 2x16GB, but it seems that the current option is both cheaper and gives more RAM, plus simplifies update (if ever needed) to 2x32GB.

Core Storage (Data Pool): 24 TB Raw / ~16.3 TiB Usable

  • Hardware4x 6 TB Seagate IronWolf HDDs (ST6000VN006, 5400 RPM, CMR).
  • Layout: Configured in a ZFS RAIDZ1 array.
  • Why: The low-speed HDDs will give less noise and less heat. I have been using 4x 4TB BRFS RAID5 for the last 4 years and I guess I won't need much larger disks or better data protection (currently running at 80% of my 10TB volume), therefore Z1, not Z2 or mirror. I initially planned to use Toshiba HDDs, but they are only 7200 RPM, with more heat and noise. I decided that with SSDs (see below) lower speeds won't be a factor. Choosing between Seagate and WD (I now use WD), I chose the former because it is slightly newer and cheaper, but maybe I'll end up with WD Red Plus 6 TB (WD60EFPX)

High-Speed Storage (Apps & Ingest Pool): 1 TB Usable (Mirror)

  • Hardware2x 1 TB NVMe SSDs with DRAM Cache (probably, Kingston KC3000).
  • Layout: Configured in a ZFS RAID 1 (Mirror).
  • Why: Chiefly a dedicated fast storage pool. SSDs with onboard DRAM are chosen to handle high IOPS workloads without stuttering.

3. Software & Storage Strategy (TrueNAS Scale)

The entire ecosystem will run on TrueNAS Scale, optimizing the hardware through precise data dataset separation:

The Docker & App Environment (fast-ssd pool)

  • Usage: The TrueNAS App service (ix-applications), all Docker containers, and active databases will live here.
  • ZFS Optimization: The dataset will be configured with a 16 KiB or 32 KiB recordsize and atime=off. This aligns perfectly with container file systems (Overlay2) and database structures, preventing write amplification and dramatically extending the lifespan of the NVMe SSDs.

The Torrent Ingest Workflow (300 Mbps Internet Connection)

  • The Problem: Downloading torrents directly to a 5400 RPM HDD array causes massive file fragmentation, high disk latency, and physical drive thrashing.
  • The Solution:
  1. Temporary Downloads: Torrents will download onto a dedicated dataset on the NVMe pool (fast-ssd/torrent-temp) with a 256 KiB or 512 KiB recordsize. The SSDs will easily handle the chaotic, random writes of torrent peers.
  2. Finished Media: Once 100% complete, the torrent client will automatically move the completed file to the HDD pool. It writes to the HDDs in one massive, sequential block, which is the easiest and fastest workload for 5400 RPM mechanical drives.
  3. Seeding: Active torrent seeding will occur from the HDD pool.
  4. Torrent Client RAM Cache: The torrent client (e.g., qBittorrent) will be allocated 512 MB to 1 GB of internal RAM cache to buffer incoming data chunks before committing them to the SSD.

The Long-Term Media Vault (tank-hdd pool)

  • Usage: Stores completed movies, series, personal backups, and cold archives.
  • ZFS Optimization: This dataset will use a 1 MiB recordsize with LZ4 or ZSTD-1 compression enabled. Large records ensure maximum sequential read/write performance from the slower 5400 RPM drives and prevent file fragmentation over time.

System Memory Management

  • ZFS ARC Limit: To prevent ZFS from consuming all 40 GB of RAM and triggering Out-Of-Memory (OOM) crashes in Docker, a post-init command script will lock the ZFS cache size: echo 17179869184 > /sys/module/zfs/parameters/zfs_arc_max.
  • The Split: This cleanly reserves 16 GB for the ZFS ARC (plenty for indexing a 16 TiB pool) and leaves ~24 GB completely free for TrueNAS core OS operations, Docker apps, and the torrent client cache.

 

reddit.com
u/TemplarB — 2 months ago