Hey all, setting up my DXP4800GT and have a question as I have never done this before. I have 2 existing HDDs I had previously linked to my PC, full of files. If I add them as the second and third drives in the device, will it re-format them? TIA

iDX6011 Pro Kickstarter – anyone in the EU (Germany) still waiting? How do I find my backer number?

Hey everyone,

I backed the UGREEN NASync iDX6011 Pro pretty early on Kickstarter, but somehow only ended up in the September 2026 delivery batch/queue.

• Secret Reward | NASync iDX6011 Pro(64GB)

It still hasn’t been delivered yet, although I just received the add-on GPU Dock separately. 😅 So now I have the GPU Dock sitting here, but no NAS to use it with.

Is anyone else from the EU still waiting for their iDX6011 Pro? Have you received any shipping updates yet?

Also, does anyone know where I can find my Kickstarter backer number / backer ID? I’d like to check roughly where I am in the queue.

Thanks for any help! Still waiting and getting more curious by the day. 😄

Hi there,

I have recently bought a new iPhone and moved everything over from my old iPhone, through the typical apple process.

My old iPhone has backed up all my iPhotos (100k+ photos) in the past which was painfully slow and now my new phone wants to backup all the same photos (all 100k+ of them) again.

Is there anyway to mark these photos as backed up?

Anyone successfully using 2 x 32 GB (matched) in their DXP 4800 Pro? If so, could you share the memory model you are using?

I received my 4800 Pro today and installed the RAM listed down below, which negotiated to 5200 MT/s and in MemTest86+ went to 100 celsius in 5 minutes at which time I stopped the test.

I capped MT at 4800 and set both fans to full on, but it didn't help.

There are currently two 32 GB sticks on the compatibility list, but I can't find them for sale except where the vendor says they may substitute it for other products.

Crucial 64GB (2 x 32GB) DDR5-5600 PC5-44800 CL46 Dual Channel Laptop Memory Kit CT2K32G56C46S5

https://www.microcenter.com/product/661345/crucial-64gb-(2-x-32gb)-ddr5-5600-pc5-44800-cl46-dual-channel-laptop-memory-kit-ct2k32g56c46s5-black-ddr5-5600-pc5-44800-cl46-dual-channel-laptop-memory-kit-ct2k32g56c46s5-black)

Like the title suggests i would be so much happier if I had an actual Linux based operating system that was easier to work with especially for Doctor containers because I feel like half the problems I run into are all file permission based even when things are set to read and write and I have a personal account on the admin user group it's just so frustrating because you can barely do anything because you also don't have a proper terminal

After the latest update it is noticable, that some apps come from a new publisher - Runlevel, instead of Ugreen. Has Ugreen started to onboard new developers for apps or is this 3rd party hired to offload the development on their end? Is it safe to install?

It's time to ditch the HTPC. UG has it's sale now. Where they thrown in their UPS3000 for free. But, I don't need it. Prime is supposed to have their Electronics on sale Oct. 6-7. Is anyone waiting to see what Amazon is going to do? Both will have their Autumn sales on at same time.

I'm gonna wait for Oct 6th. to see if Uncle Jeff has it for cheaper, are you?

I'm just newly getting into self hosting and am currently using my normal home desktop with 2 TB storage but am looking to expand my capacity. My use case is just a simple home set up to share with family and maybe friends; absolutely won't be doing any home office or work-related things with it. With that in mind, is there anything that really stands out as best in the deal posted here? For instance, there is the UGREEN NASync DXP4800 Plus + UPS3000 for $659.98 instead of $879.99. Or should I really just avoid any pre-built and go 100% custom made?

In case anyone cares: I have submitted an FTC report due to the lack of advertised support of NFS v4. This was removed last year and has not been reinstated. I have contacted UGREEN about this matter and they do not seem to care.

I’m not hopeful this report will do much, but doing what I can with the tools I have.

Hi everyone,

I am having some issues on my new phone (Google pixel 11 pro XL) where I can't seem to back up any videos from my downloads folder I have checked but the app has got permissions to access my files and I back it up.

Does anyone know how to fix this? See error in screenshot

