unRAID Server Version 6.2.4 Available


limetech

Recommended Posts

  • Replies 106
  • Created
  • Last Reply

Top Posters In This Topic

I had an issue today. About 10hrs after i upgraded to v6.2.4 from v6.2.3.

 

First the Windows 10 VM with Nvidia passthrough fell off the network. Then the mouse started to act erratically. I rebooted the VM from within Windows but it hung on Restarting for over 30mins.

 

I tried to connect to the server via web browser but i could not proceed past the login. Then I SSL into the server and tried to reboot it from the command line. It said it worked but it didn't. The last step was pulling the power chord.

 

The server and Windows 10 VM are now working again.

 

I notice every few upgrades, the VM fails to boot properly on the first boot after an upgrade. Then the issue resolves itself. Next time it happens i will post a log file.

 

Hi Chris,

 

There isn't really enough information in your post to diagnose what's going on.  First and foremost, how are you assigning a USB mouse to the VM?  Are you passing through an entire USB controller or are you just assigning the mouse using the web interface of unRAID itself.  When you say the VM dropped off the network, do you mean the VM couldn't get out to the Internet or any local systems?

 

Also, when was the last time you upgraded your VirtIO drivers inside the guest VM?

 

Lastly, please try to collect diagnostics when these things happen and post them here.  Without those diagnostics, we can't diagnose.

 

1. I am assigning the mouse using the web interface.

 

2. The VM lost connection to the internet and local network.

 

3. I wasn't looking for a fix because power cycling the server fixed the issue. I only wanted to share my upgrade experience with others.

 

4. VirtIO drivers = v0.1.118-2...which is what i used when i first built the VM.

 

5. If the problem returns after an upgrade or just randomly, i will post the system log.

 

Thanks.

Link to comment

Not working. All of my 3 windows machines cannot access the shares. I have set all security to public and restarted both unraid and the windows machines with no avail.

 

Have you set your unRAID to be the Local Master?    'Settings' >>> 'SMB'  >>>  'Workgroup Settings'  The shutdown all of your Windows and other computers that are using SMB for about ten minutes.  Then add the other computers at about two to three minute (min) intervals.

 

Have you install the dynamix  Local Master  plugin?  That plugin will show which computer has won the Election to be come the Local Master.  You can find it here:

 

      https://lime-technology.com/forum/index.php?topic=36543.0

 

Also make sure that Workgroup name is in all Caps for all of the Computers that are in the same workgroup.  (Linux and Windows treat Capitalization differently.)

Link to comment

Server is set to local master

All machines are part of the same workgroup in caps

I'll try shutting all down for 10 minutes

I'll install the plugin.

Thanks

*******

Update plugin installed and local master is the unRAID server.

Brought up one machine and still no luck.

 

Try going to the  'Control Panel'  >>>  'Credential Manager'  and deleting all of the Windows Credentials.  This has worked for some folks.  Tom wrote an excellent description that show why fixing SMB problems is so difficult.  You can read it here:

 

      https://lime-technology.com/forum/index.php?topic=26412.msg231122#msg231122

 

Link to comment

I've wiped out the credential manager on all machines. If I cant get this going ill revert back to 6.1.19. I don't feel comfortable wiping out the config files.

 

Lets try one more thing.

 

First, download your diagnostics file.  'Tools' >>> 'Diagnostics'.  Open up the zip file and navigate to the system folder. open up the file named    ifconfig.txt.

 

Look for the section named  eth0.  you will  find a line like this:

 

inet 192.168.1.242  netmask 255.255.255.0  broadcast 0.0.0.0

 

The inet parameter is the server's IP address.  (in this case---  192.168.1.242)

 

Second, take this address and open up Windows Explorer:  type    \\192.168.1.242     in the address bar. (Those are back-slashes, NOT forward-slashes!)  You should now be able to see the server with the User Shares and flash drive folders. 

Link to comment

I've wiped out the credential manager on all machines. If I cant get this going ill revert back to 6.1.19. I don't feel comfortable wiping out the config files.

 

