-
Upgrade & Migrate
How about getting a new instance running on the new hardware, and then migrating the array?
-
Upgrade & Migrate
Also asked about this in this thread: https://forums.unraid.net/topic/199098-unraid-730-731-array-startperformance-related-issues/ But what's the support like in 7.x for 9400 & 9305 -16i cards for connecting all the drives?
-
Upgrade & Migrate
Currently a pool - BTRFS (mirror) I've not really upgraded for a few reasons, primarily because everything has just been working and I didn't need any new features and haven't paid attention as a result. Secondly, when I upgraded to 6.x there were a few bugs I ran into, so I was a bit gunshy I will make a backup of anything truly important (VMs, personal files, etc) but most of the storage and function is just my Plex server now. If it was all lost that would suck, but not the end of the world. In fact, one of the things I kicked around if this would matter is making a second parity drive prior to moving. today I have a single parity drive, and 8 drives in the array. In the new server I plan to have 15+ drives, so as I understand it dual parity is pretty important at that level.
-
CowboyRedBeard started following Fix to a small issue with updating OCI docker images , UNRAID 7.3.0 --> 7.3.1 array start/performance related issues , Upgrade & Migrate and 1 other
-
UNRAID 7.3.0 --> 7.3.1 array start/performance related issues
Any recent news on this topic? I'm building new and in plans was a 9305-16i but seeing this I've paused on buying one.
-
Upgrade & Migrate
Hi guys, appreciate any help or feedback. I've been running unraid for about 9 years now, and several of those have been on my 2nd (current) server which is a SuperMicro X9DRi-LN4+. It's been pretty solid, but is getting very old and my use case has changed considerably in this time. I no longer need the CPU power that I had need for when I started. Also, I'm out of room in the current tower for more drives. I have a number of drives that have been traded out for the increase-the-storage-now shuffle over the past few years that I could put back into play for more storage on the array. As such, I've got a new build on the way. I have a few questions about the process however. I plan to migrate essentially the drives only. The USB that my unraid is on is of the same age, seems like a good time to replace that. My new system will also be an ASRock W880D4U, and with it two new NVME drives to replace my current SSD drives for the cache pool. Additionally, I'm on version 6.12.6 so I'd like to upgrade at the same time. Is there a way to transfer the USB to a drive or partition on the new server, or is it better to just get a new USB? For migration of the cache, should I move everything from the cache to the array via the mover? Also, for the upgrade, is it best to just have a fresh install of the latest unraid and then move the drives and restore things individually? There are several things I won't need to migrate like old plugins (nvidia plugin) etc. I've also made some changes over the years which are probably not relevant to the new system. Backup up the flash drive > move via mover to array > migrate drives etc? Also, I do have a great affinity for a process that allows me to roll back to the existing server should there be any problems. What's your thoughts? What am I missing?
-
How do I carefully upgrade this old rig?
I'm on 6.12.6 and have been since it came out. Everything "works" but I'm sorta weary of being this far behind. However, in times past I've upgraded and broken things... The system has been pretty solid for me for at least a year, maybe two... honestly I can't remember, and that's part of the problem. I did things along the way over the last 6 years or so, then just started ignoring system maintenance. What's the best path to upgrade and back things up to avoid problems, and then be able to roll back if I have them? An example is the USB drive I used for this system is probably almost 10 years old, and it has been running unraid the whole time. In fact, this box has been turned on with the exception of a few days for at least 6 years (on this MB and setup). When I first built this system, I had a number of VMs on here for different things and a bunch of dockers. Now it's essentially used for two very small VMs that I could live without and stuff to support Plex. Is it a consideration to just start fresh and copy over what settings I need? I've also considered building a less power hungry newer system, since I don't need this much compute power any longer. System: Supermicro X9DRi-LN4+ Dual Intel® Xeon® CPU E5-2690 v2 I have the following plugins, surely some of these are no longer compatible. What else should I review? CA Auto Update Applications 2024.03.17 CA Backup / Restore Appdata 2023.03.28c CA Cleanup Appdata 2024.11.28 Community Applications 2025.10.27 Dynamix Cache Directories 2025.11.14 Dynamix System Information 2025.11.14 Fix Common Problems 2025.08.07 IPMI support 2025.12.13 Nvidia Driver 2025.03.25 Tips and Tweaks 2025.03.06 Unassigned Devices 2025.11.18 Unassigned Devices Plus 2025.08.05a User Scripts 2025.06.21
-
"access beyond end of device" BTRFS Cache Drive
Happy to help for the sake of finding out something new for the community if you give me the commands to run... already ordered a new one.
-
"access beyond end of device" BTRFS Cache Drive
I'm on 6.12.6 and have started getting this error with my cache drive. May 1 09:30:00 Tower kernel: sd 11:0:0:0: [sdg] tag#1 access beyond end of device May 1 09:30:00 Tower kernel: I/O error, dev sdg, sector 220241888 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 May 1 09:30:00 Tower kernel: BTRFS error (device sdg1: state EA): bdev /dev/sdg1 errs: wr 101, rd 1385, flush 0, corrupt 0, gen 0 May 1 09:30:00 Tower kernel: I/O error, dev loop2, sector 13370056 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 May 1 09:30:00 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 10, rd 3331, flush 1, corrupt 0, gen 0 I found no posts on this forum, but found this: https://aufarg.github.io/btrfs-access-beyond-end-of-device.html And this is beyond my current level.... is this a thing others have seen in unraid? A reboot fixed it for me the last two times this has happened, is this an issue with the drive maybe? It's only about 2 years old. It's a Crucial CT1000MX500SSD1 Rev: M3CR043
-
VM BACKUP
There's two templates... what's the difference there?
-
Tell me about backups
What is everyone doing for backups of VMs at the moment? I saw that 6.13 / 7.0 may have snapshots built in... But in the interim, is there a good backup system that uses deltas? Currently I've just been shutting down the VM and making a copy, but those are huge files and the number of VMs I have are growing and their importance to my operations is also increasing. Thanks in advance for the advice!
-
6.10.3 to Latest Stable
- 6.10.3 to Latest Stable
Hey fam, I'm considering upgrading now that CA tells me I don't meet the minimum build version. I have been running unraid for 6+ years on this same box, and in the past had a few strange issues that went away when I upgraded to 6.10.3. So I've been apprehensive to upgrade. I run about 25 different dockers, and 4 VMs full time in addition to general services like shares. MB is a Supermicro X9DRi-LN4+, and I have the NVIDIA pass-thru situation going on (plugin). What is some general advice on finding a safe upgrade path? Also I've had this same SanDisk Cruzer Fit USB for unraid for 6 years now, and the server has been basically turned on that entire time (a few power outages & maint windows for additional drives). Should I swap that out at some point? What's the best way to back up my unraid install? I guess I'd go to latest stable which is 6.12.4 at this time, anything to look out for there? Thanks for the help!- [Support] Data-Monkey - netdata
I keep getting "not available" update status on the docker tab, is this still the right URL? https://hub.docker.com/r/netdata/netdata- 6.8.3 Disk writes causing high CPU
Any chance this could have something to do with my memory configuration or something like that? I am using the SCU cable for most of the array drives, although the Parity disk Cache drive are on the onboard SATA3 ports.- 6.8.3 Disk writes causing high CPU
Do you think this is a product of the configuration? I can't see how it's a hardware issue, so maybe reinstalling unRAID would help? Also, more than happy to post any logs / test data needed to solve this. - 6.10.3 to Latest Stable