Guill.St-P

Members
  • Posts

    55
  • Joined

  • Last visited

Everything posted by Guill.St-P

  1. same problem for me; server is up for just 2 months any clue? edit: log file attached edit2: rebooted and log is back to 1% (for now) root@Alligator:~# du -sm /var/log/* 1 /var/log/Xorg.0.log 1 /var/log/Xorg.0.log.old 1 /var/log/apcupsd.events 1 /var/log/apcupsd.events.1 1 /var/log/apcupsd.events.2 1 /var/log/apcupsd.events.3 1 /var/log/apcupsd.events.4 0 /var/log/btmp 0 /var/log/cron 0 /var/log/debug 1 /var/log/diskinfo.log 1 /var/log/dmesg 1 /var/log/docker.log 0 /var/log/faillog 1 /var/log/fluxbox.log 1 /var/log/gitflash 1 /var/log/lastlog 0 /var/log/libvirt 1 /var/log/maillog 0 /var/log/messages 0 /var/log/nfsd 123 /var/log/nginx 0 /var/log/packages 1 /var/log/pkgtools 0 /var/log/plugins 0 /var/log/preclear.disk.log 0 /var/log/pwfail 0 /var/log/removed_packages 0 /var/log/removed_scripts 0 /var/log/removed_uninstall_scripts 1 /var/log/samba 0 /var/log/scripts 0 /var/log/secure 0 /var/log/setup 0 /var/log/spooler 0 /var/log/swtpm 1 /var/log/syslog 2 /var/log/syslog.1 4 /var/log/syslog.2 0 /var/log/vfio-pci 1 /var/log/wtmp root@Alligator:~# du -sm /var/log/sa/* du: cannot access '/var/log/sa/*': No such file or directory alligator-diagnostics-20210605-0952.zip
  2. No official fix for the GUI issue with intel graphics(https://forums.unraid.net/bug-reports/stable-releases/69-after-moving-to-69-local-gui-mode-not-working-r1326/)? Is an embedded fix planned? Or users should rely on Intel-GPU-TOP Plugin? Otherwise, it's all good, thanks for the work!
  3. I can confirm that Plex HW transcoding work with the command that get me GUI back.
  4. have you try to uninstall Intel-GPU-TOP Plugin and then run what I send you in my previous message?
  5. Great to know that it's now fixed for you too. I will also wait from an official fix from limetech. It was working without the plugin on 6.8; it should also work natively on 6.9
  6. This solution works for me!!!!!!!! Thanks a lot ich777 Can I do something to make this a permanent fix or I need to wait for an OS update? (not a big deal as I rarely need to reboot my server)
  7. Ok, thanks a lot! Will try tonight and report here
  8. Thanks for the suggestion. I will try it at home tonight. When you say "load the Intel module for your onboard graphics card" how do you do that exactly? For the second part, I can do that on the black screen with the flashing cursor? Which method I should try first? Is both of those method would be permanent fixes (i.e. do I need to repeat this procedure each time I restart my server?) Thanks for the help and sorry for all the questions!
  9. Thanks for the follow-up Squid No nvidia drivers for me. I have nerdpack. Disabling it did not fix the issue. NLS and me have a very similar CPU. He have i7-4771 and I have Xeon E3-1245 v3. Both are Haswell LGA1150 CPUs with Intel HD4600 integrated graphics. Can this be the source of the issue? Like the nvidia drivers seems to be...
  10. I don't think we need to create a new topic either... Update from this morning, server is still up and runnning, but still no GUI on the server itself. No more flashing cursor either now; just a black screen. Thanks to all the unraid team and community for the support! edit: 6.9.1 update did not fixed the problem
  11. Same thing for me. I can access the GUI from a network computer, but I have a black screen with the blinking curson direct on the server. I get a video output during loading (all the white text on the black background, but no login screen) NO VM Docker autostart is disabled Array autostart is disabled Safe mode +GUI give me the same result Here is my config (very modest): Gigabyte H97N-WIFI (with latest bios) Xeon E3-1245 v3 (using onboard graphics) 16 GiB DDR3 2 HDD for the array 1 HDD for the parity 1 SSD for caching See attached file for my log alligator-diagnostics-20210308-2022.zip
  12. Just a follow-up on my case, the test took about 4h to run and terminated fine. From memory, it use to be faster (like 30 minutes); but maybe my Plex Library got bigger since the last time I ran the test... I'm available to do some testing if needed!
  13. Thanks for the quick answer, I will start it tonight and let it run overnight!
  14. the extended test is stuck checking /mnt/user/appdata for 1+ hour without any disk activity... anyone have a clue why? I only have my docket folder in this share (plex and rtorrentvpn only) Thanks!
  15. My config is similar as the onw you propose and it's fine running a couple of Dockers (Plex and rutorrent) + 5-6 plugins (using 3 out of 12GB of ram)
  16. Solved the issue; that was a simple one! and thanks for the quick answer binhex
  17. Hi all, I'm having issues getting to the webui (the docker is starting fine) I attached my log file to this message I'm a novice user so don't be afraid to ask basic questions, I will not be offensed Should I use my usual user and password from PIA or the one listed as "PPTP/L2TP/SOCKS Username and Password"? Info on my network: Routeur: 192.168.2.1 Submask: 255.255.255.0 unraid: 192.168.2.166 mac firewall turned off should I play with proxy? not sure how... I get this message on chrome when I want to launch the webui : ERR_CONNECTION_REFUSED thank a lot to everybody! rtorrent log.rtf
  18. Yes I'm using the website login starting by p........... Is there a way to confirm I'm connected via the VPN? Thank you
  19. Hi all, I've been using this docker since a couple of days; great work binhex! I just want to confirm something with you guys: Using my app/website login info for PIA doesn't work in delugevpn (the webui won't load) However, using the "PPTP/L2TP/SOCKS Username and Password" works. What is the difference between those 2 login info? Does I'm doing the right thing? Thanks all!
  20. Resurrecting an old topic... I'm looking to buy a Tripp-Lite 1000 UPS; can anyone confirm it works fine to do a clean shutdown on unRAID?
  21. Thanks a lot! This solved my problem... I was just afraid of running this command because of the last sentence... now everything is back to normal!
  22. Hi all, I had the same problem this morning (can't mount disks). I changed the disk.cfg file for no autostart Now, I'm able to boot in the GUI with the array in maintenance mode Here is what I gen when I run the xfs_repair status command with -nv in the option field After that I proceeded to the disk repair by running again the xfs_repair status command with the option field blank and I got this error message... and I don't know what to do next... I need some help from you guys! thanks
  23. I just the manual update to unRAID 6.2 and the Plex update was then available and applied successfully Thanks everybody for the help!