Paul_G

Amazing. Thank you!

Hi, I've just moved 8 drives to an enclosure with a backplane. Previously I used two SAS to SataX4 breakout cables to connect the drives to my HBA, but now they're all connected via one SAS to SAS cable between the HBA and the back plane. Because both the HBA and the backplane have two SAS ports, would there be any benefit to using a second SAS to SAS cable? Is this a terrible idea? Thanks.

I have been pondering these very questions. thanks all.

Thanks. Yes. was an nvidia driver issue. I got Plex back up and running pretty quickly by removing the NVIDIA_DRIVER_CAPABILITIES and NVIDIA_VISIBLE_DEVICES variables, and the --runtime=nvidia extra parameter (need to click on advanced view). This got Plex back in action (but without a GPU) and i've only just now had chance to try to figure out why it stopped working. Turned out to be that the card is just too old now. Logs say "The NVIDIA GeForce GT 710 GPU installed in this system is supported through the NVIDIA 470.xx Legacy drivers." . When i looked into getting these installed they aren't in the nvidia plugin anymore, as confirmed here by @ich777 all was fine when i was on Unraid 6.12.15 but no more. nevermind. That card was just junk i had lying around anyway, so no big deal.

Hi, I've just upgraded from 6.12.15 (or possibly 6.12.14) to 7.1.4 all seemed ok except Plex aint working. The few other Docker containers i've got started ok and are running, i get this when trying to start the Plex container: I removed the container and re-added via the previous apps tab, and get "The command failed" 😭 I backed up the USB before the upgrade so I should be able to roll back, but if anyone could help sort this out it would be very much appreciated. Paul. gromit-diagnostics-20250903-2033.zip

bingo. sorted. Thanks for the help just now and also for everything else you do with the apps and repos. appreciated!

Howdy, just updated to the latest version. worked just fine beforehand but now getting this -> Other docker containers are working as usual. Have disabled and enabled docker service. same. have turned the server off and on again. same. am getting some errors on the logs -> tried removing the container and the image and reinstalling from the previous apps template. seemed to make no difference, but slightly different info in logs:> 2025-01-06 22:38:05,313 INFO Included extra file "/etc/supervisor/conf.d/novnc.conf" during parsing 2025-01-06 22:38:05,314 INFO Set uid to user 0 succeeded 2025-01-06 22:38:05,342 INFO supervisord started with pid 7 2025-01-06 22:38:06,352 INFO spawned: 'start' with pid 94 2025-01-06 22:38:06,354 INFO reaped unknown pid 8 (exit status 0) 2025-01-06 22:38:06,706 DEBG 'start' stderr output: _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. 2025-01-06 22:38:06,708 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2025-01-06 22:38:06,710 DEBG 'start' stderr output: Xvnc TigerVNC 1.13.1 - built May 25 2024 17:13:24 Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Underlying X server release 12101013 Mon Jan 6 22:38:06 2025 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 5900 vncext: created VNC server for screen 0 2025-01-06 22:38:07,667 DEBG 'start' stderr output: [mi] mieq: warning: overriding existing handler (nil) with 0x55d6487ab6e0 for event 2 [mi] mieq: warning: overriding existing handler (nil) with 0x55d6487ab6e0 for event 3 2025-01-06 22:38:07,966 DEBG 'start' stderr output: WebSocket server settings: 2025-01-06 22:38:07,968 DEBG 'start' stderr output: - Listen on :6080 - Web server. Web root: /usr/share/webapps/novnc - No SSL/TLS support (no cert file) - proxying from :6080 to localhost:5900 2025-01-06 22:38:07,975 DEBG 'start' stdout output: ObRender-Message: Unable to load the theme 'Adwaita Revisited Dark' 2025-01-06 22:38:07,976 DEBG 'start' stdout output: ObRender-Message: Falling back to the default theme 'Clearlooks' 2025-01-06 22:38:08,456 DEBG 'start' stderr output: ERROR: openbox-xdg-autostart requires PyXDG to be installed 2025-01-06 22:38:10,551 DEBG 'start' stdout output: [info] tint2 not running 2025-01-06 22:38:10,597 DEBG 'start' stderr output: tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes 2025-01-06 22:38:10,611 DEBG 'start' stderr output: tint2: xRandr: Found crtc's: 1 2025-01-06 22:38:10,611 DEBG 'start' stderr output: 2025-01-06 22:38:10,612 DEBG 'start' stderr output: [1;34mtint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 96 2025-01-06 22:38:10,614 DEBG 'start' stderr output: tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'. tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc 2025-01-06 22:38:10,619 DEBG 'start' stderr output: tint2: real transparency on... depth: 32 2025-01-06 22:38:10,626 DEBG 'start' stderr output: t 2025-01-06 22:38:10,627 DEBG 'start' stderr output: int2: panel items: TSC tint2: Systray composited rendering on tint2: nb monitors 1, nb monitors used 1, nb desktops 1 tint2: panel 1 uses scale 1 2025-01-06 22:38:10,730 DEBG 'start' stderr output: tint2: Kernel uevent interface initialized... 2025-01-06 22:38:10,746 DEBG 'start' stderr output: tint2: systray window 8388621 2025-01-06 22:38:10,747 DEBG 'start' stderr output: tint2: systray started 2025-01-06 22:38:13,278 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 142 minor 6 serial 501 2025-01-06 22:38:13,279 DEBG 'start' stderr output: error 9: BadDrawable (invalid Pixmap or Window parameter) request 139 minor 4 serial 502 error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0 serial 524 any help would super cool. thanks for looking.

I just shut it down via ssh: It went off on it's own (without me having to hold down the power button). I've switched it back on and extracted more diagnostics, attached.

Good afternoon, Whenever I try to shutdown or reboot the server, it always hangs partway through the process. I always end up having to hold the power button on the front of the machine to finish the shutdown (after waiting 10 mins or so). Interestingly, it doesn't seem to have this issue when using the poweroff or reboot command when SSHing in, or using the console on the web GUI. I try not to go this route though as I'm unsure if this is a good idea or not. Any help in troubleshooting this would be appreciated. I've not really any idea what to look for in the logs. thanks, Paul. gromit-diagnostics-20240725-1314.zip

I didn't know X1 to x16 adapters were a thing. Thanks. Will look at them. And as the task isn't that heavy, and I just want a chip capable of hardware decoding H.265, I don't really want to spend big. Was hoping someone might have been down this road already 😁

Hey, I've only one PCIe x16 slot on my mobo which is being used by my HBA, so I'm looking for a GPU to go into a PCIe X1 slot to decode one or two H.265/X265 streams from Plex. Any suggestions please? 😃

@Jay3ird nice. That's where my one fell over. Lol. Thanks.

@Jay3ird awesome. What happens when you click on the Generate backup button?

I updated to Unraid V6.12.6 earlier today (still on connect plugin 2023.09.08.0637 as still the latest version). I no longer get the same errors that i screenshotted in my previous post. It looked to be resolved. The server seemed to be connected in the management access options so i went to the Unraid connect dashboard and this showed that a flash backup was already available. this seemed a bit odd as I'd only just booted the server in the new 6.12.6 update and the timestamp that was showing in the dashboard for the backup was more or less the same as the time it booted up. I tried to grab a copy of the new online flash backup to validate that it was working, but i kept getting an error. I thought I would try logging out and back into Unraid Connect and now I can't log back in, even after a server reboot!! Error: {"message":"Request failed with status code 403","data":"Oh noes! something doesn't seem right here"}

I'm fairly new here. Does anyone know if someone from Lime Technology is likely to look into it, or give an update here? It's obviously an issue. Does someone need to file a bug somewhere?