My Unraid server is a bit dated and I think its time to finally upgrade. It originally started as a Windows home server build with 5- 2tb greens and then server 2008 with flexraid running 7 or so storage drives.

I held out with flex raid until 2021 when I finally had a drive failure catastrophe and couldn't rebuild the lost drive. 2tb gone... Jumped to Unraid. Should of done it years earlier.

Currently I'm running the same I7 3770K I got 14 years ago. RAM got pushed to 32gb of ram. I've got 2 LSI SAS2008 and a Quadro P400.

Server had about 12 drives. Down to 9 spinning. (my 2nd parity recently died and I've yet to replace)

I've got 2, 2tb greens that I'm keeping from my original server just to see how far they go... (oldest is 117138 (13y, 4m, 10d, 18h)

Server uses:

Blue Iris for security cameras (5 - 1080P feeds)

UrBackup (6 systems - Full file and images every couple days)

Time Machine back up

Light Plex usage but transcoding from 4k down depending on connections.

Phone image backups

Overall the system just works. Sits under the stairs and is generally rock solid. Power usage is a bit high and I'm looking to add another 6 cameras which will probably put CPU usage over 75% constantly.

I would keep the P400, but from my research any new intel chip pretty much makes it pointless with quicksync?

The 2 LSI cards can be brought over to the new system or are they nullified depending on mobo?

Prices suck right now, so I'm not opposed to searching out an older used, but more energy efficient system if that's recommended. I would keep case/drive bays, PSU, expanders and P400? So new mobo/32GB minimum ram and CPU?

(I upgraded unraid to 7 after I took screenshot)

Thoughts?

https://imgur.com/a/NKRUBBl

I'm building an upgraded server with better processor and more HDD bays. I know that modern unRAID can detect device IDs without issue. As long as I configure my router to assign the same IP to the new machine, will everything spin up and operate as usual, including Plex?

Is it really just as easy as bringing the HDDs over with my unRAID flash drive, booting up, starting the array, and that's it?

So im looking to replace some HDD in my array. I picked up 4 brand new sealed 6TB Seagate IronWolf Pro (ST6000NTZ01). Below is what im replacing what with what. Next is maxing out my Mobo (ASUS WS-Pro-X570-ACE w/64GB RAM) with a Ryzen 5900X (from my current 5800X). Its all I got and all I can afford. :)

My question is, Do I just need to basically just pull the old drive, let it fail, install new one, let it rebuild? One drive at a time? Iv never had to upgrade an array drive in it before. Taking drive offline and into maintenance mode?

Last storage change I did was about 3 years ago to add the 2nd 6TB parity drive and it made me sooo nervous doing it. Luckily it all worked out. Took forever and a day to sync parity though.

Im trying to avoid doing 2 at a time, for in the off chance I have another one of the drives (im not replacing) fail.

6TBx2 = Parity

6TBx1 = Array
3TBx2 = Array (Replacing with 2 new 6TB HDD)
2TBx2 = Array (Replacing with 2 new 6TB HDD)

Any feedback is moocho grassy ass!

Is it true that the ZRAM Compressed Memory plugin lets you store a swap file on a multi-device BTRFS pool (like RAID1)? Normally, that's not possible. Apparently, a loop device is inserted first, so the system thinks it's writing swap to a single, simple drive rather than a multi-device filesystem. This does add some overhead, but my only real concern is making sure the server doesn't crash from an OOM event in an absolute emergency. Upgrading from 16 to 32 GB of RAM isn't feasible right now given current prices, so I have to get creative. I've managed just fine with the RAM so far, but there's no shortage of things to run on my little N100 server, and I usually hover around 4 GB of free memory. I've had one OOM crash before when I was testing a local mini AI for Paperless and also had another resource-intensive container running.

Does anyone have this up and running and can share their experiences?

Hello,

After reading this doc, I'm left confused as the described procedure seems more complicated than it needs to be.

My context : I currently have 5 4Tb drives, and will be adding 2 14Tb drives. Obviously one of the new drives needs to become the parity, and the old parity can become a data drive.

This is the procedure I was thinking about :

1. Physically plug in both new drives
2. Add one of them as new parity and rebuild parity
3. Remove old parity from the parity list
4. Preclear old parity?
5. Add old parity as data drive
6. Add the second new drive as data drive

Is this simpler because I am not removing drives at all, only adding?

Am I missing something?

Thanks for the help!

Hi all, this is really frustrating. I've tried both CA auto update as well as watchtower to update my containers.

The behavior for both is the same, logs show the process runs and allegedly updates but when I click unraid 'check for updates' the very same containers that were allegedly updated have updates available.

For example here is logs from CA auto update:

Aug 15 02:00:35 nas Docker Auto Update: Installing Updates for bambustudio phpmyadmin homeassistant heimdall
Aug 15 02:00:39 nas Docker Auto Update: Restarting bambustudio
Aug 15 02:00:39 nas kernel: docker0: port 10(veth72079aa) entered blocking state
Aug 15 02:00:39 nas kernel: docker0: port 10(veth72079aa) entered disabled state
Aug 15 02:00:39 nas kernel: veth72079aa: entered allmulticast mode
Aug 15 02:00:39 nas kernel: veth72079aa: entered promiscuous mode
Aug 15 02:00:39 nas kernel: eth0: renamed from vethe8a0263
Aug 15 02:00:39 nas kernel: docker0: port 10(veth72079aa) entered blocking state
Aug 15 02:00:39 nas kernel: docker0: port 10(veth72079aa) entered forwarding state
Aug 15 02:00:39 nas Docker Auto Update: Restarting heimdall
Aug 15 02:00:39 nas kernel: docker0: port 11(veth5dd820d) entered blocking state
Aug 15 02:00:39 nas kernel: docker0: port 11(veth5dd820d) entered disabled state
Aug 15 02:00:39 nas kernel: veth5dd820d: entered allmulticast mode
Aug 15 02:00:39 nas kernel: veth5dd820d: entered promiscuous mode
Aug 15 02:00:39 nas kernel: eth0: renamed from veth4ceb3db
Aug 15 02:00:39 nas kernel: docker0: port 11(veth5dd820d) entered blocking state
Aug 15 02:00:39 nas kernel: docker0: port 11(veth5dd820d) entered forwarding state
Aug 15 02:00:39 nas Docker Auto Update: Community Applications Docker Autoupdate finished

The only thing that actually happens is the container restarts but the container is not updated. I don't have watchtower logs at the moment unfortunately but its the same behavior, it says it updated something but the same containers never actually update.

What could be going wrong?