Unraid OS Version 7.0.0-beta.3 available

Hi,

 

after upgrading from beta 2 to beta 3, I now tried to start up a VM and get following error:

 

internal error: Child process (/usr/libexec/virtiofsd --print-capabilities) unexpected exit status 2: error: invalid value '' for '--fd ': cannot parse integer from empty string For more information, try '--help'.

 

I had no issues before the upgrade.

Any clue how to solve this?

@SimonF i actually had to reflash the bios because it was broken on every single linux distro and kernel version i tried. Now its back to some more "normal" numbers(but also wrong ones xD). Still, very funny.

Edited Sunday at 09:15 AM by Mainfrezzer

46 minutes ago, Unpack5920 said:

Hi,

 

after upgrading from beta 2 to beta 3, I now tried to start up a VM and get following error:

 

internal error: Child process (/usr/libexec/virtiofsd --print-capabilities) unexpected exit status 2: error: invalid value '' for '--fd ': cannot parse integer from empty string For more information, try '--help'.

 

I had no issues before the upgrade.

Any clue how to solve this?

run this in a cmd line

 

sed -i 's/$options\[\] = "--fd=".$argoptions\['"'"'fd'"'"'\];/if (isset($argoptions\['"'"'fd'"'"'\])) {\n    $options[] = "--fd=".$argoptions\['"'"'fd'"'"'\];\n}/' /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/virtiofsd.php 

 

fixed in next release, but you will need to re apply at boot. It is in the release notes.

32 minutes ago, Mainfrezzer said:

@SimonF i actually had to reflash the bios because it was broken on every single linux distro and kernel version i tried. Now its back to some more "normal" numbers(but also wrong ones xD). Still, very funny.

Maybe a kernel/package update may fix in future.

Just a small thing:

On stopping services (e.g. Docker) on the status bar you will see "Starting services ..."

instead of "Stopping services ..."

16 minutes ago, Unpack5920 said:

On stopping services (e.g. Docker) on the status bar you will see "Starting services ..."

That's normal, it starts the other services after stopping docker.

I had to go back to beta 2 as I find access the docker tab is way too laggy and takes a long time to response.

1 hour ago, PSYCHOPATHiO said:

I had to go back to beta 2 as I find access the docker tab is way too laggy and takes a long time to response.

Do you use docker folders?

@SimonF nope, just plain dockers but for some reason in beta3 it takes sometimes uyp to 10 seconds to load the page and lots of freezes on the same page when doing updates

6 minutes ago, Niklas said:

 

In Settings -> Docker. Do you use "Docker directory"?

 

I use docker dir with overlay2, no problems. Native on zfs gave me slowdowns.

 

I keep reading about overlay2. Is this an option given in UNRAID 7.0? Because I cannot find it in current UNRAID.

Also if it is NOT overlay2, can it be changed or needs cache disk to be reformated?

 

Finally, for zfs cache disks made pre-7.0, what is their default mode?

 

Just tried updating. 

 

Upon clicking start array I get:

 

Wrong Pool State

cache - invalid config

 

Not using zfs

 

2 minutes ago, NLS said:

 

I keep reading about overlay2. Is this an option given in UNRAID 7.0? Because I cannot find it in current UNRAID.

Also if it is NOT overlay2, can it be changed or needs cache disk to be reformated?

 

Finally, for zfs cache disks made pre-7.0, what is their default mode?

 

Yes is it is in 7 

Docker storage driver: native is my current settings.

37 minutes ago, NLS said:

 

I keep reading about overlay2. Is this an option given in UNRAID 7.0? Because I cannot find it in current UNRAID.

Also if it is NOT overlay2, can it be changed or needs cache disk to be reformated?

 

Finally, for zfs cache disks made pre-7.0, what is their default mode?

 

Added in beta3 and now default for new installs. Its in the changelog.
This is only if you used docker directory on ZFS in Setting -> Docker

You need to delete the old docker folder/dir and the zfs datasets/snapshots that the native docker zfs driver created and used.
Change storage driver from native -> overlay2 in Docker settings. Your containers will disappear but can be added again with Apps->Previous apps. No need to format anything. My cache is still ZFS.

 

 

