You are tired of hearing people express opinions you do not agree with.

You don't have sympathy for users who make such comments.

I hope the people at Limetech do not feel the same as you. As Tiffany expressed during the latest Uncast show, it is about the community.

9 minutes ago, ConnerVT said:

You are tired of hearing people express opinions you do not agree with.

You don't have sympathy for users who make such comments.

I hope the people at Limetech do not feel the same as you. As Tiffany expressed during the latest Uncast show, it is about the community.

I thought I made it clear what I was tired of, and it was not that. If you absolutely want to discuss my comment further, you can create a new thread so we don't spam this one. I'll happily discuss it in your new thread so you can express your opinion on the matter :), but I won't respond to it anymore in this thread.

13 hours ago, akoivist said:

Upgraded from 7.1.2 to 7.1.4 and containers using custom/br0 to have an own IP in the host's subnet lost that ability (did not start). Docker settings show's the custom docker network has now ip-range from those private docker networks (gw still the original). Also Docker settings screen went corrupt and did not allow to re-enable docker. Sounds a bit like usb memory corruption, but there is no other signs of that. Downgrade went ok and now everything works again.

"Normally Docker does not allow Docker containers to directly access the same subnet as the one used by the host. You can allow this under Settings → Docker by changing Host access to custom networks from disabled to enabled."

I thought that setting was for the host to access containers network, not the other way around. So enabling this setting the original ability is restored in 7.1.4?

I wonder if stuff like this should be added to Fix Common Problems or some sort of update pre-check

I was having networking issues on 7.1.2. Specifically, the server would suddenly disconnect from the network completely, full reboot was required to reconnect until it failed again. When disconnected, no network connectivity was available - couldn't ssh, webgui, or even ping the server or any docker containers. Plex might have worked, I didn't have a chance to check.

Anyway, tried upgrading to 7.1.4 in the hopes that it would fix the networking issues, and now I can't boot at all. It acts like the USB drive is not there. I've checked my BIOS settings, which are for UEFI boot with USB key and USB hard drive as the only two boot options. My USB stick seems fine as I am able to plug it into my mac and navigate the files.

Any suggestions on how to fix this? I'm tempted to restore to a backup I made of my 7.1.2 setup or try a fresh install of 7.1.4 but I'm honestly not entirely sure of the steps to do the restore from backup. Should I just use balena etcher to load the .zip backup onto the flash drive and then try a reboot?

41 minutes ago, pjaglom said:

Any suggestions on how to fix this?

Try recreating the flash drive, first backup the current one, then recreate it using the USB tool and 7.1.4, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files, and if you need more help, please start a new thread in the general support forum.

Updated from 7.12 to 7.14 with no problems..

Just the basic setup, raid and no docker, no plugins, no community applications...

Limetech Built Rack mount server (10 years old and going strong).

Supermicro X9SCL/X9SCM , Version 1.11A

American Megatrends Inc., Version 2.3a

BIOS dated: Wed 6 Jan 2021 12:00 AM

Intel® Core™ i3-3220T CPU @ 2.80GHz

16 GiB DDR3 Single-bit ECC

LSI® SAS 9211-8i PCI Express® to

6Gb/s Serial Attached SCSI (SAS)

Host Bus Adapter

1TB SSD cache

Samsung_SSD_870_EVO_1TB_S6PTNS0W215678Z

2xParity Drives

Western Digital Red, 8TB

6x Raid Drives

Western Digital Red, 8TB

USB OS Drive

Sandisk Cruzer_Fit, 8GB

On 6/30/2025 at 4:40 PM, pjaglom said:

It acts like the USB drive is not there. I've checked my BIOS settings, which are for UEFI boot with USB key and USB hard drive as the only two boot options. My USB stick seems fine as I am able to plug it into my mac and navigate the files.

Have you tried a different USB port? And if that helps, make sure that fast boot is disabled in BIOS.

Is the EFI folder on your flash drive "EFI" or "EFI-"?

If it is EFI- remove the trailing dash. That is for booting non-UEFI/legacy BIOS.

Edited July 1, 20251 yr by ConnerVT
speeling

I am running 7.1.4 and the connectivity issues are getting worse and worse. The NAS disconnects multiple times per week and needs to be force rebooted. No connection is possible after it „crashes“...

8 hours ago, Skorpion said:

I am running 7.1.4 and the connectivity issues are getting worse and worse. The NAS disconnects multiple times per week and needs to be force rebooted. No connection is possible after it „crashes“...

You should set up a syslog server and post that file after the problem arise along with your diagnostics in a new thread in General Support.

In the process of Updating now, will type as I go.

