Unraid OS version 6.11.2 available


limetech

Recommended Posts

55 minutes ago, Flendor said:

Updated to 6.11.2 and have the exact same issue as the previous update to 6.11.1

All starts well. The Array shows as starting, then the GUI drops connection

Try booting in safe mode, if that doesn't help I would suggest recreating the flash drive with a stock install, first backup current one, then just restore the bare minimum to the new flash: super.dat, your key and the pools folder, that will rule out any config issue/conflict, and if it works like that you can then reconfigure the server or restore the other config files, a few at time to see if you find the culprit.

Link to comment

Having a strange issue which i'm 90% sure is probably just a hardware thing. After updating I had drives presenting as errored after I started the array (they appeared fine prior to starting the array). After the first reboot I had 2 drives present like this. After the 2nd reboot the original 2 problematic drives were fine but another drive presented as erroring. Finally after the 3rd reboot all started up fine. I didnt change any hardware nor did I check wiring or seating of hardware. 

 

Everything running perfectly after that. 

Link to comment

I just upgraded from Unraid 6.10.3 to 6.11.2. Up until now, I couldn't discover any issues. I leave my upgrade steps here in case someone finds it useful:

 

Spoiler

- Backup user data
- Backup flash drive
- Restore /boot/config/go file to default
- Remove Nerdpack plugin (not supported anymore, replacement available)
- Remove SSD trim plugin (backed-in to Unraid 6.11)
- Disabled Docker service
- Disabled VM service
- Run update assistant in the Tools section
- Do the upgrade
- Reboot
- Re-enable Docker service
- Re-enable VM service
- Install NerdTools from community applications
- Install Python 2 via NerdTools (required for "Libvirt wake on lan" plugin)
- Enable "Libvirt wake on lan" plugin by switching from "Yes" to "No" and back to "Yes" again (Settings -> VM Manager)

- Enable SSD trim (Main -> Schedule)
- Install Powertop via NerdTools
- Restore /boot/config/go file with custom changes
- Optional: Install additional packages via NerdTools (vim, wget)
- Check system logs for errors and warnings
- Reboot again to test custom changes

 

 

Edited by T0a
missing trim
Link to comment
6 minutes ago, wtfcr0w said:

It sat there for a good 10 minutes after I was able to reach it via ssh. Checked the terminal output from the machine itself and it just stops at the samba init.

Start it in safe mode and see if it boots.  Then add plugins one at a time to see if it will boot.

Link to comment

I updated a few hours ago, was watching plex and everything froze...  I checked on the box and the array seems angry.  checked dmesg before rebooting it and got this:


[ 9927.692366] shfs[15681]: segfault at 10 ip 0000146e662715c2 sp 0000146e64c52c20 error 4 in libfuse3.so.3.12.0[146e6626d000+19000]
[ 9927.692375] Code: f4 c8 ff ff 8b b3 08 01 00 00 85 f6 0f 85 46 01 00 00 4c 89 ee 48 89 df 45 31 ff e8 18 dc ff ff 4c 89 e7 45 31 e4 48 8b 40 20 <4c> 8b 68 10 e8 15 c2 ff ff 48 8d 4c 24 18 45 31 c0 31 d2 4c 89 ee
[ 9927.708009] ------------[ cut here ]------------
[ 9927.708011] nfsd: non-standard errno: -103
[ 9927.708026] WARNING: CPU: 3 PID: 3616 at fs/nfsd/nfsproc.c:889 nfserrno+0x45/0x51 [nfsd]
[ 9927.708051] Modules linked in: rpcsec_gss_krb5 xt_nat veth xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod nct6775 nct6775_core hwmon_vid efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc i915 iosf_mbi drm_buddy ttm x86_pkg_temp_thermal intel_powerclamp drm_display_helper coretemp kvm_intel drm_kms_helper kvm drm crct10dif_pclmul crc32_pclmul igb crc32c_intel ghash_clmulni_intel aesni_intel intel_gtt i2c_i801 crypto_simd wmi_bmof cryptd rapl intel_cstate intel_uncore e1000e nvme i2c_smbus nvme_core agpgart i2c_algo_bit ahci libahci i2c_core syscopyarea sysfillrect sysimgblt intel_pch_thermal fb_sys_fops wmi video backlight acpi_pad acpi_tad button unix
[ 9927.708099] CPU: 3 PID: 3616 Comm: nfsd Not tainted 5.19.17-Unraid #2
[ 9927.708101] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H370M-ITX/ac, BIOS P4.00 03/19/2019
[ 9927.708102] RIP: 0010:nfserrno+0x45/0x51 [nfsd]
[ 9927.708119] Code: c3 cc cc cc cc 48 ff c0 48 83 f8 26 75 e0 80 3d bb 47 05 00 00 75 15 48 c7 c7 17 64 86 a0 c6 05 ab 47 05 00 01 e8 42 47 fe e0 <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 48 83 ec 18 31 c9 ba ff 07 00
[ 9927.708121] RSP: 0000:ffffc90000647d68 EFLAGS: 00010286
[ 9927.708122] RAX: 0000000000000000 RBX: ffff888103eb8030 RCX: 0000000000000027
[ 9927.708123] RDX: 0000000000000001 RSI: ffffffff820d7be1 RDI: 00000000ffffffff
[ 9927.708124] RBP: ffff88810433c000 R08: 0000000000000000 R09: ffffffff82244bd0
[ 9927.708125] R10: 00007fffffffffff R11: ffffffff82874b5e R12: ffff8885b835f540
[ 9927.708126] R13: ffff888532699a00 R14: ffff888104739180 R15: 0000000000000000
[ 9927.708127] FS:  0000000000000000(0000) GS:ffff88884fd80000(0000) knlGS:0000000000000000
[ 9927.708128] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9927.708129] CR2: 0000000000460068 CR3: 00000005dd29a004 CR4: 00000000003726e0
[ 9927.708131] Call Trace:
[ 9927.708133]  <TASK>
[ 9927.708134]  fh_verify+0x4e7/0x58d [nfsd]
[ 9927.708151]  nfsd_unlink+0x5d/0x1b9 [nfsd]
[ 9927.708168]  nfsd4_remove+0x4f/0x76 [nfsd]
[ 9927.708187]  nfsd4_proc_compound+0x434/0x56c [nfsd]
[ 9927.708205]  nfsd_dispatch+0x1a6/0x262 [nfsd]
[ 9927.708222]  svc_process+0x3ee/0x5d6 [sunrpc]
[ 9927.708255]  ? nfsd_svc+0x2b6/0x2b6 [nfsd]
[ 9927.708271]  ? nfsd_shutdown_threads+0x5b/0x5b [nfsd]
[ 9927.708287]  nfsd+0xd5/0x155 [nfsd]
[ 9927.708303]  kthread+0xe4/0xef
[ 9927.708306]  ? kthread_complete_and_exit+0x1b/0x1b
[ 9927.708308]  ret_from_fork+0x1f/0x30
[ 9927.708311]  </TASK>
[ 9927.708312] ---[ end trace 0000000000000000 ]---

