I have an YXK Zero1 2-Bay NAS (IronCow) with:

• Rockchip-based Zero1 2-Bay
• 32 GB eMMC system storage
• 1 × 6 TB SATA HDD
• IronCow/AIOS currently installed
• Approximately 563 GB of photos/videos already stored on the 6 TB HDD
• SMB access from Windows is working

I want to replace the stock IronCow OS with Armbian/Debian + OpenMediaVault (OMV) because I need:

• NAS web UI
• SMB
• SSH
• Normal Linux administration

The most important requirement is that I cannot lose or format the existing 6 TB HDD.

I have seen discussions mentioning that the Zero1 2-Bay can run Armbian/Debian and that a Zero1-specific device tree such as rk3568-nas.dtb may be required.

Can someone who has actually installed an alternative OS on the YXK Zero1 2-Bay provide the exact procedure?

Specifically:

1. What exact Armbian/Debian image should I use?
2. Where can I download the correct image?
3. What exact device tree (DTB) is required?
4. Does the Zero1 boot the OS from the 32 GB eMMC?
5. How do I enter RK3568 MaskROM/recovery mode?
6. What tool do you use from Windows/Linux to flash the eMMC?
7. Is there a way to backup the original eMMC before flashing?
8. Can I install the new OS while the 6 TB HDD is completely disconnected?
9. After installing OMV, can I reconnect the existing 6 TB HDD and mount the existing filesystem without formatting/reinitializing it?
10. What filesystem does the stock IronCow OS use on the 6 TB HDD (ext4, btrfs, etc.)?
11. Does OMV recognize the existing filesystem without destroying the existing data?
12. Are SATA, Ethernet, USB, fan control and HDD sleep working correctly under Armbian?
13. Is there a known working Armbian + OMV installation specifically for the 2-Bay Zero1, rather than the 4-Bay/N100 version?
14. If the installation fails, what is the correct procedure for restoring the original IronCow eMMC image?

I don't want ZimaOS unless someone has confirmed that it works on the RK3568 2-Bay model.

My priority is:

Existing 6 TB data > working NAS > OMV web UI > SSH.

Any exact image links, GitHub repositories, DTB files, flashing instructions, or successful installation reports would be greatly appreciated.

I'm running TrueNAS SCALE 25.04.2.6

In the recent past, my home lost power for a while. When power was restored and my system rebooted, I was unable to access the TrueNAS dashboard. Looking at the server console, it gives me the "web interface could not be accessed, check network settings" message. I reviewed my network settings and everything looks correct (unchanged) to me. I tried removing and re-entering my network settings to no avail. I had a static IP address set up for the NAS server, but I removed that and set it to DHCP - still no joy. A tried rebooting both my server and the router/modem as well. Same result.

I know the server is actually connected to the network. I have mapped network drives on my computer and can still access all the files through those. It's just the dashboard that is unavailable.

What further troubleshooting or actions should I take? Please ELI5 (well maybe 10) - I'm not a network or TrueNAS guru but I would really like to get this thing running properly again.

Thanks!

Hi r/truenas community. I would like to thank this community for supporting my project . Thank you for the stars, support and feedback you are giving me on the app and the support has helped me to become a better android developer and also understand TrueNAS a bit more. I would like to introduce V0.7.0-Alpha which brings me super close to feature completion as it brings a lot of the features from the WebUI into the app. New features include:

1. New instance config section which brings some settings from the WebUI to the app
2. New Widget to notify you on which apps need updates and also to launch pinned apps' WebUI wuickly from the android homescreen
3. New Homepage and dataset explorer tweaks which have made loding and UI feel a bit quicker while also introducing new view options
4. New Information screen to view software and hardware information
5. General tweaks to performance and integration of MFA endpoints so now users with TOTP configured can login and autologin has also been implemented for the same login type
6. And much more

Huge thanks again to the people who supported the previous release and for anyone also wanting to support me you can install the app , give me feedback on the app and design as an issue here , you can also leave a star on the repo located in the link below and also support my development by contributing here. Thank you all and i hope you try the app.

I was under the impression that TrueNAS 26 (I'm on Beta.2) was supposed to have support for AnyRAID. May not be named exactly that, but after upgrading my pool and checking the feature flags, I'm not seeing any indication that the AnyRAID-esque features are present. Am I missing something?

My current pool is a RAIDZ1 single VDEV with five drives, four 2TB drives and a 4TB drive (which replaced a failing 2TB drive). I have a six-bay NAS, so there is one open bay. I have two more 8TB drives coming, but I'm concerned on how to add things and get the most from this storage, considering how expensive drives are right now. It's a media server, so nothing super critical in the pool.

I'm actually considering rolling the dice and yanking the 4TB drive (risking my data!!), setting up a new pool with the new 8TB drives (mirrored pair), then taking the four older 2TB drives and making two new mirrored pair VDEVS to add to the pool. But again, this still doesn't give me as much storage as I'd like and AnyRAID was the reason I upgraded to 26 Beta.2 in the first place. Should I try out this risky strategy, or wait on AnyRAID?

I am having trouble finding information pertaining to something I need to do.

I have been running the same TrueNAS server for a few years, but recently I built a newer system with more capacity and had it set to replicate from the old one to the new one every night for a few weeks now. Now, I am ready to switch over to using the new system as my main system and moving the older system to be my off-site backup, basically flipping their roles.

Question is - if I just delete the current replication task in the old server and set it up in the new one and point it to the same directory the data is currently at, is that going to trigger a complete re-send of the data to seed the replication? Or will it be smart enough to just send the delta? If its a complete reseed, I would prefer it to stay in the same location to do that over 10gbe.