Paul_Ber

Community Developer
  • Posts

    371
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Paul_Ber's Achievements

Contributor

Contributor (5/14)

14

Reputation

1

Community Answers

  1. A link for LINUX instructions, https://www.mythtv.org/wiki/Nmedia_pro-lcd Needs libftdi-devel & libftdi
  2. Thanks for working on this. I think my 2 are LIS driver, one LCD came with a Media PC case(only the LCD part, no 5.25" drive bay case), maybe 2012 era plus or minus a few years. The 2nd one I ordered for Unraid but never got it working. They are not hooked up right now, maybe will pull it out. I remember having to compile the LIS driver.
  3. I find weird stuff with Networking requires to actually restart the Unraid PC to Networking glitches to clear up.
  4. This line is in my ovpn file: setenv UV_IPV6 yes Do I change the yes to no if I don't want IPV6? Changed to no and now get none of the IPV6 errors and it starts faster
  5. I have a different one, "lis VLSystem L.I.S MCE 2005 VFD T USB"
  6. Is Docker changing? https://www.reseller.co.nz/article/706245/docker-sunsets-free-team-subscriptions-roiling-open-source-projects/#:~:text=This tier included many of,April 14%2C 2023 ...
  7. Upgrading that really old Unraid server ASUSTeK COMPUTER INC. M5A97 R2.0, AMD FX-8370, 32GB ECC to what in 2023? Maybe Intel with QuickSync? Everytime I go to price it out I just say no from price. Or do I need to pick older components?
  8. Ok it is back, maybe I can ignore this? Feb 11 15:33:22 Unraid kernel: clocksource: timekeeping watchdog on CPU3: acpi_pm wd-wd read-back delay of 94425ns Feb 11 15:33:22 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 188571ns, clock-skew test skipped! Feb 11 15:33:49 Unraid kernel: clocksource: timekeeping watchdog on CPU1: acpi_pm wd-wd read-back delay of 91073ns Feb 11 15:33:49 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 161752ns, clock-skew test skipped! Feb 11 15:37:19 Unraid kernel: clocksource: timekeeping watchdog on CPU5: acpi_pm wd-wd read-back delay of 88000ns Feb 11 15:37:19 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 183263ns, clock-skew test skipped! Feb 11 15:37:30 Unraid kernel: clocksource: timekeeping watchdog on CPU3: acpi_pm wd-wd read-back delay of 87441ns Feb 11 15:37:30 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 176558ns, clock-skew test skipped! Feb 11 15:47:02 Unraid emhttpd: spinning down /dev/sdf Feb 11 15:47:13 Unraid emhttpd: spinning down /dev/sdd Feb 11 15:47:19 Unraid emhttpd: spinning down /dev/sdg Feb 11 15:48:11 Unraid emhttpd: read SMART /dev/sdf Feb 11 15:48:17 Unraid emhttpd: read SMART /dev/sdd Feb 11 15:48:26 Unraid emhttpd: read SMART /dev/sdg Feb 11 15:49:04 Unraid kernel: clocksource: timekeeping watchdog on CPU7: acpi_pm wd-wd read-back delay of 91352ns Feb 11 15:49:04 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 182704ns, clock-skew test skipped! Feb 11 15:50:21 Unraid kernel: clocksource: timekeeping watchdog on CPU1: acpi_pm wd-wd read-back delay of 87441ns Feb 11 15:50:21 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 176558ns, clock-skew test skipped! Feb 11 15:50:31 Unraid kernel: clocksource: timekeeping watchdog on CPU5: acpi_pm wd-wd read-back delay of 84368ns Feb 11 15:50:31 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 277409ns, clock-skew test skipped! Feb 11 15:51:19 Unraid kernel: clocksource: timekeeping watchdog on CPU6: acpi_pm wd-wd read-back delay of 89955ns Feb 11 15:51:19 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 176279ns, clock-skew test skipped! Feb 11 15:53:19 Unraid unassigned.devices: Removing configuration 'KINGSTON_SHSS37A240G_50026B7253083EAF'. Feb 11 15:55:39 Unraid kernel: clocksource: timekeeping watchdog on CPU6: acpi_pm wd-wd read-back delay of 78501ns Feb 11 15:55:39 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 181866ns, clock-skew test skipped! Feb 11 15:59:04 Unraid kernel: clocksource: timekeeping watchdog on CPU0: acpi_pm wd-wd read-back delay of 172927ns Feb 11 15:59:04 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 451454ns, clock-skew test skipped! Feb 11 16:03:02 Unraid emhttpd: spinning down /dev/sdf Feb 11 16:03:13 Unraid emhttpd: spinning down /dev/sdd Feb 11 16:03:19 Unraid emhttpd: spinning down /dev/sdg Feb 11 16:04:10 Unraid emhttpd: read SMART /dev/sdf Feb 11 16:04:17 Unraid emhttpd: read SMART /dev/sdd Feb 11 16:04:26 Unraid emhttpd: read SMART /dev/sdg Feb 11 16:09:18 Unraid kernel: clocksource: timekeeping watchdog on CPU3: acpi_pm wd-wd read-back delay of 173765ns Feb 11 16:09:18 Unraid kernel: clocksource: wd-tsc-wd read-back delay of 184660ns, clock-skew test skipped! unraid-diagnostics-20230211-1612.zip
  9. I did steps 1, 2, 3, 4, 5, and then 6 power on. Well the PC was on, Unraid for some reason assigned the new disk in the slot the old disk was in(I never did this). And the array came up and not the part with all the choices for the slots. So I stopped the array because I still had to preclear my replacement disk. I Unassigned the slot because I wasn't ready to assign yet. My preclear is almost done. I will assign the new disk to the old disks slot next. Then start the array, will it rebuild the missing slot on to the new disk? I guess I will know right away if it is rebuilding and my post will be not needed. Thanks. In the end it is working as intended. unraid-diagnostics-20230211-1452.zip
  10. So it looks like it would be a pain seeing this all the time. unraid-diagnostics-20230210-0300.zip
  11. Brand new Seagate 6TB drive is already getting error messages. I have never seen that high of an error rate before, is the disk DOA and I should return it? I am doing a preclear on that disk right now. Already switched from HBA to MB SATA ports and different SATA cables and it still does the error message. unraid-diagnostics-20230209-2243.zip