Edit: I was also confused about overlay2, what it was and what I needed to do. I use dir to limit write amplification and I don't like the img taking up space not used. No warnings about the space in the docker img, no need to increase the size of the img (that you need to delete if you want to make it smaller).

Edited Sunday at 09:48 PM by Niklas
confused

10 minutes ago, Adiventure said:

Just tried updating. 

 

Upon clicking start array I get:

 

Wrong Pool State

cache - invalid config

 

Not using zfs

 

Mentioned several times. Look at the top and "Recommended Comments".

Edited Sunday at 09:22 PM by Niklas

Thanks, somehow missed it.

41 minutes ago, NLS said:

I keep reading about overlay2. Is this an option given in UNRAID 7.0?

I forgot to mention this earlier, but since the kernel for beta.3 was downgraded to 6.6, it's no longer a problem using a docker folder with the zfs native driver, since only kernel 6.8+ is affected, this means that if a user wants to keep using a docker directory with the zfs native driver for v7.0, he can, though will likely run into issues again with v7.1 and a newer kernel, so still recommend using overlay2 for any new installs.

20 minutes ago, JorgeB said:

I forgot to mention this earlier, but since the kernel for beta.3 was downgraded to 6.6, it's no longer a problem using a docker folder with the zfs native driver, since only kernel 6.8+ is affected, this means that if a user wants to keep using a docker directory with the zfs native driver for v7.0, he can, though will likely run into issues again with v7.1 and a newer kernel, so still recommend using overlay2 for any new installs.

 

Good to know... now. It took me some time to change but now it's done for the future. Also no need to exclude all the zfs datasets or snapshots from view in zfs master. 😁

 

I guess the original problem could be solved in kernel and/or openzfs updates in the future too. 

 

Edit: And the slow thing mentioned earlier has nothing to do with it then?

 

Edited Sunday at 10:13 PM by Niklas

8 minutes ago, Niklas said:

Edit: And the slow thing mentioned earlier has nothing to do with it then?

If you mean docker directory with zfs native, from what I've read that can perform considerably worse, and it will make a mess with the legacy datasets, hence why I still recommend overlay2.

please add easy adjusment for zfs arc cache, 1/8 is to little

2 hours ago, Mr Q said:

please add easy adjusment for zfs arc cache, 1/8 is to little

There should be a GUI option soon, but it's not difficult to do now, you can go to Tools - System drivers, search for zfs and edit the value there, then reboot:

 

 

BTW I wanted to just let the devs know.  This issue with NFS is still in 7.0 Beta3

 

 

 

21 hours ago, JorgeB said:

I forgot to mention this earlier, but since the kernel for beta.3 was downgraded to 6.6, it's no longer a problem using a docker folder with the zfs native driver, since only kernel 6.8+ is affected, this means that if a user wants to keep using a docker directory with the zfs native driver for v7.0, he can, though will likely run into issues again with v7.1 and a newer kernel, so still recommend using overlay2 for any new installs.

 

Yes but you didn't reply my original 3 questions (as it will eventually, as you said, need to be handled).  I quote here again and put numbers to point them out:

 

22 hours ago, NLS said:

 

I keep reading about overlay2. (1) Is this an option given in UNRAID 7.0? Because I cannot find it in current UNRAID.

(2) Also if it is NOT overlay2, can it be changed or needs cache disk to be reformated?

 

(3) Finally, for zfs cache disks made pre-7.0, what is their default mode?

 

 

Edited Monday at 07:14 PM by NLS

39 minutes ago, NLS said:

 

Yes but you didn't reply my original 3 questions (as it will eventually, as you said, need to be handled).  I quote here again and put numbers to point them out:

 

 

1. Yes, in unRAID 7 only. overlay2 is not supported on ZFS before 2.2, which is what ships in unRAID 7. It's used in 6.12 but only if using an XFS image.

2. Yes, once you upgrade to 7, but you have to rebuild your containers. It's similar to the process of changing from a docker image to folder in unRAID 6.12.

3. Existing installs should remain in the zfs driver unless changed, as far as I understand.

Edited Monday at 07:53 PM by andrebrait

I tried to answer some of the questions before. It can be changed with some work but no need to format any drive. 

Edited Monday at 08:06 PM by Niklas