jaj08

Just worked for me on one of my instances, now to move on to my others.

Good to go, I had to modify the my.service file like Leifgg mentioned. Once I did that I can now access the GUI using your docker desktop app. This is perfect, thanks for the assistance.

I wasn't aware that a docker gui was now available. I would much rather not have a windows system managing the GUI. Is this included in the default install or do I need to do some searches to find this additional docker?

It seems that after a reboot I can no longer access Crashplan via the GUI to configure/monitor the status of what is going on. Has anyone else ran into this? It is real annoying, but I know the Crashplan server is functioning as my clients are backing up to it without issue. When I first noticed this problem it was early on. So I deleted my Crashplan docker and all configs for it. Sure enough rebooted and my Windows GUI once again would not communicate with it. So then I got Crashplan installed configured, and I let it run for about 3 weeks no issues, GUI remained responsive, and all seemed well. Then Unraid released the new beta so I prepared for another Reboot which I knew would kill it. Sure enough, unraid is updated, docker is running and accepting incoming backups, but my GUI client is still not able to connect to the server. On the Windows client side I have uninstalled and deleted all configs for Crashplan before installing again but it still never establishes its connection. I double checked the ui.properties file on my Windows PC and it remains configured with my unraid IP address. GUI Client continues to say it can't connect to the backup engine. I can't say this for sure as it has been a few weeks, but I'm fairly sure that when I specify reboot it, that means rebooting either unraid or my Windows PC would cause the client to never connect again. So it basically seems that I can only initialize the GUI client one time and it remains functional until its forced to reconnect at a later time.

Yes we purchased a Naked array from Lime and purchased all our drive from NewEgg....... Thanks for the response on the drive... I thought it looked OK, but another drive showed a lot less changes than this drive did so it just had me a little concerned. I really hate dealing with hard drives as I work for a small company (less than 100 employees) yet it seems like I'm always dealing with dead drives and often times its on brand new ones as well. Sometimes I think these company just gave up on making reliable drives and only care about the size these days. I'm dealing with a possible failing drive on my home unraid server as well..

My company just purchased one of Lime's MD1500 servers and I am trying to preclear all our new drives..... Could you please advise on if I should be concerned with the the below results.. I already have 1(of 5) drives that are confirmed dead via SMART reporting S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 58c58 < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 100 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 101 65c65 < 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 --- > 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 ============================================================================ root@unraid:/boot#