Seems to be a docker network bug? Am changing network type and nothing changes it remains on host. As a test I also set it to none and it remained showing as host. Didn't peak behind the curtain to see what it's doing but here's some screenshots. Anyone else or is it just my server? Maybe it's folder view plugin? 

Screenshot context - we have changed the network type to [none] but it shows as [host] could be frontend bug?

 

Edited May 14, 20251 yr by dopeytree

1 hour ago, dopeytree said:

Seems to be a docker network bug?

Please create a new bug report:

https://forums.unraid.net/bug-reports/stable-releases/

11 hours ago, cj0r said:

Between these 3 release threads, it's really difficult to gauge the stability of this release. I can't tell if these issues are just isolated to individuals with unique hardware configurations or if it's a release I should really hold off on putting into my production servers.

 

You will likely see a higher number of issues on here as there will (hopefully) be a silent majority for whom the versions work. I've upgraded through most of the rc's on 2 servers - one with a "daily driver" VM, and not seen any issues. I assume it's the edge cases that cause problems - less common hardware, more obscure docker / networking setups etc. 

If there's some data gathered around installs it would be reassuring to see some numbers of users on the latest versions.

4 hours ago, dopeytree said:

Seems to be a docker network bug?

 

Is this "really" a bug? And why do you change the Netweork type?

On my Plex-Docker, it says "Host" - i can change it to somethig else, but then plex is no longer working... so it doesnt make sense...

4 hours ago, dopeytree said:

Seems to be a docker network bug? Am changing network type and nothing changes it remains on host. As a test I also set it to none and it remained showing as host. Didn't peak behind the curtain to see what it's doing but here's some screenshots. Anyone else or is it just my server 😂

Screenshot context - we have changed the network type to [none] but it shows as [host] could be frontend bug?

 

Tried it.  Works fine for me.  Can you retry without folder.view installed.  If that fixes the issue, then post in the plugin's support thread

I've been running unraid for over a year, decided to update today from 7.0.1 to 7.1.2, surprised it didn't come back online. So I plugged an HDMI cable to check what was up and noticed it was booting straight into the bios, I changed the USB drive to another port, force reboot and it started booting but to this error. Apologies for being a photo, as I have the server in my living room, never plugged to a monitor. Any idea on what to do here?

 

Never encountered this before and all updates were a breeze. Until today

31 minutes ago, Sptz87 said:

Any idea on what to do here?

Looks like a flash drive issue.

1 hour ago, jsebright said:

You will likely see a higher number of issues on here as there will (hopefully) be a silent majority for whom the versions work. I've upgraded through most of the rc's on 2 servers - one with a "daily driver" VM, and not seen any issues. I assume it's the edge cases that cause problems - less common hardware, more obscure docker / networking setups etc. 

If there's some data gathered around installs it would be reassuring to see some numbers of users on the latest versions.

I think another challenge, in terms of getting wider testing, is that the Beta and RC releases used to be held here in the Announcements area so you had a lot more curious users willing to setup test environments or just roll the dice on installing a non-stable release. But now it's not exactly advertised to new users that there's another area hidden under the Bug Reports forum for tinkering with new cutting edge releases if they so dare.

 

 

Thank you for the work on this update.  7.0.1 to 7.1.2 with no issues.

13600k on ASRock Z790 Pro RS, 64GB DDR5, 4 NVMEs, 1 SSD, 6 HDDs

I am still running Macvlan because of Ubiquiti.

This kernel appears to have reduced power watts, as my idle (6 disks spun up) wattage is now 81w (before was 90w).  Idle (spun down) wattage is still at 45w.

33 minutes ago, JorgeB said:

Looks like a flash drive issue.

 

I just plugged it on my mac and everything seems to be there. Don't know what to do now lol, it's been rock solid until this update today

 

6 hours ago, Sptz87 said:

 

I just plugged it on my mac and everything seems to be there. Don't know what to do now lol, it's been rock solid until this update today

 

Unfortunately my advice is not going to be very helpful as I do not know exactly what causes this.  It happened to me during a 6.12.x upgrade.  First time I thought it was a bad flash drive and building a replacement resolved the issue.  Then it happened again and when trying a third drive i figured out there was nothing wrong with the first drive I replaced.  I just had this happen again during one of the 7.x upgrades, and all I do now is just change the USB port and it boots without issue.  I thought maybe I had a USB controller going out so I replaced the MOBO and it has happened on that one too.  Needless to say I really have no clue what causes it, but moving to a different port on the MOBO always seems to allow it to boot.  I am still using the first flash drive again too.  Maybe I just have horrible luck with flash drives...idk.

