August 28, 201312 yr Hi I cannot connect to my unraid server anymore, I can use a browser and see the tower GUI, so I know the server is up and running I upgraded to version: 5.0-rc16c 4 days ago and installed the PLEX server and everything was working, today I tried to install simple features when I did that I lost connection to the server, so I have I removed simple feateres and PLEX but I still can't connect to the server I really hope one of you can help we BEST Regards Michael syslog.txt
August 28, 201312 yr When you say can't connect, do you mean you can't connect to your shares? Can you get to the main web interface ok?
August 28, 201312 yr Author Hi snowboardjoe Exactly I can see the web interface but when I what to connect to my shares I can't, I have tried 2 different windows PC and a android tablet with no luck. BR Michael
August 28, 201312 yr The syslog you have is only 7 seconds long. Did you maybe copy the tail by mistake? Also, in the interest of continued troubleshooting, can you telnet into the server and verify the existence of /mnt/user?
August 28, 201312 yr Can you try downloading his syslog again? My copy is fine, 97614 bytes. Chewie, your flash drive is corrupted, causing your server to have problems reading and writing to /boot. Take it to a Windows machine and Check Disk it. Make sure you use the 'Safely Remove Hardware' tool.
August 28, 201312 yr Tried it every which way, can only get 7 seconds, 20:37:10 to 20:37:17. Same byte size... I actually started getting a similar error to that in my syslog though, the FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. part anyway...is that something one should look for in the logs you think?
August 28, 201312 yr In the past I would always have given you the same advice, about using Check Disk. But I've discovered that some users now have that single line only, with evidence of VMware use (I think it was VMware) in their system, and it appears to be harmless. I have no idea what is causing it. In his syslog, he has multiple lines about the FAT corruption, with one declaring that the system was setting the flash drive to be read-only for that session. I do see what you mean about it being apparently only 7 seconds long. I have found that when a Linux system boots, the clock does not seem to be running for the logger until all setup is finished, about the time the UnRAID module begins work. So all of the logged messages prior to that get the same clock time, in this case "Aug 28 20:37:10". A bit misleading... My own supposition is that while logging begins immediately on boot (because even the first modules have to be able to log any issues), storage and file system support are not ready yet. So it buffers everything until system setup is essentially complete, and then dumps it all to the syslog.
August 28, 201312 yr Author Hi That did the trick, I can now access my shares again, check disc did the trick. You guys are AWESOME thank you VERY much
Archived
This topic is now archived and is closed to further replies.