Jump to content
limetech

unRAID Server Release 6.2 Stable Release Available

444 posts in this topic Last Reply

Recommended Posts

I'm getting over 1GB/sec writing to unRAID now, but still getting only 500MB/sec down .... but it is no longer choppy.

 

I'm seeing the same lower read speeds, I've been trying various tweaks without success, I can write to unRAID at >1GB/s when it's caching to RAM and at ~800MB/s sustained to a NVMe cache SSD, but read speed from the same device, using user or disk shares, tops at ~500Mb/s.

 

Tom, is there any tunnables we/you could try?

Share this post


Link to post

Do you have antivirus installed?  If your AV is scanning the file as you copy it from unRAID, it can slow things down.

Share this post


Link to post

Upgrade to 6.2 Attempt number 2.

 

So I encountered the same issues so far in attempt number 2 (NIC getting reassigned, Docker going hair wire, VM's not starting). 

 

I have reconfigured the network so that is fixed. 

 

I have rebuilt all of docker however still have an issue with my Docker Versions not acting right.  Some of my dockers say "update ready", one says "up to date" and all the rest say "not available".  I have clicked "update" on all of them and the issue remains.  The one that says "update ready" finishes with "The command finished successfully!" however the message never goes away.  The ones that say "not available" are not changing status no matter what I do. 

 

Any advice on the docker issue?

 

That sounds like what several users found, lots of upgrade notices for dockers but upgrades didn't work.  I believe they all found that the same fix took care of it, deleting the docker.img (through the Docker settings page), recreating it, and adding back your containers through the Community Apps Previous Apps or through My Templates(?).

 

Squid: made the change.

 

I have already done these steps twice, how many times should I be repeating them?

 

Any advice for my docker issues?

Share this post


Link to post

Upgrade to 6.2 Attempt number 2.

 

So I encountered the same issues so far in attempt number 2 (NIC getting reassigned, Docker going hair wire, VM's not starting). 

 

I have reconfigured the network so that is fixed. 

 

I have rebuilt all of docker however still have an issue with my Docker Versions not acting right.  Some of my dockers say "update ready", one says "up to date" and all the rest say "not available".  I have clicked "update" on all of them and the issue remains.  The one that says "update ready" finishes with "The command finished successfully!" however the message never goes away.  The ones that say "not available" are not changing status no matter what I do. 

 

Any advice on the docker issue?

 

That sounds like what several users found, lots of upgrade notices for dockers but upgrades didn't work.  I believe they all found that the same fix took care of it, deleting the docker.img (through the Docker settings page), recreating it, and adding back your containers through the Community Apps Previous Apps or through My Templates(?).

 

Squid: made the change.

 

I have already done these steps twice, how many times should I be repeating them?

 

Any advice for my docker issues?

Can you post the actual screenshot where it the docker says "command finished successfully"  dockerMan used to have a nasty habit of stating that when in fact it didn't.  But, ultimately if toasting the docker.img and recreating it (and we're talking here about the docker.img file, not the container images within it) didn't work, then I'm really not quite sure.  What containers are giving this problem btw?

Share this post


Link to post

Upgrade to 6.2 Attempt number 2.

 

So I encountered the same issues so far in attempt number 2 (NIC getting reassigned, Docker going hair wire, VM's not starting). 

 

I have reconfigured the network so that is fixed. 

 

I have rebuilt all of docker however still have an issue with my Docker Versions not acting right.  Some of my dockers say "update ready", one says "up to date" and all the rest say "not available".  I have clicked "update" on all of them and the issue remains.  The one that says "update ready" finishes with "The command finished successfully!" however the message never goes away.  The ones that say "not available" are not changing status no matter what I do. 

 

Any advice on the docker issue?

 

That sounds like what several users found, lots of upgrade notices for dockers but upgrades didn't work.  I believe they all found that the same fix took care of it, deleting the docker.img (through the Docker settings page), recreating it, and adding back your containers through the Community Apps Previous Apps or through My Templates(?).

 

Squid: made the change.

 

I have already done these steps twice, how many times should I be repeating them?

 

Any advice for my docker issues?

 

Where is your docker.img?  On the cache drive?  What is the file system on the drive that is holding the docker.img?

Share this post


Link to post

Today I tried connecting to my unraid server and noticed no SMB shares are working. They don't show when browsing to the UNC root and I also noticed this in the event logs:

 

Oct  3 20:00:16 Tower emhttp: shcmd (126): chmod 0777 '/mnt/user/Downloads'

Oct  3 20:00:16 Tower emhttp: shcmd (127): chown 'Admin':'Domain Users' '/mnt/user/Downloads'

Oct  3 20:00:16 Tower emhttp: err: shcmd: shcmd (127): exit status: 1

Oct  3 20:00:16 Tower emhttp: shcmd (128): chmod 0777 '/mnt/user/Kodi'

Oct  3 20:00:16 Tower emhttp: shcmd (129): chown 'Admin':'Domain Users' '/mnt/user/Kodi'

Oct  3 20:00:16 Tower emhttp: err: shcmd: shcmd (129): exit status: 1

Oct  3 20:00:36 Tower emhttp: shcmd (142): chmod 0777 '/mnt/user/Downloads'

Oct  3 20:00:36 Tower emhttp: shcmd (143): chown 'Admin':'Domain Users' '/mnt/user/Downloads'

Oct  3 20:00:36 Tower emhttp: err: shcmd: shcmd (143): exit status: 1

Oct  3 20:00:36 Tower emhttp: shcmd (144): chmod 0777 '/mnt/user/Kodi'

Oct  3 20:00:36 Tower emhttp: shcmd (145): chown 'Admin':'Domain Users' '/mnt/user/Kodi'

Oct  3 20:00:36 Tower emhttp: err: shcmd: shcmd (145): exit status: 1

Oct  3 20:00:47 Tower emhttp: shcmd (156): mkdir '/mnt/user/Test3' |& logger

Oct  3 20:00:47 Tower emhttp: shcmd (157): chmod 0777 '/mnt/user/Test3'

Oct  3 20:00:47 Tower emhttp: shcmd (158): chown 'Admin':'Domain Users' '/mnt/user/Test3'

Oct  3 20:00:47 Tower emhttp: err: shcmd: shcmd (158): exit status: 1

Oct  3 20:00:47 Tower emhttp: shcmd (161): chmod 0777 '/mnt/user/Downloads'

Oct  3 20:00:47 Tower emhttp: shcmd (162): chown 'Admin':'Domain Users' '/mnt/user/Downloads'

Oct  3 20:00:47 Tower emhttp: err: shcmd: shcmd (162): exit status: 1

Oct  3 20:00:47 Tower emhttp: shcmd (163): chmod 0777 '/mnt/user/Kodi'

Oct  3 20:00:47 Tower emhttp: shcmd (164): chown 'Admin':'Domain Users' '/mnt/user/Kodi'

Oct  3 20:00:47 Tower emhttp: err: shcmd: shcmd (164): exit status: 1

Oct  3 20:00:47 Tower emhttp: shcmd (165): chmod 0777 '/mnt/user/Test3'

Oct  3 20:00:47 Tower emhttp: shcmd (166): chown 'Admin':'Domain Users' '/mnt/user/Test3'

Oct  3 20:00:47 Tower emhttp: err: shcmd: shcmd (166): exit status: 1

Oct  3 20:00:47 Tower emhttp: shcmd (179): chmod 0777 '/mnt/user/Downloads'

Oct  3 20:00:47 Tower emhttp: shcmd (180): chown 'Admin':'Domain Users' '/mnt/user/Downloads'

Oct  3 20:00:47 Tower emhttp: err: shcmd: shcmd (180): exit status: 1

Oct  3 20:00:47 Tower emhttp: shcmd (181): chmod 0777 '/mnt/user/Kodi'

Oct  3 20:00:47 Tower emhttp: shcmd (182): chown 'Admin':'Domain Users' '/mnt/user/Kodi'

Oct  3 20:00:47 Tower emhttp: err: shcmd: shcmd (182): exit status: 1

Oct  3 20:00:47 Tower emhttp: shcmd (183): chmod 0777 '/mnt/user/Test3'

Oct  3 20:00:47 Tower emhttp: shcmd (184): chown 'Admin':'Domain Users' '/mnt/user/Test3'

Oct  3 20:00:47 Tower emhttp: err: shcmd: shcmd (184): exit status: 1

Oct  3 20:00:54 Tower emhttp: shcmd (197): chmod 0777 '/mnt/user/Downloads'

Oct  3 20:00:54 Tower emhttp: shcmd (198): chown 'Admin':'Domain Users' '/mnt/user/Downloads'

Oct  3 20:00:54 Tower emhttp: err: shcmd: shcmd (198): exit status: 1

Oct  3 20:00:54 Tower emhttp: shcmd (199): chmod 0777 '/mnt/user/Kodi'

Oct  3 20:00:54 Tower emhttp: shcmd (200): chown 'Admin':'Domain Users' '/mnt/user/Kodi'

Oct  3 20:00:54 Tower emhttp: err: shcmd: shcmd (200): exit status: 1

Oct  3 20:00:54 Tower emhttp: shcmd (201): chmod 0777 '/mnt/user/Test3'

Oct  3 20:00:54 Tower emhttp: shcmd (202): chown 'Admin':'Domain Users' '/mnt/user/Test3'

Oct  3 20:00:54 Tower emhttp: err: shcmd: shcmd (202): exit status: 1

Oct  3 20:01:10 Tower emhttp: shcmd (215): chmod 0777 '/mnt/user/Downloads'

Oct  3 20:01:10 Tower emhttp: shcmd (216): chown 'Admin':'Domain Users' '/mnt/user/Downloads'

Oct  3 20:01:10 Tower emhttp: err: shcmd: shcmd (216): exit status: 1

Oct  3 20:01:10 Tower emhttp: shcmd (217): chmod 0777 '/mnt/user/Kodi'

Oct  3 20:01:10 Tower emhttp: shcmd (218): chown 'Admin':'Domain Users' '/mnt/user/Kodi'

Oct  3 20:01:10 Tower emhttp: err: shcmd: shcmd (218): exit status: 1

Oct  3 20:01:10 Tower emhttp: shcmd (219): chmod 0777 '/mnt/user/Test3'

Oct  3 20:01:10 Tower emhttp: shcmd (220): chown 'Admin':'Domain Users' '/mnt/user/Test3'

Oct  3 20:01:10 Tower emhttp: err: shcmd: shcmd (220): exit status: 1

Oct  3 20:01:21 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

Oct  3 20:01:58 Tower emhttp: shcmd (233): chmod 0777 '/mnt/user/Downloads'

Oct  3 20:01:58 Tower emhttp: shcmd (234): chown 'Admin':'Domain Users' '/mnt/user/Downloads'

Oct  3 20:01:58 Tower emhttp: err: shcmd: shcmd (234): exit status: 1

Oct  3 20:01:58 Tower emhttp: shcmd (235): chmod 0777 '/mnt/user/Kodi'

Oct  3 20:01:58 Tower emhttp: shcmd (236): chown 'Admin':'Domain Users' '/mnt/user/Kodi'

Oct  3 20:01:58 Tower emhttp: err: shcmd: shcmd (236): exit status: 1

Oct  3 20:01:58 Tower emhttp: shcmd (237): chmod 0777 '/mnt/user/Test3'

Oct  3 20:01:58 Tower emhttp: shcmd (238): chown 'Admin':'Domain Users' '/mnt/user/Test3'

Oct  3 20:01:58 Tower emhttp: err: shcmd: shcmd (238): exit status: 1

Oct  3 20:02:03 Tower emhttp: shcmd (251): chmod 0777 '/mnt/user/Downloads'

Oct  3 20:02:03 Tower emhttp: shcmd (252): chown 'Admin':'Domain Users' '/mnt/user/Downloads'

Oct  3 20:02:03 Tower emhttp: err: shcmd: shcmd (252): exit status: 1

Oct  3 20:02:03 Tower emhttp: shcmd (253): chmod 0777 '/mnt/user/Kodi'

Oct  3 20:02:03 Tower emhttp: shcmd (254): chown 'Admin':'Domain Users' '/mnt/user/Kodi'

Oct  3 20:02:03 Tower emhttp: err: shcmd: shcmd (254): exit status: 1

Oct  3 20:02:03 Tower emhttp: shcmd (255): chmod 0777 '/mnt/user/Test3'

Oct  3 20:02:03 Tower emhttp: shcmd (256): chown 'Admin':'Domain Users' '/mnt/user/Test3'

Oct  3 20:02:03 Tower emhttp: err: shcmd: shcmd (256): exit status: 1

 

 

I tried rebooting and also updating to the latest version, I was on 6.2 and now I just updated to 6.2.1-2016.09.22

tower-diagnostics-20161003-2013.zip

Share this post


Link to post

Can we start working on the media player NFS user share issue now that this is stable

 

http://lime-technology.com/forum/index.php?topic=51308.msg494307#msg494307

 

I'd like to second this.  I upgraded from 6.1.9 to 6.2 stable today only to discover the NFS user share was not available on my media players (Mede8er MED600X3D); only empty subfolders displayed.  Downgraded to 6.1.9 and all is back to normal.  Not asking this be placed on the highest priority list but would feel comfortable knowing it will be addressed at some point.  Thanks!

Share this post


Link to post

Can we start working on the media player NFS user share issue now that this is stable

 

http://lime-technology.com/forum/index.php?topic=51308.msg494307#msg494307

 

I'd like to second this.  I upgraded from 6.1.9 to 6.2 stable today only to discover the NFS user share was not available on my media players (Mede8er MED600X3D); only empty subfolders displayed.  Downgraded to 6.1.9 and all is back to normal.  Not asking this be placed on the highest priority list but would feel comfortable knowing it will be addressed at some point.  Thanks!

 

My networked Bluray player relies on a working NFS for 3D ISO playback, so I also would like so see this fixed please.

 

I used this rule upto unraid 6.1.9 *(ro,insecure,anongid=100,anonuid=99,all_squash) and security is set to private.

Share this post


Link to post

I'm encountering odd network related issues. This release is defiantly not "stable".

 

I can copy files from a Windows 2008 server into Unraid, but I can no longer write from my Windows 8.1 Pro desktop.

 

My laptop (on the same network) running Windows 8.1 Pro can write,  but it's prompted for a login when I try to access a share on the Unraid server. I don't have any users configured or require. In fact I can type anything for the username/password and then it lets me in.

 

I'm currently having to copy from my desktop to this windows server so I can then copy from the windows server to unraid.

 

I don't have any VMS, just a couple docker apps.

 

Should I just go back to 6.1.9?

Share this post


Link to post

I'm encountering odd network related issues. This release is defiantly not "stable".

 

I can copy files from a Windows 2008 server into Unraid, but I can no longer write from my Windows 8.1 Pro desktop.

 

My laptop (on the same network) running Windows 8.1 Pro can write,  but it's prompted for a login when I try to access a share on the Unraid server. I don't have any users configured or require. In fact I can type anything for the username/password and then it lets me in.

 

I'm currently having to copy from my desktop to this windows server so I can then copy from the windows server to unraid.

 

I don't have any VMS, just a couple docker apps.

 

Should I just go back to 6.1.9?

Are all of your shares set to Public for SMB?

Share this post


Link to post

For me yes, all my shares are public.

Just noticed that i can change settings from 'Shares/Disk?name=cache' pages.

Each time i press Apply, settings are back to previous value.

 

So SMB down, and cant even setup NFS lol

 

Any idea?

 

Share this post


Link to post

For me yes, all my shares are public.

Just noticed that i can change settings from 'Shares/Disk?name=cache' pages.

Each time i press Apply, settings are back to previous value.

 

So SMB down, and cant even setup NFS lol

 

Any idea?

 

shut the server down and pull the USB drive.  Run checkdisk on it via a Windows machine.  Put the usb back in the unRAID machine and see what happens.

Share this post


Link to post

I'm encountering odd network related issues. This release is defiantly not "stable".

 

I can copy files from a Windows 2008 server into Unraid, but I can no longer write from my Windows 8.1 Pro desktop.

 

My laptop (on the same network) running Windows 8.1 Pro can write,  but it's prompted for a login when I try to access a share on the Unraid server. I don't have any users configured or require. In fact I can type anything for the username/password and then it lets me in.

 

I'm currently having to copy from my desktop to this windows server so I can then copy from the windows server to unraid.

 

I don't have any VMS, just a couple docker apps.

 

Should I just go back to 6.1.9?

Are all of your shares set to Public for SMB?

 

Yea, my server isn't locked down, only root user, everything is public. Like I said, I don't have any users configured, never have. Everything worked fine from any computer before the update. I either can't write at all, or I get prompted for a user (which I can type anything I want and it continues normally), or I don't get prompted at all and I can write. All depends from which computer I do it from.

Share this post


Link to post

@RobJ I've attached my diag and dmesg

 

Thanks!  I've added your results and johnnie.black's results to the initial report, here, as a comparison of all of the boards.  As you can see there, there is not one suspect difference found, so I have failed to find a significant clue, so far.  There are still possible differences in how the UEFI is configured in the systems, and perhaps the non-working systems should report anything in their UEFI setup that is not default.

 

I prefer the IPMIView software from SuperMicro instead of connecting to each servers IPMI web page.  The best part is it has its own baked-in JRE, so you don't have to worry about having a compatible version installed on your computer.

  https://www.supermicro.com/products/nfo/SMS_IPMI.cfm

I didn't know that existed! And it actually works (even on the phone)!  Awesome, thank you!

 

This is interesting, and I'd like to know if IPMIView (or any other tool) has a screen buffer for the console, preserved even after the reboot.  The problem here is that what we really needed to see was the console messages (or dmesg) up until just before the reboot, on the rebooting systems, but that hasn't been possible.  If the second machine can capture the screen and still have it after the reboot, then we can know either the last error, or at least how far it got, and can narrow the suspects down.

 

I am downloading an eval copy of SuperMicro's SUM now, which should allow me to dump the current BIOS config once I figure it out.  Unfortunately I'm now one state over from my server, so getting a direct screen capture isn't possible.  If I have a chance and IPMIView seems to work stable, I'll see if I can figure out a way to capture it.

Share this post


Link to post

@RobJ I've attached my diag and dmesg

 

Thanks!  I've added your results and johnnie.black's results to the initial report, here, as a comparison of all of the boards.  As you can see there, there is not one suspect difference found, so I have failed to find a significant clue, so far.  There are still possible differences in how the UEFI is configured in the systems, and perhaps the non-working systems should report anything in their UEFI setup that is not default.

 

I prefer the IPMIView software from SuperMicro instead of connecting to each servers IPMI web page.  The best part is it has its own baked-in JRE, so you don't have to worry about having a compatible version installed on your computer.

  https://www.supermicro.com/products/nfo/SMS_IPMI.cfm

I didn't know that existed! And it actually works (even on the phone)!  Awesome, thank you!

 

This is interesting, and I'd like to know if IPMIView (or any other tool) has a screen buffer for the console, preserved even after the reboot.  The problem here is that what we really needed to see was the console messages (or dmesg) up until just before the reboot, on the rebooting systems, but that hasn't been possible.  If the second machine can capture the screen and still have it after the reboot, then we can know either the last error, or at least how far it got, and can narrow the suspects down.

 

I am downloading an eval copy of SuperMicro's SUM now, which should allow me to dump the current BIOS config once I figure it out.  Unfortunately I'm now one state over from my server, so getting a direct screen capture isn't possible.  If I have a chance and IPMIView seems to work stable, I'll see if I can figure out a way to capture it.

 

Attached are the current BIOS config, and for completion, the DMI config.  SuperMicro was super helpful in giving me an eval key for SUM!

dmi.txt

bios.txt

Share this post


Link to post

 

Now to the crux of the problem: All my shares are showing, but some of the user shares are empty when you click through network shares (Multiple windows machines as well as an ubuntu-based Kodi system), as well as through Putty and Midnight Commander.

 

Disk shares show all files correctly. Before I go through the whole diagnostics posting etc, any obvious things I may have overlooked?

 

I didn't manually create any of the user shares. UnRaid created them from the top level folders on the drives. Could that be related? Also, the really odd thing is that some of the User Shares are fine...

 

Thanks!

 

 

But that's the point, there was no known change in 6.2, which is why nothing was mentioned in the update notes.  Since then, a few users such as yourself have had issues with changes in the Windows users and credentials, so I added a note about that in the Additional Upgrade Advice.

 

There were also considerable changes in the networking configuration, which could be related, as it caused changes in a few users' setups.  But once reconfigured, that should no longer be an issue.  There has also been the common issue in a number of unRAID upgrades, where the newer kernel would identify multiple NIC's in a differing order than previously, causing eth0 to be different, which could result in loss of connectivity or other differences.  Again, once reconfigured or cable switched, no problem.  There's more about the networking changes in the Additional Upgrade Advice.

 

You quoted DoeBoye, but I can't see a connection, his appears to be a very different issue.

 

It's been theorized that the recent Windows 10 update caused the issue for some, but we still need that to be confirmed.  And it almost certainly doesn't apply to any other Windows version, unless a recent Windows update carried the same changes.

 

If you do try again, grab the diagnostics and let us take a look.  Although it does sound more like it could be an issue with Windows credentials (but I'm not an expert).

 

For the record, I never figured out exactly what the problem was. I ended up deleting all my mapped drives, shut down my server, rebooted, and recreated the mapping. Everything was back to normal.

 

A few of observations:

 

[*]Kodi lost all 'watched' status info and I had to rebuild my library as if the path was completely new... (Even though it was the same as before)

[*]I think it is definitely related to multiple NIC cards, as I had to switch ports to get the GUI to come up (due most likely to the issue RobJ outlined above regarding the kernel remapping eth0 to a different NIC

[*]To be clear, it wasn't just mapped shares that displayed as empty. It was also clicking through network neighbourhood as well as through Midnight Commander

 

Not sure if that helps anyone, but I figured it doesn't hurt to get it in the public record :)

 

This does help, and I do appreciate the information, but it seems my kodi has still managed to lose all the file locations after trying to upgrade again to 6.2.4 from 6.1.9 where the multiple NIC issue wasn't a problem, but at least now I know with this comment that it's more than likely the NIC issue.  I'll have to figure it out once I'm at home and looking at kodi to see if the paths have indeed changed or if the NAS just somehow fell off the SMB workgroup even if the paths themselves haven't changed.

Share this post


Link to post

So frustration aside with trying to correct this problem as stated above....

I've downgraded once again to 6.1.9, the last version that I can use where I'm able to view the NAS on the network.  Essentially the upgrades to 6.2 and higher all are taking the NAS off the homegroup/workgroup which technically has no members aside from the NAS, and then making it impossible to connect to.

 

On 6.1.9, the workgroup is visible on kodi and any laptop, I'm able to browse, etc, no problems.

On anything later, connections timeout and no connection can be made.

I've been attempting to alleviate this for some hours now and with absolutely no luck.

If I put the NAS on its own workgroup/homegroup, why am I unable to see said workgroup/homegroup or any other computer to join?

 

I know homegroups are a total cluster-f*ck and have caused major pains for everyone since their inception, but is anyone able to help me in the right direction with this?  All my network settings are the same as they are in 6.1.9, with the exception of that additional NIC card that 6.2.4 creates, which doesnt actually exist.  eth0 is the correct one, all the settings for it are the same.... yet no connection is able to be made, no network discovery of the NAS on any computer, no homegroup visible, etc.

 

Have a windows 7 laptop and desktop, and a windows10 laptop.  Nothing sees this NAS when it's on anything 6.2 or higher, but visible on 6.1.9.

 

I'm at a complete loss for what my next step should be so any help with this would be greatly appreciated.

Share this post


Link to post

So frustration aside with trying to correct this problem as stated above....

I've downgraded once again to 6.1.9, the last version that I can use where I'm able to view the NAS on the network.  Essentially the upgrades to 6.2 and higher all are taking the NAS off the homegroup/workgroup which technically has no members aside from the NAS, and then making it impossible to connect to.

 

On 6.1.9, the workgroup is visible on kodi and any laptop, I'm able to browse, etc, no problems.

On anything later, connections timeout and no connection can be made.

I've been attempting to alleviate this for some hours now and with absolutely no luck.

If I put the NAS on its own workgroup/homegroup, why am I unable to see said workgroup/homegroup or any other computer to join?

 

I know homegroups are a total cluster-f*ck and have caused major pains for everyone since their inception, but is anyone able to help me in the right direction with this?  All my network settings are the same as they are in 6.1.9, with the exception of that additional NIC card that 6.2.4 creates, which doesnt actually exist.  eth0 is the correct one, all the settings for it are the same.... yet no connection is able to be made, no network discovery of the NAS on any computer, no homegroup visible, etc.

 

Have a windows 7 laptop and desktop, and a windows10 laptop.  Nothing sees this NAS when it's on anything 6.2 or higher, but visible on 6.1.9.

 

I'm at a complete loss for what my next step should be so any help with this would be greatly appreciated.

 

It's hard to say without your diagnostics.  Please see Need help? Read me first!, and attach the diagnostics zip.

 

I'm not a networking expert, some here would know better, but I've been wondering if downgrading SMB to 2.0.2 would help with this issue too?  Anyone know?

Share this post


Link to post

So frustration aside with trying to correct this problem as stated above....

I've downgraded once again to 6.1.9, the last version that I can use where I'm able to view the NAS on the network.  Essentially the upgrades to 6.2 and higher all are taking the NAS off the homegroup/workgroup which technically has no members aside from the NAS, and then making it impossible to connect to.

 

On 6.1.9, the workgroup is visible on kodi and any laptop, I'm able to browse, etc, no problems.

On anything later, connections timeout and no connection can be made.

I've been attempting to alleviate this for some hours now and with absolutely no luck.

If I put the NAS on its own workgroup/homegroup, why am I unable to see said workgroup/homegroup or any other computer to join?

 

I know homegroups are a total cluster-f*ck and have caused major pains for everyone since their inception, but is anyone able to help me in the right direction with this?  All my network settings are the same as they are in 6.1.9, with the exception of that additional NIC card that 6.2.4 creates, which doesnt actually exist.  eth0 is the correct one, all the settings for it are the same.... yet no connection is able to be made, no network discovery of the NAS on any computer, no homegroup visible, etc.

 

Have a windows 7 laptop and desktop, and a windows10 laptop.  Nothing sees this NAS when it's on anything 6.2 or higher, but visible on 6.1.9.

 

I'm at a complete loss for what my next step should be so any help with this would be greatly appreciated.

 

It's hard to say without your diagnostics.  Please see Need help? Read me first!, and attach the diagnostics zip.

 

I'm not a networking expert, some here would know better, but I've been wondering if downgrading SMB to 2.0.2 would help with this issue too?  Anyone know?

 

I'm posting the 6.1.9 systemlog, followed by the 6.2.4 upgrade system log, as wel as the diagnostics.

See all attached.

 

Also for network settings tabs, as I'm rather confused about whether this is only a samba issue, or if it's underlying network.

 

6.1.9 Network settings:

Eh2WJiz.png

 

6.2.4 Network settings:

SI4LhYG.jpg

Ljlb6tq.jpg

eth1 is disabled and not up.

6.1.9.syslog-20161202-0915.zip

6.2.4.syslog-20161202-0915.zip

medianas-diagnostics-20161202-0921.zip

Share this post


Link to post

So frustration aside with trying to correct this problem as stated above....

I've downgraded once again to 6.1.9, the last version that I can use where I'm able to view the NAS on the network.  Essentially the upgrades to 6.2 and higher all are taking the NAS off the homegroup/workgroup which technically has no members aside from the NAS, and then making it impossible to connect to.

 

On 6.1.9, the workgroup is visible on kodi and any laptop, I'm able to browse, etc, no problems.

On anything later, connections timeout and no connection can be made.

I've been attempting to alleviate this for some hours now and with absolutely no luck.

If I put the NAS on its own workgroup/homegroup, why am I unable to see said workgroup/homegroup or any other computer to join?

 

I know homegroups are a total cluster-f*ck and have caused major pains for everyone since their inception, but is anyone able to help me in the right direction with this?  All my network settings are the same as they are in 6.1.9, with the exception of that additional NIC card that 6.2.4 creates, which doesnt actually exist.  eth0 is the correct one, all the settings for it are the same.... yet no connection is able to be made, no network discovery of the NAS on any computer, no homegroup visible, etc.

 

Have a windows 7 laptop and desktop, and a windows10 laptop.  Nothing sees this NAS when it's on anything 6.2 or higher, but visible on 6.1.9.

 

I'm at a complete loss for what my next step should be so any help with this would be greatly appreciated.

 

It's hard to say without your diagnostics.  Please see Need help? Read me first!, and attach the diagnostics zip.

 

I'm not a networking expert, some here would know better, but I've been wondering if downgrading SMB to 2.0.2 would help with this issue too?  Anyone know?

 

I'm posting the 6.1.9 systemlog, followed by the 6.2.4 upgrade system log, as well as the diagnostics.

 

I'm afraid I don't see anything directly wrong, nothing that clearly causes your machine to not be visible to your Windows machines.  In both 6.1.9 and 6.2.4, your Qualcomm networking appears to be setup correctly as eth0, and NTP is happy with it so networking is working, packets are flowing (not many so far, but it just started).  The networking config files look fine.  So I'll mention various other things I saw below, but I don't see how they could be limiting your visibility.

 

* You have 3 networking chipsets:

- a wireless controller on the board, no driver so it's ignored; might be a good idea to go into the BIOS and turn it off

- an Intel gigabit chipset onboard, using e1000e, not used but I think is your best one, configured and set to eth1, appears to be setup fine but no connection

- the Qualcomm Atheros gigabit chipset, using alx, 'on the board' but not 'onboard', configured and set to eth0, working fine

 

* Looks like multiple dependency problems:

- 5 old libraries being loaded from /boot/extra, including 3 old pythons(!)  - I strongly recommend deleting them all and using the NerdPack plugin to load only the latest; for 6.2 python should be 2.7.12; if at all possible, /boot/extra should be empty, use NerdPack as much as you can

--- ncurses-5.9-x86_64-2 (something else is also loading ncurses-5.9-x86_64-4)

--- python-2.6.4-i486-1 (32 bit???)

--- python-2.6.6-i486-1.txz (32 bit???)

--- python-2.7.3-i686-5PTr (32 bit???) that's 3 big pythons loaded, the correct one should be python-2.7.12-x86_64-1 from NerdPack

--- unrar-5.0.14-x86_64-1ponce

- all of the above are from 2014 or 2013

- in addition, you are running UnMenu and loading more old packages from /boot/packages; I can't see what's in there or what's loaded but I do see a dev environment loaded, a compiler and make, and I have to assume they are old too

- for example, unRAID loaded glibc-2.23-x86_64-1, UnMenu (I assume) loaded glibc-2.17-x86_64-7; both are present

--- at the end of the 6.2.4 syslog, you have a segfault and errors about "version `GLIBC_2.18' not found"; the segfault is the typical error for a dependency conflict

- it's loaded both utempter-1.1.5-x86_64-1 and utempter-1.1.6-x86_64-2

- make sure that kernel-headers-3.10.17-x86-3 is valid for 64 bit

 

* There's other evidence of old stuff, it's finding an old dynamix.plg and dynamix.kvm.manager and apcupsd; you should clean out anything older

 

* I imagine you know that ionotify.log is using up almost 2GB of flash drive space.  It hasn't been used since March.

 

* Probably a separate issue or non-issue but the Dockers appear to only be on an internal network.  Haven't used this but I think you would need to turn on bridging and set them to use br0, to make them visible externally.  The 6.2 networking changes did affect how this works, see bonienl's comments in the Additional Upgrade Advice.

 

I'm sorry I don't see a solution yet.  Workgroup name is MEDIAHOME, so any Windows machine in that workgroup should see it.  You may be the localMaster but you've been rebooting.  May need a little more time for other machines to see you.  I'm still curious about the SMB version, hope to see someone respond about that.  My apologies in advance if I have made any mistakes above.

Share this post


Link to post

So frustration aside with trying to correct this problem as stated above....

I've downgraded once again to 6.1.9, the last version that I can use where I'm able to view the NAS on the network.  Essentially the upgrades to 6.2 and higher all are taking the NAS off the homegroup/workgroup which technically has no members aside from the NAS, and then making it impossible to connect to.

 

On 6.1.9, the workgroup is visible on kodi and any laptop, I'm able to browse, etc, no problems.

On anything later, connections timeout and no connection can be made.

I've been attempting to alleviate this for some hours now and with absolutely no luck.

If I put the NAS on its own workgroup/homegroup, why am I unable to see said workgroup/homegroup or any other computer to join?

 

I know homegroups are a total cluster-f*ck and have caused major pains for everyone since their inception, but is anyone able to help me in the right direction with this?  All my network settings are the same as they are in 6.1.9, with the exception of that additional NIC card that 6.2.4 creates, which doesnt actually exist.  eth0 is the correct one, all the settings for it are the same.... yet no connection is able to be made, no network discovery of the NAS on any computer, no homegroup visible, etc.

 

Have a windows 7 laptop and desktop, and a windows10 laptop.  Nothing sees this NAS when it's on anything 6.2 or higher, but visible on 6.1.9.

 

I'm at a complete loss for what my next step should be so any help with this would be greatly appreciated.

 

It's hard to say without your diagnostics.  Please see Need help? Read me first!, and attach the diagnostics zip.

 

I'm not a networking expert, some here would know better, but I've been wondering if downgrading SMB to 2.0.2 would help with this issue too?  Anyone know?

 

I'm posting the 6.1.9 systemlog, followed by the 6.2.4 upgrade system log, as well as the diagnostics.

 

I'm afraid I don't see anything directly wrong, nothing that clearly causes your machine to not be visible to your Windows machines.  In both 6.1.9 and 6.2.4, your Qualcomm networking appears to be setup correctly as eth0, and NTP is happy with it so networking is working, packets are flowing (not many so far, but it just started).  The networking config files look fine.  So I'll mention various other things I saw below, but I don't see how they could be limiting your visibility.

 

* You have 3 networking chipsets:

- a wireless controller on the board, no driver so it's ignored; might be a good idea to go into the BIOS and turn it off

- an Intel gigabit chipset onboard, using e1000e, not used but I think is your best one, configured and set to eth1, appears to be setup fine but no connection

- the Qualcomm Atheros gigabit chipset, using alx, 'on the board' but not 'onboard', configured and set to eth0, working fine

 

* Looks like multiple dependency problems:

- 5 old libraries being loaded from /boot/extra, including 3 old pythons(!)  - I strongly recommend deleting them all and using the NerdPack plugin to load only the latest; for 6.2 python should be 2.7.12; if at all possible, /boot/extra should be empty, use NerdPack as much as you can

--- ncurses-5.9-x86_64-2 (something else is also loading ncurses-5.9-x86_64-4)

--- python-2.6.4-i486-1 (32 bit???)

--- python-2.6.6-i486-1.txz (32 bit???)

--- python-2.7.3-i686-5PTr (32 bit???) that's 3 big pythons loaded, the correct one should be python-2.7.12-x86_64-1 from NerdPack

--- unrar-5.0.14-x86_64-1ponce

- all of the above are from 2014 or 2013

- in addition, you are running UnMenu and loading more old packages from /boot/packages; I can't see what's in there or what's loaded but I do see a dev environment loaded, a compiler and make, and I have to assume they are old too

- for example, unRAID loaded glibc-2.23-x86_64-1, UnMenu (I assume) loaded glibc-2.17-x86_64-7; both are present

--- at the end of the 6.2.4 syslog, you have a segfault and errors about "version `GLIBC_2.18' not found"; the segfault is the typical error for a dependency conflict

- it's loaded both utempter-1.1.5-x86_64-1 and utempter-1.1.6-x86_64-2

- make sure that kernel-headers-3.10.17-x86-3 is valid for 64 bit

 

* There's other evidence of old stuff, it's finding an old dynamix.plg and dynamix.kvm.manager and apcupsd; you should clean out anything older

 

* I imagine you know that ionotify.log is using up almost 2GB of flash drive space.  It hasn't been used since March.

 

* Probably a separate issue or non-issue but the Dockers appear to only be on an internal network.  Haven't used this but I think you would need to turn on bridging and set them to use br0, to make them visible externally.  The 6.2 networking changes did affect how this works, see bonienl's comments in the Additional Upgrade Advice.

 

I'm sorry I don't see a solution yet.  Workgroup name is MEDIAHOME, so any Windows machine in that workgroup should see it.  You may be the localMaster but you've been rebooting.  May need a little more time for other machines to see you.  I'm still curious about the SMB version, hope to see someone respond about that.  My apologies in advance if I have made any mistakes above.

 

So... it looks like one of those dependencies in /packages could've somehow been conflicting with the network discovery.  Just deleted everything that was in there since they were in fack from 2013 and 2014, and cleared out the go script as well as that also needed some cleaning (and should've really been done before I did the 6.2.4 upgrade).... and voila! network discovery! At least from my end at work, I wasn't able to get this far and have kodi detect the workgroup, but now it is!  That has to be a good sign.

 

I'm glad you mentioned those older dependencies, reminded me I really had to go through them.

A million thank you's! Hopefully when I get home, I'll get much further with this and have this cleared out, but it's already a major improvement

Share this post


Link to post

Be aware the SMB can take a lot of time to resolve everything the network (It  was written basically back in the days when the 80368 was the 'king of the hill') and was intended to add as little overhead to the CPU as possible.  As a result, its polling intervals are actually quite long--- think minutes!  Be sure that all of the name of your workgroup on all of your computers have the same name and all are in CAPS only.  (Windows ignores capitalization and Linux honors it.  I have never figured out quite how Samba resolves this issue.)  Sometimes, the best way to resolve issues is to shutdown every computer using SMB.  Then restart with your server and after about ten minutes start to add back in your computers slowly one at a time. 

 

What OS are you having issues with?

 

Plus, there are some nagging issues as MS has recently revised their version of SMB and the Samba group is still playing catch up.  I tend to suspect that some of their updates have broken some things...

 

If you want to force your unRAID server to become the Local Master, add these lines to the 'Settings'  >>  'SMB' icon  >>  'SMb Extras' tab:

 

[global]
domain master = yes
preferred master = yes
os level = 255
 

 

You might also install the  "Local Master" plugin for Dynamix.  You can find it listed in this post:

 

 

It will show which computer on the network is the Local Master.

 

Edited by Frank1940

Share this post


Link to post

Be aware the SMB can take a lot of time to resolve everything the network (It  was written basically back in the days when the 80368 was the 'king of the hill') and was intended to add as little overhead to the CPU as possible.  As a result, its polling intervals are actually quite long--- think minutes!  Be sure that all of the name of your workgroup on all of your computers have the same name and all are in CAPS only.  (Windows ignores capitalization and Linux honors it.  I have never figured out quite how Samba resolves this issue.)  Sometimes, the best way to resolve issues is to shutdown every computer using SMB.  Then restart with your server and after about ten minutes start to add back in your computers slowly one at a time. 

 

What OS are you having issues with?

 

Plus, there are some nagging issues as MS has recently revised their version of SMB and the Samba group is still playing catch up.  I tend to suspect that some of their updates have broken some things...

 

If you want to force your unRAID server to become the Local Master, add these lines to the 'Settings'  >>  'SMB' icon  >>  'SMb Extras' tab:

 

[global]
domain master = yes
preferred master = yes
os level = 255

 

You might also install the  "Local Master" plugin for Dynamix.  You can find it listed in this post:

 

    http://lime-technology.com/forum/index.php?topic=36543.msg339559#msg339559

 

It will show which computer on the network is the Local Master.

 

Good to know about the Local Master plugin, I've installed it, and according to unraid workgroup settings, unraid is now the local master.

I believe those leftover dependencies that were in boot/packages (still from the hayday of unmenu... I know, I know, I just never got around to clearing things out, clearly a major oversight) we're causing this malfunction with the workgroups, or possibly something that was in the go script.

 

Regardless, at least from vpn'ing into my network, kodi now finds those drives that it could before, which is a very good sign at least until I get home.  Hopefully all the windows 7 and 10 computers will be able to see it as easily.  Unraid at the moment is the only thing turned on on the network at home, so that helps.

Share this post


Link to post

I'm still curious about the SMB version, hope to see someone respond about that.

 

I don't know if it will help but no harm in trying, he can try downgrading to SMB 2.0.2 or SMB 3.0.0 that is the same used by unRAID 6.1.9 (6.2.4 uses SMB 3.1.1)

 

To downgrade go to Settings -> SMB -> and add to "Samba extra configuration:"

 

max protocol = SMB2_02

 

or

 

max protocol = SMB3_00

 

Apply and then stop and re-start array, connected clients may need to reboot to reconnect, probably best to try 2.0.2 first due to the performance issues with v6.2 and SMB3.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now