• Posts

  • Joined

  • Last visited

Everything posted by scubanarc

  1. Don't we all! I think that you should focus on hardware. Unraid is a very stable operating system. If you are crashing every few days then there is (more than likely) something wrong with your hardware. I'd start with memtest86+ for a few days. This is never an easy problem to solve. If that passes, then try running with very few HDD (or, if possible, no HDD) for a few days and see if you are stable. There's usually something.
  2. I rebooted in safe mode and it helped, the root permissions stayed 755. Then I rebooted back to normal mode and the root permissions broke to 775 again. I'm running the following plugins: Community Applications Intel GPU TOP Nerd Tools ProFTPd 1.3.6 (Plugin Version: 2020.03.10.1) User Scripts zabbix_agent Nerd Tools (Nerd Pack) enabled packages: - ncurses-terminfo-6.1.20191130-x86_64-1.txz - tmux-3.1.0-x86_64-1.txz User scripts: - Just a simple delete script, does this: #!/bin/bash find /mnt/user/camera/ -mtime +44 -type f -exec rm {} \; find /mnt/user/camera/ -empty -type d -delete Anything look suspicious?
  3. Unraid 6.9.1 I'm not 100% what is going on here, but it seems that when I reboot I lose the ability to SSH with a keyfile. This is not about passwordless keyfiles, but about all keyfiles. I understand the /root/.ssh symlink and I know how to login with keyfiles. However, after a reboot they do not work anymore, and the error in /var/log/syslog is: Authentication refused: bad ownership or modes for directory / If I run "ls /" then I can see that the / filesystem is 775 (group has write). The solution for me is: chmod 755 / (group does not have write) Then my SSH keys work again. Is this normal Unraid behavior or do I have something doing this to me?
  4. I installed the 'Intel GPU TOP' pluggin and it went fine. Then I rebooted, chose GUI mode, and after a bit of normal looking boot scroll I got the blinking cursor. It's not frozen, I can still SSH in to it, but the GUI never lights up. Any other suggestions?
  5. No I have not done that, and I wasn't aware that I needed to. Thank you very much for the suggestion, I will try it and let you all know.
  6. I still have no progress on this. I've tried everything I can think of. Why I try to boot GUI mode, no matter what all I can get is a blinking cursor on a black screen. The only video card I have is the onboard intel in the CPU.
  7. I think that I'm in a similar boat as you, except I don't have a video card added, I'm just trying to boot the onboard. I have 2 suggestions for you (although neither worked for me): 1 - Disable UEFI and see if it works (in other words, do a traditional BIOS boot): 2 - Try the nomodeset trick:
  8. 6.9.1 I'm having the exact same problem as this post: UNABLE TO BOOT INTO GUI MODE Everything works fine except GUI mode. I can boot normally into console mode, and I can ssh in no problem. But when I choose "Boot GUI" I get the boot log as usual, then the screen goes blank and I get a blinking cursor at the top-left corner of my screen. I've tried the "nomodeset" fix and it didn't help. I bet if I could disable UEFI mode it would work fine, since that seems to have fixed it for others. HOWEVER... my motherboard is an ASRock J4105M and it does not have a traditional BIOS. It only has UEFI according to tech support. Even if I disable "Fast Boot" mode it still boots UEFI. As far as I can tell there is no way to disable UEFI and boot traditional BIOS. And it appears that I need traditional BIOS to make GUI mode work. Are there any other workarounds that I can pursue to get GUI mode to work?
  9. Thank you so much! This works perfectly on 6.9.0 with an intel x64 cpu. The template was a nice touch. I agree with everyone in here that Zabbix Agent 2 is necessary since so many people use their unraid servers as a docker host. @fabianonline, any chance we'll get agent 2 in the near future?
  10. I'm upgrading my cache driver to a larger size, and I'm following this guide: Which uses the mover to clear out your cache drive before the swap. After step 4, I check the cache drive to see if it is empty. It's mostly empty, except for all of the symlinks in: /mnt/cache/appdata/binhex-plex/Plex Media Server/Metadata It seems that the mover cannot move these. To save them I used ssh and moved them with the mv command to a safe spot, and I'll move them back after the update. I wish I had just moved the files manually to start with. Now I have a split pair of directories to move back to the new cache drive.
  11. Maybe related... mine got a new MAC address after the update. I think it is related to the network bond picking a different NIC. Not sure. Anyway, it took some arp cache flushes and settings in my DHCP server to get back to talking. I only figured it out because I got an alert that a new device joined my network, and it had the same name as my missing server.