Gragorg

I cannot get firefox on IOS to see any of my tailscale addresses. Safari works fine. Any ideas? On another note how or when do docker containers update their tailscale version? Is there any way to force it?

Using home server as an exit node while at the cottage I get 72.8Mbps on a 50 Mbps cottage connection.

Since you ran the repair with "-n" nothing was actually changed it just does a dry run to show you what it would do. You need to remove the -n to actually allow it to make the repairs. There is a great spaceinvaderone video on this if you want more information found here.

Have you tried changing to another port? Have you put your USB in a windows computer and run chkdsk?

Your going to want to post the full diagnostics.

Your going to need to post your diagnostics for the experts to look at.

They setup syslog server in unraid settings. Something to consider if it happens again.

You would need to capture diagnostics from before the unclean shutdown. Did it run a parity check upon restart?

Is this docker depreciated? Still runing 1.80 from 6 months ago.

Apparently I just needed to set a proper path for ISOs. I'll leave this here incase it helps someone in the future.

Was about to setup my first VM. Enabled the VM service but go "Libvirt Service failed to start." on the VM tab. I rebooted thinking I may have to but it had no affect. Any help would be appreciated. tower-diagnostics-20250906-1047.zip

All those steps you listed are good. Be sure to make sure all plugins and dockers are upto date before updating. Also be sure to read the release notes to see if anything else is recommended.

It very well could be that sata card. Marvell and raid cards are not recommended due to huge amount of problems. Check out this post for recommended controllers.

Post your diagnostics for the experts

Currently using zdev pools I believe Option 1 is what is supported. Zdev expansion will be added when Open ZFS 2.3 is added to Unraid. I haven't been paying attention if this has happened yet as I dont use zdevs.

The array in Unraid runs like individual disks without striping data. This allows you to add one disk at a time. In fact they dont even have to be the same size as long a the parity drive is the equal or greater to the largest drive. What your suggesting above would be a 4 disk striped pool (zfs usually) and then you could add 4 identical disk to expand the pool. The downside to the array like JorgeB stated is the performance is based on a single disk since the data is not stripped. You can set it up either way based on your use case. Most around here use the array option for the flexibility since most are just media servers.

Post your Diagnostics

I believe this is the post Jorgeb is talking about.

If you remove your parity drive the you are rebuilding without parity protection. I would add the second parity first and rebuild and then replace parity one with the larger drive and rebuild it. Then you will be doing both rebuilds with parity protection.

For me it was mapping tmp and transcode directories in the docker template to an external directory.

Post your diagnostics

Post your diagnostics

Spaceinvader made a video on this awhile ago. It is a bit older but the information is still relevant. Here is that video. Most of the Issues are for VMs and graphics cards. If I were you I would get it running exactly as you had it including the SSD pool. After it is all good do the pool upgrade and add the extra data drives after.

Start by posting your diagnostics for the experts. Also did you run check filesystem from the GUI for disk 2?

My APC Back-UPS RS 700G has worked perfectly with the built in UPS support.