3 hours ago, Kilrah said:

Those don't support RAID, being able to have mirrored boot drives was kind of a primary feature.

ZFS has its merits for sure, but what's wrong to let users have their options?

I have been experiencing an issue with virtiofs mounts hanging on my debian guests, changing XML virtiofsd config hasn't helped. There's a similar issue report at https://gitlab.com/virtio-fs/virtiofsd/-/work_items/133 which references a fix in QEMU versions 10.2.0 or higher. It doesn't look like it's been added to QEMU 10.1.2.

Is there a reason for why this specific version of QEMU was picked?

6 minutes ago, TomE said:

I have been experiencing an issue with virtiofs mounts hanging on my debian guests, changing XML virtiofsd config hasn't helped. There's a similar issue report at https://gitlab.com/virtio-fs/virtiofsd/-/work_items/133 which references a fix in QEMU versions 10.2.0 or higher. It doesn't look like it's been added to QEMU 10.1.2.

Is there a reason for why this specific version of QEMU was picked?

10.2 was not released when the internal betas started. I will review with the team to see if we can bump the release.

I'm having big problems with docker service since going to internal boot (I switched with beta2). Yes, posted about it in the bugs forum (slow docker start thread).

I have done some changes since so I can't just go back to the older usb backup. Would it work to backup internal boot, put back on USB, skip grub-folder and make sure to copy only the EFI-folder from older backup to USB? No tpm migration as my server doesn't have tpm.

Edit

I can't say for sure it will make any difference going back to USB but I'm open to try.

Edited April 3Apr 3 by Niklas

32 minutes ago, Niklas said:

Would it work to backup internal boot, put back on USB, skip grub-folder and make sure to copy only the EFI-folder from older backup to USB? No tpm migration as my server doesn't have tpm.

This is not officially supported, but you should be able to boot using the flash drive again. Remember to update the config files first; you can use rsync for example

Mount the flash drive first

mkdir /x

mount /dev/sdX1 /x

rsync -av /boot/config/ /x/config/

Then reboot using the flash drive, if any changes are made while using the flash drive, and you want to go back to internal boot, I recommend using the wizard again.

Note that for a split pool, this will mean reformatting the data partition as well.

2 hours ago, JorgeB said:

This is not officially supported, but you should be able to boot using the flash drive again. Remember to update the config files first; you can use rsync for example

Mount the flash drive first

mkdir /x

mount /dev/sdX1 /x

rsync -av /boot/config/ /x/config/

Then reboot using the flash drive, if any changes are made while using the flash drive, and you want to go back to internal boot, I recommend using the wizard again.

Note that for a split pool, this will mean reformatting the data partition as well.

Thanks. Back on usb for now. I emptied my split pool, blkdiscarded the drives until going internal boot later.

No change for the start time of docker service at boot or array start/stop.
"Server rc.docker: rebuild container abc123" for all containers take a lot of time. Big containers make it taking a very long time, up to 10 minutes. The container at the top fails to start (AdGuard Home with tailscale hook) (it tries but fails for some reason), no problem starting it manually when docker service is done with whatever its doing.

Edited April 3Apr 3 by Niklas

I know what it is, doh! It is when I have --mac-address="02:42:xx:xx:xx:xx" set in extra parameters. It rebuilds every container on every start of docker if that is set.

It takes time and for big containers it can delay start for minutes.

Removed all my set mac's and now back to normal (but router sees random macs for my containers again).

Back to internal boot.. 😅

Edited April 3Apr 3 by Niklas

One thing i want to mention and i also could not find this information in the announcement?

The internal boot Pool will count in to the License of maximal Array devices.

I only was informed after moving to dedicated internal boot pool, that i can't start my array anymore as i do not have the correct license...

I would understand if i use a NON dedicated boot pool, but i moved from 1 USB device to the 2 USB device pool.

@JorgeB maybe you could implement an check that checks the current array count with the planned boot pool count and verifys the current license if its enough afterwards.

Went now from Pro to Plus (or the other way arround) as i really needed the array but yeah, sucks a little bit (again, probably i overead it anywhere)
Or overthink the decision that an dedicated boot pool will be added to the license count.

Edit: Found the mentioning in this thread from JorgeB about the license count, but nothing official?

Edited April 4Apr 4 by unr41dus3r

Possible to get mptcp support added to the kernel (could be used by proxies like npmplus)?

Edited April 5Apr 5 by Niklas

I have activated 'internal boot'. The licensing is still bound to the flash drive (had to order the TPM module for my Supermicro MB). In the GUI it looks like that:

Why it is still called 'FLASH'?

But here it shows the NVME...

Edited April 7Apr 7 by shire

46 minutes ago, shire said:

Why it is still called 'FLASH'?

It's just the name of the zfs pool, not related to the device.

I think I'll have mastered all matters of cosmology and astro-physics before I understand the benefit of SSD boot/licensing on Unraid, but glad some people are getting a kick out of it. Now... when the time comes for a brand new docker UI with full compose and multi-container support... then I'll be smashing plates and yelling from the rooftops.

