Posts: 400
Joined: Jun 2015
I could use the smaller slower SD card with a clean install of OpenElec but if I'm going to troubleshoot with that I'd just re-install on the better SD card.
All I did was edit the samba.config.sample file to be a true config file with the added code to access the storage folder. Then suddenly it want's credentials that don't exist. No way to get into the config file to change/delete it.
Posts: 3,575
Joined: Mar 2011
Reputation:
194
2016-01-27, 21:50
(This post was last modified: 2016-01-27, 21:53 by trogggy.)
If you've nothing on the bigger card you're bothered about then by all means start from scratch. But it takes 5 minutes to write a fresh openelec to your second card, then boot it up and see if you have access.
If it works, moving anything you want from the existing card is straightforward.
If it doesn't - you still have the same problem as now, except you know it's not down to your settings on the pi. And you've not lost your existing data.
Edit: and if you've edited the samba.conf file as I described there's no way it can be affecting access. If you want to test that you can always re-name it on the pi in the kodi file manager (eg to oldsamba.conf - so it's ignored) and re-boot.
Posts: 400
Joined: Jun 2015
If this credentials issue isn't something that people with far more knowledge of openelec than I know something about then something has gone tits-up with the config file. And I'm betting it's not a file I can access directly on the card through a card reader. Bo-urns.
Posts: 3,575
Joined: Mar 2011
Reputation:
194
2016-01-27, 22:32
(This post was last modified: 2016-01-27, 22:34 by trogggy.)
If you think something's gone wrong with the config file then get rid of it.
Turn on your tv.
Pick up the remote.
Navigate to System > Appearance > File Lists.
Check 'show hidden files'.
Open the file manager in kodi.
Click 'add source', navigate to 'root filesystem' and add it as a source.
Now go into that source... root > storage > .config > samba.conf.
Use the context menu to re-name or delete that file.
Reboot.
Edit: and 99.9999% it won't make any difference.
Posts: 400
Joined: Jun 2015
(2016-01-27, 22:32)trogggy Wrote: If you think something's gone wrong with the config file then get rid of it.
Turn on your tv.
Pick up the remote.
Navigate to System > Appearance > File Lists.
Check 'show hidden files'.
Open the file manager in kodi.
Click 'add source', navigate to 'root filesystem' and add it as a source.
Now go into that source... root > storage > .config > samba.conf.
Use the context menu to re-name or delete that file.
Reboot.
Edit: and 99.9999% it won't make any difference.
Thanks for the info on how to delete the config file within Kodi. Why don't you believe it will make a difference? Pi went from no credentials to instant credentials when rebooting after adding the config in the first place after a number of reboots without the need for credentials prior. It's the only thing that changed between working and not..
Posts: 400
Joined: Jun 2015
I'm confused. You said removing the config file won't make a difference but then said if the change in behavior happened immediately after adding it then there is something wrong with it. That's what I believe, the config file is doing something to mess things up and that's why I want to remove it if possible. It's the second time this credentials issue has popped up when I've edited the config file with the noted code to allow access to the storage folders.
Posts: 3,575
Joined: Mar 2011
Reputation:
194
That's okay, I'm confused too!
Obviously if the credentials issue appeared as soon as the samba.conf file was added then it looks like a likely culprit. It's just that there's nothing in it that should cause a problem (if the file is correct).
I would try:
1. Re-name samba.conf to oldsamba.conf, re-boot, see if the problem's gone.
2. If not, write a new openelec to your second sd card, see if the problem's gone.
3. If not, start looking outside the pi for the problem.
Do you still have ssh access (eg putty)?
If you can't connect to the pi via windows explorer (smb) you could try using winSCP or similar.
Posts: 400
Joined: Jun 2015
LOL I knew you were the crazy one, not I!!!
I figured it out. The samba.conf file was actually empty for some unknown reason. So it was causing an error. I used your tip to delete it through Kodi on the Pi and now it's all back working. Corrected the issue with no content and now have full access to the storage folder. Thanks again for pointing me in the right direction, even if we both ended up lost.
Posts: 3,575
Joined: Mar 2011
Reputation:
194
How the heck did you manage to do that?
Putting a blank samba.conf file in place sounds like a good way to cock up smb access.
As I said...
' if you've edited the samba.conf file as I described there's no way it can be affecting access.'
And 'If you saw a change in behaviour as soon as you added the new file it suggests there's something wrong with it.'
Sounds about right, no?
Good that it's working anyway. And if you can see the whole storage folder in windows explorer you've obviously done the samba.conf correctly this time.
Posts: 400
Joined: Jun 2015
No idea what happened. The file was 0kb in size. It was the issue, whatever was wrong with it. All fixed now. Lesson learned for next time I forget how to do these things.
Posts: 400
Joined: Jun 2015
Going to bump my thread to ask what log and what in the log I need to look for to find out why a Pi2 will continue to crash and reboot at random moments when executing a CinemaVision sequence. I don't have hours and hours to collect logs and figure out ways to post the massive things then weeks to wait for answers if/when someone has the time to help out. Better to go in with some knowledge then continue to flounder in the open sea.
