dalben

I've had no issues until 6.8 rc3. Previous 6.7 and 6.6 versions etc worked fine.

Added them to a dedicated post on this issue:

I've recreated the problem to catch the diagnostics. 2 sets attached. rc1 where everything works fine on both coreelec and android. rc3 where I cannot access shares from my coreelec install nor from my android phone. The coreelec was told to use min SMB2 and max SMB3. When rc3 threw errors, I dropped to min SMB1 and max SMB3 but there was no change to the behavior. The kodi logs on the coreelec show the following under rc3, not sure if it's useful: 2019-10-19 13:37:40.535 T:3346269056 ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://USERNAME:PASSWORD@TDM/videos/AFL' unix_err:'16' error : 'Invalid argument' 2019-10-19 13:37:40.535 T:3346269056 ERROR: GetDirectory - Error getting smb://TDM/videos/AFL/ 2019-10-19 13:37:42.276 T:4093889968 ERROR: CGUIMediaWindow::GetDirectory(smb://TDM/videos/AFL/) failed tdm-diagnostics-20191019-0539 - 68rc3.zip tdm-diagnostics-20191019-0528 - 68rc1.zip

I see a similar issue with a Coreelec install I have. RC1 works fine, RC3 doesn't. Shares can't be accessed.

Um, I see some with a leading Cap, others all caps. Like MOTHERBOARD. Fwiw the new login screen follows the entered case. When the server name isn't a word, but an acronym, leading caps just looks odd.

Yes. Stick it into a Windows pc and you have full access to the usb.

My coreelec kodi setup was unable to access the server. Couldn't open shares. I regressed back to 6.8rc1 and it's all working again. If you want any logs for anywhere let me know and once the server is free I can try again. Fwiw the shares are SMB. Coreelec told to use min smb2 and Max smb3. I tried smb1 min but it didn't help.

What's the reasoning it's by design? Surely what makes more sense is to take the case as it's entered into the identification field.

This is still present in RC3. Might be nothing for those without OCD

Had a look at that. That's another container/window browser to open to get to it. I'm looking for something that's in the same window/tab I'm in if that makes sense. It's not a big issue, but a nice to have. But I will look at code server for the hacking of other peoples code that I do.

With the need to jump out into the CLI for at certain times, and not being a Linux diehard, it would be handy if the GUI had a notepad/scratchpad time page where we could but the various commands we need to use in CLI for easy reference. I have a textfile on my desktop with it now but it might be handy to have it as a page/plugin/menu option on the Unraid GUI as, at least for me, that's always open and on the screen when I click the Putty icon.

Could be related to this:

Well done. You've been nominated for the most useful reply award. You must be proud.

Thanks for the update. Based on what you've found, is there a possibility this issue could trigger disk read errors. Ive had a few recently and while they could be coincidence / batch timing related, I'm wondering if there is a connection.

I dont use Mover. The stalls come when one of the media download dockers pulls down a file, into cache, then moves into the library, which is on the array. Or if I am just working on other stuff and accidentally start a file copy or move while media is streaming.

My only gripe here is that limetech released an RC (rc4) with an expected fix. Now they have stopped that and are telling us to wait for the next version. Why the change? We all know limetech release time lines are as consistent as lottlo numbers so we're in a situation where this fix could be 1 day or 1 month away. I'm at breaking point where I have to do something now as the family has had enough of the stalled streaming. If I have to downgrade, I will, but there's a good chance I'll have to find another solution going forward. Unraid was great when I was the only real user of the server. Now that it anchors the family's entertainment I need something more reliable.

It is a showstopper. If this issue isn't fixed then anyone that uses their UnRaid server primarily for media streaming through a household will have to find another solution. The Unraid show is effectively stopped for them. Using your argument that downgrading is a viable solution, then no issue would ever be considered a showstopper. Limetech was happy to throw out rc4 when they thought that would resolve the problem. It didn't. So if a resolution has been found why hasn't rc5 with that fix been released? Why has there been a change of approach in resolving this issue?

Is it worth trying to load up Unraid 6.6.7 to see if there is a difference. 6.7 seems to have some weird performance issues.

Actually now that you mention it I've had 3 of my disks (spinners) throw read errors and end up disabled recently (4 week period) . I have no reason to believe it's related to this bug but it's interesting you have seen the same. I've RMA'd 2 and mamanged to get one going again. I put it down to a bad batch and just one of those things but I may downgrade to 6.6.7 for a while.

OK. Fair enough. I'll blame you 😉

Oh don't get me wrong. I love Unraid and nothing gets close to it. But unlike the old days, now there are demanding family members who just expect things to work. That's a bit worrying if they still aren't sure what the issue is and are hoping it's related to another issue they are fixing. The SQL corruption is an easy fix, use a cache drive. This issue has no easy fix.

Agree but this issue has made me review Unraid as the central server that runs most of the houses needs. This is a pretty big issue, if a copy happens while streaming video the movie just stops. Media streaming and the associated media harvesting and organising dockers is my main reason for unraid. To not have a single acknowledgement, other than now through a 3rd party, that they are aware of the issue and addressing it is poor form. It's a big issue, it needed those affected to be put at some ease. I've been around since the 4.x days so I'm acutely aware of what 'released soon' means. I hope we see something normal people 'soon' so I can fend off the wife and kids.

I loved the idea of PiHole but after a server issue this week while I was out of the country, the family were without internet access due to the DNS setting pointing to the pihole docker which was down. I may need to build a Pi with POE to get the small, single cable pihole device I need. Unless anyone can suggest how to configure things so that the family isn't left in the 20th Century if the container doesn't come up.

I had a similar issue. I found one of the docker cfg files somewhere (on flash I think) had the old lan ip range/address listed despite changing everything on the webgui. I made the changes in the config, started docker service again and all good. Can't access the server at the moment to give a better clue as to the cfg file.