September 27, 201312 yr EDIT/UPDATE: Annnnd a chkdsk repair worked and I'm back up and in action. Many thanks to jonathanm. Cheers! Greetings, I have had a stable unRAID server on build 4.5.6 for many years now. This morning when I turned on the unRAID tower I was unable to access the file share through the typical \\tower or even the IP at \\192.168.1.101. The server is booting up fully and I can access the web console. It says everything has started and does not report any issues ("Started - Configuration Valid"). From the same computer, I can ping tower and its IP address, but am not able to access any file shares (nothing at the network location). All other computers on my network see the same issue. I do not know of any changes to the hardware or the software overnight that would explain this behavior. I was able to telnet into the server to attempt to get a syslog to post here, but received the following error: root@Tower:~# cp /var/log/syslog /boot/syslog.txt cp: cannot create regular file `/boot/syslog.txt': Read-only file system Is my Lexar Firefly USB drive causing an issue here? If it won't let me make the log file, I wonder if it's dying, being seen as read-only, etc, and is otherwise causing a problem. Any suggestions on how to further diagnose the issue or has anyone seen anything like this before? Thanks in advance for your input.
September 27, 201312 yr Author Annnnd a chkdsk repair worked and I'm back up and in action. Many thanks to jonathanm. Cheers!
Archived
This topic is now archived and is closed to further replies.