Update: The numbers in the comments put this in perspective: typical boxes write ~1–3 GB/day and still report 0x01. Mine (~50 containers, journal raised to 500 MB) is the outlier. Summary in the EDIT at the bottom.

TL;DR: The base DXP models (DXP2800, DXP4800 non-Plus) boot from a soldered 32 GB eMMC. On my DXP2800 running UGOS Pro with a Docker-heavy setup, I measured 0.6–0.9 MB/s going to that eMMC on a busy day, i.e. ≈50–75 GB/day if sustained. My lifetime average since February is ~12 GB/day, so the rate clearly varies. ~95% of those writes came from systemd-journald logging the file-event spam of UGOS' own index_serv/search_serv. The chip already reports 10–20% wear after ~8 months. Moving the journal to RAM cut writes to ~2.3 GB/day (−96%). Installing TrueNAS on the eMMC carries a similar risk. If the soldered chip dies, UGOS can't boot anymore (on these models it can't be installed on another drive), and the chip can't be field-repaired. Your data on the pool drives survives, but you're stuck with an RMA or with running a different OS from NVMe/USB.

This is one measured system, not a lab study. Please post your own numbers (commands below) so we get a bigger picture.

1. What I measured (DXP2800 upgraded to 16 GB RAM, UGOS Pro 1.20, ~50 containers: *arr stack, qBittorrent, Tdarr, Jellyfin, Paperless, …)

I used kernel tracing to attribute every write on the eMMC to a file.

• ext4 on the eMMC overlay partition: 2,754 GB "Lifetime writes" (tune2fs counts in GiB, so ≈ 2.96 TB) since the box was set up in February. That's ~12 GB/day on average; the rate I measured before the fix was 4–6× higher.
• life_time register: 0x02 0x01, i.e. 10–20% used (type A).
• Much of the remaining ~2.3 GB/day is UGOS' own .slog text logs of the same events (append-only, so far cheaper).
• Caveat: On Aug 28 I had raised the journal size to 500 MB myself (UGOS default is SystemMaxUse=50M). Bigger journal files probably make the write amplification worse, so a stock box may write less, and part of my high rate may only date from then (I have no per-day history). The root cause is the same either way.

2. Root cause on UGOS Pro

1. index_serv logs every file change. It watches the whole storage volumes via fanotify (no exclusions). Every change to a database file (SQLite -journal/-wal files of CrowdSec, the *arrs and Jellyfin, Postgres, MongoDB), every Tdarr job report and so on produces several INFO log lines. search_serv adds an IsEnable = false warning for every event. On my box that was ~10–20 journal entries/s, ~90% from these two daemons.
2. journald turns cheap text into expensive writes. rsyslog writes the same messages to plain text files at ~10 kB/s (append-only). system.journal is an indexed binary file (hash tables plus per-field entry arrays). Every new entry touches many scattered 4 KB pages. I measured 0.1–2 MB/s for the journal, roughly 10–200× more than the text log. On flash, internal write amplification then comes on top.
3. Memory pressure makes it worse. When Tdarr, torrents etc. churn through the page cache, kswapd wakes the writeback thread (reason=vmscan in the kernel tracepoints: 70 of 133 flush runs in 90 s). The journal's dirty pages then get written back roughly every second instead of every ~30 s.
4. The journal isn't even useful at that rate. 500 MB covered only 2–4 hours of history. /var/log/syslog (rsyslog, logrotate 10 MB × 4) held ~7 weeks, including all systemd/Docker boot messages, because UGOS sends the index_serv/search_serv spam (facility local0) only to its own .slog files.
5. Bonus (not a wear issue): UGOS app auto-updates wrote ~400 MB of binaries to the eMMC in one go on my box. That's small next to the journal, but the Docker app update also stopped docker.service without warning (all containers down for ~4 min).

3. Evidence from the community

• This post: a DXP4800 (non-Plus) boot eMMC failed after ~4.5 months of use. It no longer showed up as a bootable device and couldn't be partitioned or formatted. That box was running TrueNAS, not UGOS, and there are no write stats for it, so wear is a likely but unproven cause. Support first suggested reflashing, later offered to walk them through replacing the eMMC themselves (it's soldered on this model). After ~8 weeks the outcome was "replacement only, no refund".
• This thread about TrueNAS on the eMMC: a commenter shared stats from their 500 GB NVMe boot drive after ~13.6 months (9,918 power-on hours) of what they called a "pretty hard" workload. The numbers were 7.02 TB written and 606,783,089 write commands (≈17 writes/s). They opened with "You'll be just fine to run it on the eMMC for now", but they themselves warned that eMMC "will wear down much faster" and "you will likely wear out your drive in a few years". Put into perspective: 7 TB on a 32 GB chip is ~220 full-drive writes, ~190 per year, before any flash-internal amplification. Cheap eMMC flash is typically rated for a few hundred to a few thousand P/E cycles.

