Bossman

Running V4.7 Pro Pentium class machine with Promise Sata 300 TX 4 controller, locking cables and likely 1 GB of ram. 8 drives installed. Seagate and WD 500 GB or 1 TB. Leading up to this problem, the system had been hanging. It would reply to pings, but not to telnet or web access and the shares were unavailable at this time. A reboot fixed the issue and everything was accessible but the problem would repeat. We had this exact issue with another system that came and went without intervention other than constant reboots for 4 weeks or so. to this day the other system is fine. Parity checks are fine. Both systems are on large high end UPS's with other servers. On this system the shares are no longer available. The exact message when you try to access a share is as follows: "\\unraidrack81 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The Server service is not started" User shares are enabled and security is set to simple. There is no difference when accessing by name or by IP address. The error is seen from multiple machines but not end with "The Server service is not started" I hope I have enough of the system log attached. I'm using a windows telnet and I don't think I have it all. Any suggestions are appreciated. stoage_server_logs.txt

Thanks for a great thread! Not as clean as I hoped, but I got things working. I would have had no luck without this thread. I did have one snag. When I used this in my go file I had problems. # Start Rsync installpkg /boot/packages/rsync/rsync-2.6.6-i486-1.tgz /boot/packages/rsync/rc.d/S20-init.rsyncd The Error: line 10: syntax error: unexpected end of file. This is what my S20-init.rysncd file looks like: if ! grep ^rsync /etc/inetd.conf > /dev/null ; then cat <<-EOF >> /etc/inetd.conf rsync stream tcp nowait root /usr/sbin/tcpd /usr/bin/rsync --daemon EOF read PID < /var/run/inetd.pid kill -1 ${PID} fi cp /boot/packages/rsync/rsyncd.conf /etc/rsyncd.conf If I add #!/bin/bash at the beginning I get "Bad interpreter" as the error. I changed my GO to the following and everything seems to work. I found the info here: http://lime-technology.com/wordpress/?page_id=34 installpkg /boot/packages/rsync/rsync-2.6.6-i486-1.tgz rsync --daemon --config=/boot/packages/rsync/rsyncd.conf I'm not sure if I've crippled things or not, but the various steps provided in this post got me to the point where testing and now backing up was something I could do.

Another feature that would be an amazing addition to the GUI

This is all really great stuff guys. Now Tom just needs to stick it in his code and GUI for all of us that are *nix challenged.

With this in mind, could the future hold some sort of "shadowcopy" scheme where the UnRAID system could help protect my users from their own stupidity? That and GUI based Rsync could my my like sort of " Utipian like"