unRAID Server Release 6.0-beta15-x86_64 Available


Recommended Posts

Well, I apologise in advance, but let's face it, it's inevitable....

 

When is beta 16 /RC1 going to be released?

 

;D

Surely the question is, are we going to see 6.0 released before the 1 year anniversary of the date by which it was said it was going to be released?

 

It's so late they are beginning to call it Duke Nukem.

 

So much for regular updates......

Link to comment
  • Replies 506
  • Created
  • Last Reply

Top Posters In This Topic

Well, I apologise in advance, but let's face it, it's inevitable....

 

When is beta 16 /RC1 going to be released?

 

;D

Surely the question is, are we going to see 6.0 released before the 1 year anniversary of the date by which it was said it was going to be released?

 

It's only been 226 days over budget since the officially declared release deadline on 6.0 FINAL. They have another 138 days left until September 30, 2015.

 

Link to comment

I have a problem on 6beta15.

 

When I install a VM, using br0 as network, I have connection only for a minute or so after installing the network drivers. Then the VM says "no internet connection" and I cant connect anything on the LAN. If I disable br0 and use virbr0 as bridge it works. I always get an IP address from my router. But cant send any traffic.

 

I have a 2 nic bond, but I have also tried to break the bond, using only one nic, but no change.

 

Any ideas?

 

/jowe

 

Edit: and suddenly it just works, that's strange...

 

edit2: Same thing after restart, no connection. And 20min later its just working.

Link to comment

When I install a VM, using br0 as network, I have connection only for a minute or so after installing the network drivers. Then the VM says "no internet connection" and I cant connect anything on the LAN. If I disable br0 and use virbr0 as bridge it works. I always get an IP address from my router. But cant send any traffic.

virbr0 is meant to be a NAT style connection, so should not be getting an address from your router

 

What is the name of the bridge you have configured under Settings->Network?  I assume that this is br0?  You should not name that bridge as virbr0  as that would conflict with the built in NAT virbr0.  The bridge under Settings->Network is the one that should get an address from your router.

 

Edit: and suddenly it just works, that's strange...

 

edit2: Same thing after restart, no connection. And 20min later its just working.

Seen other reports like this.  Not sure what they mean and what is causing that behaviour.
Link to comment

When I install a VM, using br0 as network, I have connection only for a minute or so after installing the network drivers. Then the VM says "no internet connection" and I cant connect anything on the LAN. If I disable br0 and use virbr0 as bridge it works. I always get an IP address from my router. But cant send any traffic.

virbr0 is meant to be a NAT style connection, so should not be getting an address from your router

 

What is the name of the bridge you have configured under Settings->Network?  I assume that this is br0?  You should not name that bridge as virbr0  as that would conflict with the built in NAT virbr0.  The bridge under Settings->Network is the one that should get an address from your router.

 

Exactly, br0 is the bridge under settings/network, virbr0 is the setting under each VM. I Always get IP from router (when using br0) even when i cant connect to anything.

 

 

Link to comment

Exactly, br0 is the bridge under settings/network, virbr0 is the setting under each VM. I Always get IP from router (when using br0) even when i cant connect to anything.

At that point what does the 'ifconfig' command show?  I was wondering if you have sensible DNS and gateway settings at this point?  Also can you ping anything using either the ip address or the name?  I would suggest that the router is the first one to try as if you cannot get there you are not going to get any further.
Link to comment

At that point what does the 'ifconfig' command show?  I was wondering if you have sensible DNS and gateway settings at this point?  Also can you ping anything using either the ip address or the name?  I would suggest that the router is the first one to try as if you cannot get there you are not going to get any further.

 

I cant ping the gateway. I can ping the unraid box, but not other windows boxes on the network.

 

root@Tower:~# ifconfig

bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST>  mtu 1500

        ether 00:30:48:64:29:56  txqueuelen 0  (Ethernet)

        RX packets 3559491  bytes 416895856 (397.5 MiB)

        RX errors 0  dropped 3598  overruns 0  frame 0

        TX packets 4516088  bytes 5533667616 (5.1 GiB)

        TX errors 0  dropped 2 overruns 0  carrier 0  collisions 0

 

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.1.101  netmask 255.255.255.0  broadcast 192.168.1.255

        ether 00:30:48:64:29:56  txqueuelen 0  (Ethernet)

        RX packets 3485118  bytes 260219893 (248.1 MiB)

        RX errors 0  dropped 18244  overruns 0  frame 0

        TX packets 2719416  bytes 5414381427 (5.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.42.1  netmask 255.255.0.0  broadcast 0.0.0.0

        ether 56:84:7a:fe:97:99  txqueuelen 0  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 1214  bytes 163292 (159.4 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500

        ether 00:30:48:64:29:56  txqueuelen 1000  (Ethernet)

        RX packets 3681405  bytes 572528054 (546.0 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 4736734  bytes 6263548612 (5.8 GiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 16  memory 0xd8900000-d8920000

 

eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500

        ether 00:30:48:64:29:56  txqueuelen 1000  (Ethernet)

        RX packets 3720061  bytes 582469314 (555.4 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 4743473  bytes 6274561479 (5.8 GiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 17  memory 0xd8a00000-d8a20000

 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        loop  txqueuelen 0  (Local Loopback)

        RX packets 22015  bytes 2386488 (2.2 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 22015  bytes 2386488 (2.2 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

veth4521fd1: flags=67<UP,BROADCAST,RUNNING>  mtu 1500

        ether ae:32:36:0f:43:a6  txqueuelen 0  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 1169  bytes 155675 (152.0 KiB)

        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:ac:97:cc  txqueuelen 0  (Ethernet)

        RX packets 88212  bytes 9255008 (8.8 MiB)

        RX errors 0  dropped 801  overruns 0  frame 0

        TX packets 357006  bytes 526679939 (502.2 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        ether fe:54:00:c5:8a:f9  txqueuelen 500  (Ethernet)

        RX packets 27391  bytes 3259547 (3.1 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 123545  bytes 96781028 (92.2 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

Link to comment

I assume that ifconfig is from within unRAID?  If so it is a bit strange that neither eth0 or eth1 have IP addresses.  What IP address do you expect your unRAID box to have?  It might also be worth seeing what an ifconfig (or ipconfig if a Windows VM) shows from inside the VM itself.

Link to comment

I assume that ifconfig is from within unRAID?  If so it is a bit strange that neither eth0 or eth1 have IP addresses.  What IP address do you expect your unRAID box to have?  It might also be worth seeing what an ifconfig (or ipconfig if a Windows VM) shows from inside the VM itself.

 

Yes, its from unraid. When you activate bond, the ip is set on bond0. And when you activate bridge, the ip I s set on br0, so 192.168.1.101 is the ip of the tower.

 

If I ping the VM from another Windows box it replies, and after that I can ping that box from the VM, but I still cant ping GW.

 

The ipconfig of the VM shows that I have and IP from the router (I also tried with a Windows DHCP server, same result). /release and /renew is no problem, but doesnt solve anything.

 

Link to comment

root@Tower:~# ifconfig

bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST>  mtu 1500

        ether 00:30:48:64:29:56  txqueuelen 0  (Ethernet)

        RX packets 3559491  bytes 416895856 (397.5 MiB)

        RX errors 0  dropped 3598  overruns 0  frame 0

        TX packets 4516088  bytes 5533667616 (5.1 GiB)

        TX errors 0  dropped 2 overruns 0  carrier 0  collisions 0

 

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.1.101  netmask 255.255.255.0  broadcast 192.168.1.255

        ether 00:30:48:64:29:56  txqueuelen 0  (Ethernet)

        RX packets 3485118  bytes 260219893 (248.1 MiB)

        RX errors 0  dropped 18244  overruns 0  frame 0

        TX packets 2719416  bytes 5414381427 (5.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.42.1  netmask 255.255.0.0  broadcast 0.0.0.0

        ether 56:84:7a:fe:97:99  txqueuelen 0  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 1214  bytes 163292 (159.4 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500

        ether 00:30:48:64:29:56  txqueuelen 1000  (Ethernet)

        RX packets 3681405  bytes 572528054 (546.0 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 4736734  bytes 6263548612 (5.8 GiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 16  memory 0xd8900000-d8920000

 

eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500

        ether 00:30:48:64:29:56  txqueuelen 1000  (Ethernet)

        RX packets 3720061  bytes 582469314 (555.4 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 4743473  bytes 6274561479 (5.8 GiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 17  memory 0xd8a00000-d8a20000

 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        loop  txqueuelen 0  (Local Loopback)

        RX packets 22015  bytes 2386488 (2.2 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 22015  bytes 2386488 (2.2 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

veth4521fd1: flags=67<UP,BROADCAST,RUNNING>  mtu 1500

        ether ae:32:36:0f:43:a6  txqueuelen 0  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 1169  bytes 155675 (152.0 KiB)

        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:ac:97:cc  txqueuelen 0  (Ethernet)

        RX packets 88212  bytes 9255008 (8.8 MiB)

        RX errors 0  dropped 801  overruns 0  frame 0

        TX packets 357006  bytes 526679939 (502.2 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        ether fe:54:00:c5:8a:f9  txqueuelen 500  (Ethernet)

        RX packets 27391  bytes 3259547 (3.1 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 123545  bytes 96781028 (92.2 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

I have little experience with bonding and network virtualization, but how can eth0 and eth1 and br0 and bond0 all have the same MAC?  I can see the physical MAC mapped to a software MAC, but this still seems to break the rules, having multiple NIC presences with the same MAC?  Is that possibly causing all the dropped packets?

 

The large number of dropped packets could explain the intermittent nature of the connection.

 

Edit:  Can someone with a similar but working setup (dual NIC's with bonding and Dockers enabled) provide us with their ifconfig report?

Link to comment

I have little experience with bonding and network virtualization, but how can eth0 and eth1 and br0 and bond0 all have the same MAC?  I can see the physical MAC mapped to a software MAC, but this still seems to break the rules, having multiple NIC presences with the same MAC?  Is that possibly causing all the dropped packets?

 

The large number of dropped packets could explain the intermittent nature of the connection.

 

Edit:  Can someone with a similar but working setup (dual NIC's with bonding and Dockers enabled) provide us with their ifconfig report?

 

You pointed me in the right direction! I changed the bonding mode from balanced rr, to 802.3ad. And reconfigured the ether channel on the switch, I still have some drops on br0, but much less. And its working on the VMs!

 

Thanks!

Link to comment

... Tom's VERY quick at releasing an "a" version  ....

 

don't forget ... the bee's and cee's come even quicker  ;D

 

Well ... looks like RC1 didn't have the a's, b's, and c's problem => it just bit the dust entirely within 24 hours in favor of an RC2  :) :)

 

Link to comment

... Tom's VERY quick at releasing an "a" version  ....

 

don't forget ... the bee's and cee's come even quicker  ;D

 

Well ... looks like RC1 didn't have the a's, b's, and c's problem => it just bit the dust entirely within 24 hours in favor of an RC2  :) :)

 

All the more reason it should have been considered a beta.

Link to comment
  • 4 weeks later...

Is there any location where we can download previous versions of unRAID like this one?  I'm running RC5 but getting the  usb 2-1.2: reset high speed USB device number "x" messages on both my ESXi host and on my unRAID server itself.  I want to test out an older version.  Can these only be gotten by emailing support?

Link to comment

Seeing your posts i checked my syslog and found 1 entry of the usb reset error.

It's only one entry so not so bad. But i don't know what it means.

 

I have a second ESXI server (both are running 5.5 btw) with identical setup(even usb sticks) that does not show these errors.

Link to comment

Seeing your posts i checked my syslog and found 1 entry of the usb reset error.

It's only one entry so not so bad. But i don't know what it means.

 

I have a second ESXI server (both are running 5.5 btw) with identical setup(even usb sticks) that does not show these errors.

 

That's very strange.  Me logs are filled with those messages for as long as I have a VM on with the USB device added to it.  The moment I shut off the VM the messages stop.

Link to comment

Yeah that's definately strange.

The only usb device i've got assigned on my own server is the unraid stick.

On my other server i've got 2 devices, one for unraid (which gives no errors), and one special usb device, but no way of getting to syslogs there.

 

You said there were errors in ESXi somewhere? Where is this log you mentioned?

Link to comment

Yeah that's definately strange.

The only usb device i've got assigned on my own server is the unraid stick.

On my other server i've got 2 devices, one for unraid (which gives no errors), and one special usb device, but no way of getting to syslogs there.

 

You said there were errors in ESXi somewhere? Where is this log you mentioned?

 

Open the following address in  your webrowser:  https://"IP Address of your ESXi host"/host and you'll see vmkernal.log in there.

Link to comment

Yeah that's definately strange.

The only usb device i've got assigned on my own server is the unraid stick.

On my other server i've got 2 devices, one for unraid (which gives no errors), and one special usb device, but no way of getting to syslogs there.

 

You said there were errors in ESXi somewhere? Where is this log you mentioned?

 

Open the following address in  your webrowser:  https://"IP Address of your ESXi host"/host and you'll see vmkernal.log in there.

 

Thanks,

 

Both server show the error's and seems to be only on unraid forwarded devices.

It's not bad though, 2 error's on the entire log.

 

What's the consequence of these errors?

Link to comment

Yeah that's definately strange.

The only usb device i've got assigned on my own server is the unraid stick.

On my other server i've got 2 devices, one for unraid (which gives no errors), and one special usb device, but no way of getting to syslogs there.

 

You said there were errors in ESXi somewhere? Where is this log you mentioned?

 

Open the following address in  your webrowser:  https://"IP Address of your ESXi host"/host and you'll see vmkernal.log in there.

 

Thanks,

 

Both server show the error's and seems to be only on unraid forwarded devices.

It's not bad though, 2 error's on the entire log.

 

What's the consequence of these errors?

 

 

I honestly don't know if there is any consequence at all.  However I'm noticing serious slowness issues with regard to my unRAID VM so I'm searching for causes.  The webgui will be instantaneous for a few clicks and then it starts taking 20-30 seconds to load pages.  Even browsing directories on the USB via telnet is really slow just changing directories or doing things like manually starting unMenu.  It's very random but constant enough that it's driving me crazy.

Link to comment
Guest
This topic is now closed to further replies.