lucid finch
So I edited this document to enable samba share as the ubuntu guide said to put a load of stuff at the bottom of a very long doc
My samba share stopped working so I go
sudo editor /etc/samba/SMB.conf
The document looks totally different
CasaOS
Huge writing saying
do not modify
A disclaimer from CasaOS
Then a lot of fruit stuff about file rights stuff with mostly yes as the answer
Why has this changed so much?
lucid finch
Hi @nova charm me again
What's with the above and the /etc/samba/SMB.casao.conf file now running samba?
nova charm
This part is done by @vital vortex
vital vortex
i am coming
@lucid finch Can you talk about your environment first, such as system and system version, casaos version, and problems encountered
lucid finch
Sure @vital vortex thanks for your help
It's an old pc and it's running Ubuntu 22.04.1 LTS jammy jellyfish
As stock on minimal install (I do have ACPI boot error r/Ubuntu said don't worry about them)
CasaOS is v 0.3.7 but most of my time and issues were on the previous
I had everything working and nearing the end of my set up then a power cut screwed my stuff up, I managed to pull the data off the HDD then repair it then transfer the data back to it. There is a help page called 'containers won't start' by me for a step by step of situation
I'm going to fresh install Ubuntu as there are a lot crap left over from me experimenting and cuz I still can't get samba to work again
What I'm thinking is that as I had left the machine running almost non stop and had set up samba with the ubuntu way, then when I turned off the machine and on again the next day, CasaOS changed the config files and things went wrong
TLDR and sanity check for me
On my next fresh install reboot pc after installing CasaOS and then set up SMB after. Hopefully straight into /ect/samba/SMB.caso.conf file
I hope that makes sense and doesn't sound like a crazy person
runic thicketBOT
GG @lucid finch, you just advanced to level 6!
lucid finch
I just checked the time line I had got these files swapped over and working before the power cut
lucid finch
Point of clarification I can access my Nvidia shield from ubuntu fine, I cannot point anything on my shield to the hdd or ubuntu
At /media/myubuntuuser
My getting multiple WD_RED 6TB
1 2
lucid finch
Hey @vital vortex think I might of fixed this
Dead simple really; I just needed to bang a 2 on the end of the paths in CasaOS.conf file
It's still a mystery how and why this changed from the 1 I put after the power cut but it's a win.
vital vortex
Okay, let me tell you about the working mechanism of casaos and smb.
When casaos is installed and updated, if the user has smb installed and working, then smb will backup the lost configuration file and update it to be taken over by casaos. If you want to revert, you just need to revert the backup configuration file. If your problem has been solved please send me a clear reply, thanks!
random ferry
I can see the SMB share file, but when I use my android phone to access the folder, it said access deny. I use the userid which is configed in SMB.
vital vortex
casaos now only supports guest users, you can try
random ferry
Thanks. However, when I use anonymouse login, it reports the same error. Any hints?
nova kernel
Hi. can anyone help me with casaos smb?