colev14
-
Posts
44 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by colev14
-
-
Just installed a P400 Quadro to help out my old ryzen 1600 af with Plex transcoding. I set it up per the instructions, but every time I try to go into the nvidia-driver plugin settings, my entire server gui locks up and never recovers. I can't open the settings or get any other pages to load. I have to ssh in and reboot. I've attached my diagnostics. Any ideas what could be causing this issue?
Plex docker settings:
Transcoding settings inside plex:
-
I swapped out my motherboard/cpu/ram to a backup PC I have. I switched from my x570, 3900x to an itx mobo and 3400G with a different ram kit. The server ran perfect for 2 weeks. I use that second system for backups though. I figured the issue might be the motherboard. I bought a new B550 board and put my old cpu and ram back in it. The server locked up again after 3 days. I am going to try swapping the ram from the backup system into this one and see if that does anything. This ram is new from January 2023 and was working fine previously. I don't really understand why that would be the issue. I'm thinking maybe it's the cpu? I had been using the 3900X in my gaming PC for 2 years with no issues. I upgraded to the 5900X and swapped the 3900X into my server. So I don't really think that's the issue. At think point, I'm not sure what to think. Swapping the ram and if that doesn't work, I'll swap my old Ryzen 1600AF into the system and see if that does anything.
My only other thought is it could be the GPU. But I have an old amd rx540 that is in there right now and I have an old nvidia gpu. I don't remember what model. Super old, basically just useful for display out. And the server crashes with both of them. So I don't think it's the GPU.
-
I purchased the molex to sata connectors and that seems to have solved the problem. Thank you!
-
Awesome, thank you. They'll be here tomorrow and I'll give them a shot.
-
2 hours ago, itimpi said:
How many ways does it split? A SATA->SATA splitter tends to be unreliable if it is more than 2 way as the SATA connection cannot handle much current, whereas a Molex->SATA gets away with a 4 way split.
I ordered these 4to1 sata cables. In have a define 7 XL so the extra length helps reach the drives furthest away from the psu. https://a.co/d/gthadWF
Is there another one you would recommended?
-
1 minute ago, trurl said:
What about power connections? Any splitters?
Yes, I have 2 sata power splitters because I don't have enough cables for my PSU. I only have 1 splitter per full size cable though. I guess I can try replacing those. The ones I have now are pretty old from amazon.
-
24 minutes ago, trurl said:
Yes, this is connection problem with disk7
I just recently reseated all the sata cables to troubleshoot another issue. Could this be an issue with the hba card or power supply?
-
Getting an ata error I haven't encountered before in my syslog. I think I narrowed it down to disk 7, and in the logs for that disk I see this in red:
Unraid kernel: ata6.00: exception Emask 0x50 SAct 0x3f8 SErr 0xb0802 action 0xe frozenWith a bunch of other yellow warnings as well:
Feb 1 20:05:19 Unraid kernel: ata6.00: exception Emask 0x50 SAct 0x3f8 SErr 0xb0802 action 0xe frozen Feb 1 20:05:19 Unraid kernel: ata6.00: irq_stat 0x00400000, PHY RDY changed Feb 1 20:05:19 Unraid kernel: ata6: SError: { RecovComm HostInt PHYRdyChg PHYInt 10B8B } Feb 1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 1 20:05:19 Unraid kernel: ata6.00: cmd 60/08:18:c8:b0:82/04:00:76:04:00/40 tag 3 ncq dma 528384 in Feb 1 20:05:19 Unraid kernel: ata6.00: status: { DRDY } Feb 1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 1 20:05:19 Unraid kernel: ata6.00: cmd 60/00:20:d0:b4:82/04:00:76:04:00/40 tag 4 ncq dma 524288 in Feb 1 20:05:19 Unraid kernel: ata6.00: status: { DRDY } Feb 1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 1 20:05:19 Unraid kernel: ata6.00: cmd 60/08:28:d0:b8:82/00:00:76:04:00/40 tag 5 ncq dma 4096 in Feb 1 20:05:19 Unraid kernel: ata6.00: status: { DRDY } Feb 1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 1 20:05:19 Unraid kernel: ata6.00: cmd 60/c8:30:d8:b8:82/03:00:76:04:00/40 tag 6 ncq dma 495616 in Feb 1 20:05:19 Unraid kernel: ata6.00: status: { DRDY } Feb 1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 1 20:05:19 Unraid kernel: ata6.00: cmd 60/08:38:a0:bc:82/04:00:76:04:00/40 tag 7 ncq dma 528384 in Feb 1 20:05:19 Unraid kernel: ata6.00: status: { DRDY } Feb 1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 1 20:05:19 Unraid kernel: ata6.00: cmd 60/00:40:a8:c0:82/04:00:76:04:00/40 tag 8 ncq dma 524288 in Feb 1 20:05:19 Unraid kernel: ata6.00: status: { DRDY } Feb 1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED Feb 1 20:05:19 Unraid kernel: ata6.00: cmd 60/08:48:a8:c4:82/00:00:76:04:00/40 tag 9 ncq dma 4096 in Feb 1 20:05:19 Unraid kernel: ata6.00: status: { DRDY } Feb 1 20:05:19 Unraid kernel: ata6: hard resetting link Feb 1 20:05:25 Unraid kernel: ata6: found unknown device (class 0) Feb 1 20:05:29 Unraid kernel: ata6: softreset failed (device not ready) Feb 1 20:05:29 Unraid kernel: ata6: hard resetting link Feb 1 20:05:35 Unraid kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 1 20:05:35 Unraid kernel: ata6.00: configured for UDMA/133 Feb 1 20:05:35 Unraid kernel: ata6: EH complete -
On 1/10/2024 at 5:08 AM, JorgeB said:
Nothing that I can see about that, there are some strange network related errors which I don't remember seeing before, not sure if they can be a problem:
2024-01-09T13:30:23+00:00 Unraid dhcpcd[1721]: eth0: 00:e0:4c:0e:2a:3d(00:e0:4c:0e:2a:3d) claims 192.168.50.112 2024-01-09T13:35:21+00:00 Unraid dhcpcd[1721]: eth0: 00:e0:4c:0e:2a:3d(00:e0:4c:0e:2a:3d) claims 192.168.50.112I was able to have the server work for a week straight before it locked up again, followed by another week of uptime before locking up, and now it locked up after 3 days. Is there anything in these logs that show anything? I know I keep asking the same thing, I'm just not sure what else to do. I am now back in safe mode with only plex running. I moved everything else over to another proxmox server. My last resort after this will be to move plex to proxmox and just use the unraid server as an nfs server.
Edit: decided to downgrade to 6.12.4 and take it out of safe mode and see if that does anything. If it locks up again, I'll go back to safe mode with only Plex running, then safe mode with nothing running again.
-
On 12/19/2023 at 9:41 AM, JorgeB said:
Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
I was able to get the server to run for 8 days without locking up running it in safe mode with docker disabled. I started up plex for 3 days and it worked fine, so I started up all the Arrs along with cloudflared docker and after 2 days it locked up again. Is there anything in the syslog that points to one of the docker containers being the issue? I'm thinking about running the Arrs/Plex on a 2nd PC in proxmox and mounting my unraid server as an NFS share and using it that way in safe mode.
-
Hello, I got a warning notification that the parity check was cancelled, but on the main page it says it was finished with zero errors. I have been having some issues with the server locking up, so the server is booted in safe mode right now to see if I can rule out any hardware issues. Could that be causing the error?
-
Is there any way to determine which one it is? I'm not sure how to read the logs properly. I have not tried safe mode before. What should I do after booting to safe mode?
-
Hello, I recently started having an issue where my server will lock up and no longer be accessible via the GUI. I also can't ping it or ssh or anything. I started writing the logs to the flash drive and attached the syslog and syslog-previous. I'm not really sure what the issue is. My server has been running for 20+ days consistently for the past few months. But the past couple weeks it will only run for 2-3 days before locking up. I've also added the diagnostics, but those were from after the most recent restart.
-
A reboot seems to have fixed the issue. Not really sure what happened.
-
I just got a popup on my server that there's an issue with my usb device. I've attached an image that shows the popup. It switches back and forth between no device and blacklisted every few minutes. Every once and while it will switch back to recognizing the flash drive and it looks fine again. I've tried downloading diagnostics, but it is not letting me. I'm guessing my usb drive failed. In the past I've had issues with the flash drive getting excessive writes, but I never really got a response on it:
-
Attempted to run a long smart test on the drive and it failed and says "read failure" so I'm thinking it's dead now.
-
Just got a notification that one of my drives had read errors. Fix common problems says:
QuoteIf the disk has not been disabled, then Unraid has successfully rewritten the contents of the offending sectors back to the hard drive. It would be a good idea to look at the S.M.A.R.T. Attributes for the drive in question
The disk has not been disabled and still shows as green on the main tab.
Seeing this in the disk log:
Sep 24 12:08:57 Unraid kernel: critical medium error, dev sdh, sector 2619386232 op 0x0:(READ) flags 0x4000 phys_seg 65 prio class 2I'm not sure if the disk is completely dead and I need to replace it, or if it's still good? If it's bad is there a way to manually mark it as bad so my shares will stop downloading to it?
-
On netdata it looks like the sda drive is having the most issues. And on the unraid dashboard that is the flash drive.
-
It's happening again now during a sabnzbd download and it seems like the usb stick is causing the issue. I don't really understand what is going on there, because it's not even mapped to anything in the docker template.
-
On 9/19/2023 at 3:22 AM, JorgeB said:
Try rebooting and start the containers one by one to see if it gets worse after a specific one.
It appears to be Photoprism that is having the biggest impact. Is there any reason why it would be reading from the flash drive?
-
I've been dealing with IO Wait issues for months now. I've searched through the forum and tried all kinds of solutions. My most recent effort was changing the cache drive from btrfs to XFS. Now it seems like the issue is worse than ever. It took me 2 hours to even be able to login to the server. Everything is locked up and incredibly slow. I've added my logs and some relevant pictures below. I can see that the disk sda is busy, but I think that is my usb stick, so I'm not really sure why that would be the case. I've also updated my bios to the most recent version. It's weird because my dockers appear to be working fine, it's just the unraid UI that is slow and becomes inaccessible. I've tried pinning cpu cores to every docker container to keep some available to the server but that didn't really make a difference.
Looking for any help to get my server to be usable again.
-
I'm getting a invalid source error. I made a backup of my appdata and it appears to have been successful. I've attached the debug log from the backup. When I try to restore from that exact same backup I get the invalid source error. I am not trying to restore my appdata from the old plugin, you can see in the first image I am selecting the ab_ folder.
-
Guys, I swear I literally purchased a 2nd unraid license to run on a 2nd server for tinkering so I don't mess up my main server. But somehow I end up doing this on my main one anyway. I just never learn. I ended up solving the issue myself. I went into ZFS master and enabled destructive mode. Then changed the name of the dataset and the dataset location to appdatatest and then all my old appdata popped up exactly where it was before. Everything works fine now.
-
Hello, I was following the new Spaceinvaderone video on creating a dataset for each appdata folder. I created a dataset on the cache drive for appdata and suddenly my appdata is saying it's 587MB, when previously it was many GB. I can see that there is still 300GB being used on the cache, which is what was being used before. When I go into the file browser and calculate the size, it's saying 87.6 GB though. So I'm not really sure what happened to my old appdata. Everything appears to have been deleted. There are just the folders for the docker containers that are running that got generated fresh.
[Plugin] Nvidia-Driver
in Plugin Support
Posted
I had C states disabled before, I changed the top slot to pcie gen 3, I enabled 4G decoding. I don't think the 1600af supports resizeable bar. It didn't show up in my bios settings and I my bios is updated. I was getting the same issues. Then I decided to try it on my phone and it works. So I tried it on another phone and the windows client and it works. It seems like the problem is with the plex web client. I don't think anybody on my server uses that, so I think I am good to go now. Thanks!