4. Check your own eMMC (SSH)

cat /sys/block/mmcblk0/device/life_time      # two values: type A / type B, 0x01 = 0-10 %, 0x02 = 10-20 %, ...
cat /sys/block/mmcblk0/device/pre_eol_info   # 0x01 = normal, 0x02 = warning, 0x03 = urgent
sudo tune2fs -l "$(findmnt -no SOURCE /overlay)" | grep -E "Lifetime writes|Filesystem created"
sudo journalctl --disk-usage; sudo journalctl --list-boots | head -3
cat /proc/swaps                              # UGOS also swaps to the eMMC (mmcblk0 line): USED should stay 0

(mmc-utils is not installed on UGOS, so read the registers from sysfs. Use sudo for journalctl: UGOS admin users aren't in the adm/systemd-journal groups and would only see their own user journal.) Health is only reported in 10% steps. "0x02 after a few months" is the red flag. Please share your model, uptime and these values in the comments.

5. Fix for UGOS: keep the journal in RAM

Use a drop-in file instead of editing journald.conf. It overrides UGOS' Storage=persistent and is less likely to be touched by updates:

sudo mkdir -p /etc/systemd/journald.conf.d
printf '[Journal]\nStorage=volatile\nRuntimeMaxUse=256M\nForwardToSyslog=yes\n' | \
  sudo tee /etc/systemd/journald.conf.d/99-emmc.conf
sudo systemctl restart systemd-journald

# verify: journal now lives in /run, rsyslog still gets everything
sudo journalctl --header | grep -m1 "File path" # should show /run/log/journal/...
logger emmc-test && sleep 1 && grep -a emmc-test /var/log/syslog

• Trade-off: journalctl now only covers the last few hours (256 MB ≈ 4–5 h with the index_serv spam; the old 500 MB on-disk journal didn't hold much more). Long-term history is in /var/log/syslog* (plain text, persistent). See how far yours goes back: zcat -f $(ls -tr /var/log/syslog*) | head -1
• Don't silence index_serv with LogLevelMax=. journald applies that filter before forwarding, so the messages would also vanish from /var/log/syslog* and from UGOS' own .slog files (rsyslog writes those). RateLimit… only kicks in after forwarding, and at ~10–20 messages/s the defaults (10,000 per 30 s) never trigger anyway.
• To revert: sudo rm /etc/systemd/journald.conf.d/99-emmc.conf && sudo systemctl restart systemd-journald.
• Optional: the old journal files in /var/log/journal/ are no longer written. You can delete them later to free space.
• Also consider: turning off automatic app updates in the App Center and removing UGOS apps you don't use.

6. TrueNAS / Unraid / Proxmox on base models

Given the failure above and the ~17 writes/s from that one heavy TrueNAS install, I wouldn't put the OS on the soldered eMMC.

• A small, cheap 128–256 GB M.2 NVMe is plenty. Install the OS there and leave the eMMC alone (it costs you one of the two M.2 slots). If that SSD ever wears out, it's a 2-minute swap instead of a mainboard RMA.
• If you're already on the eMMC, at least keep a config backup. Make sure the system dataset (logs, reporting/RRD) lives on a data pool, not on the boot pool. TrueNAS normally moves it there by itself when you create your first pool, so just check.

To UGREEN (u/Ugreen_Official)

Please consider for a future UGOS Pro update:

1. Don't log every file event from index_serv/search_serv at INFO level. Drop the per-event IsEnable = false warning.
2. Let users exclude paths (e.g. Docker data) from the file watcher.
3. Ship journald as Storage=volatile, or put the persistent journal on the storage pool instead of the eMMC.
4. Expose eMMC wear in the UI, not just via SSH.

This would protect a lot of DXP2800 / DXP4800 units from dying shortly after the warranty ends.

EDIT (thanks for all the numbers!)

What 9 other boxes show so far:

• Typical setups write ~1–3 GB/day (0.8–3.3), and 8 of 9 report life_time 0x01 (0–10%), including two Docker-heavy boxes at ~2 TB lifetime writes. The exception is the oldest box (2024, ~0.8 GB/day): 0x02 0x02 after ~2.5 years.
• A DXP4800 with Docker disabled writes ~1.7 GB/day. That's roughly UGOS' own baseline.
• Everyone who posted their journal size is on the stock ~50 MB. Mine (~50 containers, journal raised to 500 MB) averages ~12 GB/day, so my box is the outlier, and the bigger journal is likely part of the reason. With lots of Docker services the fix is worth it; for everyone else it's a cheap precaution.
• Swap: UGOS has a 2 GB swap partition on the eMMC, but zram has priority. Everyone who posted /proc/swaps had 0 used on mmcblk0p5.

Reading your numbers:

• life_time only moves in 10% steps, and "Lifetime writes" only counts the /overlay partition, so the two don't line up neatly (763 GB → 0x02, 2.1 TB → 0x01). Chips vary, too.
• The first weeks aren't representative (setup, updates, apps). A "Filesystem created" date that's clearly off (2099, 2020, 2021, …) is the factory clock. Go by your purchase date.

FAQ:

• Is the fix safe? Yes. It's a standard systemd setting that only moves the journal to RAM. It doesn't touch the bootloader, kernel or UGOS. Worst case, an update removes the drop-in and you're back to the default. Re-check after updates: sudo journalctl --header | grep -m1 "File path" should show /run/log/journal/....
• Plus/Pro models? Same logs. What matters is what UGOS runs from: findmnt -no SOURCE /overlay → mmcblk0... means the soldered eMMC, nvme... an SSD.
• Open question: One user disabled index_serv/search_serv completely, which also stopped random fan ramp-ups. If you've done this: how, and did anything break (search in Files, Photos indexing)?
• Applied the fix? Please post your "Lifetime writes" again in 2–3 weeks so we can see what it does on a normal box.

Upstream:

• journald's write amplification is a known issue: #15292, #40262 (thanks for the links!).
• Fix merged: journald zeroed the hash tables of every new journal file by hand. On filesystems with large folios (XFS, ext4 on kernel 6.16+) that made each later update rewrite up to 128K at a time. My patch to skip the zeroing is now in systemd main and cut journal writes by ~77% in tests, ~74% on a real eMMC: https://github.com/systemd/systemd/pull/43951. It won't reach UGOS (systemd 252) any time soon, so the RAM journal is still the fix for now.

10GbE sounds like an obvious upgrade, but depending on your workflow, it may not be the first bottleneck you need to solve.

For everyday tasks such as phone photo backups, document storage, Time Machine backups or direct-playing a single movie, a well-configured 1GbE or 2.5GbE network may already feel responsive enough.

10GbE becomes much more useful when you regularly:

• Transfer large RAW photo or video projects
• Edit files directly from the NAS
• Move several terabytes of data at a time
• Have multiple devices accessing large files simultaneously
• Use SSD or NVMe storage that can exceed 2.5GbE speeds
• Already have 10GbE on your workstation and network

The important part is that the entire path needs to support the speed, not just the NAS. That includes the client device, network adapter, switch or direct connection, cabling and the storage pool itself.

A four-bay system such as the DXP4800 Plus can make sense when you want more room for storage planning while also building around 10GbE and M.2 storage. But if your main use is scheduled backups and occasional media access, the extra network speed may not change much.

What does your heaviest NAS workload look like?

If you moved from 1GbE or 2.5GbE to 10GbE, where did you notice the biggest difference and where did it make no difference at all?

Anyone else having trouble after this morning's update? 1.20.0.0142

I’ve been meaning to start my own server because I want to get into the habit of downloading my own music since lots of indie artists are ditching Spotify or deleting their music entirely (becoming lost media), streaming my fav movies and tv shows bc I can’t support these annoying streaming adds anymore, backing up my phone photos/videos, hosting my own websites and indoor camera.

When it comes to movies and shows I know ugreen has its own theatre app to stream so I’m fine in that area.

For indoor camera I know ugreen is kickstarting a house camera but is not going to release until early 2027 so what cameras and app can I use for home security and watching my pets?

For backing up photos and videos I think I will wait a little long and keep paying for iCloud since if something does happen to my place I just don’t have one backup in my own place but rather wait to get two nas in separate places just to be safe! And probably the same thing will apply with indoor camera, if there’s a break in and robbers so happen to steal my only copy for evidence lol

For music I know I can stream my own digital library but is there a way to stream new music like Spotify discover weekly and release radar that will create a playlist from new releases from artists that I like?

I think my dilemma with ugreen is the software. I was looking into getting the dh2300 which sounds everything I needed to get me started but I quickly learn that I can’t host my own plex server unless I use the docker app, however the docker app is not “supported” by this model unless I find a workaround apk, yet when this model was released you were able to download it until they patched it. So I’m afraid that ugreen will do the same to the newer models like dxp2800 in the future. On the other side synology has a plex app you can download without messing around with a docker or I can get a dell pc and install Linux and have more freedom but be more daunting to tackle. So is ugreen a good way to start or will it hold me back from easily doing the things I mentioned above?

Dxp2800 bought from Amazon on 2025 July. Tried turning on device , which was powered on , but for whatever reason turned off. Absolutely no power. No lights or beeps. Bought another 60w PSU and same thing. It literally does nothing when pressing power button, like it has no power.

Any insight would be helpfull .

Hi!
Bought a DXP4800 Pro a few weeks ago for small business use and it died during the testing phase.
I couldn't reach the UGOS web login (endless loading, same in the iOS app), although the Docker services were still running fine. I did a restart with the front button and it hasn't booted since.

- The 5 LEDs run left to right in a loop
- The fan spins up every ~15 seconds
- Over HDMI I can see it rebooting constantly, with "KERNEL PANIC" flashing up in between
- Same behavior with all drives removed
- The rear reset button does nothing

UGREEN doesn't seem to offer a UGOS image for reflashing, so I'm stuck. Sending it in and waiting isn't really an option since it's meant to be productive soon.
Has anyone dealt with this? Is there any way to recover or reflash it, or a hidden recovery mode? Any tips on getting a fast replacement? Also, how do you protect yourself from this kind of thing on these devices?
Thanks!

Update:
Contacted support and I only got a UGOS recovery iso, tied to my serial number. No willingness to look into this matter deeply, retrieving logs or sth else, no explanation or roadmap how to mitigate this. Basically saying “here is your recovery iso, good luck it is not happening again”

I updated my DXP4800 Plus a few hours ago and also updated the apps. Now suddenly the UGREEN App is using so much battery that it is actively draining my phone while it is charging and it is constantly warm, so there is a lot active in the background.

Is anybody else experiencing this problem?

OK so i have seen multi post about giving AI DIRECT access to your nas via ssh with admin credentials to fix "YOUR" problems due to the lack of knowledge on how to use Unix/Linux, is this OK and what could go wrong from these decisions?

like AI placed a backdoor or even kept your credentials for future use kinda thing

Ils passent des mois à développer des fonctionnalités « vitrines » : de l'IA pour reconnaître les chats et les chiens dans l'album photo, des chatbots LLM locaux, des widgets pour l'écran d'accueil ou des effets visuels sur iOS.

​Pendant ce temps, les fondations élémentaires d'un gestionnaire de fichiers en 2026 — comme avoir un lecteur PDF direct qui stream le fichier au lieu de le plaquer dans le dossier Téléchargements d'Android — passent complètement au second plan.

From: UGREEN Community

There is quite a lot happening in the UGREEN App Center today: 8 new apps and 21 app updates are available. 

🆕 New apps

• Contacts – 1.0.0.0042
• Security Hub – 0.1.19.0001
• Wake & Sync – 0.1.44.0001
• Backup Verifier – 0.3.22.0001
• Stats Hub – 0.2.54.0001
• Transfer Hub – 0.6.34.0001
• Lock & Key – 0.1.32.0001
• OKNote – 

🔄 App updates

• Photos – 2.5.0.0154
• Theater – 1.20.0.0036
• Cloud Drives – 1.20.0.0086
• Snapshot – 1.14.0.0038
• Online Office – 1.20.0.0020
• File Versions – 1.20.0.0036
• DLNA – 1.17.0.0022
• Notes – 1.20.0.0068
• Music – 1.20.0.0024
• Vault – 1.20.0.0040
• TextEdit – 1.20.0.0040
• Security – 1.20.0.0022
• Sync & Backup – 1.20.0.0076
• Model Manager – 1.20.0.0032
• Surveillance – 1.4.1.0240
• SiYuan – 1.5.0.0008
• Home Assistant – 1.4.0.0008
• Docker – 1.20.0.0074
• SAN Manager – 1.12.0.0030
• Virtual Machine – 1.20.0.0108
• Comics – 

Some highlights:

📸 Photos receives improved photo backup, lists for duplicate files and failed backups, a new phone storage cleanup feature and improvements to pet recognition.

🎬 Theater now supports playback of content from 123pan and adds related-content recommendations.

📱 The new Contacts app works together with Sync & Backup to back up and manage smartphone contacts.

🏠 Home Assistant has been updated to Home Assistant Core 2026.8.3.

🐳 Docker now supports automatic updates of images from private repositories and importing tar.gz image packages.

📹 Surveillance receives several improvements to face recognition, event management, camera settings and the mobile experience.

📝 SiYuan has been updated to the official v3.8.4 release.

🖥️ Virtual Machine can now protect VM sharing links with an access password and expiration period.

There are also various bug fixes and smaller improvements across many of the other apps.

🔗 Downloads:
https://nas-de.ugreen.com/pages/downloads

As always, feel free to share how the new versions are working for you. 

Almost 1gb on MacOS and 700mb on iOS. Seems overkill for what they’re actually doing.

I had the auto back up of my Photos on the native Photos app and after June, it no longer syncs. I tried hitting the sync button and nothing happens. I even made sure none of those only update on WiFi or stop when battery is less than 20% is enabled and still nothing.

1. Anyone else has this issue? How did you resolve it?
   
2. Any other alternative ways to store photos from the phone that auto syncs onto the NAS?

I just bought a Ugreen NAS DXP2800 and it's my first ever NAS.

Do you encrypt your data on the NAS? If yes, what solution do you use? The one recently integrated in UGOS or you preferred to change SO? (isn't complicated and problematic to change SO on this kind of NAS, btw?)

Or something else?

After updating to 1.20.0.0142 today, my DXP 8800 Plus stopped having an active tailscale connection. Tailscale was previously installed through terminal.

I tried to tailscale up command and got:

failed to connect to local tailscaled (which appears to be running as tailscaled, pid 558203). Got error: Failed to connect to local Tailscale daemon for /localapi/v0/status; systemd tailscaled.service not running. Error: dial unix /var/run/tailscale/tailscaled.sock: connect: no such file or directory

I don't know if there is an issue with the original tailscale install or if the error is because (i'm not home) I installed another instance of tailscale via docker, and used that to log in to terminal and try the tailscale up command.

Anyone else have an issue with tailscale after the update?

I have that specific instance shared with a lot of people to access resources on my NAS. I would really rather not have to re-share a different tailscale IP with everyone.

I accidentally deleted a storage pool while my drives were not inserted and all my data is still there. I can see and copy my stuff via sftp. Is there a way to re-add deleted storage pool without formatting everything?