Ace319 Posted March 26 Share Posted March 26 tank-diagnostics-20240326-1525.zip Im at a loss guys. Unraid has been working amazingly well for years and after this last string up upgrades and having to upgrade a couple of drives ive been having so many issues. 1) I've recently upgraded to 2 refurb 12tb hdds which were swapped to be the 2 parity drives. Things were going reasonably okay and were running. At one point in the process 1 of the 12tb wasnt able to be located so I changed some wires around and it worked find. I had to change cases to support the additional drives so things werent just hanging out on the ouside of the case. Now its currently happening again with both drives. So both 12tb drives are unable to be found by unraid. They appear when I put them on an external usb attachment as an unassigned drive. 2) gui issue. When i powerup the server on the screen i see the bios then unraid opens and asks how to boot so I select GUI mode. Once its finished booting I used to get a login screen and then the main page but now it just goes to a blinking cursor after it finishes booting. Im able to log in remotely on another PC Quote Link to comment
Ace319 Posted March 26 Author Share Posted March 26 Okay so its a white label 3.3v issue. Why did it work before????? still having the gui issue Quote Link to comment
JorgeB Posted March 27 Share Posted March 27 13 hours ago, Ace319 said: 2) gui issue. Post the diagnostics. Quote Link to comment
Ace319 Posted March 27 Author Share Posted March 27 3 hours ago, JorgeB said: Post the diagnostics. I thought I did in the first post? or did you want me to pull a specific file out of there? tank-diagnostics-20240327-0848.zip Quote Link to comment
JorgeB Posted March 27 Share Posted March 27 Sorry, they are usually at the bottom of the post, missed them at the top. Is this the GPU you have the monitor connected to? Mar 26 17:15:36 Tank kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 240 Mar 26 17:15:36 Tank kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 240 Mar 26 17:15:36 Tank kernel: NVRM: The NVIDIA Quadro FX 580 GPU installed in this system is Mar 26 17:15:36 Tank kernel: NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please Mar 26 17:15:36 Tank kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more Mar 26 17:15:36 Tank kernel: NVRM: information. The 550.40.07 NVIDIA driver will ignore Mar 26 17:15:36 Tank kernel: NVRM: this GPU. Continuing probe... Mar 26 17:15:36 Tank kernel: NVRM: No NVIDIA GPU found. Quote Link to comment
Ace319 Posted March 27 Author Share Posted March 27 1 hour ago, JorgeB said: Sorry, they are usually at the bottom of the post, missed them at the top. Is this the GPU you have the monitor connected to? Mar 26 17:15:36 Tank kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 240 Mar 26 17:15:36 Tank kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 240 Mar 26 17:15:36 Tank kernel: NVRM: The NVIDIA Quadro FX 580 GPU installed in this system is Mar 26 17:15:36 Tank kernel: NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please Mar 26 17:15:36 Tank kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more Mar 26 17:15:36 Tank kernel: NVRM: information. The 550.40.07 NVIDIA driver will ignore Mar 26 17:15:36 Tank kernel: NVRM: this GPU. Continuing probe... Mar 26 17:15:36 Tank kernel: NVRM: No NVIDIA GPU found. Yes connect via display port. So i need an older driver? It was working before without any drivers installed. Quote Link to comment
JorgeB Posted March 27 Share Posted March 27 1 hour ago, Ace319 said: So i need an older driver? Looks like it, @ich777should be able to confirm if that driver is still available, or re-post in the Nvidia plugin support thread. Quote Link to comment
ich777 Posted March 27 Share Posted March 27 1 minute ago, JorgeB said: Looks like it, @ich777should be able to confirm if that driver is still available, or re-post in the Nvidia plugin support thread. Already answered in the Nvidia Driver support thread, this card is basically obsolete and even the legacy driver won't work on Unraid. 1 Quote Link to comment
ich777 Posted March 27 Share Posted March 27 1 hour ago, Ace319 said: It was working before without any drivers installed. Have you yet tried to uninstall the driver and see if it works afterwards? Quote Link to comment
Ace319 Posted March 27 Author Share Posted March 27 I'll do that tonight working on somethings atm. But a week ago i didnt have any drivers/plugins and things were fine. I only started looking into drivers when I noticed this issue started happening. And everything was fine before. I was able to see the bios/unraid boot menu/and unraid login and main screen. I dont know what changed.... Quote Link to comment
ich777 Posted March 27 Share Posted March 27 1 minute ago, Ace319 said: I dont know what changed.... The driver does execute nvidia-xconfig on boot and that's may why you won't get a blinking cursor but why did you install the Nvidia driver it in the first place? Quote Link to comment
Ace319 Posted March 27 Author Share Posted March 27 (edited) 5 minutes ago, ich777 said: The driver does execute nvidia-xconfig on boot and that's may why you won't get a blinking cursor but why did you install the Nvidia driver it in the first place? Because I was getting the blinking cursor. Before that I would boot to unraid GUI and it was fine (albeit not the best resolution for the monitor but working). Then after the above upgrades to parity drives it started booting to this blinking cursor. Edited March 27 by Ace319 Quote Link to comment
Ace319 Posted March 27 Author Share Posted March 27 Btw Really appreciate all the help and quick replies from you guys! I hope this is just a stupid error on my part that I'm making Quote Link to comment
Ace319 Posted March 27 Author Share Posted March 27 Removed drivers and restarted > no change. blinking cursor after booting up Quote Link to comment
Ace319 Posted March 28 Author Share Posted March 28 @ich777@JorgeBany other thoughts? -The graphics driver is only if I wanted to run a vm or transcode with it right? So I wouldnt need a driver at all? -I dont understand how it was working fine before and now all of a sudden doesnt work lol -Can I just pop the unraid usb into my main pc and boot it from there and see what happens with different hardware? Or is that a bad idea? Quote Link to comment
JorgeB Posted March 28 Share Posted March 28 1 minute ago, Ace319 said: -The graphics driver is only if I wanted to run a vm or transcode with it right? The GPU driver is usually required for GUI mode, it's not for non GUI mode. Quote Link to comment
ich777 Posted March 28 Share Posted March 28 50 minutes ago, Ace319 said: -I dont understand how it was working fine before and now all of a sudden doesnt work lol Diagnostics again please? Please also look if you have a log file for Xorg in the directory /var/log/ Quote Link to comment
Ace319 Posted March 28 Author Share Posted March 28 1 hour ago, ich777 said: Diagnostics again please? Please also look if you have a log file for Xorg in the directory /var/log/ tank-diagnostics-20240328-1550.zip dont think i see that log file. diagnostics attached. Quote Link to comment
ich777 Posted March 29 Share Posted March 29 9 hours ago, Ace319 said: I don't think that this is the /var/log directory from your server, it seems more likely that you are using Krusader from binhex and you are in the containers /var/log directory. I see nothing suspicious from your logs however may I ask why you are still on Unraid 6.12.6? Unraid 6.12.9 was released a few days ago. Quote Link to comment
Ace319 Posted March 29 Author Share Posted March 29 6 hours ago, ich777 said: I don't think that this is the /var/log directory from your server, it seems more likely that you are using Krusader from binhex and you are in the containers /var/log directory. I see nothing suspicious from your logs however may I ask why you are still on Unraid 6.12.6? Unraid 6.12.9 was released a few days ago. Thought it was an unwritten rule in the community to wait a week before updating XD. I'll update and report back in. I'll also try to find that file you requested..... Quote Link to comment
ich777 Posted March 29 Share Posted March 29 10 minutes ago, Ace319 said: I'll update and report back in. I'll also try to find that file you requested..... Open up a Unraid terminal and issue: ls -la /var/log/ Quote Link to comment
Ace319 Posted March 29 Author Share Posted March 29 29 minutes ago, ich777 said: Open up a Unraid terminal and issue: ls -la /var/log/ Quote Link to comment
ich777 Posted March 29 Share Posted March 29 4 minutes ago, Ace319 said: Please do: cat /var/log/Xorg.0.log Quote Link to comment
Ace319 Posted March 29 Author Share Posted March 29 10 minutes ago, ich777 said: Please do: cat /var/log/Xorg.0.log root@Tank:~# cat /var/log/Xorg.0.log [ 49.385] X.Org X Server 1.21.1.7 X Protocol Version 11, Revision 0 [ 49.385] Current Operating System: Linux Tank 6.1.64-Unraid #1 SMP PREEMPT_DYNAMIC Wed Nov 29 12:48:16 PST 2023 x86_64 [ 49.385] Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot,/bzroot-gui [ 49.385] [ 49.385] Current version of pixman: 0.42.2 [ 49.385] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 49.385] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 49.385] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 27 16:40:48 2024 [ 49.387] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 49.397] (==) No Layout section. Using the first Screen section. [ 49.397] (==) No screen section available. Using defaults. [ 49.397] (**) |-->Screen "Default Screen Section" (0) [ 49.397] (**) | |-->Monitor "<default monitor>" [ 49.397] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 49.397] (==) Automatically adding devices [ 49.397] (==) Automatically enabling devices [ 49.397] (==) Automatically adding GPU devices [ 49.397] (==) Automatically binding GPU devices [ 49.397] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 49.397] (++) FontPath set to: /usr/share/fonts/TTF [ 49.397] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 49.397] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 49.397] (II) Loader magic: 0x62dd40 [ 49.397] (II) Module ABI versions: [ 49.397] X.Org ANSI C Emulation: 0.4 [ 49.397] X.Org Video Driver: 25.2 [ 49.397] X.Org XInput driver : 24.4 [ 49.397] X.Org Server Extension : 10.0 [ 49.401] (--) PCI:*(2@0:0:0) 10de:0659:10de:063a rev 161, Mem @ 0xfa000000/16777216, 0xa0000000/536870912, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072 [ 49.401] (II) Open ACPI successful (/var/run/acpid.socket) [ 49.401] (II) LoadModule: "glx" [ 49.402] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 49.413] (II) Module glx: vendor="X.Org Foundation" [ 49.413] compiled for 1.21.1.7, module version = 1.0.0 [ 49.413] ABI class: X.Org Server Extension, version 10.0 [ 49.539] (==) Matched nouveau as autoconfigured driver 0 [ 49.539] (==) Matched nv as autoconfigured driver 1 [ 49.539] (==) Matched modesetting as autoconfigured driver 2 [ 49.539] (==) Matched fbdev as autoconfigured driver 3 [ 49.539] (==) Matched vesa as autoconfigured driver 4 [ 49.539] (==) Assigned the driver to the xf86ConfigLayout [ 49.539] (II) LoadModule: "nouveau" [ 49.539] (WW) Warning, couldn't open module nouveau [ 49.539] (EE) Failed to load module "nouveau" (module does not exist, 0) [ 49.539] (II) LoadModule: "nv" [ 49.540] (WW) Warning, couldn't open module nv [ 49.540] (EE) Failed to load module "nv" (module does not exist, 0) [ 49.540] (II) LoadModule: "modesetting" [ 49.540] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 49.546] (II) Module modesetting: vendor="X.Org Foundation" [ 49.546] compiled for 1.21.1.7, module version = 1.21.1 [ 49.546] Module class: X.Org Video Driver [ 49.546] ABI class: X.Org Video Driver, version 25.2 [ 49.546] (II) LoadModule: "fbdev" [ 49.547] (WW) Warning, couldn't open module fbdev [ 49.547] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 49.547] (II) LoadModule: "vesa" [ 49.547] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 49.550] (II) Module vesa: vendor="X.Org Foundation" [ 49.550] compiled for 1.21.1.4, module version = 2.6.0 [ 49.550] Module class: X.Org Video Driver [ 49.550] ABI class: X.Org Video Driver, version 25.2 [ 49.550] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 49.550] (II) VESA: driver for VESA chipsets: vesa [ 49.550] (++) using VT number 7 [ 49.552] (EE) open /dev/dri/card0: No such file or directory [ 49.552] (WW) Falling back to old probe method for modesetting [ 49.552] (EE) open /dev/dri/card0: No such file or directory [ 49.553] vesa: Refusing to run, Framebuffer or dri device present [ 49.553] (EE) Screen 0 deleted because of no matching config section. [ 49.553] (II) UnloadModule: "modesetting" [ 49.553] (EE) Device(s) detected, but none match those in the config file. [ 49.553] (EE) Fatal server error: [ 49.553] (EE) no screens found(EE) [ 49.553] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 49.553] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 49.553] (EE) [ 49.555] (EE) Server terminated with error (1). Closing log file. root@Tank:~# Quote Link to comment
Ace319 Posted March 29 Author Share Posted March 29 tank-diagnostics-20240329-0941.zip Updated OS. Diag attached Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.