doubley

Members
  • Posts

    28
  • Joined

  • Last visited

Recent Profile Visitors

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

doubley's Achievements

Noob

Noob (1/14)

3

Reputation

  1. Hi Jorge, do you know if this has been fixed as of the latest, 6.12.1? I've been having issues added a vdev of a smaller capacity to my zpool, unsure if due to user error or this bug still existing.
  2. Doesn't seem to have fixed it. I deleted the pool and remade it with the same settings and same issue. Should I just wait for RC3 or is my issue different? Can upload diagnostics if helpful.
  3. To be clear, will pools created with encryption in RC2 begin working in RC3, or will I need to reformat? I had a 7 drive zpool with encryption working great until I had rebooted, ultimately getting the same error as OP.
  4. Just updated and testing both JellyFin and Plex, still no dice for me. Is there any configuration needed for those who have gotten it working? @ljm42 said he had JellyFin working, but my understanding is that with these RCs we shouldn't need to add anything in config files on the unRAID side - it should work out of the box. Obviously on the Plex/JF side of things, I have --device=/dev/dri in my extra arguments.
  5. Please see the attached diagnostics. Server uptime is only about 6 hours so hopefully there isn't too much to sift through. Memory usage is 10GB/64GB presently, and generally never exceeds 32GB/64GB. tower-diagnostics-20210907-0348.zip
  6. Hello! I'm encountering an issue and I'm in a bit of a pickle. After a data drive swap in my main array and a UD plugin update, I am no longer able to mount certain drives in UD. I have a total of 10 drives in UD. 2 SSDs, 7 pre-existing HDDs, and 1 new HDD. The 2 SSDs and 1 new HDD mount fine, but the 7 pre-existing HDDs no longer mount. When attempting to mount, the log shows: Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] physical block alignment offset: 4096 Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] 4096-byte physical blocks Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Write Protect is off Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Mode Sense: 73 00 00 08 Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 6 22:08:32 Tower kernel: sdaa: sdaa1 Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Attached SCSI disk Sep 6 22:08:52 Tower emhttpd: WDC_WUH721818ALE6L4_3WKXN7LJ (sdaa) 512 35156656128 Sep 6 22:08:52 Tower emhttpd: read SMART /dev/sdaa Sep 6 22:09:56 Tower unassigned.devices: Adding disk '/dev/sdaa1'... Sep 6 22:09:56 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>' Sep 6 22:09:56 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. ' Sep 6 22:15:30 Tower unassigned.devices: Adding disk '/dev/sdaa1'... Sep 6 22:15:30 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>' Sep 6 22:15:30 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. ' Sep 6 22:18:48 Tower unassigned.devices: Adding disk '/dev/sdaa1'... Sep 6 22:18:48 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>' Sep 6 22:18:48 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. ' This is the same error show for all 7 of my drives which previously mounted just fine. Anyone have any insight? I really need to get this fixed ASAP as these drives contain data I need to access. I have tried reinstalling the plugin as well as full server restarts, neither seem to help.
  7. Based on @ljm42's comment above, I reverted back to 6.9.2 for the time being as it sounds like they have some work to do before RC2 / final release.
  8. Hi all, I was previously on Unraid 6.9.2 stable and used my Intel 11700 for Plex and Jellyfin hardware encoding. Since Rocket Lake S wasn't officially supported with that version of Unraid, I had to use i915.force_probe=4c8a in syslinux.conf to get it all working. I upgraded to Unraid 6.10.0 RC1 and it immediately didn't work. My frist though was since Rocket Lake is officialy supported, I removed i915.force_probe=4c8a from syslinux.conf. lspci -v Here is the output of lspci -v on 6.9.2: and again on 6.10.0 RC1: cd /devi/dri returns the expected results chmod is still in my go file as well In my Plex container (linuxserverIO), I have it configured as follows: And it's enabled in Plex: But it no worky :< Sometimes the transcoder crashes all together and gives an error stating such, and sometimes, as pictured above, it fails over to software encoding. The log is full of errors regarding it: Let me know if the full Plex logs would be helpful, or if the error is immediately apparent based on the information already provided.
  9. Has anyone gotten Rocket Lake S iGPU encoding/decoding to work? I had it working on 6.9.2 stable using i915.force_probe=4c8a into syslinux.conf, however I can't get it working with 6.10RC1. I removed i915.force_probe=4c8a from syslinux.conf since it seems Rocket Lake is now supported; lspci -v now shows RocketLake-S: 6.9.2 lspci -v: 6.10 RC1 lspci-v: I can navigate to /dev/dri and the expected files show up and my go file still contains: So as far as I can tell, everything should be working, but the iGPU still isn't working in Plex or Jellyfin. Unsure if this is related to a 6.10 RC1 issue or if something is wrong with my configuration.
  10. I hope this gets some attention from @limetech. Seems to be a common issue. Anything we can do to help diagnose?
  11. Cool - let me know how it goes. I have my server at a buddy's house ~6 hours away, so it's not as easy for me to swap hardware in and out. Very interested to see the results.
  12. I wanted to add I'm having the exact same experience as you, but haven't had a chance to diagnose hardware issues. Unraid 6.8.3 is stable as a rock for me, Unraid 6.9 the trouble maker. I first had this issue on 6.9 RC2, figured it was a RC-related issue, and rolled back. Now that I'm on 6.9 stable, still the same thing. I've rolled back to 6.8.3 again as it's seeming like this is a software issue of some kind. I wonder if this is somehow related to ICH's Nvidia Driver plugin? That seems to be a commonality between your system and mine - both using GPUs. Ryzen 3950x 64GB 3000Mhz GTX 1650 EVGA 750w Gold
  13. Okay, so I lied a little. I do keep all .torrent files, but I have 11,103 in that folder and I only have ~150 I like to permanently seed. So I'm not really sure how I can easily utilize that. But I do appreciate the advice!