Link to comment
13 minutes ago, Mr Q said:

Becouse of New version 6.11.2 my sata card is no longer recognized https://www.amazon.nl/gp/product/B09K3FT3ZZ/ref=ppx_yo_dt_b_asin_image_o05_s03?ie=UTF8&th=1

even after a roleback to version 6.11.1

 

please fix this, my server is down now !!!

 

 

Seems unlikely that the new version would stop your SATA card being recognised.    If rolling back to the previous working version does not fix your problem then you have something else going on.

 

I would suggest you go back to the 6.11.2 release and then post your system’s diagnostics zip file taken on that release to give us a chance to see what might be going wrong.

Link to comment
24 minutes ago, itimpi said:

Seems unlikely that the new version would stop your SATA card being recognised.    If rolling back to the previous working version does not fix your problem then you have something else going on.

 

I would suggest you go back to the 6.11.2 release and then post your system’s diagnostics zip file taken on that release to give us a chance to see what might be going wrong.

Fixed, had to do a complete powercycle, power off and back on, sorry

Link to comment
On 11/4/2022 at 5:02 PM, limetech said:

VM Manager

If you boot a VM from a passed physical USB device there is a new setting called Enable USB boot which must be set to Yes. This is due to feature change in the latest OVMF component.

 

Changes:

  • Add boot order for USB and USB Boot option. Using 'boot order' field VM can boot from a passed-through NVMe controller/device.

 

I'm a bit worried to update due to this.  I have Windows 11 booting directly from an NVMe already.  Had to fight this boot order thing a long way to get the VM back before.

 

I've attached my current XML.  Anyone think I may have a problem after this update?

 

Thanks!

craigr

 

win11 NOV 16 2022.xml

Edited by craigr
updated xml
Link to comment
28 minutes ago, craigr said:

 

I'm a bit worried to update due to this.  I have Windows 11 booting directly from an NVMe already.  Had to fight this boot order thing a long way to get the VM back before.

 

I've attached my current XML.  Anyone think I may have a problem after this update?

 

Thanks!

craigr

 

win11 NOV 16 2022.xml 5.86 kB · 0 downloads

The change is to expose the boot order on the gui.  USB Boot option sets boot dev = 'fd',  which for the new firmware it is required or a boot order for the USB device.

 

if no boot orders are specified the boot dev = 'hd' is used.

 

There is a update to the OVMF firmware so not sure if that will change anything for you. But you should be able to set boot order for the nvme to get it to boot, not sure why it didn't work for you.

 

I cannot see your existing being changed by this update, but there is always a chance it may.

 

image.thumb.png.cac785d03e52849b26c99f2aa11784e2.png

  • Like 1
  • Thanks 1
Link to comment
  • SpencerJ unpinned and unfeatured this topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.