Lets try one more thing.

 

First, download your diagnostics file.  'Tools' >>> 'Diagnostics'.  Open up the zip file and navigate to the system folder. open up the file named    ifconfig.txt.

 

Look for the section named  eth0.  you will  find a line like this:

   

 

[/code]

inet 192.168.1.242  netmask 255.255.255.0  broadcast 0.0.0.0

 

The inet parameter is the server's IP address.  (in this case---  192.168.1.242)

 

Second, take this address and open up Windows Explorer:  type    \\192.168.1.242     in the address bar. (Those are back-slashes, NOT forward-slashes!)  You should now be able to see the server with the User Shares and flash drive folders.

 

This is what the file says:

 

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.6  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 00:25:90:57:9e:a9  txqueuelen 1000  (Ethernet)
        RX packets 1419455  bytes 211967415 (202.1 MiB)
        RX errors 0  dropped 56100  overruns 0  frame 0
        TX packets 1282458  bytes 3318919791 (3.0 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 02:42:cd:e7:d7:41  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 28760  bytes 2034678 (1.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether 00:25:90:57:9e:a9  txqueuelen 1000  (Ethernet)
        RX packets 1424034  bytes 238004584 (226.9 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2403349  bytes 3402779201 (3.1 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf7e00000-f7e20000  

eth1: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 00:25:90:57:9e:a8  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xf7d00000-f7d20000  

gre0: flags=128<NOARP>  mtu 1476
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

gretap0: flags=4098<BROADCAST,MULTICAST>  mtu 1462
        ether 00:00:00:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ip_vti0: flags=128<NOARP>  mtu 1364
        tunnel   txqueuelen 1  (IPIP Tunnel)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.255.255.255
        loop  txqueuelen 1  (Local Loopback)
        RX packets 6179117  bytes 642850649 (613.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6179117  bytes 642850649 (613.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tunl0: flags=128<NOARP>  mtu 1480
        tunnel   txqueuelen 1  (IPIP Tunnel)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethde531ee: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 0e:8a:10:9a:e0:80  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 28760  bytes 2034678 (1.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:02:8d:99  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 52:54:00:02:8d:99  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

I found something strange in the network.cfg file the IP address of my server is 192.168.1.6 not 192.168.1.22

# Generated settings:
USE_DHCP="yes"
IPADDR="192.168.1.22"
NETMASK="255.255.255.0"
GATEWAY="192.168.1.1"
DHCP_KEEPRESOLV="no"
DNS_SERVER1="192.168.1.1"
DNS_SERVER2=""
DNS_SERVER3=""
BONDING="no"
BONDING_MODE="1"
BRIDGING="yes"
BRNAME="br0"

Link to comment

I'd like to recommend reading the Additional Upgrade Advice, especially the networking section, as there have been a number of changes made with 6.2.

 

Thanks. I did have an issue with no connectivity. I had to switch the Ethernet port to one that I wasn't using. IPMI is working fine. I feel like their is an issue with unraid not broadcasting itself. Is their a way to reset the network configuration?

Link to comment

I just updated from 6.2.2 directly to 6.2.4.

 

Update went well, but VM stopped working. When starting, I get the error message "Execution error.internal error: Did not find USB device 5ac:1281".

 

Full diagnostic attached. Thanks for your help!

 

Why would you have an Apple iOS device in recovery mode permanently attached to your virtual machine? Clearly you meant to remove that from the configuration after you were done recovering it, right? Maybe this is one more plus for hotplug capability? There's a hotplug plugin, but I don't know if it automatically detaches devices which have been unplugged from the host machine.

Link to comment

"Reported performance issues with some low/mid range hardware.  No movement on this yet."

 

What type of hardware would be low/mid?

 

Is there still an issue with AMD FX CPUs and VMs?  I might of asked this elsewhere but cannot find it.

 

Low-end is the likes of Atom D525 and AMD E350 and the likes.  Mid-end I think is stuff like Sempron and Core2.

Link to comment

"Reported performance issues with some low/mid range hardware.  No movement on this yet."

 

What type of hardware would be low/mid?

 

Is there still an issue with AMD FX CPUs and VMs?  I might of asked this elsewhere but cannot find it.

 

Low-end is the likes of Atom D525 and AMD E350 and the likes.  Mid-end I think is stuff like Sempron and Core2.

 

I haven't really noticed much with my Sempron 140. I'm alseep when it runs Parity checks and I use another trash box spare machine to do my Pre-Clears too.

I'm not running any Dockers or anything big in the Plugins either. Not correcting you just agreeing with what you said. ;)

 

Last preclear results on my configuration in my profile.

Duration: 8 hours, 24 minutes, 49 seconds. Average speed: 66.0 MB/s

Link to comment

"Reported performance issues with some low/mid range hardware.  No movement on this yet."

 

What type of hardware would be low/mid?

 

Is there still an issue with AMD FX CPUs and VMs?  I might of asked this elsewhere but cannot find it.

 

Low-end is the likes of Atom D525 and AMD E350 and the likes.  Mid-end I think is stuff like Sempron and Core2.

 

I haven't really noticed much with my Sempron 140. I'm alseep when it runs Parity checks and I use another trash box spare machine to do my Pre-Clears too.

I'm not running any Dockers or anything big in the Plugins either. Not correcting you just agreeing with what you said. ;)

 

Where you will really be seeing the performance issues is if you go to dual parity.  Because it uses matrix operations, it takes a lot more CPU capability than single parity, or a modern generation (>2014) processor whose instruction set includes a particular instruction which performs that operation. 

 

EDIT:  There are two operations where dual parity will really affect speed.  The first is the parity check.  My non-correcting parity speeds for my Test Bed server went from 104.1MB/s  to 47.2MB/s... Complete discussion of this issue is here:  http://lime-technology.com/forum/index.php?topic=51036    Speeds with the current release have improved to 64.2 Mb/s. 

 

The second one will be writing to the protected array.  I have never actually run any tests to get the exact impact as the measurement of transfer speeds has so many variables to make the elimination of them a monumental task. 

 

Plus, it appears that AMD processors are more impacted than Intel processors. 

 

I don't know how many people have actually changed to dual parity.  I suspect that the number with low end hardware is actually fairly low because the cost of that second parity drive.  I further suspect that the people who have converted are using higher end hardware to start with which is less impacted because it (1) has the CPU horsepower to handle the math or (2) is new enough to have the matrix instruction included. Or in many cases both!

Link to comment

Basically any CPU is fine as long as you're not running Dockers or VMs => i.e. if your server is purely a NAS, you don't need a lot of "horsepower."    One of my servers is on a SuperMicro Atom D525 board, and it works perfectly for what I use it for, which is just a NAS.  It can also stream videos with no problem, although that's not it's primary use.  My media server and backup servers both have significantly better processors ... but they also don't idle at 18 watts like that trusty little Atom  :)

Link to comment

My media server and backup servers both have significantly better processors ... but they also don't idle at 18 watts like that trusty little Atom  :)

 

Something more modern will idle way lower than the Atom.  My i3-6100 idles at 8W.

 

What motherboard?  ... and is that the idle draw when ON (NOT in S3 mode) ??

 

Link to comment

That 8W may just be the CPU alone, not counting the entire system.

 

Not sure how that would be measured -- but it's hard to believe the entire system idles at 8w unless it's in S3 sleep.

 

The 18w my system idles at is the full system powered up -- NOT in sleep.  Hard to believe a CPU with a 51w TDP (the i3-6100) will idle appreciably lower than on with a 13w TDP (the D525).  That 18w includes the motherboard, CPU, memory, disk controller, NIC, and the 6 disks (3TB WD Reds) powered down but still drawing a small amount (0.4w each according to their specs).

 

 

Link to comment

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.