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.

lordbeavis

Members
  • Joined

  • Last visited

Everything posted by lordbeavis

  1. that did the trick. thanks
  2. i keep trying to update my containers that are in the docker compose file and it keeps failing on containers i have removed "=== Updating: Media Server === Pulling latest images... service "sabnzbd" has neither an image nor a build context specified: invalid compose project ✗ Failed to pull images for media_server, update aborted X Stack Media Server failed to updating (exit code: 1) ======================================== === All operations complete === ========================================"
  3. i think i may have found out my issue, it seems that one of my cache pools may have been corrupted or a drive damaged. i have removed one set of drives from my server and removed the other 2 pools from my shares. after copying the files back to the array i havent had the issue yet in 3 days
  4. i may have found my issue, my download nvme cache pool is either corrupt or one of the drives are bad. i have removed both drives and will run it for a week to see if i still have my docker issues
  5. this morning i wake up to not being able to access my local unraid server. I can boot into safe mode and mount drives in recovery but it will not mount the array normally. i have run a memory test and smart check on all drives, everything passes. i have attached my diag file tower-diagnostics-20240701-1626.zip
  6. this seems to be related to my issue https://github.com/moby/moby/issues/29638
  7. im still having this issue and have to reboot my server at least once a week
  8. i reverted back to 6.12.9 i didn't start having this issue till i upgraded to 6.12.10. i will report back in a day or so to see if it continues
  9. it just happened at 1:56 am pst. heres my new diagnostic tower-diagnostics-20240602-0157.zip
  10. i have tried this and clearing the log files but nothing fixes it. a temp solution is to reboot but eventually i end up with the same error
  11. i am getting this error: "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: unable to apply cgroup configuration: mkdir /sys/fs/cgroup/docker/1c0b39233374276b0b6f2e860f93dcfa1660d5588da8a672688d21c4af1ec2f1: no space left on device: unknown" i have tried deleting the log files in /run and that along with restarting the docker service worked once. now no matter what i do i cant update or start any new containers tower-diagnostics-20240514-1701.zip
  12. i have a hp mediasmart ex470 that i am trying to get fully functional with unraid the issue seems to be with the driver. it doesnt connect at the full speed this post has info on the same problem i have run into other than using a usb dongle, what can i do to get this working? I have no experience compiling kernels, but there is another post describing changes that would have to be made to an older kernel to get it functioning here https://www.howtoforge.com/creating-the-sis191-gigabit-ethernet-driver-on-linux-2.6 I have attached my diagnostic log. i have tried both Version: 6.9.0-rc2 and 6.9.0 hpstorage-syslog-20210302-2251.zip
  13. ok... my 4gb of ddr2 ram must have failed. got the 2 blue and 2 red after pressing the pinhole button in the front currently waiting for a AMD Athlon 64 X2 3250e to be delivered, so i needed to tear it apart anyways but i changed to a 2gb ddr2 800mhz. havent run the memtest86+ on the new ram but my issue with not being able to activate the trial key is gone. with 6.9.0-rc2 the link speed on my adapter 100 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 01) Mar 2 14:45:43 HPSTORAGE kernel: sis190: sis190 Gigabit Ethernet driver 1.4 loaded Mar 2 14:45:43 HPSTORAGE kernel: sis190: 0000:00:04.0: Read MAC address from EEPROM Mar 2 14:45:55 HPSTORAGE kernel: sis190 0000:00:04.0 eth0: mii ext = 0000 Mar 2 14:45:55 HPSTORAGE kernel: sis190 0000:00:04.0 eth0: mii lpa=c5e1 adv=01e1 exp=000f Mar 2 14:45:55 HPSTORAGE kernel: sis190 0000:00:04.0 eth0: link on 1000 Mbps Full Duplex mode Mar 2 14:45:55 HPSTORAGE dhcpcd[1294]: br0: carrier acquired Mar 2 14:45:55 HPSTORAGE kernel: bond0: (slave eth0): link status definitely up, 100 Mbps full duplex Mar 2 14:45:55 HPSTORAGE kernel: bond0: (slave eth0): making interface the new active one so i am back to not connecting at 1gbit hpstorage-syslog-20210302-2251.zip
  14. hmmm.....i found some info on this but i am in over my head regarding compiling a kernel https://www.howtoforge.com/creating-the-sis191-gigabit-ethernet-driver-on-linux-2.6
  15. How did you get the network port to run at full speed? it is super flaky and mine wont even register the trial license. It has an SiS 191 chipset
  16. i confirm. says the same for me
  17. First I have to say thank you. I have been ripping my hair out trying to get gpu passthrough working on my ryzen 2600 on a b450m with a Vega 56 and a Rx 550. Thanks to your patched kernel, I can start the VM with the Vega fine an put it to sleep or reboot it fine, but when I shut it down within a few min the fan goes turbo on the Vega and even after using the server standby script to reset my gpu from spaceinvader1 the GPU is disconnected but doesn't reconnect and I am unable to start the VM untill I reboot.

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.