akawoz

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by akawoz

  1. When going through this account migration it reminded me that Unraid still has a very old (and no longer active) email address. I've successfully migrated using that old email address but when I attempt to change the email address I get the message that the email address was changed successfully, but then on logout and login I notice that it will only accept the old email address (which has reverted in the account settings). I've attached a screen recording. Any ideas? Recording 2023-03-06 084040.mp4
  2. I'll chime in - using this same board with Unraid, have 4x of these (no ECC currently): root@Preston:~# sudo dmidecode --type 17 | more # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.3.0 present. Handle 0x0028, DMI type 17, 92 bytes Memory Device Array Handle: 0x0021 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8 GB Form Factor: DIMM Set: None Locator: DIMMA1 Bank Locator: P0_Node0_Channel0_Dimm0 Type: DDR4 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2667 MT/s Manufacturer: Corsair Serial Number: 00000000 Asset Tag: 9876543210 Part Number: CMK16GX4M2Z3200C16 Rank: 1 Configured Memory Speed: 2667 MT/s Minimum Voltage: 1.2 V Maximum Voltage: 1.2 V Configured Voltage: 1.2 V Memory Technology: DRAM Memory Operating Mode Capability: Volatile memory Firmware Version: Not Specified Module Manufacturer ID: Bank 3, Hex 0x9E Module Product ID: Unknown Memory Subsystem Controller Manufacturer ID: Unknown Memory Subsystem Controller Product ID: Unknown Non-Volatile Size: None Volatile Size: 8 GB Cache Size: None Logical Size: None
  3. Yes full Plex hardware transcoding on QSV, will keep like this until the next stable version of Unraid ships. It sounds like Linux kernel 5.16.x has big updates for the i915 iGPU driver so fingers crossed that the next stable version of Unraid 6.10 ships with this. 6.9.2 is the current stable release of Unraid.
  4. this was my solution that allows full Plex hardware transcoding on QSV- linking here just in case it helps:
  5. I'm been doing a bunch of testing after replacing my Xeon E5-2696v2 + GPU and Supermicro motherboard setup with a Z590 + i5-11400 combo using Quicksync and have arrived at a stable solution that allows me to hardware transcode with the latest Plex builds. I have issues with any Unraid release from 6.10.0-RC1 including RC2 and the latest test builds beyond that. Regardless of my setup including blacklisting i915 in favour of GPU Top I still have crashes when Plex uses hardware transcoding (incl current build 1.25.5.5492). My server will hang (no video, keyboard, mouse) and drop from the network. Requires hard reset. My solution: Unraid: 6.9.2 Plex 1.25.5.5492 config/modprobe.d/i915.conf = options i915 force_probe=4c8b no GPU top or GPU statistics installed My force_probe=4c8b because when I tried 4c8a I got a message in dmesg that told me to use 4c8b instead. My CPU config is below for reference. Hope this helps someone - this was very frustrating going from an incredibly stable Xeon build to an i5-11400 and having unpredictable crashes without anything in the logs. Cheers! Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 12 On-line CPU(s) list: 0-11 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 167 Model name: 11th Gen Intel(R) Core(TM) i5-11400 @ 2.60GHz Stepping: 1 CPU MHz: 4203.711 CPU max MHz: 4400.0000 CPU min MHz: 800.0000 BogoMIPS: 5184.00 Virtualization: VT-x L1d cache: 288 KiB L1i cache: 192 KiB L2 cache: 3 MiB L3 cache: 12 MiB NUMA node0 CPU(s): 0-11 Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled v ia prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Enhanced IBRS, IBPB conditional, RS B filling Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtr r pge mca cmov pat pse36 clflush dts acpi mmx f xsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rd tscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperf mperf tsc_known_freq pni pclmulqdq dtes64 monit or ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc _deadline_timer aes xsave avx f16c rdrand lahf_ lm abm 3dnowprefetch cpuid_fault invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_ adjust bmi1 avx2 smep bmi2 erms invpcid mpx avx 512f avx512dq rdseed adx smap avx512ifma clflus hopt intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku ospke avx512_vb mi2 gfni vaes vpclmulqdq avx512_vnni avx512_bit alg avx512_vpopcntdq rdpid fsrm md_clear flush_ l1d arch_capabilities
  6. I had exactly this happening with my SAS drives under 6.9.1 when I started using the SAS spindown plugin, see my post here: Same case, same backplane, but using SM motherboard with integrated HBA.
  7. Did you ever get any further with this - I'm trying to manually add Mysterium as a docker container but with little luck (openvpn doesn't start).
  8. Quick update - I uninstalled the SAS spin down plugin (as that was my only change apart from the the 6.9 -> 6.9.1 upgrade. Rebooted and no errors so far. Will leave for another couple of days and if no errors will reinstall the plugin to test
  9. I'm seeing almost identical error numbers on two ST4000NM0023 (via onboard LSI SAS2308 on Supermicro X9DRD-7LN4F) one day after updating to 6.9.1 and also one day after running a successful parity check (on 6.9.0 just prior to upgrading to 6.9.1) I've never seen issues with these drives before. Only other change was the installation of the SAS spin down plugin (which I'm now removing to test). Diags attached. preston-diagnostics-20210311-1519.zip
  10. Version: 6.8.0-rc5 Rebooted today and noticed this for the first time: Array is started No change if using incognito browser or clearing cache/cookies. Diags attached. Cheers. preston-diagnostics-20191125-2158.zip
  11. @Squid was correct - problem was faulty SATA power cable - in this case a molex to SATA converter. Thanks for your help!
  12. Thanks @johnnie.black - I rebooted between drive attempts. Agree, def hardware. Will progress +12hrs. Thanks for looking at my logs, cheers!
  13. Haven't done the reseat process yet - but I'm wondering why the whole rest of the array is running just fine, except when I rebuild drive 12. Lots of reads and writes going on to the other 11 drives just fine. Remember the second drive I tried was connected using completely different cabling, to a different HBA (motherboard based).
  14. Interesting - I've changed only one thing (with anything remotely to do with cabling, power, devices) in the last 6mths; plugged a NiMH battery charger into the same outlet that the server is plugged into. Did this about a week ago. Will try a rebuild again with that removed. Feels a bit like voodoo, but it is a cheap one sourced from Aliexpress. UPDATE: OK that wasn't the problem. Start getting write errors immediately when I start the array. Will power down and try to reseat everything tomorrow and report back.
  15. OK, after running unraid for years I've found something to stump me. I had a drive fail recently with write errors (drive 12/sdq) - giving the red cross in the drive list. I removed the drive from the array and ran an extended SMART test on it - which finished without error. I next ran a full pre-clear cycle (full read, full zero, full read) which also ran without error. I added the drive back into the array thinking the drive controller had maybe remapped some bad sectors and I was OK again (for now), only to have the rebuild fail on the drive with more write errors. Decided this drive really was bad so went to the store and purchased an identical WD Red 3TB drive. Conducted a full pre-clear cycle which it passed with flying colours. Added drive back into the array and it failed during rebuild with write errors. This replacement drive was added to a different controller (on-board vs LSI 9211-8i) with different SATA and power cables and mounted in a different chassis location. So now I'm completely stumped. Two drives, both that pre-clear just fine, both fail during rebuild in around the same place (~ 5%) with write errors (different sectors listed).The only commonality is that they are both in drive position 12 and seem to fail very early in the rebuild process. Anyone got any idea where I start troubleshooting this? No other issues with my array and unraid implementation; its been very stable for the last couple of years and normally has uptimes measured in many months at a time. Diagnostics attached. preston-diagnostics-20170527-1427.zip
  16. NZBGet is now updated to v17.0 but when I specify that version (or any of the testing versions) my container fails to compile from source. https://github.com/nzbget/nzbget/releases Latest version that works OK is v16.4. Any ideas?
  17. anyone see this with RC2 - WebGUI updates not working
  18. OK team, well now I'm really confused: My Win10 VM has gone from suspending at least once every 30 mins to running continuously all night. The ONLY change I have made in that time was the recreation of my docker.img file (size stayed the same) which does live on the same SSD's as my VM qcow2 files. Will keep monitoring but I don't understand how this could be related.
  19. Its not actually my cache drive - I've got a 4TB WD RED that I use for cache (2TB+ free at any time) and a couple SSD's mounted with unassigned devices that hold the VM and appdata files. So don't expect any large temp data to be hitting that SSD. Will do a new Win 10 VM install and see if behaviour is same. Attached a full view (with SN's removed) :-)
  20. Yep - that was my first guess, but nope: https://goo.gl/photos/AcetDXn5Gatck3Qn8
  21. Grasping at straws you see - sometimes regular PC BIOS have these settings that can override Windows config. And I've done all of the wiki items prior to original post.
  22. Tried this - no change. See my original post :-)