zer0zer0

Members
  • Posts

    38
  • Joined

  • Last visited

Everything posted by zer0zer0

  1. I'm excited to see this container, but it doesn't want to come up on my server Just gets stuck at 12/11/202311:31:59 AM API: Starting... 12/11/202311:32:00 AM PROXY: Starting...
  2. So, it won't rebuild from parity? That data is only recoverable using testdisk or similar?
  3. Hmm, all of the other disks also start at 8? Device Start End Sectors Size Type /dev/sdb1 8 2441609210 2441609203 9.1T Linux filesystem /dev/sdc1 8 2441609210 2441609203 9.1T Linux filesystem /dev/sdd1 8 2441609210 2441609203 9.1T Linux filesystem /dev/sde1 8 2441609210 2441609203 9.1T Linux filesystem /dev/sdf1 8 2441609210 2441609203 9.1T Linux filesystem
  4. It was definitely formatted with xfs and then all of a sudden just threw that error root@DARKSTOR:~# fdisk -l /dev/sde Disk /dev/sde: 9.1 TiB, 10000831348736 bytes, 2441609216 sectors Disk model: HUH721010AL4204 Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 14CEF3CF-1F72-48D2-8C97-83C61932AE02 Device Start End Sectors Size Type /dev/sde1 8 2441609210 2441609203 9.1T Linux filesystem
  5. Same result unfortunately Sorry, could not find valid secondary super block
  6. It’s going to take a while 😃 why /dev/md4p1 and not /dev/sde?
  7. All of a sudden one of my disks gave me the dreaded error of unmountable, no supported file system Disk 4 - HUH721010AL4204_7PH0NGHC (sde) Check xfs filesystem is totally missing from the gui for this disk, but there for all the other array disks? Running a check from the CLI comes back with could not find a valid secondary superblock Where do I go from here apart from just replacing the drive? Diagnostics zip attached darkstor-diagnostics-20230810-2128.zip
  8. While I'm waiting I flashed the latest firmware and the drive is now reporting no smart issues, passes the tests and is ripping at 220-250MB/sec. Very weird, but I'll take it while I wait for a replacement to arrive. Haha
  9. As far as I can tell all of the drives are operating as expected and all connections are fine. It might start our at ~28MB/sec and then it will drop under 10 🙃 I do get a weird result for smart test on the parity drive - Background short Failed in segment --> 3 But it reports are healthy at the same time? Diagnostics file attached Diskspeed tests are also good when benchmarking the drives But, as you can see here the parity drive is only being written really slowly unraid-diagnostics-20230522-1659.zip
  10. I'm not sure what's up, but I'm on 6.10.0-rc8 and I'm not seeing it no matter what I search for in community apps (version 2022.05.15) Searching for "docker folder" comes up with totally irrelevant results and searching for your repo only shows your other awesome work!!
  11. I can confirm that it's there on my 6.10.0-rc2 server with a Mellanox CX3 card as well, and I have used it to change the interface mapping
  12. I'm curious if this is the intended behavior when using the web gui on 6.10.0-rc2? If you use something like http://unraidserver.local it converts it to a really ugly url like this https://a9673c7c842a20425e043d8330e376af784c757b2.unraid.net/ And at the same time you can't get to it because it doesn't resolve nicely with pihole/unbound running on Unraid itself, and I had to go in and create a new local dns entry
  13. Hmm, apt installing python3 and then running those whitelist scripts works perfectly for me... sudo apt update sudo apt install python3
  14. I made things as simple as possible and I'm just using /torrents as my path mapping, so I don't think that's the issue. Yes the file gets downloaded and I can see it sitting in the /torrents directory and it starts seeding I've also run DockerSafeNewPerms a few times, but that hasn't changed anything. I can get around it by using nzbToMedia scripts for the time being, but it's weird I can't get it working natively
  15. Anyone else having issues getting torrents to complete with Sonarr? I have paths mapped properly, and have tried qbittorrent, rtorrent, deluge, etc. without any luck Sonarr sends torrents perfectly, and the torrent clients download them perfectly Then the completion just doesn't happen and there's no logs
  16. Are you sure you’re forcing it to transcode? can you see the nvidia card if you run nvidia-smi from inside the docker terminal?
  17. I've seen times when nvidia-smi doesn't show anything but it is actually transcoding. You should be sure you are forcing a transcode and then check in your Plex dashboard for the (hw) text like this...
  18. binhex plexpass container is working well for me
  19. hmmm, seems it might even be a SuperMicro X10 and/or Xeon E5 v3 specific issue. No issues on my E3-1265L v3 running on an AsRock Rack E3C224D2I @StevenD can run 6.9rc2 with hypervisor.cpuid.v0 = FALSE on his setup with ESXi 7, SuperMicro X9, and E5-2680v2 cpu's Thanks to @ich777, I can confirm that you can run the latest 6.9rc2 with a modified bzroot that has the 6.9.0-beta35 microcode
  20. I saw the boot freeze with just the hypervisor.cpuid.v0 = FALSE in the vmx file and no hardware pass through at all. So it should be independent of video cards etc.
  21. I rolled back to UnRAID version 6.9.0-beta35, and this issue is resolved. I'm not sure what changed exactly, but it might be something to do with CPU microcode
  22. I talked to @StevenD and dropped back to UnRAID version 6.9.0-beta35 like he's running, and this issue is resolved
  23. @jwiener3 - This issue is resolved if you drop back to UnRAID version 6.9.0-beta35
  24. I'm seeing an issue when using ESXi and setting hypervisor.cpuid.v0 = FALSE in the vmx file. The system will not boot if you assign more than one cpu to the virtual machine. I'm using ESXi 6.7 with the latest patches and UnRAID 6.9.0-rc2. At first I thought it was an issue with passing through my Nvidia P400, but it happens even without any hardware passed through. My diagnostic zip file is attached. Here is a thread from another user discussing the same issue - darkstor-diagnostics-20210111-1047.zip
  25. To follow up on my issues, I can boot if I choose just one cpu, so it's probably not an issue with this plugin specifically. It is more likely to be UnRAID itself. If I set one cpu and also hypervisor.cpuid.v0 = FALSE in the vmx file I can get it to boot and the plugin appears to be working as expected. @ich777- if you can think of any logs etc. to get this resolved let me know