Categories: braindump

UGREEN NASync DXP6800 Pro - initial bringup

Table of Contents

I purchased a UGREEN NASync DXP 6800 Pro. This comes with a 12th Gen Intel® Core™ i5-1235U.

These are my notes from initial bringup; mainly backing up the pre-installed Ugos so that I can wipe the included 128GB NVMe and install another Linux distribution on it.

But only initial bring up, I have not even given it a 10 GBE network port yet. Need to get a RJ-45 SFP+, but I do have 4 ports left on my 10 GBE switch.

Just like with other NAS hardware I repurposed in the past, I expect to write further posts about this DXP6800 Pro.

Introduction

I’ve actually had this for a few weeks now, having taken part in Ugreen’s Kickstarter back in March.

I did not use the pre-installed Ugos for more than a quick check that the device I bought was functional, mainly because it seems geared towards a target audience I am not a member of. But the hardware is good and the build quality is on par or better than on my QNAP TS-473A. Do note that the Ugreen does frequent OS updates and that if all you want is a Network Attached Storage, then Ugos might be a good choice for you. It’s just not for me. I bought this box because of the modern CPU, the 3/5" bays, the NVMe bays and the maximum RAM I can plug in. I always planned to install a distro of my choice.

So expect this post to only be about initial bring up and backing up the Ugos shipped on the 128 GB NVMe. That NVMe is large enough for my base OS needs and harder to reach than the other two NVMe slots. If you are queasy about wiping the Ugos, you can just disable the NVMe in firmware setup and install your OS to one of the 2 easily accessible NVMe slots.

Installing different distributions will be handled in one or more separate posts.

What’s in the Box

Since the models in the lineup do not only differ by the used chassis (esp number of 3.5 inch carriers), but also by the used CPU and number of RAM and NVMe slots, do check Ugreen’s specification comparison page before assuming things in this braindump apply to other models.

The main selling points for me were:

  • 12th Gen Intel(R) Core(TM) i5-1235U
  • 2 free NVMe slots, easily accessible behind a sprint loaded cover at the bottom of the case
  • 2 SO-DIMM slots, easily accessible behind the same cover, DDR5, up to 4800 MT/s, on die ECC (ODECC) supported
  • 2x 10 GBE NICs, while SFP+ is my preference , RJ-45 is acceptable
  • 6x 3.5 inch SATA bays

And other notable bits in the one I bought are

  • 128 GB NVMe installed, containing Ugos, AFAIK case needs disassembly to swap
  • 8 GiB RAM, enough for NAS services (e.g. openmediavault)
  • 2x Thunderbolt™ 4 ports
  • 1 PCIe slot
  • HDMI port, 8K capable
  • SD 4.0 Card Reader
  • 2x USB 3.2 Gen 2 port
  • 2x USB 2.0 port

When I decided if I should buy the DXP6800 Pro or not, the very appealing kickstarter price made the decision easy after I read the section Specifications at https://www.kickstarter.com/projects/urgreen/ugreen-nasync-next-level-storage-limitless-possibilities. While the compare page linked above is nice, it wants to load scripts from over a dozen domains (in addition to the expected ugreen.com), so I still use the image on Kickstarter today when looking up specs ofg the 6800.

Entering Firmware Setup

If you understand German and like me happen to be a reader of c’t, then see Ausgabe 14/2024 page 74ff (Starker Auftritt; Zwei Netzwerkspeicher des neuen Herstellers Ugreen im Test)_ for a test report.

  • connect a screen via HDMI and a USB keyboard (I used my PiKVM)
  • power on
  • wait until grub shows
  • type c to enter a command, before the grub timeout (3 seconds) expires!
  • enter the gub command fwsetup
  • system reboots into firmware setup

You can expect pretty much any modern Linux distro, to add a grub menu entry to enter firmware setup for you when you install it.

Watchdog Timer

Watchdog Timer (wdt) settings can be found firmware setup.

My Point of View

Ugreen got a lot of angry post in the kickstarter concerning the watchdog.

Let me be crystal clear, a wdt is not part of some nefarious plot, it is a super useful hardware component basically pushes the reset button for you when the operating system stops responding.

All you need to do is tell your OS to signal to the wdt regularly that it is still alive or switch it off.

Out of the box (ootb) the DXP6800 Pro has wdt enabled in firmware and a timeout of 180 seconds. These are reasonable and sensible settings for a vendor that ships an appliance (that ideally is also using A/B boot), meaning they not only sell you the hardware and the software as a bundle, but also set their chosen bootloader up to gracefully handle failed boots by falling back to a previously working boot.

What I do, install my own OS, naturally includes setting up the wdt to my liking, just like I pick other settings for my use case, I really felt sorry for the engineers that picked good settings only to have half clued up users (thy know enough to replace the shipped OS, but not enough to configure their OS and/or installer to feed the wdt, nor do they know how to disarm the wdt).

These are also sensible settings for any OS that starts feeding the wdt within 180 seconds of power on. When I install Fedora, RHEL or Proxmox VE, configuring any present wdt is normal.

FWIW, in thoise cases my preferred settings are

  • do not arm until fed the first time
  • hard reset the box if armed and not fed in N seconds (usually 60 seconds for my homelab machines)
  • allow to disarm (nowayout=0)

But, this ootb setting means two things;

  1. I need to configure and save my firmware settings within 3 minutes of poweron. Not an issue for me.
  2. I need to start feeding the wdt within 3 minutes of poweron. Once I configured and tested the watchdog timer in the OS, that is not an issue with RHEL (nor with any RHEL variants), not an issue with Fedora and not an issue with ProxmoxVE.

