[Bridge 0 Seems to be gone with 6.6]

Do you mean "br0" or did you define your own custom network "bridge.0" ?

The newer version of Docker included in Unraid 6.6 has changes in the networking part. We adopted so networks generated by Unraid continue to work as before, but there is no guarantee for custom networks made by the user.

[[6.6.0] sftp transfer issues]

Port 22 is used by the SSH daemon. I don't know if winSCP sets up a secure tunnel via SSH to do FTP.

The FTP server application itself hasn't changed.

In my tests with winSCP set up as FTP client it works flawless.

[[6.6.0] sftp transfer issues]

The built-in FTP server runs on port 21.

[Unraid OS version 6.6.0-rc4 available]

The official 6.6.0 version is out. Please use this version.

If any issues they can be reported under the 6.6.0 stable release.

[[6.6.0] sftp transfer issues]

AFAIK the built-in FTP server does not support sftp, I am surprized it could work on sftp.

To verify the correct operation I copied the near 60TB file back from my desktop to disk5 of my server. All without problem.

[[6.6.0] sftp transfer issues]

I just tested FTP download using winSCP client with FTP protocol. And have no problem to download a near 60GB file from the server to my desktop.

Have you tried a different FTP client?

[[6.6.0] sftp transfer issues]

Unraid doesn't have a sFTP server built-in, what are software you using?

[6.6.0-rc4 Share Settings not discernable]

It was reported before, but I don't have a usual suspect.

[6.6.0-rc4 Share Settings not discernable]

Problably one of your plugins interfering. Start in safe mode to check.

 

[6.6.0RC4 - nginx upstream timed errors]

See 

 

 

[After rc3, my VM lost network access, after rc4, VNC died as well]

Perhaps newer kernel plays a role, which was updated in rc3 and rc4 again.

It is not the first time things "change" due to kernel changes...

[After rc3, my VM lost network access, after rc4, VNC died as well]

1 minute ago, Barafu said:

Seems to be connected with BIOS: SeaBIOS works, OVMF does not.

Makes sense.

SeaBIOS is for legacy BIOS, while OVMF requires UEFI, which I doubt your BIOS supports, seen its 'age'.

[6.6.RC4 unclean shutdown detected]

Reboot and Power Down perform a clean shutdown, that is services and the array are stopped first (the same chain of actions when "Array Stop" is pressed).

 

To ensure the system can continue, there is a timer built-in and the timer setting must be long enough to allow all services, including Docker and VM to stop in time. Nothing dsngerous in my opinion, in a well behaved system.

[After rc3, my VM lost network access, after rc4, VNC died as well]

7 minutes ago, Barafu said:

while for Linux VM-s I can't see nothing.

It is something related to your system which prevents the VM proper start up.

As a test could stop one VM and temporary assign more memory to the other VM?

[6.6.RC4 unclean shutdown detected]

If the shutdown timer (see my earlier post) is set shorter than it takes your VM (and array) to stop, Unraid continues with a unclean shutdown. Increase the shutdown timer to e.g. 120s.

[After rc3, my VM lost network access, after rc4, VNC died as well]

The message you see in VNC means the VM didn't start properly.

 

I just installed Debian 9.5.0 (I downloaded the latest version from the Debian site) with the exact same settings as you and all works fine. Doesn't explain of course your issue.

 

General observations on your hardware:

1. The BIOS is dated 2008, have you checked for any newer version?

2. Your RAM is only 4GB, which makes running VMs very tight. Better to have 8GB or 16GB

[After rc3, my VM lost network access, after rc4, VNC died as well]

7 minutes ago, Barafu said:

I suspect that may be it is not the version, but the update process itself?

Difficult to tell what is causing the issue on your system.

I can't replicate the issue. Existing and newly created VMs on my system all have VNC access.

Can you post a screenshot of the issue you are seeing?

[6.6.RC4 unclean shutdown detected]

See also Settings -> Disk Settings -> Shutdown time-out to adjust the time to wait

[After rc3, my VM lost network access, after rc4, VNC died as well]

I am running Ubuntu server 18.04.1 without issues. What version are you using?

[Unraid OS version 6.6.0-rc4 available]

1 minute ago, dlandon said:

That error comes from the UD plugin.

I have the same error message, but no UD installed.

This message was also present in RC3, and haven't experienced any negative impact.

[6.6.0RC3 - can't change disks included in existing share]

This is working fine for me. Included disks and Excluded disks can be added or removed without problem.

 

Have you tried with your system started in safe mode?

 

[[6.6 rc3] Bonding enabled by default]

This behavior exists since version 6.0 was introduced.

By default bonding is enabled to allow people to connect to any available port of their system and avoid them complaining about their connection not working because they didn't use eth0 (which happened frequently in the past).

 

[6.6.0RC3 - can't remove existing cpuset-cpus settings from mineos docker]

Previously the only way to add cpu pinning to docker containers is by giving the necessary statement in "extra parameters". Removing that statement should make everything unpinned again. Not sure why this one container didn't work. A fluke?

 

[6.6.0RC3 - custom VM XML edits not preserved when use CPU pinning page]

1 hour ago, DZMM said:

I lost my emulatorpin line which is part of the <cputune> section

I made an update which preserves the "emulatorpin" section.

[6.6.0RC3 - can't remove existing cpuset-cpus settings from mineos docker]

Switch to Advanced view and remove the entry from "extra parameters"

 

Ps. I believe the latest version of "CA Fix Common Problems" will detect and tell you to change. Worthwhile to run this plugin and let it find incompatabilities.