Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

blackb0x13

Members
  • Joined

  • Last visited

Everything posted by blackb0x13

  1. it probably isnt, i agree. it does allow me access however. i was able to mount the drive and im moving stuff off it as it allows. then ill trigger a parity check maybe and go from there. i still dont know how it happened but like i said, ill replace the cables once im back home and report another diagnostics.
  2. the system so far has been up for 36 hours, when i get back next saturday i will replace the cables and i will follow up then. thanks!
  3. tower-diagnostics-20260411-0831.zipive attached my diagnostics. so the system is up BUT i had to do a new config and stated that the parity was correct. i however didnt add the sus bad drive. im not sure how to proceed now with one bad 20tb, one new 22tb drive. i rather not buy yet another drive. i thought about using unassigned devises and moving stuff off the drive. if im able to. thanks for the help
  4. sunday night, i noticed that there was a disk that was emulated. so i jump and ordered a new disk, unfortunately, it was 22tb vs the required 20tb, which 20tb is my largest and my parity. so i put the new drive it and unraid wants to copy the parity. the parity copies but i noticed there was another disk missing so i reboot and F me, it wants to copy again, im now at nearly 50 hours of copying. now, this morning at 3am, i get up and notice its done so i start the array and it gets stuck in mounting disks. my logs are full of this " 2026-04-10T19:16:46-04:00 Tower kernel: md: disk0 read error, sector=3907839696 2026-04-10T19:16:46-04:00 Tower kernel: md: disk0 read error, sector=3907839696 2026-04-10T19:16:46-04:00 Tower kernel: md: disk0 read error, sector=3907840168" im unsure what to do now. nothing seems to respond and seems that it wont accept the previous parity disk now. im unsure what direction to go now and any help will be welcomed.
  5. yeah there is no bios update and it does seem to happen with the GPU or anytime the GPU gets accessed for any reason like nvtop or nvidia-smi or even the GPU plug in the dashboard. not sure how to further troubleshoot the issue.
  6. i changed my motherboard to an asus z790 with the latest bios. i have a 3070ti installed on the top slot and an lsi16 installed underneath. im using immich. during boot up AND when i just uploaded a video from my phone to immich, the syslog spat this out: 2026-01-22T15:28:02-05:00 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) 2026-01-22T15:28:02-05:00 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477) 2026-01-22T15:28:02-05:00 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529) i have been back and forth with the motherboard settings, but the latest according the google is to append the syslinux config under unraid OS from "append initrd=/bzroot" to "append initrd=/bzroot acpi_osi="Windows 2020"" not really sure what this is and i dont want to mess around too much on the OS side till i know more. ill mess with the bios all day. other log snippets: root@Tower:~# dmesg | grep ACPI [ 0.000000] BIOS-e820: [mem 0x000000007099c000-0x0000000070bebfff] ACPI data [ 0.000000] BIOS-e820: [mem 0x0000000070bec000-0x0000000070e1efff] ACPI NVS [ 0.000000] reserve setup_data: [mem 0x000000007099c000-0x0000000070bebfff] ACPI data [ 0.000000] reserve setup_data: [mem 0x0000000070bec000-0x0000000070e1efff] ACPI NVS [ 0.000000] efi: ACPI=0x70beb000 ACPI 2.0=0x70beb014 TPMFinalLog=0x70d0c000 SMBIOS=0x73401000 SMBIOS 3.0=0x73400000 MEMATTR=0x69a6e818 ESRT=0x69c52218 RNG=0x70b32c18 TPMEventLog=0x70a27018 [ 0.004996] ACPI: Early table checksum verification disabled [ 0.004997] ACPI: RSDP 0x0000000070BEB014 000024 (v02 ALASKA) [ 0.004999] ACPI: XSDT 0x0000000070BEA728 00010C (v01 ALASKA A M I 01072009 AMI 01000013) [ 0.005002] ACPI: FACP 0x0000000070BE9000 000114 (v06 ALASKA A M I 01072009 AMI 01000013) [ 0.005005] ACPI: DSDT 0x0000000070B48000 0A0126 (v02 ALASKA A M I 01072009 INTL 20200717) [ 0.005007] ACPI: FACS 0x0000000070E1E000 000040 [ 0.005008] ACPI: FIDT 0x0000000070B47000 00009C (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.005010] ACPI: SSDT 0x0000000070B45000 00038C (v02 PmaxDv Pmax_Dev 00000001 INTL 20200717) [ 0.005012] ACPI: SSDT 0x0000000070B3F000 005D34 (v02 CpuRef CpuSsdt 00003000 INTL 20200717) [ 0.005013] ACPI: SSDT 0x0000000070B3C000 002D13 (v02 SaSsdt SaSsdt 00003000 INTL 20200717) [ 0.005015] ACPI: SSDT 0x0000000070B38000 00334F (v02 INTEL IgfxSsdt 00003000 INTL 20200717) [ 0.005017] ACPI: HPET 0x0000000070B37000 000038 (v01 ALASKA A M I 01072009 AMI 01000013) [ 0.005018] ACPI: APIC 0x0000000070B36000 0001DC (v05 ALASKA A M I 01072009 AMI 01000013) [ 0.005020] ACPI: MCFG 0x0000000070B35000 00003C (v01 ALASKA A M I 01072009 AMI 01000013) [ 0.005021] ACPI: SSDT 0x0000000070B33000 001F1A (v02 ALASKA Ther_Rvp 00001000 INTL 20200717) [ 0.005023] ACPI: NHLT 0x0000000070B31000 00002D (v00 ALASKA A M I 01072009 AMI 01000013) [ 0.005025] ACPI: LPIT 0x0000000070B30000 0000CC (v01 ALASKA A M I 01072009 AMI 01000013) [ 0.005026] ACPI: SSDT 0x0000000070B2C000 002357 (v02 ALASKA TbtTypeC 00000000 INTL 20200717) [ 0.005028] ACPI: SSDT 0x0000000070B29000 002A83 (v02 ALASKA PtidDevc 00001000 INTL 20200717) [ 0.005029] ACPI: DBGP 0x0000000070B28000 000034 (v01 ALASKA A M I 01072009 AMI 01000013) [ 0.005031] ACPI: DBG2 0x0000000070B27000 000054 (v00 ALASKA A M I 01072009 AMI 01000013) [ 0.005033] ACPI: SSDT 0x0000000070B26000 000C1F (v02 ALASKA UsbCTabl 00001000 INTL 20200717) [ 0.005034] ACPI: DMAR 0x0000000070B25000 000088 (v01 INTEL EDK2 00000002 01000013) [ 0.005036] ACPI: FPDT 0x0000000070B24000 000044 (v01 ALASKA A M I 01072009 AMI 01000013) [ 0.005037] ACPI: SSDT 0x0000000070B22000 001D9C (v02 INTEL xh_rps14 00000000 INTL 20200717) [ 0.005039] ACPI: SSDT 0x0000000070B1E000 0039DA (v02 SocGpe SocGpe 00003000 INTL 20200717) [ 0.005041] ACPI: SSDT 0x0000000070B1A000 0039DA (v02 SocCmn SocCmn 00003000 INTL 20200717) [ 0.005042] ACPI: UEFI 0x0000000070C5D000 00063A (v01 INTEL RstVmdE 00000000 INTL 00000000) [ 0.005044] ACPI: UEFI 0x0000000070C5C000 00005C (v01 INTEL RstVmdV 00000000 INTL 00000000) [ 0.005045] ACPI: BGRT 0x0000000070B19000 000038 (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.005047] ACPI: WPBT 0x0000000070A30000 000040 (v01 ALASKA A M I 00000001 ASUS 00000001) [ 0.005048] ACPI: TPM2 0x0000000070A2F000 00004C (v04 ALASKA A M I 00000001 AMI 00000000) [ 0.005050] ACPI: PHAT 0x0000000070A2E000 0005F1 (v01 ALASKA A M I 00000005 MSFT 0100000D) [ 0.005052] ACPI: WSMT 0x0000000070B2F000 000028 (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.005053] ACPI: Reserving FACP table memory at [mem 0x70be9000-0x70be9113] [ 0.005054] ACPI: Reserving DSDT table memory at [mem 0x70b48000-0x70be8125] [ 0.005054] ACPI: Reserving FACS table memory at [mem 0x70e1e000-0x70e1e03f] [ 0.005055] ACPI: Reserving FIDT table memory at [mem 0x70b47000-0x70b4709b] [ 0.005056] ACPI: Reserving SSDT table memory at [mem 0x70b45000-0x70b4538b] [ 0.005056] ACPI: Reserving SSDT table memory at [mem 0x70b3f000-0x70b44d33] [ 0.005057] ACPI: Reserving SSDT table memory at [mem 0x70b3c000-0x70b3ed12] [ 0.005057] ACPI: Reserving SSDT table memory at [mem 0x70b38000-0x70b3b34e] [ 0.005058] ACPI: Reserving HPET table memory at [mem 0x70b37000-0x70b37037] [ 0.005058] ACPI: Reserving APIC table memory at [mem 0x70b36000-0x70b361db] [ 0.005059] ACPI: Reserving MCFG table memory at [mem 0x70b35000-0x70b3503b] [ 0.005059] ACPI: Reserving SSDT table memory at [mem 0x70b33000-0x70b34f19] [ 0.005060] ACPI: Reserving NHLT table memory at [mem 0x70b31000-0x70b3102c] [ 0.005060] ACPI: Reserving LPIT table memory at [mem 0x70b30000-0x70b300cb] [ 0.005061] ACPI: Reserving SSDT table memory at [mem 0x70b2c000-0x70b2e356] [ 0.005061] ACPI: Reserving SSDT table memory at [mem 0x70b29000-0x70b2ba82] [ 0.005062] ACPI: Reserving DBGP table memory at [mem 0x70b28000-0x70b28033] [ 0.005063] ACPI: Reserving DBG2 table memory at [mem 0x70b27000-0x70b27053] [ 0.005063] ACPI: Reserving SSDT table memory at [mem 0x70b26000-0x70b26c1e] [ 0.005064] ACPI: Reserving DMAR table memory at [mem 0x70b25000-0x70b25087] [ 0.005064] ACPI: Reserving FPDT table memory at [mem 0x70b24000-0x70b24043] [ 0.005065] ACPI: Reserving SSDT table memory at [mem 0x70b22000-0x70b23d9b] [ 0.005065] ACPI: Reserving SSDT table memory at [mem 0x70b1e000-0x70b219d9] [ 0.005066] ACPI: Reserving SSDT table memory at [mem 0x70b1a000-0x70b1d9d9] [ 0.005066] ACPI: Reserving UEFI table memory at [mem 0x70c5d000-0x70c5d639] [ 0.005067] ACPI: Reserving UEFI table memory at [mem 0x70c5c000-0x70c5c05b] [ 0.005067] ACPI: Reserving BGRT table memory at [mem 0x70b19000-0x70b19037] [ 0.005068] ACPI: Reserving WPBT table memory at [mem 0x70a30000-0x70a3003f] [ 0.005068] ACPI: Reserving TPM2 table memory at [mem 0x70a2f000-0x70a2f04b] [ 0.005069] ACPI: Reserving PHAT table memory at [mem 0x70a2e000-0x70a2e5f0] [ 0.005069] ACPI: Reserving WSMT table memory at [mem 0x70b2f000-0x70b2f027] [ 0.078455] ACPI: PM-Timer IO Port: 0x1808 [ 0.078460] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.078461] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [ 0.078461] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [ 0.078461] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [ 0.078462] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [ 0.078462] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [ 0.078463] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [ 0.078463] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) [ 0.078463] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) [ 0.078464] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) [ 0.078464] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) [ 0.078464] ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) [ 0.078465] ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) [ 0.078465] ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) [ 0.078466] ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) [ 0.078466] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1]) [ 0.078466] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1]) [ 0.078467] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1]) [ 0.078467] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1]) [ 0.078467] ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1]) [ 0.078468] ACPI: LAPIC_NMI (acpi_id[0x15] high edge lint[0x1]) [ 0.078468] ACPI: LAPIC_NMI (acpi_id[0x16] high edge lint[0x1]) [ 0.078469] ACPI: LAPIC_NMI (acpi_id[0x17] high edge lint[0x1]) [ 0.078469] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [ 0.078514] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.078515] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.078518] ACPI: Using ACPI (MADT) for SMP configuration information [ 0.078518] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.172091] ACPI: Core revision 20240827 [ 0.191711] ACPI: PM: Registering ACPI NVS region [mem 0x70bec000-0x70e1efff] (2306048 bytes) [ 0.192286] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 0.259334] ACPI: Added _OSI(Module Device) [ 0.259335] ACPI: Added _OSI(Processor Device) [ 0.259336] ACPI: Added _OSI(Processor Aggregator Device) [ 0.290171] ACPI: 12 ACPI AML tables successfully acquired and loaded [ 0.295910] ACPI: Dynamic OEM Table Load: [ 0.295916] ACPI: SSDT 0xFFFF8881016C3000 000394 (v02 PmRef Cpu0Cst 00003001 INTL 20200717) [ 0.296488] ACPI: Dynamic OEM Table Load: [ 0.296492] ACPI: SSDT 0xFFFF8881019DA800 000689 (v02 PmRef Cpu0Ist 00003000 INTL 20200717) [ 0.297097] ACPI: Dynamic OEM Table Load: [ 0.297100] ACPI: SSDT 0xFFFF88810198A600 0001AB (v02 PmRef Cpu0Psd 00003000 INTL 20200717) [ 0.297645] ACPI: Dynamic OEM Table Load: [ 0.297648] ACPI: SSDT 0xFFFF8881019DB000 0004B5 (v02 PmRef Cpu0Hwp 00003000 INTL 20200717) [ 0.298321] ACPI: Dynamic OEM Table Load: [ 0.298325] ACPI: SSDT 0xFFFF8881019E0000 001BAF (v02 PmRef ApIst 00003000 INTL 20200717) [ 0.299179] ACPI: Dynamic OEM Table Load: [ 0.299183] ACPI: SSDT 0xFFFF8881019E2000 001038 (v02 PmRef ApHwp 00003000 INTL 20200717) [ 0.299925] ACPI: Dynamic OEM Table Load: [ 0.299929] ACPI: SSDT 0xFFFF8881019E4000 001349 (v02 PmRef ApPsd 00003000 INTL 20200717) [ 0.300708] ACPI: Dynamic OEM Table Load: [ 0.300711] ACPI: SSDT 0xFFFF8881016CA000 000FBB (v02 PmRef ApCst 00003000 INTL 20200717) [ 0.305244] ACPI: Interpreter enabled [ 0.305259] ACPI: PM: (supports S0 S3 S5) [ 0.305260] ACPI: Using IOAPIC for interrupt routing [ 0.305278] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.305834] ACPI: Enabled 6 GPEs in block 00 to 7F [ 0.313541] ACPI: \_SB_.PC00.XHCI.RHUB.HS14.PRBT: New power resource [ 0.317826] ACPI: \_SB_.PC00.CNVW.WRST: New power resource [ 0.323644] ACPI: \_TZ_.FN00: New power resource [ 0.323672] ACPI: \_TZ_.FN01: New power resource [ 0.323699] ACPI: \_TZ_.FN02: New power resource [ 0.323724] ACPI: \_TZ_.FN03: New power resource [ 0.323749] ACPI: \_TZ_.FN04: New power resource [ 0.324102] ACPI: \PIN_: New power resource [ 0.324269] ACPI: PCI Root Bridge [PC00] (domain 0000 [bus 00-e0]) [ 0.335465] ACPI: PCI: Interrupt link LNKA configured for IRQ 0 [ 0.335498] ACPI: PCI: Interrupt link LNKB configured for IRQ 1 [ 0.335531] ACPI: PCI: Interrupt link LNKC configured for IRQ 0 [ 0.335564] ACPI: PCI: Interrupt link LNKD configured for IRQ 0 [ 0.335596] ACPI: PCI: Interrupt link LNKE configured for IRQ 0 [ 0.335628] ACPI: PCI: Interrupt link LNKF configured for IRQ 0 [ 0.335660] ACPI: PCI: Interrupt link LNKG configured for IRQ 0 [ 0.335692] ACPI: PCI: Interrupt link LNKH configured for IRQ 0 [ 0.339295] ACPI: bus type USB registered [ 0.339408] PCI: Using ACPI for IRQ routing [ 0.358760] pnp: PnP ACPI init [ 0.361057] pnp: PnP ACPI: found 7 devices [ 76.375377] ACPI: button: Sleep Button [SLPB] [ 76.376486] ACPI: button: Power Button [PWRB] [ 76.381736] ACPI: button: Power Button [PWRF] [ 76.387121] ACPI: thermal: Thermal Zone [TZ00] (28 C) [ 76.435149] ACPI: bus type drm_connector registered [ 76.922781] ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 125.260780] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) [ 125.260786] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477) [ 125.260788] ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529) [ 125.354507] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) [ 125.354511] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477) [ 125.354512] ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529) [ 307.716223] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) [ 307.716228] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477) [ 307.716230] ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529) [ 309.418262] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) [ 309.418269] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477) [ 309.418271] ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529) [ 311.069465] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) [ 311.069471] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477) [ 311.069472] ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529) [ 327.640256] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) [ 327.640261] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477) [ 327.640263] ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529) [ 329.311772] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) [ 329.311777] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477) [ 329.311779] ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529) [ 330.988571] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) [ 330.988577] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477) [ 330.988578] ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529) [ 1703.452273] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) [ 1703.452279] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477) [ 1703.452280] ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529)
  7. attached is log from kodi. kodi.log
  8. So, has anyone had an issue where Kodi will no longer play any files using the jellyfin add on? It was working fine but today it said there was an error and nothing plays anymore.
  9. hey sorry for the ridiculously late reply. I have moved the LSI card to the other slot and limited the speed in the bios for PCIE4 which hasnt caused any issues, however, did you mean this "pcie_aspm=off " from your post?
  10. another note. the second i posted this (of course) it shot up to over 142.3mb.... then it froze. system is no longer responding so i shut it down via the power button and moved the LSI card to different slot. data rebuild started again @ 3.9 mbs. new diagnostics posted added. tower-diagnostics-20240131-1432.zip
  11. I upgraded the hardware and im now using a Gigabyte B760M-C, intel i7 14700k and 64 gigs of ram. For a while now I've had a disk thats shown SMART errors and i finally got a drive via RMA that works (2 previous DOE) Im using a Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (9600i-16 flashed IT) Currently, my rebuild is going @ 4.1mb a sec, 27 days to go 😵 I been searching the forums and i've done a few things, one, check bios for PIC speeds, so far ive done 4.0, 3.0 and auto with no difference in speeds. Ive changed physical PCI-E ports and im using the recommended port for a GPU according to the gigabyte but i also tried the second PCI port. This port, upon boot, gives me a ton of errors, here a copy+paste from the log. "Jan 31 07:48:07 Tower kernel: pcieport 0000:01:00.0: [ 0] RxErr Jan 31 07:48:07 Tower kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:01:00.0 Jan 31 07:48:07 Tower kernel: pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jan 31 07:48:07 Tower kernel: pcieport 0000:01:00.0: device [10b5:8724] error status/mask=00000001/0000a000" this error seems to fill up my log but the system still boots (FCP warns me of this - /var/log is getting full (currently 100 % used) The supposed "slower" port that would only run @ 4x didnt give me any errors. Theres no way i can wait a month almost and hope there arent any power issues, or anything else, that would cause me not to have to start the data rebuild all over. To note, i still have the drive with errors, just no connected. Help? tower-diagnostics-20240131-1412.zip
  12. probably just one VM to start with. i was actually thinking between an i5/7. when time comes, i will check prices and go from there i guess.
  13. Greetings all. Long time a forum stalker and Unraid user. Currently, I'm using: ASRock A75M-HVS/ AMD A8-3870 with 8 gigs of DDR3. Other notable hardware is an LSI-9300-16i with 14 drives with cache and parity (68tb) and I plan to add 2 exos 18tb's soon, sitting on a Rosewill RSV-4500U case. Software-wise, I use the suite in 'arr apps, Jellyfin and a few other apps as well such as Krusader, Home Assistant, pihole (2nd DNS). One of my issues is that since my video file sizes are so big (some 60gig) for some movies, the current system struggles so push out multiple streams, and jellyfin crashes. I think the time has come on this 10+ year-old mobo/cpu/ram combo to be retired. I would like to use some VMs (windows maybe) and access it from any room in the house but I am unsure as to what else the future may hold. My plan is to upgrade to an Intel Gigabyte B760M C (https://www.amazon.com/dp/B0BZQ1PWGJ/?coliid=I2JWK4RTH1LTIX&colid=2AH9YPK86IMQO&psc=1&ref_=cm_sw_r_cp_ud_lstpd_5JD8TRAWE37CYA344S2C) and at least 32 gig of corresponding ram. Here is the part that I am unsure of... i want a CPU with integrated graphics (intel 770) and at first, i chose an i9. The price combined made me rethink the idea to an i7. Since my current system is so old with no GPU for transcoding, all my front ends can do the transcoding with the weakest being a simple cell phone, Nvidia shield, an Xbox and other HTPC's. Everything is, for the most part hard ethernet wired and I dont do any compression on my movies. I like that sweet bitrate when I use my almost/projector setup that being ran by the HTPC with a NTC 1660 6gig. The most video streams at one time may be 4. I guess I'm just torn between my CPU choices. Do I go crazy with an i9? will this be a waste? is i7 good enough? or is all this overkill and should I just stick with an i5? On another note, this upgrade should be made to last 5+ years as this hardware is currently 12 years old but only using it for unraid since 2016. Looking at at sub $700 budget for the mobo, cpu and ram combo but the lower, the higher the W.A.F Thoughts? Suggestions? Real world experience? thanks all!
  14. This is my concern actually.
  15. I have to do more research but seems that an x299 board may work with the right cpu. Looked at some server boards but it's way overpriced for my case use
  16. Any suggestions?
  17. Greetings, long time stalker, first time poster. Trying to keep this as short as possible; Currently I have a 14 drive array set up. I want to upgrade my hardware to allow the use of an Nvidia GPU for video transcoding on the fly. I want to use two (which I own but currently only using one) supermicro AOC-SAS2LP-MV8 SAS HBA. I would need 3 pci-e slots with the ones for the sas cards at 8x. Can't seem to find the right combination or verification that using all 3 pci-e slots (1@16x and 2@8x) would work. Looking to go Intel this time around. Any suggestions will be welcomed. Thanks!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.