[VU+ Solo2] Samba not starting

[duoduo]

Hi guys,

Since updating to 036 from 033 on both my solo2 and zero, Samba won't start on either. I have tried to stop ftp and nfs as suggested in another post but this doesn't make any difference.

Anyone else have the same issue or know how to fix please?

 

[Willmoore]

Mine wouldn't start and I had to FTP some files to etc/samba - see post 7 of this thread

http://www.world-of-satellite.com/showthread.php?47611-OpenViX-3-2-Release-thread

 

[duoduo]

Thank you for the reply, I tried that but still hasn't solved it buddy

 

[chaser]

Yeah. There seems to be an issue with the samba.conf file. I had 2 files in /etc/samba:

smb.conf-opkg 1,207 bytes
smb.conf 586 bytes

I just renamed smb.conf to smb.conf-user then renamed smb.conf-opkg to smb.conf and then I was able to start samba.

This basically did the same as detailed in the linked thread above.

 

[duoduo]

Excellent thank you so much, sorted...

 

[Tkr001]

Did you fresh flash 36? If not I suspect that's the cause of your problem and I would flash to prevent future problems.

 

[duoduo]

Yes I fresh flashed so it wasn't that. Strange one, as no one else has posted the same issue.

 

[chaser]

For me, this was definitely on a fresh flash of 36 with setting restore. However, I've just noticed that I have the same issue on one of my other boxes which is still running build 35 of vix, so I'm guessing this issue might have been dormant on my various systems since it was reported on the release thread.

 

[Willmoore]

I'm sure he did do a fresh flash as did I. I think the issue is due to doing a settings restore which was advised.

 

[chaser]

I think the issue is due to doing a settings restore

Indeed. Think we're all sorted now

 

[chaser]

Just a quick follow up...

As mentioned in a previous post, I noticed this problem on one of my boxes running Vix 35. I fixed the problem with that box still on 35, and then did a settings backup / couch flash 36 / settings restore, and samba was working perfectly when the box came back on line. For me anyway, the issue was almost certainly dormant and was nothing to do with the 35 to 36 update.