2 minutes ago, Espressomatic said:

I think I'll have mastered all matters of cosmology and astro-physics before I understand the benefit of SSD boot/licensing on Unraid, but glad some people are getting a kick out of it. Now... when the time comes for a brand new docker UI with full compose and multi-container support... then I'll be smashing plates and yelling from the rooftops.

the compose manger plus plugin is gaining traction and adds compose abilties to unraid.
https://forums.unraid.net/topic/197334-plugin-compose-manager-plus/

this has my vote for implementation to the host os.

Dedicated boot pool drives should not count towards the total drive count, just like USB boot doesn't. Split boot pool drives being counted though, is fair enough.

Just fyi:

TPM registration just works fine after installing a separate TPM module. Even after moving the data from flash to a nvme drive beforehand.

20 hours ago, bmartino1 said:

the compose manger plus plugin is gaining traction and adds compose abilties to unraid.
this has my vote for implementation to the host os.

It looks like it has great bones and could make the basis of a new Unraid release. It could definitely do with some UI/UX love, but I acknowledge that the current state is trying to shoehorn a lot of functionality into what the Unraid base webUI offers.

Would it be possible to move the license from an single USB to the Internal Boot Devices (which are 2 USB for me) or one of the USB devices in the new USB Pool?

6 minutes ago, unr41dus3r said:

Would it be possible to move the license from an single USB to the Internal Boot Devices (which are 2 USB for me) or one of the USB devices in the new USB Pool?

Not at the moment; the license flash drive must be formatted FAT32 and have the label UNRAID, so you would need to use 3 flash drives total in that scenario.

2 hours ago, unr41dus3r said:

Would it be possible to move the license from an single USB to the Internal Boot Devices (which are 2 USB for me) or one of the USB devices in the new USB Pool?

To expand on JorgeB's comment above:

With USB licensing:

Drive 1 -- USB flash drive or DOM, 8GB minimum, boot pool member

Drive 2 -- USB flash drive or DOM, 8GB minimum, boot pool member

Drive 3 -- existing USB license drive, with no size restrictions, holds the license key as before

With TPM licensing:

Drive 1 -- USB flash drive or DOM, 8GB minimum, boot pool member

Drive 2 -- USB flash drive or DOM, 8GB minimum, boot pool member

License -- stored on dTPM or fTPM.

As a suggestion, you might want to consider these dirt cheap yet very solid low end industrial drives which are likely to contain 15nm MLC -- eBay item number: 326046070546.

If you get them, please run ChipGenius and share the output.

Edited April 10Apr 10 by Lolight

Thanks for the update. I’ve finally been able to get rid of my USB boot drive. For months, even after swapping it for an identical Samsung one, every reboot was a nightmare—I’d spend hours fighting with USB errors...

Now everything is working perfectly!

My next step is to figure out (it’s still a bit abstract to me) how to easily move my 3 dockers (Plex, FileZilla, and a backup docker) onto the internal SSD. I want to free up my data drives so they can spin down and go to sleep from time to time.

34 minutes ago, Soundhacker said:

how to easily move my 3 dockers (Plex, FileZilla, and a backup docker) onto the internal SSD. I want to free up my data drives so they can spin down and go to sleep from time to time.

Start a new thread in General Support with your Diagnostics. I help people with this all the time.

16 hours ago, trurl said:

Start a new thread in General Support with your Diagnostics. I help people with this all the time.

I followed a guide, everything is OK ! Easy ! But thanks !

What a wonderfull release !! Everything's running perfectly !

Hearing all the woes some people have had with USB drives, makes me think I've been pretty lucky. My original USB (Verbatim Store N Go 16GB) is still going strong (touches wood).

59 minutes ago, Lebowski89 said:

Hearing all the woes some people have had with USB drives, makes me think I've been pretty lucky. My original USB (Verbatim Store N Go 16GB) is still going strong (touches wood).

There's no mystery behind why some drives offer long-term reliability while others suffer from disastrous performance.

You can easily assess your Verbatim drive's potential longevity by checking its components -- it takes just a few minutes.

5 hours ago, Lolight said:

There's no mystery behind why some drives offer long-term reliability while others suffer from disastrous performance.

You can easily assess your Verbatim drive's potential longevity by checking its components -- it takes just a few minutes.

Still, it’s quite difficult to find your way around with the massive amount of hardware available. Based on recommendations, I had chosen some good quality Samsung drives (or so I thought), in a fairly small form factor, both USB 2.0 and 3.0.

It’s just the nature of USB flashes drives to give up the ghost without warning... I tried external ports, then the internal USB 2.0 header... Always a struggle (and yet I don't reboot often; I even bought a UPS to avoid shutdowns as much as possible). It’s the same story with my work USB drives; I know I regularly have to replace them. Anyway, booting internally is absolutely perfect now—I’m no longer at the mercy of a USB drive’s whims.