I’ve been considering using DietPi on my UGREEN DXP4800 Plus NAS and wanted to ask if it was worth it. It already came with a pre-installed OS but I find it limited and am unsure whether to migrate and where to migrate to.
IDK if it’s possible, but you will lose your warranty if you install a 3rd party OS on the UGreen NAS.
I’m fine with losing warranty. I still left the base OS (UGOS) on the SSD so i think it should be fine either way
I’m having an issue where using the UEFI installer immediately takes me to the grub CLI and BIOS/CSM loads the installer but had some error having to do with the kernel. I additionally tried doing debian → dietpi-install but that resulted in a blank screen with only the blinking command line cursor, and when re-booting into debian being encountered with a CLI.
Is there any way to get around this or is DietPi simply not supported on ugreen nas?
officially? nope we don’t have tested this.
where at which stage if the installer??
Do you know whether this NAS supports 64-bit EFI binaries? There were some Intel box cases which support 64-bit distros but weirdly 32-bit EFI only, which is neither supported (shipped with) our x86_64 images, nor dietpi-installer.
This occurred just after clicking install
I think so. I’m not sure how to check for this though.
Do you have a Debian UEFI image which works on the board, or used the Debian installer on it? You could then check whether grub-efi-ia32 is installed, or grub-efi-amd64:
dpkg -l | grep grub-efi
Running this command outputted
ii grub-efi-amd64 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii grub-efi-amd64-bin 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
ii grub-efi-amd64-signed 1+2.06+13+deb12u1 amd64 GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian)
This is on Debian 18.
You mean Debian 12 (Bookworm)? Debian 18 does not exist. However, 64-bit EFI is installed, so that is not the problem.
Just to be sure, when you use the official Debian installer, you get a functional Debian? And above output is result from that Debian image? Can you check also which kernel is installed, and some other info:
dpkg -l | grep linux-image
cat /etc/initramfs-tools/{initramfs.conf,modules}
cat /etc/default/grub
The packages are all the same, and our config is mostly default, hence I wonder what the difference is.
Oh, I apologize for the confusion there lol
Yes. When using the debian installer, I was able to boot from USB and install debian on the NAS without any issues. Yes, these commands were run from the debian image.
root@oscnet-main-dxp4800plus:~# dpkg -l | grep linux-image
ii linux-image-6.1.0-27-amd64 6.1.115-1 amd64 Linux 6.1 for 64-bit PCs (signed)
ii linux-image-6.1.0-28-amd64 6.1.119-1 amd64 Linux 6.1 for 64-bit PCs (signed)
ii linux-image-amd64 6.1.119-1 amd64 Linux for 64-bit PCs (meta-package)
root@oscnet-main-dxp4800plus:~# cat /etc/initramfs-tools/{initramfs.conf,modules}
#
# initramfs.conf
# Configuration file for mkinitramfs(8). See initramfs.conf(5).
#
# Note that configuration options from this file can be overridden
# by config files in the /etc/initramfs-tools/conf.d directory.
#
# MODULES: [ most | netboot | dep | list ]
#
# most - Add most filesystem and all harddrive drivers.
#
# dep - Try and guess which modules to load.
#
# netboot - Add the base modules, network modules, but skip block devices.
#
# list - Only include modules from the 'additional modules' list
#
MODULES=most
#
# BUSYBOX: [ y | n | auto ]
#
# Use busybox shell and utilities. If set to n, klibc utilities will be used.
# If set to auto (or unset), busybox will be used if installed and klibc will
# be used otherwise.
#
BUSYBOX=auto
#
# KEYMAP: [ y | n ]
#
# Load a keymap during the initramfs stage.
#
KEYMAP=n
#
# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz | zstd ]
#
COMPRESS=zstd
#
# COMPRESSLEVEL: ...
#
# Set a compression level for the compressor.
# Defaults vary by compressor.
#
# Valid values are:
# 1 - 9 for gzip|bzip2|lzma|lzop
# 0 - 9 for lz4|xz
# 0 - 19 for zstd
#
# COMPRESSLEVEL=3
#
# DEVICE: ...
#
# Specify a specific network interface, like eth0
# Overridden by optional ip= or BOOTIF= bootarg
#
DEVICE=
#
# NFSROOT: [ auto | HOST:MOUNT ]
#
NFSROOT=auto
#
# RUNSIZE: ...
#
# The size of the /run tmpfs mount point, like 256M or 10%
# Overridden by optional initramfs.runsize= bootarg
#
RUNSIZE=10%
#
# FSTYPE: ...
#
# The filesystem type(s) to support, or "auto" to use the current root
# filesystem type
#
FSTYPE=auto
# List of modules that you want to include in your initramfs.
# They will be loaded at boot time in the order below.
#
# Syntax: module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod
root@oscnet-main-dxp4800plus:~# cat /etc/defaults/grub
cat: /etc/defaults/grub: No such file or directory
Okay, regular kernel and initramfs-tools config is just defaults. For GRUB it was a typo:
cat /etc/default/grub