dalben
-
Posts
1463 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by dalben
-
-
Case should always matters. Windows was the first OS I worked with where userid case wasn't an issue.
-
I have a couple of modeprobe commands in my go file. Can they still be run from there or should they be somewhere else? the system temp plugin isn't working with rc1 and rc 4
# start sensors
modprobe coretemp
modprobe nct6775 -
rc3 and adding server min protocol = NT1 to smb-extra.conf worked for me.
Here are the 2 testparm -sv outputs. One is rc1 and the other rc3 before the smb-extra.conf change.
Also note the coreelec install is linux, not android.
-
1
-
-
If there is anything I can do to test whether the patches solve the issue before the next release, let me know.
-
13 minutes ago, limetech said:
Maybe something to do with latest Samba release. Maybe SMB min/max protocol not right. Maybe netbios needs to be either enabled or disabled. Maybe ws-discovery daemon needs to be enabled/disabled.
The report is over 2 threads so let me consolidate and add more here:
There was no issue on rc1 and previous releases. I have supplied diags from rc1 and rc3
Corelelec was set to SMB min 2 max 3, I changed that to min1 max 3 but no change. I don't know how to change the setting on an Android phone
WS-Discovery on Unraid was enabled, I disabled, no change
Netboid was enabled on unraid, I disabled, no change
AFP Legacy was enabledon unraid, i disabled, no change.
QuotePretty sure you can keep investigating and let us all know what the solution is.
I have, reverting back to rc1 solves the problem for me. If you're expecting me to work out what's changed between rc1 and rc3 that's created this issue then I'm out of my depth. Happy enough to try different things when asked to help identify the issue, but I've reached my technical limitations.
-
1
-
-
4 hours ago, limetech said:
Something about invalid chars in the path?
Not sure. All I can tell you is it's worked fine for years up to 6.8rc1. With rc3 I can't connect to server shares.
-
4 minutes ago, Squid said:
Looks the same on my system...
Same. I'm using the White theme
-
6 minutes ago, Dazog said:
NFS and Samba has been broken on KODI since 6.7
I will try and test RC3 when I can.
I've had no issues until 6.8 rc3. Previous 6.7 and 6.6 versions etc worked fine.
-
17 hours ago, dalben said:
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.
16 hours ago, Frank1940 said:Come on people, where are your diagnostic files?
diagnosticsAdded 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.
-
1
-
-
3 minutes ago, bonienl said:
Consistency, all title fields on the Dashboard page use capitalization.
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.
-
5 minutes ago, local.bin said:
Contractual docs for clients, call me paranoid.
It boots and and the leds light and then after booting completes both ports go dead, no lights on the server or the switch.
Is it possible to restore the 'previous' directory while accessing the stick outside of the server?
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
-
2 hours ago, saarg said:
Stop stealing movies then until 6.8 is out.
Well done. You've been nominated for the most useful reply award. You must be proud.
-
1
-
-
43 minutes ago, limetech said:
The issue is that writes originating from a fast source (as opposed to a slow source such as 1Gbit network) completely consume all available internal "stripe buffers" used by md/unraid to implement array writes. When reads come in they get starved for resources to efficiently execute. The method used to limit the number of I/O's directed to a specific md device in the Linux kernel no longer works in newer kernels, hence I've had to implement a different throttling mechanism.
Changes to md/unraid driver require exhaustive testing. All functional tests pass however, driver bugs are notorious for only showing up under specific workloads due to different timing. As I write this I'm 95% confident there are no new bugs. Since this will be a stable 'patch' release, I need to finish my testing.
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.
-
1
-
-
1 hour ago, bonienl said:
Change your mover schedule to outside viewing hours. This prevents writes to the array while reading (streaming) is going on.
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.
-
13 minutes ago, Dazog said:
It's saturday, It's possible @limetech is a person.
They haven't failed to update us when they can.
NO one works 24/7.
Give them time to verify and test.
6.8 has ALOT of changes, what do you think will happen if they rush it and break something else.
Be reasonable with your expectations.
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.
-
4 hours ago, sirkuz said:
It's not a "show stopper" issue. Backporting would be silly...wasted dev time IMHO. The fact that they acknowledged and fixed in next major rev makes me happy. I don't have anything configured for 6.7.x that prevented a downgrade and I doubt most do.
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?
-
1
-
1
-
-
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.
-
1 minute ago, johnnie.black said:
It's me who suspects both issues are related, don't know what Tom thinks about that.
OK. Fair enough. I'll blame you 😉
-
1
-
-
35 minutes ago, Marshalleq said:
Well said. Though you get what you pay for. Unraid is pretty cheap really. I run servers and things on mine, but really Unraid is a long way off from being a mission critical type of setup. It's most definitely aimed at home installations.
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.
12 minutes ago, johnnie.black said:Just to add that while Tom mentioned they are trying to fix this issue for v6.8-rc1, I suppose that if it takes longer than expected, or if for example the SQL corruption issue is unrelated and fixed before this, I would expect they could release rc1 with this as a known issue.
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.
Parity Summary incorrect after pause
-
-
-
-
-
in Prereleases
Posted
Ah, ok, thanks. I'll have a look at the plugin as if it allows me to stop selected services and docker containers when doing the parity check it might be handy.
Thanks