adammerkley

Members
  • Posts

    122
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

adammerkley's Achievements

Apprentice

Apprentice (3/14)

5

Reputation

1

Community Answers

  1. Upgraded from 6.12.6 to 6.12.8 without issue.
  2. I was able to launch tmux by deleting /tmp/tmux-0 first, but any idea why this would be neccessary? rm -r /tmp/tmux-0/
  3. Getting this when trying to run tmux like I have a thousand times before: directory /tmp/tmux-0 has unsafe permissions I ran Docker Safer New Permissions but that didn't resolve (Not sure that touches /tmp anyway.)
  4. The info for the RTL8168(B)/RTL8111(B) PCI Drivers plugin on the App store calls out 8411 too .
  5. Upgrade from 6.12.4 went fine. Didn't follow the instructions on stopping the array, but I encountered no issues anyway.
  6. Did you ever get an answer to this? I see this message upon boot too. Doesn't seem to be harming anything, but just knowing it's there is annoying
  7. I replaced all of the SAS-SATA cables for drives connected to my HBA, and the SATA cables for drives connected to the motherboard. I also removed the molex splitters I had deployed to deliver power to the backplane/drive cages. Just completed a parity check with no errors.
  8. Looking for a sanity check here. Parity check kicked off last night at 6PM. A few minutes into the parity check a bunch of errors like the below popped up. I've ordered replacement SAS->SATA cables for my HBA drives, and replacement SATA cables for my motherboard-connected drives. Anything else I should be looking for? I've attached diagnostics. Oct 6 18:10:08 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 6 18:10:08 Tower kernel: ata3.00: cmd 60/f8:a8:68:53:ab/03:00:0c:00:00/40 tag 21 ncq dma 520192 in Oct 6 18:10:08 Tower kernel: res 40/00:80:60:3f:ab/00:00:0c:00:00/40 Emask 0x50 (ATA bus error) Oct 6 18:10:08 Tower kernel: ata3.00: status: { DRDY } Oct 6 18:10:08 Tower kernel: ata3: hard resetting link Oct 6 18:10:14 Tower kernel: ata3: found unknown device (class 0) Oct 6 18:10:18 Tower kernel: ata3: softreset failed (1st FIS failed) Oct 6 18:10:18 Tower kernel: ata3: hard resetting link Oct 6 18:10:24 Tower kernel: ata3: found unknown device (class 0) Oct 6 18:10:26 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 6 18:10:26 Tower kernel: ata3.00: configured for UDMA/133 Oct 6 18:10:26 Tower kernel: ata3: EH complete tower-diagnostics-20231007-0824.zip
  9. Apologies if this has been asked previously, I searched the thread and couldn't find it. I started a 3 cycle pre clear on a 16TB drive a few days ago. It's almost finished with the post-read on cycle 1. Is it possible to change the settings to just 1 cycle at this point?
  10. I am currently running a preclear of a new 16TB drive. I just got a notification that UD has an update available. Should I update or hold off? If I have to hold off, I suppose I'll need to tell CA Auto-Update to not run until the preclear completes.
  11. Suddenly getting "Conversion failed. A required codec could not be found or failed to install." when trying to play media. This warning appears in the plex console when playing fails: [Transcode] HTTP error requesting GET https://plex.tv/api/codecs/h264_decoder?build=linux-x86_64-standard&deviceId=cfb78a4e-ef5f-4d89-8c6c-ecb622afcfa9&oldestPreviousVersion=1%2E2%2E7%2E2987-1bef33a&version=fa235d6-3855 (6, Couldn't resolve host name) (Could not resolve host: plex.tv) I've tried deleting the codecs folder, and also chmod'ing it to 777 but still get the error. Edit: Changing VERSION from plexpass to public has resolved this behavior.
  12. Upgraded just fine from 6.7.2. Now to look into replacing OpenVPN with WireGuard... Thanks for all your hard work.
  13. Can someone walk me through how to get this running behind an NGINX reverse proxy? I'm using the linuxserver.io LetsEncrypt container.