-
Posts
10185 -
Joined
-
Last visited
-
Days Won
196
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by limetech
-
-
Fixed in 6.11.1
-
Changed Status to Retest
-
Fix put into 6.11.1
-
1
-
-
Changed Status to Solved
-
Changed Status to Retest
-
This has been incorporated into Unraid OS 6.11.1 release, but does need a manual xml edit:
-
1
-
-
17 minutes ago, D.Romeleitis said:
With 6.11 you get an invalid user/password error.
This is reported by windows when trying to connect?
In Unraid OS 6.10 (and all Unraid OS releases I think) it's not possible to set a user name of the form "[email protected]".
-
8 minutes ago, D.Romeleitis said:
The problem with permitting access to shares occurs when your username is your email address. With Windows you normally login with your (Microsoft) email address. Since 6.11 this is a problem.
Please elaborate.
-
1 hour ago, onyxdrew said:
I tried this NTML and the above SMB version setup. I tried each by themselves, and together, nothing made any difference... my user with an @ sign don't work, I still get prompted to log in by windows whne accessing share. If I type in my user without na @ in the username, it works, even if I type the @ user/pass out it does not work. This is how I'm supposed to enter those right?+
Change
#ntlm_auth = Yes
to
ntlm_auth = Yes
The # character means it's a comment.
What do you mean by "my user with an @ sign"?
-
11 hours ago, wgstarks said:
I see that there aren't any global or share name tags so I may be getting confused by what I've read on smb.org. Are those tags not required at all here?
The options specified in /etc/samba/smb.conf and config/smb-extra.conf are all put into the [global] section.
The options specified in /etc/samba/smb-fruit.conf or config/smb-fruit.conf are added to each share. You don't have to specify any sections.
-
1
-
-
11 hours ago, wgstarks said:
Would still like to know if I should delete my current settings from smb-extra though.
Yes
-
1
-
-
38 minutes ago, wgstarks said:
What would be the recommended way to apply the fruit settings to every share? Do I need to add every share to smb-fruit.conf?
If config/smb-fruit.conf exists then it is added to the settings for every share automatically, else the contents of /etc/samba/smb-fruit.conf is added to every share automatically.
You can examine after array Started with this command:
testparm -sv
In upcoming 6.11.1 the 'flash' share is omitted from this treatment, instead the 'fruit' settings for that share are fixed - this is because the USB flash using vfat filesystem.
-
For those with macOS issues - please do not put anything related to "fruit" settings in config/smb-extra.conf.
That file will set "global settings" and the fruit stuff needs to be per-share. Only create/modify config/smb-fruit.conf if you want to experiment with non-default settings.
Also, please set your 'flash' export setting to No if running 6.11.0 or earlier. Once 6.11.1 is published you should be able to re-export 'flash' share if you want (though not recommended).
-
For those with macOS issues - please do not put anything related to "fruit" settings in config/smb-extra.conf.
That file will set "global settings" and the fruit stuff needs to be per-share. Only create/modify config/smb-fruit.conf if you want to experiment with non-default settings.
Also, please set your 'flash' export setting to No if running 6.11.0 or earlier. Once 6.11.1 is published you should be able to re-export 'flash' share if you want (though not recommended).
-
Add this to "Settings/SMB/SMB Extras/Samba extra configuration"
ntlm auth = Yes
Please report back if this solves connectivity issues.
-
For those still stuck, add this to "Settings/SMB/SMB Extras/Samba extra configuration"
ntlm auth = Yes
Please report back if this solves connectivity issues.
-
You need to copy all the bz* files, including the .sha256 files from a release to the root of your flash boot device. Also should copy the file 'changes.txt' since some plugins look at that to determine release version.
-
Bottom of this post says fixed in kernel 5.19.11
https://forum.archlinux.de/d/34561-video-probleme-mit-5191-arch2-1/3
Unraid 6.11.1 is using 5.19.12 kernel.
-
2
-
-
On 9/24/2022 at 9:02 PM, JaredC01 said:
Just wanted to say that I've also got this issue on the full release of 6.11. Currently running 2x Toshiba 2TB Enterprise drives from eBay (per their info, sample drives), and only one is showing up after a reboot. Likely not one of the bigger issues for most, but I'll have to downgrade. Same message in the system logs:
Sep 24 22:45:52 Home kernel: nvme nvme1: globally duplicate IDs for nsid 1
Sep 24 22:45:52 Home kernel: nvme nvme1: VID:DID 1179:0119 model:TOSHIBA CONTROLLER MODEL NUMBER SAMPLE firmware:1CZA6064
Device info from lspci:
05:00.0 Non-Volatile memory controller [0108]: Toshiba Corporation Device [1179:0119]
06:00.0 Non-Volatile memory controller [0108]: Toshiba Corporation Device [1179:0119]Just happened to see this. Added quirk for that device but realize we have no way of testing and can't guarantee proper operation.
-
Changed Status to Solved
-
Just to be sure, please try a 'safe mode' boot in 6.11 and verify your nvme devices still don't show up.
-
Are all these reports only applicable to Time Machine backup operations?
-
Nothing changed in this area of the code, but really need diagnostics in order to tell what's happening. i believe our diagnostic gathering script will anonymize commands in 'go' to fetch the keyfile but you could verify this first.
-
On 9/25/2022 at 10:02 AM, howyoulikethat said:
My question is what does the "Permit Reformat" checkbox next to it do? There is zero documentation on that.
Checking this will let array Start and all devices which cannot be luksOpen'ed will appear as 'Unformatted' where you could then Reformat. Of course you would only do this for devices that you know do not contain data you need.
[6.11.0] domain.cfg written on every load of some GUI pages
in Stable Releases
Posted
Changed Status to Retest