Attempting to move from Unraid 7.0.0-beta.2 to Unraid 7.1.4-rc.1. I am hopeful for this to go smoothly.
Backing up Flash.
Commencing update.
Update is downloading...
Update is installing...
System Is rebooting....
Ping command scrolling with Destination Host Unreachable.
Ping command has a response, web ui is loaded.
ZFS pool of 84 bulk storage drives detected.
ZFS pool of 4 high speed cache drives detected.
Starting array....
High Speed Cache Online.
Bulk Storage.... Unmountable: wrong or no file system.
*** Technical Knowledge with Unraid/ Linux is very limited. Unsure how to proceed/attempt to resolve. Determining best path ***
*** Path determined ***
Downloading Diagnostics
Logging support ticket. #13563
Performing Downgrade back to 7.0.0-beta.2
System Is rebooting....
Ping command scrolling with Destination Host Unreachable.
Ping command has a response, web ui is loaded.
Starting array...
We are back online.

Conclusion Upgrade Failed. Lack of user knowledge to correctly troubleshoot/resolve.

11 minutes ago, Zeebie said:

Conclusion Upgrade Failed. Lack of user knowledge to correctly troubleshoot/resolve.

Just for interest why did you try to update to a rc release rather than the stable one?

35 minutes ago, itimpi said:

Just for interest why did you try to update to a rc release rather than the stable one?

I installed an intel arc card into the server, for transcoding and at the time, it wasn't supported on the other versions of unraid available at the time, but beta.2 and thats why I am on beta.2

Why try and update to RC? because i am probably an idiot.

Edited July 3, 20251 yr by Zeebie

Just now, Zeebie said:

Otherwise i wouldn't of moved to it.

You tried to install a 7,1,4 rc when 7.1.4 stable (which is more recent) is available!

If you try the 7.1.4 stable release make sure that you capture your system's diagnostics zip file as that is likely to identify why you have any issue.

3 minutes ago, itimpi said:

You tried to install a 7,1,4 rc when 7.1.4 stable (which is more recent) is available!

I see what I have done, when I went to update it, it defaulted to that and I assumed it was the right one :|
Ill give 7.1.4 a shot now.

9 minutes ago, Zeebie said:

I see what I have done, when I went to update it, it defaulted to that and I assumed it was the right one :|
Ill give 7.1.4 a shot now.

If it fails in the same way (which is what one would expect) then if you can afford to wait a while before reverting then posting your diagnostics (preferably in a new thread under General) might get you a quick resolution if it is something we have seen before.

1 minute ago, itimpi said:

If it fails in the same way (which is what one would expect) then if you can afford to wait a while before reverting then posting your diagnostics (preferably in a new thread under General) might get you a quick resolution if it is something we have seen before.

Same issue :(
lenovo-hr630x-diagnostics-20250703-1729.zip

I suspect your issue revolves around this:

Jul 3 17:28:55 Lenovo-HR630X emhttpd: pool-one: zfs spares not supported

I would think that @JorgeB as an expert on this sort of thing will know how to get around this.

31 minutes ago, Zeebie said:

Same issue :(

ZFS spares are not currently supported, that on the release notes for 7.0.0, you need to remove them, then reimport the pool, if you need help on how to do that, please start a new thread on the general support forum and can can post step by step instructions.

Just now, JorgeB said:

ZFS spares are not currently supported, that on the release notes for 7.0.0, you need to remove them, then reimport the pool, if you need help on how to do that, please start a new thread on the general support forum and can can post step by step instructions.

No worries, I can do that by my self, do we know if that feature is planned in the future? I like of like having the spares available there.

5 minutes ago, Zeebie said:

do we know if that feature is planned in the future?

I think that is the plan, spares were disabled for now because a hot spare would not automatically kick in if there was an issue with the pool, so it could give the user a false sense of security, once auto-replace for spares gets implemented, it should support them again.

Updated my Backup Server from 7.0.1. to 7.1.4 without problems...however my backup server is a very uncomplicated setup. No Dockers, No VM, etc.

Edited July 3, 20251 yr by HardwareHarry

Anyone got problem with scheduled parity checks happening daily on 7.1.4? https://forums.unraid.net/topic/191798-getting-daily-scheduled-parity-checks-2x-have-completed-fine-so-why/

1 hour ago, dopeytree said:

Anyone got problem with scheduled parity checks happening daily on 7.1.4? https://forums.unraid.net/topic/191798-getting-daily-scheduled-parity-checks-2x-have-completed-fine-so-why/

The only time we have seen this it is because the schedule settings were wrong. I suggest you post a screenshot of your settings.

Schedule settings:






Parity Tuning Settings:

Parity History: