jsebright

So, now that the discussion around new licensing is starting to ease off a bit, I'd like to ask the obvious question... When can we see v7 and the next round of exciting new features?

Doesn't sound unfair to me. But... Along with a Pro licence, I've currently got a trial for a small install that I need to licence. I can either buy a basic key or extend / wait and buy a starter licence. Will there be a period of time during which I can make that choice - either by both being available, or knowing the new pricing in advance?

Thanks for replying. Not sure what the risks are of just plugging in a plain cable and seeing what's shown. Obviously nothing should go wrong, but I don't want to trash two servers if they both try to send power when they shouldn't! Might try to find some donor machines to try with first off to check that nothing bad happens even if the hardware and software will be completely different. I just don't want any of the magic smoke to come out of the chips because they won't work the same after that.

This might be a daft idea but... I'm setting up a second unraid server on an unused laptop to run some basic services. This is much lower powered than my main unraid server so I don't need to worry about leaving it on all the time. The main one has many disks, better CPU & ram and will still be used for some VM's, bigger protected storage and backups. I was thinking about faster networking between the two because I'm limited by the 1gb port on the laptop. I remember a very long time ago networking two windows PCs using a firewire cable that was configured as a network, and wondered if I could do the same with USB3 and make a direct attachment between the two machines as they're physically close together. (This would be in addition to them both going to the switch). Some research has revealed some usb cables with a device in the middle which refer to themselves as "Windows Easy Transfer Cable". Searching Amazon, this is an example (not currently available for me, but something similar might be). https://www.amazon.com/Plugable-Transfer-Thunderbolt-Software-Migration/dp/B0BGRVS51T/ So, would this sort of cable present itself as an ethernet adaptor in both servers that could then be configured to use as a fast sync / fileshare connection? Would a plain usb cable do the same thing (USB-A or USB-C) ? It seems this could be a very cheap way to get fast networking between two machines and only using a USB port.

I went quite early on this, but another uneventful upgrade. Many thanks.

Rolled back and it was still not working, but I didn't do a restore Tried swapping "cable" but it didn't make a difference. Could be something failing at a bad time, so have taken the card out and will try it in another machine soon. Not keen on rebooting the switch as it's POE and have quite a few devices hanging off it. I haven't tried swapping ports on the switch. Seems like it might not be a 6.12.4 issue specifically. Thanks for suggestions and support @JorgeB & @andber

Done. Thanks.

Upgrade from 6.12.3 to 6.12.4 appeared to go OK, but I have a network card issue. I have a 10gb fibre card, and onboard 1gb nic. These are set to a bond and it mainly uses the 10gb (onboard is enabled for WOL - a script after waking forces the 10gb card to be active). My fibre card is constantly showing as disconnected (Interface Ethernet Port 1 is down. Check cable!) . Changing designations between eth0 and eth1 makes no difference. It is listed in system devices as [15b3:1003] 02:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3] The new system drivers shows two drivers: mlx4_core Mellanox ConnectX HCA low-level driver Inuse net/ethernet/mellanox/mlx4 mlx4_en Mellanox ConnectX HCA Ethernet driver Inuse net/ethernet/mellanox/mlx4 I have the Mellanox Firmware Tools installed - which seems to report the card OK. Anyone else with this issue?

Some of the Kingston G2 readers supposedly available at Amazon UK for those interested. Had a usb fail about 4 years ago and I think it was painless to get a replacement licence.

I can confirm that changing the policy worked for me and I am now able to access private shares. For others and my future reference (as per link above) run secpol.msc browse to Security Settings > Local Policies > Security Options > Network security: LAN Manager authentication level Mine was "Not Defined", changed it to "Send NTLMv2 response only". Worked immediately , no need to logout / reboot. Edit: I see @systract had issues after a few minutes, I will monitor to see how long this lasts for.

I need to log that I'm also experiencing this, but not on all clients. Possibly restricted to Windows 11 as a windows 10 VM (not on Unraid) has no problems. All was fine on 6.10 Changing to "Secure" means I can read, but as Guest, and don't have permission to create a user. Have tried removing details in Credential Manager, but that makes no difference. Oddly enough in the machine that can access private shares I can't see anything in saved credentials. I think I am using a local account on that one, and a Windows / Microsoft account on the one which is having problems...

