Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

mrvnsk9

Members
  • Joined

  • Last visited

  1. @Lazaros Chalkidis The widget is showing all disks defined in /var/local/emhttp/disks.ini. My disks.ini has 24 disks defined while my array only has 8 disks in it. All of the "empty" entries in the disks.ini file have status="DISK_NP". Would it be possible for you to have a toggle to automatically filter status="DISK_NP" entries in the disks.ini file? Here's an example entry: ["disk8"] idx="8" name="disk8" device="" id="" size="0" sectors="0" sector_size="0" transport="" rotational="" discard="" removable="" spundown="0" status="DISK_NP" format="-" temp="*" numReads="0" numWrites="0" numErrors="0" type="Data" color="grey-off" spindownDelay="-1" spinupGroup="" idSb="" sizeSb="0" deviceSb="" luksState="0" fsType="auto" fsStatus="-" autotrim="" compression="" warning="" critical="" exportable="no" comment="" fsColor="grey-off" fsEmpty="no" fsSize="0" fsFree="0" fsUsed="0"
  2. I upgraded to 7.3.0-rc1 a couple of hours ago. It was a few hours after your latest release on GitHub.
  3. EDIT: Adding runtime: nvidia into the compose file appears to have fixed the issue. Previously, it wasn't required when using the deploy: notation. I'm not sure what changed, but adding the runtime back fixed the issue. I'm leaving this here in case it helps someone else out. After upgrading beyond 7.2.5-rc1, I am unable to start containers using my Nvidia GTX 970. The newer kernel versions do not appear to have a working - at least for the GTX 970 - 580 series driver. 580.125 is the last driver version that worked for me. Diagnostics are attached and additional information is below. Any help would be appreciated. Nvidia Info: Nvidia Driver Version: 580.142 Open Source Kernel Module: No Installed GPU(s): 0: NVIDIA GeForce GTX 970 0C:00.0 GPU-f2b9c44f-accf-5c81-4303-1f1c97c38b39 GPU Driver Support: 0: NVIDIA GeForce GTX 970 Detected via: nvidia-smi Chip codename: GM204 Architecture: Maxwell Kernel module support: proprietary-only Device ID input: 0x13C210DE Normalized ID: 13c2 Supported candidates: 580.142 Recommended Driver: 580.142 (best-available) nvidia-smi Output: Thu Apr 23 22:21:09 2026 +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 580.142 Driver Version: 580.142 CUDA Version: 13.0 | +-----------------------------------------+------------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+========================+======================| | 0 NVIDIA GeForce GTX 970 On | 00000000:0C:00.0 Off | N/A | | 47% 39C P8 13W / 250W | 2MiB / 4096MiB | 0% Default | | | | N/A | +-----------------------------------------+------------------------+----------------------+ +-----------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=========================================================================================| | No running processes found | +-----------------------------------------------------------------------------------------+ Error when starting via docker compose: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: ldcache error: process /sbin/ldconfig failed with error code: 1 Example Docker Compose Service: services: plex: container_name: plex image: ghcr.io/hotio/plex restart: always network_mode: host tmpfs: - /transcode volumes: - $DATADIR/plex:/config - $MEDIADIR/media:/data environment: - TZ=$TZ - UMASK=002 - PLEX_BETA_INSTALL=true - PLEX_CLAIM_TOKEN=************ - PLEX_ADVERTISE_URL=************** deploy: resources: reservations: devices: - driver: nvidia capabilities: - gpu count: all healthcheck: test: curl --connect-timeout 15 --max-time 100 --silent --show-error --fail "http://$IP_ADDRESS:32400/identity" >/dev/null interval: 15s timeout: 5s retries: 5 start_period: 60s labels: net.unraid.docker.icon: https://raw.githubusercontent.com/walkxcode/dashboard-icons/master/png/plex.png net.unraid.docker.webui: http://$IP_ADDRESS:32400/web dragon-diagnostics-20260423-2201.zip
  4. Edit: Reverting back to BTRFS from ZFS on my cache pool where my appdata is stored fixed the issue. I rolled back to 6.12.1 after having some issues with docker containers after updating to 12.6.2. I am getting a kernel panic when attempting to start containers using "docker compose up -d". Everything was running fine prior to updating to 12.6.2. I also tried disabling the Nvidia runtime in the docker compose file to see if I had an issue there. It didn't make a difference. Let me know if more information is needed. Here is a screen shot of the server console and diagnostics are attached. dragon-diagnostics-20230630-2315.zip
  5. mrvnsk9 changed their profile photo
  6. I'm considering dumping the mellanox card in favor of intel as well. I suppose I'll hold out a while for the fix. I do appreciate all the hard work the devs do as well. What intel card are you looking considering? I've been looking at the x520, but I'm not sure that's the best option.
  7. Thanks for the information. I guess I missed that in the release notes and my forum searches. I'll run the on-board NIC until this is resolved. Thanks for the information.
  8. Connecting the on-board NIC restores connectivity. Looks like there's a known issue with Mellanox NICs at the moment. I'll leave the on-board NIC connected until that issue is resolved. Thanks for the help.
  9. After upgrading to 6.10.2, I am no longer getting an IP address. I am using a Mellanox MCX311A-XCAT ConnectX-3 @ eth1 on an AMD platform. IMMOU is also disabled. I didn't have any issues with this NIC prior to upgrading. The diagnostics are attached. Any help would be greatly appreciated. - Brian dragon-diagnostics-20220606-1740.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.