7 hours ago, Sptz87 said:

I just plugged it on my mac and everything seems to be there. Don't know what to do now lol, it's been rock solid until this update today

 

 

Run the MAC equivalent of Windows'   chkdsk   on the Unraid Flash drive.  I suspect that some sectors on the flash drive may have gotten corrupted when the new files were being written to the drive. 

 

EDIT:  If this does not fix it, start a new thread in the General Support forum.  This thread is for comments not solving problems that take more then one of two posts. 

Edited May 14, 20251 yr by Frank1940

On 5/12/2025 at 4:09 PM, bmartino1 said:

what command can you give an example?

as i run script and tested this and unless the command is still doing stuff it will not show a new line

 

what command are you running?

 

22 hours ago, beaverly72 said:

 

 Needless to say I really have no clue what causes it, but moving to a different port on the MOBO always seems to allow it to boot.  I am still using the first flash drive again too.  Maybe I just have horrible luck with flash drives...idk.

Disable Fast Boot in BIOS, should solve this (had the same issue)

1 hour ago, RowdyBurns said:

 

curl doesn't print a new line by default. The ls did.

Not sure if this has been asked but was curious why these changed are released as .X updates rather than using the patching mechanism that was just released/implemented.

 

Some of these fixes seem to be good candidates for the patching tool.

 

No issues with updating from 7.1.1 to 7.1.2.

16 hours ago, Atherel said:

Disable Fast Boot in BIOS, should solve this (had the same issue)

That is disabled unfortunately, thanks though.  Had an unresponsive server today, at least from a UI standpoint.  This has never happened before.  Will create a thread for that.

Has anyone tried the "mover empty disk" feature to verify it's working correctly in 7.1.2?

 

Kevin

Update from 7.1.1 to 7.1.2 without problems. 👍

Updated from 7.0.1 to 7.1.2 without incident.  So far so good.  All VM's and Dockers started and are running.

14 hours ago, kolepard said:

Has anyone tried the "mover empty disk" feature to verify it's working correctly in 7.1.2?

It's working fine for me.

On 5/14/2025 at 5:40 PM, beaverly72 said:

 

Unfortunately my advice is not going to be very helpful as I do not know exactly what causes this.  It happened to me during a 6.12.x upgrade.  First time I thought it was a bad flash drive and building a replacement resolved the issue.  Then it happened again and when trying a third drive i figured out there was nothing wrong with the first drive I replaced.  I just had this happen again during one of the 7.x upgrades, and all I do now is just change the USB port and it boots without issue.  I thought maybe I had a USB controller going out so I replaced the MOBO and it has happened on that one too.  Needless to say I really have no clue what causes it, but moving to a different port on the MOBO always seems to allow it to boot.  I am still using the first flash drive again too.  Maybe I just have horrible luck with flash drives...idk.

I've only been using Unraid for a couple of months and only with 7.0.1 but I briefly had the same issue where I needed to change USB ports every time I rebooted. I'm also at a loss as to why because just as I was going to make a bug report the issue went away. Everything in my DIY NAS is new except for the storage drives. The only 2 things that changed from my initial setup are that as I finished getting my NAS to how I wanted it, I was rebooting it much less than in the initial setup phase where I was rebooting several times a day. It was my first time using Unraid or a NAS so I took a couple of weeks to get comfortable. The problem with the USB suddenly appeared near the end of that phase. The other thing that changed was that the USB was originally plugged into a 2.0 port and right now it's plugged into a 3.2 port.

On 5/16/2025 at 5:53 AM, beaverly72 said:

That is disabled unfortunately, thanks though.  Had an unresponsive server today, at least from a UI standpoint.  This has never happened before.  Will create a thread for that.

You could downgrade to what you had working before. Rolling back works fairly well.

On 5/14/2025 at 9:43 AM, jsebright said:

You will likely see a higher number of issues on here as there will (hopefully) be a silent majority for whom the versions work.

 

I kicked off an update to 7.1.0 on one system while sitting waiting to take off at an airport boarding gate - while away I didn't have the time to dive deep, but everything I needed while away seemed to be working so....

 

 

16 hours ago, xokia said:

You could downgrade to what you had working before. Rolling back works fairly well.

I wish I would have done that to begin with.  I was sure it was the flash drive, then the MOBO so this was probably more than six months ago now.  I do not have those backups anymore and my configuration has changed quite a bit since then.  Seems like it is probably worthy of it's own thread at this point.

Edited May 19, 20251 yr by beaverly72
note new thread needed