During installation time of a self chosen OS, you want to either have the installer (of the OS you install) feed the wdt or disable it in firmware setup for the duration of installation.

After installation of your OS of choice, if your installed OS supports a wdt and you configured it, consider switching it on again in firmware setup. It’s actually useful to have a wdt hard-reboot the NAS if the OS running on it stopped responding.

Expect more details on what settings I use in distro hopping posts on this hardware.

Disable Watchdog Timer

If you want or need to disable the Watchdog Timer;

  • Enter firmware setup
  • navigate to Advanced / Watchdog Settings
  • set Watch Dog Control to Disabled
  • save and exit firmware setup before the 180 seconds (ootb setting) expire!

Boot With Vendor OS, Ugos

To ensure the hardware was not dead on arrival and to apply any available firmware updates, I booted into the Ugreen’s OS, called Ugos, and did the following;

  • set admin user name and password
  • skip when asked if I want to connect to cloud
  • set update to notify only
  • decline analytics
  • go to Settings / Update & Restore
  • update from 1.0.0.0556 to latest available that day, 1.0.0.1150
  • restart when prompted
  • tried all 3 fan speeds successfully, set back to Default
  • set LEDs to 50% brightness
  • enabled ssh, but not sftp, encryption level high
  • also, switched off WebFind at Settings / About / Device analysis

A Peek Over ssh

I ssh-ed in from my Fedora 40 machine and had a quick look around on Ugos before installing a different operating system.

Based on a recent distro, Debian 12, nice. Password requested on sudo, nice. Old school net.ifnames=0 biosdevname=0, not nice. It’s 2024, please use modern features.

pcfe@t3600 ~ $ ssh DXP6800PRO-7F5A.internal.pcfe.net -l someusername
The authenticity of host 'dxp6800pro-7f5a.internal.pcfe.net (192.168.50.110)' can't be established.
ED25519 key fingerprint is SHA256:CtJFpSg5QStYP0Jwjn8J9dVE0h6F6xuufa8t9U0VySc.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'dxp6800pro-7f5a.internal.pcfe.net' (ED25519) to the list of known hosts.
someusername@dxp6800pro-7f5a.internal.pcfe.net's password: 
X11 forwarding request failed on channel 0
Linux DXP6800PRO-7F5A 6.1.27 #10 SMP PREEMPT_DYNAMIC Wed May 29 18:12:42 CST 2024 x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Could not chdir to home directory /home/someusername: No such file or directory
someusername@DXP6800PRO-7F5A:/$ date
Sun Jul 28 05:36:11 PM CEST 2024
someusername@DXP6800PRO-7F5A:/$ free -h
               total        used        free      shared  buff/cache   available
Mem:           7.5Gi       1.9Gi       3.7Gi        53Mi       2.7Gi       5.5Gi
Swap:             0B          0B          0B
someusername@DXP6800PRO-7F5A:/$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1     259:0    0 119.2G  0 disk 
├─nvme0n1p1 259:1    0   256M  0 part /boot
├─nvme0n1p2 259:2    0     2G  0 part 
├─nvme0n1p3 259:3    0    10M  0 part /mnt/factory
├─nvme0n1p4 259:4    0     2G  0 part /rom
├─nvme0n1p5 259:5    0     2G  0 part 
├─nvme0n1p6 259:6    0     4G  0 part /ugreen
└─nvme0n1p7 259:7    0   109G  0 part /overlay
someusername@DXP6800PRO-7F5A:/$ efibootmgr -v
BootCurrent: 0002
Timeout: 3 seconds
BootOrder: 0002
Boot0000* Windows Boot Manager	HD(1,GPT,ddf9b55b-f866-40cc-8240-f9a4c49cbe72,0x800,0x96000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...n................
Boot0002* debian	HD(1,GPT,99009e79-d999-a659-32e5-993bfb698a01,0x22,0x80000)/File(\EFI\debian\shimx64.efi)..BO

someusername@DXP6800PRO-7F5A:/$ cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
OS_VERSION=1.0.0.1150
BUILD_ID=1.00.1150

someusername@DXP6800PRO-7F5A:/$ id
uid=1000(someusername) gid=10(admin) groups=10(admin),100(users)
someusername@DXP6800PRO-7F5A:/$ sudo -i
[sudo] password for someusername: 


BusyBox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

root@DXP6800PRO-7F5A:~# 

root@DXP6800PRO-7F5A:~# cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz2 root=PARTUUID=9ed7ef69-6317-1a44-a26c-e004f5d4d652 rootwait console=tty0 overlay=/dev/mmcblk0p7 overlayfs=ext4 net.ifnames=0 biosdevname=0

root@DXP6800PRO-7F5A:~# lscpu
Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         39 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  12
  On-line CPU(s) list:   0-11
Vendor ID:               GenuineIntel
  BIOS Vendor ID:        Intel(R) Corporation
  Model name:            12th Gen Intel(R) Core(TM) i5-1235U
    BIOS Model name:     12th Gen Intel(R) Core(TM) i5-1235U To Be Filled By O.E.M. CPU @ 1.9GHz
    BIOS CPU family:     205
    CPU family:          6
    Model:               154
    Thread(s) per core:  2
    Core(s) per socket:  10
    Socket(s):           1
    Stepping:            4
    CPU(s) scaling MHz:  44%
    CPU max MHz:         4400.0000
    CPU min MHz:         400.0000
    BogoMIPS:            4992.00
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq
                          dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexprio
                         rity ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku os
                         pke waitpkg gfni vaes vpclmulqdq rdpid movdiri movdir64b fsrm md_clear serialize arch_lbr ibt flush_l1d arch_capabilities
Virtualization features: 
  Virtualization:        VT-x
Caches (sum of all):     
  L1d:                   352 KiB (10 instances)
  L1i:                   576 KiB (10 instances)
  L2:                    6.5 MiB (4 instances)
  L3:                    12 MiB (1 instance)
NUMA:                    
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-11
Vulnerabilities:         
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
  Srbds:                 Not affected
  Tsx async abort:       Not affected
full dmidecode output (click to expand) 
root@DXP6800PRO-7F5A:~# dmidecode 
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.6.0 present.
# SMBIOS implementations newer than version 3.5.0 are not
# fully supported by this version of dmidecode.
Table at 0x5BBAC000.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
	Vendor: American Megatrends International, LLC.
	Version: 5.27
	Release Date: 02/23/2024
	Address: 0xF0000
	Runtime Size: 64 kB
	ROM Size: 0 MB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
		Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
		5.25"/360 kB floppy services are supported (int 13h)
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 kB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 5.27

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: UGREEN
	Product Name: DXP6800 Pro
	Version: RP0R0160
	Serial Number: [REDACTED]
	UUID: 03000200-0400-0500-0006-000700080009
	Wake-up Type: Power Switch
	SKU Number: Default string
	Family: UGREEN NAS

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: Default string
	Product Name: Default string
	Version: Default string
	Serial Number: Default string
	Asset Tag: Default string
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: Default string
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
	Manufacturer: Default string
	Type: Desktop
	Lock: Not Present
	Version: Default string
	Serial Number: Default string
	Asset Tag: Default string
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0
	SKU Number: Default string

Handle 0x0004, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Internal Connector 1
	Internal Connector Type: None
	External Reference Designator: External Connector 1
	External Connector Type: None
	Port Type: None

Handle 0x0005, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Internal Connector 2
	Internal Connector Type: None
	External Reference Designator: External Connector 2
	External Connector Type: None
	Port Type: None

Handle 0x0006, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Internal Connector 3
	Internal Connector Type: None
	External Reference Designator: External Connector 3
	External Connector Type: None
	Port Type: None

Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Internal Connector 4
	Internal Connector Type: None
	External Reference Designator: External Connector 4
	External Connector Type: None
	Port Type: None

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Internal Connector 5
	Internal Connector Type: None
	External Reference Designator: External Connector 5
	External Connector Type: None
	Port Type: None

Handle 0x0009, DMI type 9, 17 bytes
System Slot Information
	Designation: Slot 1
	Type: 32-bit PCI Express x1
	Current Usage: Available
	Length: Short
	ID: 1
	Characteristics:
		3.3 V is provided
		PME signal is supported
	Bus Address: 0000:00:00.0

Handle 0x000A, DMI type 9, 17 bytes
System Slot Information
	Designation: Slot 2
	Type: 32-bit PCI Express x1
	Current Usage: Available
	Length: Short
	ID: 1
	Characteristics:
		3.3 V is provided
		PME signal is supported
	Bus Address: 0000:00:00.0

Handle 0x000B, DMI type 9, 17 bytes
System Slot Information
	Designation: Slot 3
	Type: 32-bit PCI Express x1
	Current Usage: Available
	Length: Short
	ID: 1
	Characteristics:
		3.3 V is provided
		PME signal is supported
	Bus Address: 0000:00:00.0

Handle 0x000C, DMI type 9, 17 bytes
System Slot Information
	Designation: Slot 4
	Type: 32-bit PCI Express x1
	Current Usage: Available
	Length: Short
	ID: 1
	Characteristics:
		3.3 V is provided
		PME signal is supported
	Bus Address: 0000:00:00.0

Handle 0x000D, DMI type 9, 17 bytes
System Slot Information
	Designation: Slot 5
	Type: 32-bit PCI Express x1
	Current Usage: Available
	Length: Short
	ID: 1
	Characteristics:
		3.3 V is provided
		PME signal is supported
	Bus Address: 0000:00:00.0

Handle 0x000E, DMI type 10, 6 bytes
On Board Device Information
	Type: Unknown
	Status: Enabled
	Description: Device 1

Handle 0x000F, DMI type 11, 5 bytes
OEM Strings
	String 1: Default string

Handle 0x0010, DMI type 12, 5 bytes
System Configuration Options
	Option 1: Default string

Handle 0x0011, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 1
		en|US|iso8859-1
	Currently Installed Language: en|US|iso8859-1

Handle 0x0012, DMI type 26, 22 bytes
Voltage Probe
	Description: Voltage Probe #1
	Location: Motherboard
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x0013, DMI type 26, 22 bytes
Voltage Probe
	Description: Voltage Probe #2
	Location: Motherboard
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x0014, DMI type 27, 15 bytes
Cooling Device
	Temperature Probe Handle: 0x0000
	Type: Power Supply Fan
	Status: OK
	OEM-specific Information: 0x00000000
	Nominal Speed: Unknown Or Non-rotating
	Description: Cooling device #1

Handle 0x0015, DMI type 27, 15 bytes
Cooling Device
	Temperature Probe Handle: 0x0000
	Type: Power Supply Fan
	Status: OK
	OEM-specific Information: 0x00000000
	Nominal Speed: Unknown Or Non-rotating
	Description: Cooling device #2

Handle 0x0016, DMI type 27, 15 bytes
Cooling Device
	Temperature Probe Handle: 0x0000
	Type: Unknown
	Status: OK
	OEM-specific Information: 0x00000000
	Nominal Speed: Unknown Or Non-rotating
	Description: Cooling device #3

Handle 0x0017, DMI type 28, 22 bytes
Temperature Probe
	Description: Temperature Probe #1
	Location: Motherboard
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x0018, DMI type 28, 22 bytes
Temperature Probe
	Description: Temperature Probe #2
	Location: Unknown
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x0019, DMI type 28, 22 bytes
Temperature Probe
	Description: Temperature Probe #3
	Location: Unknown
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x001A, DMI type 28, 22 bytes
Temperature Probe
	Description: Temperature Probe #4
	Location: Unknown
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x001B, DMI type 29, 22 bytes
Electrical Current Probe
	Description: Electrical Probe #1
	Location: Motherboard
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x001C, DMI type 29, 22 bytes
Electrical Current Probe
	Description: Electrical Probe #2
	Location: Unknown
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x001D, DMI type 29, 22 bytes
Electrical Current Probe
	Description: Electrical Probe #3
	Location: Unknown
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x001E, DMI type 29, 22 bytes
Electrical Current Probe
	Description: Electrical Probe #4
	Location: Unknown
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x001F, DMI type 29, 22 bytes
Electrical Current Probe
	Description: Electrical Probe #5
	Location: Unknown
	Status: OK
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x0020, DMI type 32, 11 bytes
System Boot Information
	Status: No errors detected

Handle 0x0021, DMI type 34, 11 bytes
Management Device
	Description: Management Dev #1
	Type: Unknown
	Address: 0x00000000
	Address Type: Unknown

Handle 0x0022, DMI type 39, 22 bytes
System Power Supply
	Power Unit Group: 1
	Location: Default string
	Name: Default string
	Manufacturer: Default string
	Serial Number: Default string
	Asset Tag: Default string
	Model Part Number: Default string
	Revision: Default string
	Max Power Capacity: Unknown
	Status: Present, OK
	Type: Switching
	Input Voltage Range Switching: Auto-switch
	Plugged: Yes
	Hot Replaceable: No
	Input Voltage Probe Handle: 0x0012
	Cooling Device Handle: 0x0014
	Input Current Probe Handle: 0x001F

Handle 0x0023, DMI type 39, 22 bytes
System Power Supply
	Power Unit Group: 1
	Location: Default string
	Name: Default string
	Manufacturer: Default string
	Serial Number: Default string
	Asset Tag: Default string
	Model Part Number: Default string
	Revision: Default string
	Max Power Capacity: Unknown
	Status: Present, OK
	Type: Switching
	Input Voltage Range Switching: Auto-switch
	Plugged: Yes
	Hot Replaceable: No
	Input Voltage Probe Handle: 0x0013
	Cooling Device Handle: 0x0015
	Input Current Probe Handle: 0x001E

Handle 0x0024, DMI type 39, 22 bytes
System Power Supply
	Power Unit Group: 1
	Location: Default string
	Name: Default string
	Manufacturer: Default string
	Serial Number: Default string
	Asset Tag: Default string
	Model Part Number: Default string
	Revision: Default string
	Max Power Capacity: Unknown
	Status: Present, OK
	Type: Switching
	Input Voltage Range Switching: Auto-switch
	Plugged: Yes
	Hot Replaceable: No
	Cooling Device Handle: 0x0016

Handle 0x0025, DMI type 44, 9 bytes
Unknown Type
	Header and Data:
		2C 09 25 00 00 00 01 01 00

Handle 0x0026, DMI type 45, 26 bytes
Firmware Inventory Information
	Firmware Component Name: BIOS Firmware
	Firmware Version: 5.27
	Firmware ID: 00000000-0000-0000-0000-000000000000
	Release Date: 02/23/2024
	Manufacturer: Default string
	Lowest Supported Firmware Version: 5.27
	Image Size: 10 MB
	Characteristics:
		Updatable: Yes
		Write-Protect: No
	State: Enabled
	Associated Components: 1
		0x0000

Handle 0x0027, DMI type 16, 23 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 64 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x0028, DMI type 17, 92 bytes
Memory Device
	Array Handle: 0x0027
	Error Information Handle: Not Provided
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: Unknown
	Set: None
	Locator: Controller0-ChannelA-DIMM0
	Bank Locator: BANK 0
	Type: Unknown
	Type Detail: None

Handle 0x0029, DMI type 17, 92 bytes
Memory Device
	Array Handle: 0x0027
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8 GB
	Form Factor: SODIMM
	Set: None
	Locator: Controller1-ChannelA-DIMM0
	Bank Locator: BANK 0
	Type: DDR5
	Type Detail: Synchronous
	Speed: 4800 MT/s
	Manufacturer: Samsung
	Serial Number: [REDACTED]
	Asset Tag: 9876543210
	Part Number: M425R1GB4BB0-CQKOL  
	Rank: 1
	Configured Memory Speed: 4800 MT/s
	Minimum Voltage: 1.1 V
	Maximum Voltage: 1.1 V
	Configured Voltage: 1.1 V
	Memory Technology: DRAM
	Memory Operating Mode Capability: Volatile memory
	Firmware Version: Not Specified
	Module Manufacturer ID: Bank 1, Hex 0xCE
	Module Product ID: Unknown
	Memory Subsystem Controller Manufacturer ID: Unknown
	Memory Subsystem Controller Product ID: Unknown
	Non-Volatile Size: None
	Volatile Size: 8 GB
	Cache Size: None
	Logical Size: None

Handle 0x002A, DMI type 19, 31 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x001FFFFFFFF
	Range Size: 8 GB
	Physical Array Handle: 0x0027
	Partition Width: 1

Handle 0x002B, DMI type 43, 31 bytes
TPM Device
	Vendor ID: INTC
	Specification Version: 2.0
	Firmware Revision: 600.18
	Description: INTEL
	Characteristics:
		Family configurable via platform software support
	OEM-specific Information: 0x00000000

Handle 0x002C, DMI type 45, 26 bytes
Firmware Inventory Information
	Firmware Component Name: TPM Firmware
	Firmware Version: 2580012.1E0903
	Firmware ID: Not Specified
	Release Date: 2021-05-15T00:00:00Z
	Manufacturer: INTEL
	Lowest Supported Firmware Version: Not Specified
	Image Size: Unknown
	Characteristics:
		Updatable: No
		Write-Protect: No
	State: Enabled
	Associated Components: 1
		0x0000

Handle 0x002D, DMI type 20, 35 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x001FFFFFFFF
	Range Size: 8 GB
	Physical Device Handle: 0x0029
	Memory Array Mapped Address Handle: 0x002A
	Partition Row Position: Unknown

Handle 0x002E, DMI type 221, 12 bytes
OEM-specific Type
	Header and Data:
		DD 0C 2E 00 01 01 00 04 00 00 00 00
	Strings:
		FSP Binary Version

Handle 0x002F, DMI type 221, 26 bytes
OEM-specific Type
	Header and Data:
		DD 1A 2F 00 03 01 00 0C 00 BD 40 00 02 00 00 00
		04 30 00 03 00 01 12 10 00 00
	Strings:
		Reference Code - CPU
		uCode Version
		TXT ACM version

Handle 0x0030, DMI type 221, 26 bytes
OEM-specific Type
	Header and Data:
		DD 1A 30 00 03 01 00 0C 00 BD 40 00 02 00 00 00
		00 00 00 03 04 10 01 1E 03 09
	Strings:
		Reference Code - ME
		MEBx version
		ME Firmware Version
		Consumer SKU

Handle 0x0031, DMI type 221, 47 bytes
OEM-specific Type
	Header and Data:
		DD 2F 31 00 06 01 00 0C 00 BD 40 00 02 03 FF FF
		FF FF FF 04 00 FF FF FF 01 00 05 00 FF FF FF 01
		00 06 00 02 46 00 00 00 07 00 04 00 00 00 00
	Strings:
		Reference Code - PCH
		PCH-CRID Status
		Disabled
		PCH-CRID Original Value
		PCH-CRID New Value
		OPROM - RST - RAID
		PCH Hsio Version

Handle 0x0032, DMI type 221, 82 bytes
OEM-specific Type
	Header and Data:
		DD 52 32 00 0B 01 00 0C 00 BD 40 00 02 00 00 00
		04 BF 00 03 00 0C 00 BD 40 00 04 05 FF FF FF FF
		FF 06 00 00 00 00 04 00 07 00 00 00 00 04 00 08
		00 FF FF FF FF FF 09 00 24 00 06 00 00 0A 00 00
		00 00 43 20 0B 00 02 02 00 00 00 0C 00 FF FF FF
		FF FF
	Strings:
		Reference Code - SA - System Agent
		Reference Code - MRC
		SA - PCIe Version
		SA-CRID Status
		Disabled
		SA-CRID Original Value
		SA-CRID New Value
		OPROM - VBIOS
		IO Manageability Engine FW Version
		PHY Build Version
		Thunderbolt(TM) FW Version
		System Agent Manageability Engine FW Version

Handle 0x0033, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 96 kB
	Maximum Size: 96 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Data
	Associativity: 12-way Set-associative

Handle 0x0034, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 64 kB
	Maximum Size: 64 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Instruction
	Associativity: 8-way Set-associative

Handle 0x0035, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L2 Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 2560 kB
	Maximum Size: 2560 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: Other

Handle 0x0036, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L3 Cache
	Configuration: Enabled, Not Socketed, Level 3
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 12 MB
	Maximum Size: 12 MB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Multi-bit ECC
	System Type: Unified
	Associativity: 12-way Set-associative

Handle 0x0037, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 256 kB
	Maximum Size: 256 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Data
	Associativity: 8-way Set-associative

Handle 0x0038, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 512 kB
	Maximum Size: 512 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Instruction
	Associativity: 8-way Set-associative

Handle 0x0039, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L2 Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 4 MB
	Maximum Size: 4 MB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: 16-way Set-associative

Handle 0x003A, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L3 Cache
	Configuration: Enabled, Not Socketed, Level 3
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 12 MB
	Maximum Size: 12 MB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Multi-bit ECC
	System Type: Unified
	Associativity: 12-way Set-associative

Handle 0x003B, DMI type 4, 48 bytes
Processor Information
	Socket Designation: U3E1
	Type: Central Processor
	Family: Core i5
	Manufacturer: Intel(R) Corporation
	ID: A4 06 09 00 FF FB EB BF
	Signature: Type 0, Family 6, Model 154, Stepping 4
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Multi-threading)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: 12th Gen Intel(R) Core(TM) i5-1235U
	Voltage: 0.8 V
	External Clock: 100 MHz
	Max Speed: 4400 MHz
	Current Speed: 1980 MHz
	Status: Populated, Enabled
	Upgrade: <OUT OF SPEC>
	L1 Cache Handle: 0x0038
	L2 Cache Handle: 0x0039
	L3 Cache Handle: 0x003A
	Serial Number: To Be Filled By O.E.M.
	Asset Tag: To Be Filled By O.E.M.
	Part Number: To Be Filled By O.E.M.
	Core Count: 10
	Core Enabled: 10
	Thread Count: 12
	Characteristics:
		64-bit capable
		Multi-Core
		Hardware Thread
		Execute Protection
		Enhanced Virtualization
		Power/Performance Control

Handle 0x003C, DMI type 131, 64 bytes
OEM-specific Type
	Header and Data:
		83 40 3C 00 35 00 00 00 00 00 00 00 00 00 00 00
		F8 00 82 51 00 00 00 00 21 20 00 00 01 00 10 00
		03 09 1E 00 00 00 00 00 FE 00 FF FF 00 00 00 00
		00 00 00 00 26 00 00 00 76 50 72 6F 00 00 00 00

Handle 0x003D, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:00:00.0

Handle 0x003E, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Video
	Type: Video
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:00:02.0

Handle 0x003F, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 2
	Bus Address: 0000:00:0d.0

Handle 0x0040, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 3
	Bus Address: 0000:00:0d.2

Handle 0x0041, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 4
	Bus Address: 0000:00:0d.3

Handle 0x0042, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 5
	Bus Address: 0000:00:14.0

Handle 0x0043, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 6
	Bus Address: 0000:00:14.2

Handle 0x0044, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 7
	Bus Address: 0000:00:15.0

Handle 0x0045, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 8
	Bus Address: 0000:00:15.1

Handle 0x0046, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 9
	Bus Address: 0000:00:16.0

Handle 0x0047, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - SATA
	Type: SATA Controller
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:00:17.0

Handle 0x0048, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 10
	Bus Address: 0000:00:1f.0

Handle 0x0049, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Sound
	Type: Sound
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:00:1f.3

Handle 0x004A, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 11
	Bus Address: 0000:00:1f.4

Handle 0x004B, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: Onboard - Other
	Type: Other
	Status: Enabled
	Type Instance: 12
	Bus Address: 0000:00:1f.5

Handle 0x004C, DMI type 221, 103 bytes
OEM-specific Type
	Header and Data:
		DD 67 4C 00 0E 01 00 FF FF FF FF FF 02 00 FF FF
		FF FF FF 03 04 FF FF FF FF FF 05 06 FF FF FF FF
		FF 07 08 FF FF FF FF FF 09 00 FF FF FF FF FF 0A
		00 FF FF FF FF FF 0B 00 FF FF 00 00 00 0C 00 00
		21 00 65 10 0D 00 FF FF FF FF FF 0E 00 00 07 00
		00 00 0F 00 13 05 05 5F 16 10 00 FF FF FF FF FF
		11 00 FF FF FF FF FF
	Strings:
		Lan Phy Version
		Sensor Firmware Version
		Debug Mode Status
		Disabled
		Performance Mode Status
		Disabled
		Debug Use USB(Disabled:Serial)
		Disabled
		ICC Overclocking Version
		UNDI Version
		EC FW Version
		GOP Version
		Royal Park Version
		Platform Version
		RST PreOS Version
		TCSS PD0 Version
		TCSS PD1 Version

