Unraid OS version 6.11.3 available


limetech

Recommended Posts

Upgrade went smoothly. Boot took just over 7 minutes, hanging with the last output being Samba stuff for almost 5 minutes.

Same bug as 6.11.2 where I had to tick "show password" to get the "Start" button enabled for the array (password filled via password manager, not typing or copy/paste)

Link to comment
10 hours ago, craigr said:

Yes, my pool devices were assigned again (thank the maker).  I did of course have a backup from 6.11.1.  I recreated the flash drive from scratch using a fresh download of 6.11.1 and copied over my config directory.

 

image.thumb.png.867d506e04ce150c0b365c64e77f9649.png

 

Funny thing too is that my SSD cache pools use the SATA ports on the MB and the cache drive uses a port on my LSI controller.  Why lose ALL cache drives?!?

 

10 hours ago, craigr said:

I can try 6.11.3 again later when I have more time and get the log files.  Right now, I just need a functioning computer.

 

10 hours ago, JorgeB said:

Please do, and if you see the same issues post the diags in a new thread in the general support forum.

 

Well, I updated from 6.11.1 to 6.11.3 and the problem did not reoccur.  My cache disks are all assigned and intact.  I have rebooted multiple times to test and it's all fine.  Something with the upgrade between 6.11.2 to 6.11.3 obviously went sideways that did not happen after I reverted back to 6.11.1 and upgraded from there.

 

Oh well.

 

Now if I could only get my Windows 11 VM to boot more than once with boot order enabled...  but I have a work around for that so I can live with it for now.

 

Thanks,

craigr

  • Like 1
Link to comment

I just logged onto the forum to get some help with a 12TB drive I was adding to my array that wasn't formatting after pre-clear... If only that upgrade notification came earlier! Will report back if 6.11.3 doesn't solve the problem...

 

Update - Formatting working as expected now. Thanks!

Edited by sreknob
update
  • Upvote 1
Link to comment

I normally don't post the gory details of a bug and bug fix/workaround.  For the issue where 6.11.2 could not format devices larger than 2TB here is what was the cause and the fix that went into 6.11.3.

 

First, the reason this got published without this issue being caught is that my test server with devices larger then 2TB were already formatted.  Other test servers, which are actually VM's had smaller virtual devices and formatting worked ok with them.  So sorry about that, sometimes sh*t happens, but this particular bug would not have caused any data loss.  Anyway....

 

The bug was in the 'sgdisk' utility included in the "gptfdisk" package, where version 1.0.9 was released on April 15, 2022.  This was integrated into Unraid OS very early in 6.11 development and appeared in 6.11.0 on Sep 23, 2022, where it works fine.  But then the libpopt library was updated on Oct 19, 2022, and included in a larger slackware package called "aaa_libraries" which was integrated into Unraid 6.11.2.  The libpopt library includes functions used by nearly all C-based utilities to parse command line options.

 

The sgdisk command also uses this library to parse command line options. The bug is that sgdisk was referencing freed memory due to how a function in libpopt was implemented. But this didn't cause problems because that freed memory wasn't reused until after sgdisk already referenced it. Well along comes an upgrade to the libpopt library which frees memory differently which caused sgdisk now to reference garbage data and fail as described.

 

Author of gptfdisk added a fix but for some reason has not published a new release.

 

Edit: the fix was to revert gptfdisk to 1.0.8 which used the earlier version of libpopt, and to also revert libpopt to the earlier version.

  • Like 9
  • Thanks 11
  • Upvote 1
Link to comment

Thanks for the transparency.   Also, a big thank you for identifying and fixing the issue rather quickly.

 

Although I was not impacted by the bug, many new users or existing users building new systems or upgrading disks were impacted.  It is easy to see how this particular issue fell through the cracks and went undetected until release; however, as it is now a known scenario hopefully it has been added to future pre-release testing regimens.  It's kind of a big deal when a disk cannot be added to an array because it cannot be formatted.  😁

  • Like 1
Link to comment
5 minutes ago, kevon27 said:

my server is  no longer reachable on my network. I cannot ping or ssh into the machine.

Sometimes, the network.cfg and network-rules.cfg can get messed up.  It has been known to happen in upgrades.  Delete these files from the config folder on your unRAID flash drive and reboot.  New default files will be created but your server will get a DHCP address.  You can then change network settings if you need to.

 

Alternatively, if you have a flash drive backup from before the problem occurred, you can try restoring these files from the backup.

Edited by Hoopster
  • Like 1
Link to comment
1 minute ago, JorgeB said:

Clear browser cookies.

Thanks! Didn't even cross my mind. Sure enough that did it, now to go reset all my settings for my dockers that use cookies lol

 

While I was trying to figure this out I noticed that there is the option for both VNC and SPICE in the VM? What is the difference? Is one better then the other?

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.