September 15, 200916 yr I seem to be having a pretty common problem, I can't connect to my server. The web interface works fine. I tried a different NIC. I even tried a fresh install of unraid on just my parity drive so I wouldn't risk messing up anything on my data drives, and it worked fine. So I'm confident it's not a hardware problem. I also tried the chckdsk on my flash drive and it didn't turn up any errors. I'm pretty sure it's some kind of a samba issue. I tried to check the samba logs as suggested on another post. It told me permission denied. At the end of startup it displays smbd: no process killed. It then repeats it in the login line. I'm attaching my syslog. I'd obviously like to fix it. If I can't could I start with a fresh unraid install. Maybe just loose my user shares. I would be a pain to have to start over with just the disk shares but better than loosing everything. Any suggestions would be appreciated.
September 15, 200916 yr I seem to be having a pretty common problem, I can't connect to my server. The web interface works fine. I tried a different NIC. I even tried a fresh install of unraid on just my parity drive so I wouldn't risk messing up anything on my data drives, and it worked fine. So I'm confident it's not a hardware problem. I also tried the chckdsk on my flash drive and it didn't turn up any errors. I'm pretty sure it's some kind of a samba issue. I tried to check the samba logs as suggested on another post. It told me permission denied. At the end of startup it displays smbd: no process killed. It then repeats it in the login line. I'm attaching my syslog. I'd obviously like to fix it. If I can't could I start with a fresh unraid install. Maybe just loose my user shares. I would be a pain to have to start over with just the disk shares but better than loosing everything. Any suggestions would be appreciated. You can't see the shares from what OS? Windows? or a MAC? or a media player? You state the web-interface works... That is a huge first step. The LAN shares use an entirely different protocol... as you know... Is the "Workgroup" name set to the same name as the others on your LAN? Do you have a firewall on the PC blocking access? What do you see with the following two commands? (entered at the command prompt, after logging onto the unRAID server) smbstatus testparm To stop and re-start start the samba process manually (and possibly see any error messages) type: killall smbd nmbd /usr/sbin/smbd -D /usr/sbin/nmbd -D Once the shares are made available, it is the job of the MASTER BROWSER on your LAN to track the available shares. It is usually one of the PCs on your LAN as described in this Microsoft document: http://support.microsoft.com/kb/188001 It is possible for unRAID to volunteer to be the MASTER BROWSER if you set "Local Master" to "Yes" on your settings page. Joe L.
September 15, 200916 yr Author smbstatus gives : /var/cache/samba/locking.tsb not initialised killall smbd numbed gives : smbd: no process killed. That's the same message I get at the end of boot up currently. Again leading me to a samba problem. testparm gives : Can't find include file /boot/config/smb-extra.conf processing section "[Flash]" "all other disks" Loaded services file OK Server role: ROLE_STANDALONE As far as connected systems I've got two Macs, two PC's running XP, one running Vista, and one running Win 7 RC. It's fairly complicated but had been working fine for a while. The Win 7 is recent as is the vista install. I hadn't been running ant-virus on the vista HTPC until recently. Is it possible that one of those systems took over the master browser role and isn't communicating properly, limiting my access to the Unraid server. I'd been running the same router for about 7 years and upgraded about a month ago to a netgear with wireless N. I started having drop outs about that time. I blamed the router, it seemed to affect all the systems. They'd just loose access for a little while. I tried a different router, that's when I finally lost all contact. I switched back to the netgear, but haven't been able to connect since. Is it possible that all the network problems corrupted some samba file that I can't see. I've used a few Linux distro's, but have a very limited knowledge of the command line so I've used up about all my tricks. I just set the Unraid to master in the online settings, and I've got one more firewall to check and make sure that port 138 is open. Hopefully I've given the masters enough info to give some more suggestions. This setup has been stable through quite a few upgrades, both hardware and software over about 2 years. This is the first problem I haven't been able to solve. Any help would be much appreciated I really need to get this back online again. Thanks
September 15, 200916 yr Author I'm back in business. I thought on a whim I'd install bubbaraid. I thought maybe it would at least give me some more info to help troubleshoot. Well I played around a little while, then I checked my network places and everything is there. I'm playing a movie off it right now. Why it worked I have no idea, but I'm happy none the less. For the future if anyone knows why it wasn't working please chime in. Obviously the sense of urgency is gone now, but any info would still be appreciated. Thanks for your help.
September 17, 200916 yr This looks similar to this thread, with the following lines common to both: Tower emhttp: shcmd (30): killall -HUP smbd Tower emhttp: _shcmd: shcmd (30): exit status: 1 Unfortunately, in that thread I blew the advice, when I confused the "killall -HUP" with some other command, don't even remember what. Both are using v4.5-beta6 and there are clearly some changes to the Samba usage with the new _shcmd function. I checked a number of recent syslogs and there also appears to be a difference in the logging of the start of Samba, sometimes it is and other times it is not. That makes it hard to diagnose problems with Samba startup. Perhaps a Linux expert can help out here? Are there other log files that might have relevant clues?
Archived
This topic is now archived and is closed to further replies.