Handle 0x004D, DMI type 133, 44 bytes
OEM-specific Type
	Header and Data:
		85 2C 4D 00 F9 B4 95 78 4D 92 0A 41 96 39 12 38
		62 B2 8A 63 00 86 80 08 16 12 20 26 12 86 80 01
		00 00 00 61 72 57 18 03 00 00 00 00

Handle 0x004E, DMI type 136, 8 bytes
OEM-specific Type
	Header and Data:
		88 08 4E 00 00 00 00 00

Handle 0x004F, DMI type 14, 8 bytes
Group Associations
	Name: $MEI
	Items: 1
		0x0000 (OEM-specific)

Handle 0x0050, DMI type 219, 106 bytes
OEM-specific Type
	Header and Data:
		DB 6A 50 00 01 04 01 55 02 00 90 06 01 85 39 20
		00 00 00 00 40 00 00 00 00 00 00 02 00 40 00 02
		FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
		FF FF FF FF FF FF FF FF 03 00 00 00 80 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00
	Strings:
		MEI1
		MEI2
		MEI3
		MEI4

Handle 0x0051, DMI type 136, 6 bytes
OEM-specific Type
	Header and Data:
		88 06 51 00 00 00

Handle 0x0052, DMI type 14, 23 bytes
Group Associations
	Name: Firmware Version Info
	Items: 6
		0x002E (OEM-specific)
		0x002F (OEM-specific)
		0x0030 (OEM-specific)
		0x0031 (OEM-specific)
		0x0032 (OEM-specific)
		0x004C (OEM-specific)

Handle 0x0053, DMI type 127, 4 bytes
End Of Table

root@DXP6800PRO-7F5A:~#

Backup the Vendor OS

Because I wanted to repurpose the 128 GiB in the, not so easy to access, NVMe slot number 3 but I might want to put the DXP6800 Pro back into as shipped state if I decide not to keep it or if I have a warranty event.

Note that some partitions look like they contain device specific info, e.g. factory/sn.txt, so I added a small text file to remind me that this is the one I got via Kickstarter, just in case I like the hardware so much that I get more than one. Mind you, for that to happen, the 2 performance cores and 8 efficiency cores would need to be good enough for homelab use with Ceph or ProxmoxVE.

Backup Partition Table of 128 GB NVMe

This is safe to do from within the booted OS.

sgdisk --backup=sgdisk-nvme0n1.bin /dev/nvme0n1

and copied the resulting sgdisk-nvme0n1.bin file to another machine.

