BAlGaInTl Posted March 12, 2021 Share Posted March 12, 2021 (edited) I recently upgraded to 6.9.0, and I thought everything went fine. Today I rebooted my windows system, and it said it couldn't reconnect to my user shares. These are the ones that I had specifically set up for different user accounts. All of the other regular shares for media and such are there. I've tried rebooting, but no luck. I can see that the disks are there with no errors. I can also see that the files are still there. What would make the "user" shares disappear? Edited March 15, 2021 by BAlGaInTl solved Quote Link to comment
ChatNoir Posted March 12, 2021 Share Posted March 12, 2021 Please share your diagnostics in your next post. (Tools/Diagnostics) Quote Link to comment
BAlGaInTl Posted March 12, 2021 Author Share Posted March 12, 2021 The diagnostics are attached. The shares used to be visible at //dmitri/user/ What was once the "user" share was segregated from my other shares and was on Disk 3/4 only. Like I said... I can still see the data physically on the disk, but the share is gone. None of my applications or media touch those two drives. All of that stuff is working as normal. Any help/insight is appreciated. Thanks. dmitri-diagnostics-20210312-0700.zip Quote Link to comment
Squid Posted March 12, 2021 Share Posted March 12, 2021 shareReadList="" shareWriteList="..." That share has no authorized users to read it. Try setting up the user permissions again in the share (Toggle something off / on if necessary) Quote Link to comment
BAlGaInTl Posted March 12, 2021 Author Share Posted March 12, 2021 9 hours ago, Squid said: shareReadList="" shareWriteList="..." That share has no authorized users to read it. Try setting up the user permissions again in the share (Toggle something off / on if necessary) I guess that's the problem... there is no share listed for it. There's no place for me to set permissions. I don't know where it could have gone. Maybe I'm missing something. Quote Link to comment
Squid Posted March 12, 2021 Share Posted March 12, 2021 46 minutes ago, BAlGaInTl said: there is no share listed for it. What does that mean? Quote Link to comment
BAlGaInTl Posted March 13, 2021 Author Share Posted March 13, 2021 1 hour ago, Squid said: What does that mean? It just doesn't seem to exist in my shares. I know it was set up, because I have //server/user mapped on multiple computers here in my house and they all stopped working. This is what I see on my shares now: Media is the main share where I have movies tv home videos etc. The share "user" used to be there I think... It used two separate physical disks from the rest of the shares. It worked for so long without issue, I don't even remember how I had it set up. The two disks are still there... I can still browse the physical disks and see the files. I just can't connect by SMB, and and all my network mappings broke. Can a share named "user" just be recreated using Disk 3,4 and it will go back to working? I'm just perplexed as to how it just disappeared in the first place. There seems to be config files pointing to it in diagnostics, but it seems to be gone from any unraid menu. Quote Link to comment
Squid Posted March 13, 2021 Share Posted March 13, 2021 Reason is this (when I try and add a "user" share) From the command prompt, you need to rename the share to some else: cd /mnt/user mv user my_users Quote Link to comment
BAlGaInTl Posted March 13, 2021 Author Share Posted March 13, 2021 I guess I'm confused. Is that a change introduced in 6.9.0? I've been running it this way for a couple years. I can certainly try that tomorrow. Quote Link to comment
Squid Posted March 13, 2021 Share Posted March 13, 2021 Yeah, because of the introduction of cache pools, certain things had to be banned from being a share name. Quote Link to comment
ElectricBadger Posted March 14, 2021 Share Posted March 14, 2021 Is there a list of banned share names anywhere? I'd like to check mine are OK before I hit the update button 😁 Quote Link to comment
Squid Posted March 14, 2021 Share Posted March 14, 2021 3 hours ago, ElectricBadger said: Is there a list of banned share names anywhere? I'd like to check mine are OK before I hit the update button 😁 reservedNames="parity,parity2,parity3,diskP,diskQ,diskR,disk,disks,flash,boot,user,user0,dev,disk0,disk1,disk2,disk3,disk4,disk5,disk6,disk7,disk8,disk9,disk10,disk11,disk12,disk13,disk14,disk15,disk16,disk17,disk18,disk19,disk20,disk21,disk22,disk23,disk24,disk25,disk26,disk27,disk28,disk29,disk30,disk31" Along with any of the following within the share name : \ / * < > | " ? Or the same name as any of your cache pools 1 Quote Link to comment
BAlGaInTl Posted March 15, 2021 Author Share Posted March 15, 2021 On 3/12/2021 at 8:53 PM, Squid said: Reason is this (when I try and add a "user" share) From the command prompt, you need to rename the share to some else: cd /mnt/user mv user my_users So renaming the share worked and everything showed up. I just had to give users permission to that share again. It seems like the upgrade script should check to see if that's an issue before the upgrade. Either way, thank you for the help on getting this fixed. I was racking my brain. Thanks. Quote Link to comment
Fiservedpi Posted March 21, 2021 Share Posted March 21, 2021 @Squid when I try to rename my “disks” share that I made a while back I’m getting “resources in use” error do you know how I can stop the “resources” so I can get it renamed. Quote Link to comment
Squid Posted March 21, 2021 Share Posted March 21, 2021 /mnt/disks is anything you've mounted via Unassigned Devices, and is perfectly fine. We're talking about stuff within /mnt/user Quote Link to comment
Fiservedpi Posted March 21, 2021 Share Posted March 21, 2021 Ok so unnasigned is excempt got it I got the warning in common problems but it doesn’t apply since it’s an unnasigned share. Quote Link to comment
Squid Posted March 21, 2021 Share Posted March 21, 2021 FCP is only checking for whats in /mnt/user, so you've got a share in there that's disallowed $reservedNames = ["parity","parity2","parity3","diskP","diskQ","diskR","disk","disks","flash","boot","user","user0","dev","disk0","disk1","disk2","disk3","disk4","disk5","disk6","disk7","disk8","disk9","disk10","disk11","disk12","disk13","disk14","disk15","disk16","disk17","disk18","disk19","disk20","disk21","disk22","disk23","disk24","disk25","disk26","disk27","disk28","disk29","disk30","disk31"]; 1 Quote Link to comment
smashingtool Posted March 28, 2021 Share Posted March 28, 2021 (edited) This issue is biting me now and the fixes above have not worked. After a reboot the share gets recreated every time. I'm completely locked out of SMB access again after it was sorta working before one of the reboots... I never saw "disks" as a share in the gui, but I did see the folder in the root of one of my disk shares. I also saw a disks.cfg file in my flash drive somewhere, do i need to delete that (or NOT delete that)? Edited March 28, 2021 by smashingtool Quote Link to comment
Squid Posted March 28, 2021 Share Posted March 28, 2021 You have a docker container that is referencing /mnt/user/disks You should be able to see that on the docker page and hitting the caret to expand any of the path mappings. 1 Quote Link to comment
smashingtool Posted March 28, 2021 Share Posted March 28, 2021 (edited) 36 minutes ago, Squid said: You have a docker container that is referencing /mnt/user/disks You should be able to see that on the docker page and hitting the caret to expand any of the path mappings. Hmm, I have several mappings to /mnt/disks, but i don't see anything to /mnt/user/disks... Oof, yeah, you're kinda right but in a different way. I do the following mappings with my dupeguru containers: /storage/disks <> /mnt/disks /storage <> /mnt/user I've always done that for the purpose of simpler file browsing in there, but that must be what is actually making the linkage Anyway, you're my hero, ill clean this up and that should fix it... Edit: Yep, all fixed. Thank you! Edited March 28, 2021 by smashingtool Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.