Is it possible to use something like the like/thanks indicators on this topic to provide some quick feedback options along the lines of: I've installed it and it worked first time. I've got it running after a few attempts. It didn't work for me so I rolled back. Lots of the posts following an announcement are along the lines of "Installed no issues" which is very reassuring to see for those of us with only one server and feeling a bit cautious (but still wanting the latest thing). This would give users the ability to respond with a bit of feedback, and some visible counts for those looking for reassurance. Love what you're doing, but waiting for a week or two before I jump in with this one!

Thanks! That's good to know.

Great work guys. When can we see an RC for 6.11 ? 😁

Did a scan of the flash and it came up OK, so am saving that option for later. I swapped cards that I need (10gb & drive controller), and removed a PCIE usb card that I can swap for another in a bit. I've finally got the "Interface Rules" back and can assign eth0 and eth1. I've not yet been successful in splitting the IOMMU groupings yet and have been trying unsuccessfully to get that to work. This is probably where some of the issues came in. I have also experienced problems with network not coming back up after waking from sleep - probably related, see this post: Going off topic. My ideal setup is where I can use onboard (intel HD930) graphics for a VM and perhaps some transcoding (quite rare), pass through a usb hub to the VM, Fibre connection as main, with gb for waking from sleep, server will go to sleep at night and wake up OK when needed. Stopping that is that I can't manage to split the audio part of the HD930 out into it's own IOMMU (so am using an extra card), and have been having problems with the network cards not working - seemingly when I've got the USB controller in (that was being stubbed). Possible issue remains is that some combination of hardware has prevented the Network-Rules from being created / maintainable. I'm going to try a different USB card and could try more moving around of cards to see if I manage to break the audio out and don't need the additional graphics - although I'm sure that will cause problems with getting VMs to use the onboard.

Time to re-create the flash drive? I'm not on the "My Servers" yet - will that slow down provisioning a new one if necessary. Appreciate the swift help. Thanks.

renamed networked.cfg - I can't see that a replacement has been created, but I haven't re-configured anything. No network-rules.cfg either. I'd been looking for a config file thinking there might be an issue with it but couldn't find one. I've recently swapped motherboard (and cpu), so the mac address of eth0 will have changed.

Oh yes. Very similar issues. Thought it was just me and continuinually fiddling with hardware that broke it. I was finding the server wakes up from a wake packet, but I couldn't get it to work. Having a keyboard attached and manually logging in and doing a reboot, gave a clean reboot. But I had to do that blind as my screen freezes on the login prompt (even before sleep) - presumably due to having intel_gpu_top plugin installed. I've set it to shutdown instead of sleep - takes longer to "wake up" but is more reliable. Would be nice if we could force the networking to restart on waking.

Same here - not sure if it happened in rc3 or rc4 though. Changing ownership of the appdata files (just for misbehaving dockers) to nobody:users seemed to fix it for me.

That's correct, I did. Struggling to get it to work again though. Going back to VNC, uninstalling all drivers & old devices before adding the graphics will probably help.

I haven't - that's where it all goes wrong. You're stuck with the default drivers. I'm on 6.9.2 and not ready to try 6.10 yet - still waiting for the next RC, "soon?". I'm hoping that updates to KVM/QEMU will help, as may future bios updates, and updated drivers from AMD. For now I've reverted back to adding a physical graphics card for VM work. A bit disappointing.

Sorry, no idea where the xvga='yes' came from. I try to stick to the Forms mode when editing VMs. As I said, for me I got to a state where there was no display but the VM was running and able to serve a remote desktop. I also saw the Microsoft Basic Adapter, but just did a reboot and the screen came up. I'm not 100% sure if the output is from HDMI or DP>HDMI adapter (I'm then running two long HDMI leads to another room). I don't get multi monitor from the basic adapter so it might be that only one of the outputs is working. If you are able to test a display port connection it might show something. I'm not seeing any errors in the logs. Sorry I can't offer more help - I don't understand enough to explain what's going on.

<hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <address bus='1' device='6'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> This is the section with the graphics - all the "hostdev" bits. The bit I edited was the line <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> I don't have the graphics & audio bound to VFIO. I don't think that the whole script will help - I've not got a full understanding of what it does, and it's probably a bit of a mess due to previous changes to this machine. The important points are Q35 Seabios, no other devices (add them later), get remote desktop working first (whilst graphics are VNC) so you can log in remotely if the display doesn't work (after you've changed the graphics) then you can check device manager and reboot.