Ace319
-
Posts
35 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Ace319
-
-
@ich777Im upgrading to a cpu with igpu (i7-12700k) so no need to keep digging into this just on behalf. But thanks for everything!
-
1
-
-
21 minutes ago, JonathanM said:
Are you sure you selected the box to "Write corrections to parity"?
I followed the guide as well as the video before doing anything. But Im sure I screwed up somewhere because all these corrections shouldnt be happening.
But like you said it sounds like the user script didnt actually do anything for that drive before I removed it.
-
5 minutes ago, JonathanM said:
Deleting files doesn't clear the drive. The entire drive must have zeroes written to it, so when it is removed the parity is still valid. Preclear DOES write all zeroes, but you can't preclear a drive while it's in the array. There is a script that does clear the drive while it's in the array so you can remove it without recalculating parity, but the script doesn't work well for many people, it's very slow.
I think you need to stop the array, unassign the parity drive, start the array so it forgets it, stop the array, assign the parity drive so it will recalculate from scratch.
A clear drive in Unraid terms is all zeroes. A drive with all the files deleted, or formatted, even if it shows an empty filesystem still has a whole mess of ones and zeroes on it, some from the deleted files, some from the filesystem itself.
Yeah I used the script... The script finished like like 10 minutes. So youre saying that the script did nothing haha.
Understood. And yes the drive is removed and parity check is running/fixing. so everything should be good when it finishes
-
7 minutes ago, JonathanM said:
Apparently the drive to be removed was not fully cleared.
Generally writing all zeroes to a drive takes many many hours, even days sometimes. How long did that step take for you?
I used krusader and the built in file manager (found that this froze a few times).
Everything was clear off the drive (it was 3tb) But it took maybe 24hours.
The drive in question had pending sectors and it was my slowest WD Green 5400 drive so I wanted to take it out anyway.
So I removed it and I'm currently doing a preclear on it rn but it is running SO SLOW. screenshot below. I figure Im just going to remove it completely and us it for an extra- extra redundancy for pics/home vids.
-
7 minutes ago, JonathanM said:
Maybe you accidentally checked "Parity is valid" after you did the new config?
I did method below and you are supposed to check the parity is valid box?
The "Clear Drive Then Remove Drive" Method
14. Click the check box for Parity is already valid, make sure it is checked!
-
47 minutes ago, JorgeB said:
If you removed an array drive parity should be resynced instead, a parity check will be much slower due to all the errors.
I thought I did - I followed all the steps on the walkthrough and spaceinvaderone's video (which are the same steps).
This is my monthly parity check. I didnt run it manually after I shrunk my array.
-
-
9 hours ago, ich777 said:
Oh, things where working quiet differently back then.
However I would strongly recommend that you either get a card that is supported by the Nvidia Driver plugin but I will look into that but as said it will take some time.
May I ask why you need GUI mode in the first place?
I've never needed GUI mode. At 6.8.3 and the years before my server was working well in the background and I didnt even have a monitor attached to the server. I only discovered gui mode after I started upgrading and having issues.
That being said now that there is a GUI mode its a lot easier to troubleshoot problems at the server especially for someone like me who is not super tech savy. Ex. my ethernet was down for a few days after a power surge and I had no idea why I couldnt connect to my server because all my other devices (all wifi) was working fine- even after rebooting my modem several times.
In that example I could have turned on the monitor to my server and see that it was a network issue and not an unraid issue.
Honestly GUI mode will make accessibility for newcomers a lot easier than having to deal with terminal.
-
8 hours ago, ich777 said:
May I ask if you know on which version it worked previously?
I have to look into this but this will take some time…
Definitely on 6.8.3. I backed up my flash and upgraded back in mid Feb 2024.
-
tank-diagnostics-20240329-0941.zip
Updated OS. Diag attached
-
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:~# -
29 minutes ago, ich777 said:
Open up a Unraid terminal and issue:
ls -la /var/log/
-
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.....
-
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.
-
@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?
-
Are they white label drives?? I just ran into the white label 3.3v issue
-
Removed drivers and restarted > no change. blinking cursor after booting up
-
Any updates or resolutions? Having thr same issue now
-
Did you ever get this resolved? It's happening to me rn
-
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
-
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.
-
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....
-
17 minutes ago, ich777 said:
Please read the first recommended post on top.
There is no easy way to do that.
Sorry but I can‘t help here since this card is simply not supported.
Maybe try to get a slightly newer card like a Quadro P400 or similar that is supported by the plugin.
I would still recommend that you get something like a Nvidia T400 since it‘s a recent card.
If you don't plan or want to use acceleration within Docker containers through your Nvidia graphics card then don't install this plugin!
Okay so this isnt needed for me and my needs and my issue has nothing to do with a missing driver. or at least nothing to do with this plug in. THanks for the quick reply!
-
Hi I have a NVIDIA Quadro FX 580 GPU that im using solely for the purpose of being able to see the GUI on a monitor attached to the server. Not using to for transcoding or anything as my mobo (asrock p67 extreme 4 gen 3) does not have integrated video output for my i5-2500k.
Monitor is connected via displayport to the vid card and I can see the bios>select unraid boot to GUI> then once its all done and booted all I see is a blinking cursor. Not sure if this was due to a recent update but things have been fine for a long time (i was able to see the GUI and main unraid page just fine).
I tried this plug-in but looks like i need a legacy NVIDIA-Linux-x86_64-340.108. So how do I install this? I am quite green to terminal use and what not so I really dont want to mess anything up.
Recommended controllers for Unraid
in Storage Devices and Controllers
Posted · Edited by Ace319
Just realized I still have this thing
https://www.amazon.com/gp/product/B07KNXZFRH/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
Will this 9211-8i work?
Or should I aim for a 9300? Or should I leave it alone because it was a good option?