7 minutes ago, JorgeB said:

That suggests a plugin is causing the issue, you can uninstall or disable them from loading, then retest after re-enabling them one by one.

I now move all the plugins mv /boot/config/plugins.disabled/*.plg /boot/config/plugins/ and restarted the server....

Then I can shortly login into the webgui, after 1-3 Minutes the gui is gone.

Is there a way to downgrade ? 

 

Can i overwrite these files (from 6.12.13) on the stick to downgrade ?

bzimage

bzroot

bzmodules

bzfirmware

 

4 minutes ago, kobelka said:

Is there a way to downgrade ?

Tools - Downgrade

Just now, JorgeB said:

Tools - Downgrade

The Webgui shuts down after 1 - 3 Minutes.... Is there a way on the console or usb-Stick like i wrote ?

1 minute ago, kobelka said:

Is there a way on the console or usb-Stick like i wrote ?

1 to 3 minutes should give you time to downgrade, it's instantaneous, but you can also move the files from the previous folder on the flash overwriting the existing ones.

Did not work, i could press the downgrade button but than it hangs....

But now i have the logs on my stick

 

Edit: syslog.txt deleted

 

 

 

Edited November 28, 20241 yr by kobelka

16 hours ago, paperblankets said:

This seems pretty close to a public disclosure that diagnostics had sensitive information in it before now.
Re unraid forums:
Maybe the unraid team should be sending a message to anyone with a *-diagnostics-*.zip attachment upload suggesting users delete attachments if they are leaking credentials (or just if they don't require support anymore)?

Otherwise the forums are kind of open session for bad actors to go harvest vpn credentials from unsuspecting users.

Does unraid have a timeline of how long ps.txt has been included in diagnostics? Is it every diagnostic upload or is it a subset of configurations?

I filed a bug report back in April, didn't get any traction until the last beta release. If the system has a docker container that passes username and password in its run command, it's also included in ps.txt. 

 

I would agree that they should remove all diagnostics files forum posts to be safe.

 

 

1 hour ago, kobelka said:

Did not work, i could press the downgrade button but than it hangy....

But now i have the diagnostics on my stick

This announce post is perfect for quick questions or comments only, please start a new thread in the general support forum, and post the complete diagnostics.

I've done it now.
First I downgraded by replacing all the bz* files on the stick with those from version 6.12.13. Then I had problems with the br0 and the coral tpu driver. After I fixed these, I did the update again and now everything is running on 6.12.14! Thanks for the help @JorgeB
The next time (hopefully never), I will start an extra thread.

14 hours ago, warpspeed said:

Just checking the release notes, no particular fixes for the NFS issues a bunch of folks have been experiencing on the recent 6.12 series?

 

e.g. no mention of this

 

Some work was done on this issue and it should be resolved.

After this update I get many of my shares showing a cache is not found. Oddly enough I never used this cache for any of them and they go straight to the array.

 

 

1 minute ago, ONI said:

After this update I get many of my shares showing a cache is not found. Oddly enough I never used this cache for any of them and they go straight to the array.

This means the share cfg is referencing a pool that doesn't exist, click on the share to adjust the settings, you may need to just do a dummy chance, then click apply.

This upgrade did a lot of dommage to my setup.

 

Upgraded from 6.12.13 to 6.12.14 like I did the previous update waiting for everything to be perfect before the reboot. (The last upgrades before this one went all fine)

 

1. On 6.12.14, the unraid server was reachable only to start to see the login page, but not enough time to login (even with a filling macro to login instantly).
2. Seems to be a network issue with the version 6.12.14 of Unraid, because even the router stop to see the Unraid server.
3. Per chance the Unraid GUI was working.
4. I had to downgrade without network.

 

After the downgrade:

• Boot in GUI mode, just show a black screen with a white flashing underscore and I cannot write anything.
• Drivers plugins are missing
• But I can access Unraid interface on the local network and it stays connected and had network access now. (like it was perfectly fine for that before the update)

 

The Update 6.12.14 was very interesting for the CVE issues it corrects, but it should have access to the network.

 

On 6.12.14 before the downgrade I tried to change the network config a few times (with GUI) to make it works and reachable in the local network even with over 6 reboots. (I know that after the update we could have to reboot a second time with some plugins but it didn't help with the issue.)

 

So is there a way to repair my Unraid to get the GUI mode working again without losing all the setup?

 

Will it be a fix for this network issue with Unraid 6.12.14?

 

Also, when looking on the Reddit feed about his update, I'm not the only one with not network access to Unraid after the update.

 

Edited November 28, 20241 yr by Amachamax
Formating for better reading and added details on 6.12.14

15 minutes ago, Amachamax said:

but it should have access to the network.

Please create a new bug report and post the diagnostics.

1 hour ago, Amachamax said:

After the downgrade:

• Boot in GUI mode, just show a black screen with a white flashing underscore and I cannot write anything.
• Drivers plugins are missing

Downgrading should not remove any drivers, unless maybe they didn't install correctly when you upgraded, what drivers were you using?

8 hours ago, Michael_P said:

I filed a bug report back in April, didn't get any traction until the last beta release. If the system has a docker container that passes username and password in its run command, it's also included in ps.txt. 

IMHO such sensitive credentials should be never be passed over through a Variable and should always be passed through by a file.

But this is not the topic of this thread.

3 hours ago, Amachamax said:

Drivers plugins are missing

Did you wait for the notifications from your server that it is safe to reboot?

Thank you for all your work.  Upgrade from 6.12.13 went smoothly.

Upgraded 6.12.13 -> 6.12.14 reboot froze but after powering off then back on it booted fine. So far no noticeable issues, thanks for the update.

12 hours ago, JorgeB said:

This means the share cfg is referencing a pool that doesn't exist, click on the share to adjust the settings, you may need to just do a dummy chance, then click apply.

Thanks I selected another pool and then put it back and after saving the changes it fixed the issue.

 

Thanks.

Upgraded 4 systems, no issues.

Upgrade went well for me. No issues.

 

For those having problems with Windows shares not showing up any more, try adding your server name and IP to the host file in Windows under C:\Windows\System32\drivers\etc\hosts. Worked for me and my server shows up in my Network devices list giving me access to my shares.

Edited November 29, 20241 yr by m411b

Update went fine.

Upgraded ok, no problems at all. 

 

Thank you

There have been multiple reports of issues with the Realtek driver plugin after upgrading to 6.12.14, the stock in-tree driver should still work fine, if you have the driver plugin installed it may be better to uninstall it before updating, or keep that in mind, if you have connectivity issues after updating.

 

 

JorgeB I have already uninstalled my RTL8125 plugin, but after updating the system to 6.12.14, can I reinstall RTL8125 plugin/drivers or hold off yet?