details of backing up the partition table 
root@DXP6800PRO-7F5A:~# parted /dev/nvme0n1 print
Model: YSO128GTLCW-E3C-2 (nvme)
Disk /dev/nvme0n1: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      17.4kB  268MB   268MB   fat16              legacy_boot
 2      268MB   2416MB  2147MB
 3      2417MB  2427MB  10.5MB  ext4
 4      2427MB  4575MB  2147MB
 5      4575MB  6722MB  2147MB  ext4
 6      6722MB  11.0GB  4295MB  ext4
 7      11.0GB  128GB   117GB   ext4

root@DXP6800PRO-7F5A:~# parted --machine /dev/nvme0n1 print
BYT;
/dev/nvme0n1:128GB:nvme:512:512:gpt:YSO128GTLCW-E3C-2:;
1:17.4kB:268MB:268MB:fat16::legacy_boot;
2:268MB:2416MB:2147MB:::;
3:2417MB:2427MB:10.5MB:ext4::;
4:2427MB:4575MB:2147MB:::;
5:4575MB:6722MB:2147MB:ext4::;
6:6722MB:11.0GB:4295MB:ext4::;
7:11.0GB:128GB:117GB:ext4::;

Backup parttition table of NVMe containing Ugos, see also https://wiki.archlinux.org/title/GPT_fdisk#Backup_and_restore_partition_table.

check for space in current directory

root@DXP6800PRO-7F5A:~# pwd
/root
root@DXP6800PRO-7F5A:~# df -h .
Filesystem      Size  Used Avail Use% Mounted on
overlay         107G  175M  102G   1% /

Save partition data to a backup file in current directory.

root@DXP6800PRO-7F5A:~# sgdisk --backup=sgdisk-nvme0n1.bin /dev/nvme0n1
The operation has completed successfully.

root@DXP6800PRO-7F5A:~# ls -lh sgdisk-nvme0n1.bin 
-rw-r--r-- 1 root root 18K Jul 28 17:54 sgdisk-nvme0n1.bin

Backup Ugos on 128GB NVMe, Using Fedora 40 x86_64 KDE Live

That part of the backup will need booting another OS. I want to dd the 6 small partitions and to have a consintent backup, one does not dd partitions that are mounted and in active use.

That specific ISO simply because Fedora is my default distro and I had Fedora-KDE-Live-x86_64-40-1.14.iso available on my fileserver. You can use any modern Linux distro to do this.

  • Write ISO to USB stick (I used Fedora Media Writer)
  • prepare a second stick for the saved partitions (ext4, simply with Gnome Disks)
  • Live stick to USB3 port on back of DWP6800
  • scratch space stick to USB3 port on front of DWP6800
  • ssh in to vefify both sticks seen and trigger reboot
lsblk and reboot 
root@DXP6800PRO-7F5A:~# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    1  59.8G  0 disk 
└─sda1        8:1    1  59.7G  0 part /mnt/@usb/sda1
sdb           8:16   1  28.8G  0 disk 
├─sdb1        8:17   1   2.5G  0 part /mnt/@usb/sdb1
├─sdb2        8:18   1  12.5M  0 part /mnt/@usb/sdb2
└─sdb3        8:19   1   300K  0 part 
sr0          11:0    1  1024M  0 rom  
nvme0n1     259:0    0 119.2G  0 disk 
├─nvme0n1p1 259:1    0   256M  0 part /boot
├─nvme0n1p2 259:2    0     2G  0 part 
├─nvme0n1p3 259:3    0    10M  0 part /mnt/factory
├─nvme0n1p4 259:4    0     2G  0 part /rom
├─nvme0n1p5 259:5    0     2G  0 part 
├─nvme0n1p6 259:6    0     4G  0 part /ugreen
└─nvme0n1p7 259:7    0   109G  0 part /overlay
root@DXP6800PRO-7F5A:~# systemctl reboot

Broadcast message from root@DXP6800PRO-7F5A on pts/1 (Sun 2024-07-28 19:00:03 CEST):

The system will reboot now!

root@DXP6800PRO-7F5A:~# Connection to guest09 closed by remote host.
  • enter firmware setup again, set F40 Live USB to be first boot entry.
  • since this is a KDE Plasma Live stick, one can mount the scratch stick simply within the graphical desktop
  • save each partition to a separate file using a quick and dirty loop for i in $(seq 1 6); do dd if=/dev/nvme0n1p${i} of=/run/media/liveuser/duoStick/dd-image-of-nvme0n1p${i}.img status=progress; done
  • overly cautious natures might want to also save the large partition number 7 or just the whole device nvme0n1, I chose not to, based on the c’t article where the author also did not back up partition 7 but successfully restored the NASync to run with Ugos.
commands used to image the 6 partitions

first look at the block devices I see now that I booted Fedora 40 Live

liveuser@localhost-live:~$ sudo -i
root@localhost-live:~# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0   2.3G  1 loop 
loop1         7:1    0   8.8G  1 loop 
├─live-rw   253:0    0   8.8G  0 dm   /
└─live-base 253:1    0   8.8G  1 dm   
loop2         7:2    0    32G  0 loop 
└─live-rw   253:0    0   8.8G  0 dm   /
sda           8:0    1  28.8G  0 disk 
├─sda1        8:1    1   2.5G  0 part /run/initramfs/live
├─sda2        8:2    1  12.5M  0 part 
└─sda3        8:3    1   300K  0 part 
sdb           8:16   1  59.8G  0 disk 
└─sdb1        8:17   1  59.7G  0 part /run/media/liveuser/duoStick
sr0          11:0    1  1024M  0 rom  
zram0       252:0    0   7.5G  0 disk [SWAP]
nvme0n1     259:0    0 119.2G  0 disk 
├─nvme0n1p1 259:1    0   256M  0 part 
├─nvme0n1p2 259:2    0     2G  0 part 
├─nvme0n1p3 259:3    0    10M  0 part 
├─nvme0n1p4 259:4    0     2G  0 part 
├─nvme0n1p5 259:5    0     2G  0 part 
├─nvme0n1p6 259:6    0     4G  0 part 
└─nvme0n1p7 259:7    0   109G  0 part

First, test what 6 commands in a loop look like (with just a dumb prepending of echo)

root@localhost-live:/run/media/liveuser/duoStick# for i in $(seq 1 6); do echo dd if=/dev/nvme0n1p${i} of=/run/media/liveuser/duoStick/dd-image-of-nvme0n1p${i}.img status=progress; done
dd if=/dev/nvme0n1p1 of=/run/media/liveuser/duoStick/dd-image-of-nvme0n1p1.img status=progress
dd if=/dev/nvme0n1p2 of=/run/media/liveuser/duoStick/dd-image-of-nvme0n1p2.img status=progress
dd if=/dev/nvme0n1p3 of=/run/media/liveuser/duoStick/dd-image-of-nvme0n1p3.img status=progress
dd if=/dev/nvme0n1p4 of=/run/media/liveuser/duoStick/dd-image-of-nvme0n1p4.img status=progress
dd if=/dev/nvme0n1p5 of=/run/media/liveuser/duoStick/dd-image-of-nvme0n1p5.img status=progress
dd if=/dev/nvme0n1p6 of=/run/media/liveuser/duoStick/dd-image-of-nvme0n1p6.img status=progress

looks fine, so backup using the loop (drop the echo)

root@localhost-live:/run/media/liveuser/duoStick# for i in $(seq 1 6); do dd if=/dev/nvme0n1p${i} of=/run/media/liveuser/duoStick/dd-image-of-nvme0n1p${i}.img status=progress; done
524288+0 records in
524288+0 records out
268435456 bytes (268 MB, 256 MiB) copied, 0.608714 s, 441 MB/s
2120159744 bytes (2.1 GB, 2.0 GiB) copied, 48 s, 44.2 MB/s
4194304+0 records in
4194304+0 records out
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 48.7446 s, 44.1 MB/s
20480+0 records in
20480+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0.252092 s, 41.6 MB/s
2125758976 bytes (2.1 GB, 2.0 GiB) copied, 60 s, 35.4 MB/s
4194304+0 records in
4194304+0 records out
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 60.599 s, 35.4 MB/s
2143335424 bytes (2.1 GB, 2.0 GiB) copied, 64 s, 33.5 MB/s 
4194304+0 records in
4194304+0 records out
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 64.1494 s, 33.5 MB/s
4258763264 bytes (4.3 GB, 4.0 GiB) copied, 143 s, 29.8 MB/s
8388608+0 records in
8388608+0 records out
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 143.973 s, 29.8 MB/s
root@localhost-live:/run/media/liveuser/duoStick# sync
root@localhost-live:/run/media/liveuser/duoStick# sha256sum dd-image-of-nvme0n1p* > dd-image-of-nvme0n1pX.sha245sums
  • eject the stick cleanly, again could do this via GUI because of the flavour of live USB I used.
  • copied to my homelab’s existing fileserver and verified transfer was fine
[root@fileserver UGREEN NASync DWP6800 Pro]# sha256sum -c dd-image-of-nvme0n1pX.sha245sums
dd-image-of-nvme0n1p1.img: OK
dd-image-of-nvme0n1p2.img: OK
dd-image-of-nvme0n1p3.img: OK
dd-image-of-nvme0n1p4.img: OK
dd-image-of-nvme0n1p5.img: OK
dd-image-of-nvme0n1p6.img: OK
  • shut down the F40 KDE Plasma Live cleanly

Restore Vendor OS

Should I ever need to restore Ugos, then I would

  1. boot a live USB
  2. restore the partion table using the backup created earlier with sgdisk
  3. ensure the new parttable is active
  4. write back the 6 images using dd
  5. sync for good measure
  6. make an ext4 on the (not backed up) partition nvme0n1p7 that Ugos uses as an overlay
  7. shut the live USB down cleanly
  8. try to boot Ugos

Pick a NAS distribution

I decided to give TrueNAS 24.10 SCALE (Electric Eel) a try.

While I found installation straightforward, if you need details follow one of These

added 16 GiB RAM

With the factory 8 GiB RAM, I get in TrueNAS

  • Free: 0.3 GiB
  • ZFS Cache: 4.0 GiB
  • Services: 3.1 GiB

While it works with the existing 8 GiB RAM, a 16 GiB stick was only 50€. Refer to UGREEN’s compatibility list if you want to know what the vendor tested. So in a few days I’ll have 8+16=24 which should do for now.

While my initial plan was to max out memory on this host, but where I live, 48 GiB DDR5 SO-DIMMs still seem not in stock at the vendors I trust.

FIXME: link to ark.intel.com page for the CPU as no 48 GiB modules tested by vendor (yet).

update 2025-05-29

Oh oops, I just noticed I never switched this post from draft to published. Fixed now.

Because the old 5900 RPM 4TB drives I put in are not super quiet, the machine has been off more than on. Currently all it does is serve as my backup fileserver, the primary one is a VM on our main hypervisor.

When on, TrueNAS SCALE (these days I have it on 25.04.1) is unobtrusive as an NFS server and as an Emby server.

Related