Jump to content

savestheday

Members
  • Content Count

    305
  • Joined

  • Last visited

Community Reputation

0 Neutral

About savestheday

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Hi all! I have been having SMART errors with one of my drives (disk 11). I probably should have just replaced it straight away but I instead decided to upgrade a smaller empty drive (disk 7) and start copying the data over from disk 11 via unBALANCE. The reason I did it this way was I figured that if I got all of the data off, I could format disk 11 as XFS so that when I replaced the disk it would be in the correct format. Thinking back, I should have just replaced disk 11 leaving ReiserFS and then replaced disk 7 and done the copy and format. *sigh* unBALANCE was in the middle of the move from disk 11 to disk 7 last night, about 50% through, when the monthly Parity Sync kicked off. I am disappointed that I didn't even think of the monthly parity check when I started the unBALANCE move. This morning, I cannot access the web gui, cannot SSH into the box, and none of my dockers are accessible. I have IPMI so I am able to see that the server has not kernel panic'd. unBALANCE web gui is still accessible though not progressing in its file move. I cannot login to the server even via IPMI (see attached pic). At this point, should I just restart the server? Should I be concerned about any damage to the parity of the array? I should also mentioned that I excluded Drive 11 from all user shares before starting the process since I didnt want any data getting written to it during the move. The new replacement disk for disk 11 will be here today but I assume before anything, I will at the very least need to do a parity check before replacing the drive. Thank you!
  2. so this was working up until 6.3.2 but now I am getting: "Unable to monitor entire Dropbox folder hierarchy. Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem." again in the logs. My GO file is setup correctly and I have the /boot/config/sysctl.conf correctly set. Any ideas?
  3. So I hit another kernel panic this morning. I forgot to turn on the Fix Common Issues troubleshooting last night but I was able to capture a picture. Same scenario as I posted about in 6.3.0: CA Backup kicks off at 5 am from cache drive to /mnt/disk17 WebGui is unavailable SSH into unRAID (surprisingly) still works VM's remain working
  4. Ok, Docker was frozen this morning (not a big deal, it froze when I tried to force an update a container. This has happened before but the we gui becomes unresponsive). Server was still running and functioning. I went to reboot via "powerdown" and got the attached error message. I am guessing MD15 is drive 15? I never saw this message in 6.2.4. If I have to replace drive 15, it's not a huge deal I am just concerned that I never saw this in 6.2.4. http://imgur.com/a/KezW2
  5. Yup, the panic happened before you reset the system, so nothing is captured. Might be wise to put Fix Common Problems into troubleshooting mode and then wait until the next panic. If nothing happens within say a month, then reboot to stop the troubleshooting mode Thank you. I am going to turn this on tonight and see if the AppData job will cause another lockup/KP. You could hook up a monitor to the server and the Kernel panic info will be on the screen. Take a picture (actually, take a lot of pictures if youare suing a cellphone camera) and pick one one that is in focus, with no camera 'shake' and not flash reflection concealing the text. Post the picture... Yeah I should have done that this morning. I do have a monitor hooked up and will def take a pic if it happens again.
  6. Yup, the panic happened before you reset the system, so nothing is captured. Might be wise to put Fix Common Problems into troubleshooting mode and then wait until the next panic. If nothing happens within say a month, then reboot to stop the troubleshooting mode Thank you. I am going to turn this on tonight and see if the AppData job will cause another lockup/KP.
  7. Upgraded to 6.3.0 yesterday. I too had a kernel panic this morning - my first unRAID KP ever. I didn't get a chance to take to a picture of the screen but I believe it said ReiserFS was part of the trace. This kernel panic happened after CA plugin did its daily appdata backup at 5 am this morning. I only know this because I got the email that AppData backup started but did not get an email that it completed. I have attached the diagnostics ZIP tho I dont think this captures a Kernel Panic. Thank you! diagnostics-20170206-1005.zip
  8. This was an issue with experimental branch, but the master branch should be ok. Can you make sure you're on the newest image? If you're on the newest image, can you post the rest of your configuration so I can replicate? You can leave out the username/password. Thx for the quick reply! I will delete and re-create and see if that helps. I'll post the results!
  9. Using PIA with NZBGet after upgrading to 6.2.4 and it cannot resolve the VPN address. Other dockers with this PIA VPN are working. Anyone else seeing this? 2016-11-07 10:04:20,423 DEBG 'start-script' stdout output: Mon Nov 7 10:04:20 2016 RESOLVE: Cannot resolve host address: us-east.privateinternetaccess.com: Name or service not known
  10. Hi! Is there anyway that the Docker container can run this as part of its startup script? "Unable to monitor entire Dropbox folder hierarchy. Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem."
  11. Hi Pducharme, I changed it in the Docker settings.
  12. Hey all, So just an update on my Unifi issues: I changed the linking from /var/lib/unifi/data to /usr/lib/unifi/data and now everything works for me. I am on 5.0.7 now and I don't see an update for any new Docker.
  13. Update: ever since updating the docker to 5.0.7, the keystore is no longer recognized I think it's a Symlink issue The Docker maps to /var/lib/unifi which /usr/lib/unifi is symlinked to. It appears that the directories are totally different with what is mapped. Anyone seen an issue like this?
  14. Sure. docker exec -it UniFi /bin/bash cd /usr/lib/unifi rm keystore I was asked to confirm the removal. Once I restarted the Docker, the app data folder now had a full config (even tho I had not mapped that like I did previously). Btw, Ubiquiti has an article on how do this in a more official way (I used Keystore Explorer from a UBNT forum post) https://help.ubnt.com/hc/en-us/articles/212500127-UniFi-SSL-certificate-error-upon-opening-controller-page Forum post I used: https://community.ubnt.com/t5/UniFi-Wireless/Your-own-SSL-key-and-cert/td-p/285508