Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,867

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    In that case it's not possible to rebuild the other disk since parity will no longer be valid with it, which disk is this?
  2. JorgeB
    If I understood correctly one of the clients still works with v6.11?
  3. JorgeB
    Looks like a board problem, swap parity with the disk1 using SATA1 and see if Unraid detects parity and not the other disk.
  4. JorgeB
    Then it's not an iGPU problem, did you try Unraid v6.10.3 to see if there's any difference?
  5. JorgeB
    It's not taking, which of those disks is parity?
  6. JorgeB
    Try swapping both the power and SATA cables with an existing disk, then see if the issue follows the disk.
  7. JorgeB
    Still in IDE mode: 00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller [1002:439c] Subsystem: ASUSTeK Computer Inc. SB7x0/SB8x0/SB9x0 IDE Controller [1043:834e] Kernel driver in use: pata_atiixp Kernel modules: pata_atiixp
  8. JorgeB
    Yep.
  9. JorgeB
    Type in the Ubuntu console: lspci -nn It will list all the devices, then note the vendor/device ID from the iGPU, example: Then edit /syslinux/syslinux.cfg on the Unraid flash drive and add the correct vendor/device ID to the append line vfio-pci.ids=xxxx:xxxx, example label Unraid OS menu default kernel /bzimage append initrd=/bzroot Becomes label Unraid OS menu default kernel /bzimage append initrd=/bzroot vfio-pci.ids=1002:515e The see if the boots.
  10. JorgeB
    There are 2 ports from the onboard SATA controller set to IDE, go to the board BIOS and change them to AHCI/SATA, then post new diags.
  11. JorgeB
    Those files/folders are for the dockers you have installed, they are not stock, you should ask for help in the appropriate docker support thread, assuming one exists, you can click on the docker for the link.
  12. JorgeB
    It should stick, but do this instead: -start array in maintenance mode: -in the console type xfs_repair -v /dev/md2 If and only if it asks for -L type xfs_repair -vL /dev/md2 When done start the array in normal mode and post new diags.
  13. JorgeB
    Stop the array, click on disk2 and change the filesystem from "auto" to "xfs", then check filesystem on the emulated disk2.
  14. JorgeB
    Please post new diags after booting Unraid.
  15. JorgeB
    Now unassign disk2, start the array in normal mode and post new diags.
  16. JorgeB
    AFAIK there's no config.yml for dockers in the stock Unraid install, what is the path to that file?
  17. JorgeB
    Disk6 dropped offline so there's no SMART report, when you swapped the port did you swap the cables also? Disk1 is also showing what look like power/connection issues.
  18. JorgeB
    Lets see if @bonienlcan take a look, not my area of expertize.
  19. JorgeB
    If you cannot cancel the check type "powerdown" in the console, if it doesn't shutdown after 5 minutes o so you'll need to force it, then check/replace cables on disk3 and post new diags after array start.
  20. JorgeB
    It's not the identifiers it's the nsdi Because the kernel in v6.10 didn't check that, newer kernel does, like mentioned Tom created a quirk for a different device, I'm sure he can do the same for yours, but it's still a device problem.
  21. JorgeB
    Difficult for me to say if that's software or hardware, one thing you can try is to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  22. JorgeB
    Sep 28 15:40:38 unraid kernel: nvme nvme0: globally duplicate IDs for nsid 1 This is a device problem, and a "quirk" needs to be added to the kernel, LT did it for another device before, they might be able to do it for yours, but it's still a device problem: https://lore.kernel.org/all/[email protected]/t/
  23. JorgeB
    Double check you're doing it correctly following the instructions linked above, you could also bind the the iGPU to VFIO-PCI, but since Unraid doesn't boot you'd need to boot with a different Linux to get the device list.
  24. JorgeB
    Please post the diagnostics from v6.11.0
  25. JorgeB
    You should cancel the rebuild, replace the cable and start over, since there's no other parity drive the sectors where the read errors happened will be skipped in the rebuilt disk, resulting in data corruption, assuming they had data.
×
×
  • Create New...