Jump to content

FreeMan

Members
  • Content Count

    1219
  • Joined

  • Last visited

Community Reputation

50 Good

About FreeMan

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Location
    Indiana

Recent Profile Visitors

1379 profile views
  1. DO NOT CLICK FORMAT! Generate diagnostics (Tools -> Diagnostics) and attach the complete .zip file to your next post. DO NOT DO ANYTHING ELSE UNTIL YOU GET SOME ADVICE! Too many people have had tales of woe (data loss) from trying to fix things themselves when they're new to UNRAID. Just be patient, someone will help you. Also, provide some more detail: * Have you ever built parity or just not since you removed the drive? * Is the drive recognized by the mobo when it's plugged into an internal SATA port? * Is it recognized by UNRAID when it's plugged into an internal SATA port? * Why are you using a SATA -> USB adapter? What problem are you tying to solve with that?
  2. I ran into MCEs with my old server. The recommendations from here were that I contact the CPU & motherboard vendors to see if there was anything they could do/help with. I ended up having to replace the CPU. Not saying that's guaranteed to be your only course of action here, but bracing you for the worst. Wait for someone more knowledgeable to chime in, but you may want to at least start checking with your vendors.
  3. If you've got a SATA port to plug the SSD into, there should be no problem. You'll have a 2.5" device going into a spot where a 5.25" device is designed to go, though, so you'll need a mounting adapter. You can plan for expansion and get a 4 by 2.5" caddy that will fit in and give you room for 3 future SSD/laptop sized spinners, or you can get a 5.25" to 2.5" adapter to put just the single drive in there. Others have mounted SSDs just about anywhere in their cases using double sided tape or Velcro strips.
  4. Even if the router had lost power, the "warning" and "alert" notifications should have shown up in browser, but didn't. Any additional thoughts?
  5. Yes. Everything electronic in the house is. They have their own ups. Sent from my moto g(7) using Tapatalk
  6. I just had a brief power outage - it was 10-20 seconds. On my primary server (NAS), I got the "On UPS" and "Off UPS" alerts appearing in browser, but they did not appear via Pushover. On the backup server (Backup) I didn't get them in browser, nor did I get them via Pushover. I'm 100% certain that my Pushover connection is working - I get 4 notifications per day of array status from each server, plus speedtest plugin notifications every 2 hours. Additionally, just to be sure, I went to the Notification Agent settings on both machines and did a test. They both came through in a couple of seconds. Here is my primary server notification setup: And here is the backup server notification setup: I've also attached diagnostics for both machines. Any ideas why they're not showing up in-browser on one server and why they're not getting pushed to Pushover by either server? nas-diagnostics-20200510-1321.zip backup-diagnostics-20200510-1322.zip
  7. Thanks, @ken-ji. On my main server, cat known_hosts |grep backup yields "CTNPW0sjfvk=" as the last several characters. On the backup server, cat ssh_host_ecdsa_key.pub yields "yDxNTBhImms=" as the last several characters. Obviously something's changed somewhere. The date time stamps on the NAS-rsync-key* files and the authorized_keys files match between the main and backup servers. The math between now and my uptime report for the servers indicates that these were created very shortly after I rebooted the server (I believe it was for the 6.8.3 update), which makes sense since that's when I would have discovered that I couldn't connect again. Both machines are located in my house and on the same network. My son can VPN in and he is the only other person who knows the root pwd, but he's too busy with classes to be doing any messing around with the servers, and, frankly, is disappointingly uninterested in doing so (despite his CS major). I'm not concerned with regenerating the keys because I'm (as) certain (as I can reasonably be) that the server hasn't been messed with from the outside. There are zero port forwards to the backup server. There are a couple to the main server (looking at them again, I believe I can shut almost all down at this point). Any other thoughts on things to check before I create new key files? I will likely change the passwords on both servers to something longer and more complex, just to be on the safe side.
  8. Now it seems that something is changing on the servers to invalidate the keys each time the server(s) reboot. The contents of my main server's go file: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & cd /root/ mkdir .ssh/ chmod 700 .ssh/ cp /boot/config/ssh/NAS-rsync-key /root/.ssh/ #cp /boot/config/ssh/NAS-rsync-key.pub /root/.ssh/ cp /boot/config/ssh/known_hosts /root/.ssh/ cd /root/ chmod 700 .ssh/ #chmod 600 .ssh/NAS-rsync-key.pub chmod 644 .ssh/authorized_keys and the contents of my backup server's go file: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & cd /root/ mkdir .ssh/ chmod 700 .ssh/ cp /boot/config/ssh/NAS-rsync-key.pub /root/.ssh/ chmod 600 /root/.ssh/NAS-rsync-key.pub cp /boot/config/ssh/authorized_keys /root/.ssh/ chmod 600 /root/.ssh/authorized_keys On the main server, I don't copy over the .pub file (I don't need the public key there, do I?). My servers rebooted a couple of days ago after I updated to 6.8.3, and now I get an error @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ When I try any rsync command. I have to redo the keygen procedure to generate a new key pair to get it to work. Thoughts or tips? I have to r
  9. Glad to hear you got it working! Please edit your original post and add "[Solved]" to the post title so others know that there is a resolution to this issue. It will help keep them from reading a post trying to help, and it will help others with a disk problem in knowing where to look to find a possible solution.
  10. unBalance is a plug in that is designed to move your files from disk to disk with just a couple of button clicks. It's like using Krusader, but automated and eliminates the risk of data loss by accidentally moving from a user-share to a disk-share (or vice versa). The built in Mover only moves files from the cache drive to the array (or vice versa, depending on cache use settings).
  11. Thank you @squid - XML files restored and all dockers updated properly! I have also installed CA Backup, configured for a weekly backup, and clicked "backup now"! Great work as always!!
  12. Further update, @Squid: A) I misread the path in your original post. I stopped looking at ../config/plugins when I didn't see a directory for each of the dockers. 1) After rereading, I see that I'm supposed to continue on to ../dockerMan/templates_user B) Browsing to that directory from Windows, there are no files there at all, so I attempted to copy from my late-Jan flash backup. 1) Windows asked if I wanted to overwrite the files. 2) Not seeing any in Windows, I opened a shell to the server and changed to the directory. 3) I see 0-byte XML files for each of the 5 dockers, each with perms of 600 Obviously, the 0-byte files are not very helpful. Are the 600 permissions correct? If so, I'll restore my backups and chmod the perms to ensure they're correct. If that's not correct, what should they be?
  13. Ah! I do have a flash drive backup from when late Jan when I was having issues with this server. Simply copy the .../config/plugins/* files from the backup to the flash drive on the server and run the updates? Wow... looking at the backup, I just realized that all the configs for all my plugins are missing, too, not just the dockers. No, that's wrong - the plugin configs are there, just the Dockers are missing. Maybe I should put this off until after lunch to be sure I'm focused and can get it right the first time...
  14. Certainly not intentionally but there are no files there at all. Which, I suppose means that the other dockers will fail to update when an update is pushed out for them. When I click the icon in Docker view, I do not get "Edit" as a menu option - just "Update", "Start" and "Remove". I was thinking that I could go into "Edit" make a change, unmake the change, then hit "Apply" to get it to recreate the config files for me... Is the fix to uninstall & reinstall? I would think that, since there are no XML files there, that I'll have to reconfigure everything by hand? Wait! I do have CA-Backup running... No, no I don't. Considers foot thoroughly shot...
  15. Before anyone yells at me that this isn't the Docker support forum... I've got CA configured to automatically update all dockers and plugins daily. On one of my servers, I've got 3 docker containers that won't update. I'm running these 3 dockers on both of my servers and they've updated just fine on the other server so I know the issue isn't with the dockers themselves. Since there is no "general" Docker support thread, and no way to post a general question in the docker support forum, it's gotta go here... When I attempt to update them by hand, they all give me: The only thing I install by hand is the CA plugin itself. After that, everything is installed via CA, so the answer to that question is an unequivocal "YES"! Attached diagnostics for the server in error, along with a screen shot of the 3 dockers that won't update. backup-diagnostics-20200303-0857.zip