Jump to content

JorgeB

Moderators
  • Posts

    67,893
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. AFAIK nothing changed with that, please post the diagnostics from v6.11
  2. The docker image can be easily recreated, but you might also be missing some appdata content, do you have an appdata backup?
  3. See if this one works better: https://forums.unraid.net/topic/123638-unraid-6115-最新的r8125和r8152网卡驱动补丁/
  4. The Realtek Linux in tree driver stopped working since v6.10, you can use this custom driver posted by another user: https://forums.unraid.net/topic/123638-unraid-6115-最新的r8125和r8152网卡驱动补丁/
  5. Both disks look healthy, emulated disk3 is mounting, if contents look correct you can rebuild on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  6. I would start by creating a new stock v6.11.5 install on a different flash drive, no key needed, just to confirm it boots in normal mode and it's some config issue.
  7. Since the disks dropped offline there were no SMART reports, so post new diags now after array start, but the disks should be OK.
  8. Backup current flash drive, recreate using the USB tool or manually, restore the config folder from the backup.
  9. If you want to try again do it and if you see the same please post the diagnostics.
  10. Log is being spammed with these: Nov 21 15:25:59 Unraid kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184) Nov 21 15:25:59 Unraid kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477) This is a BIOS issue, look for a BIOS update.
  11. There's filesystem corruption on the NVMe device, best bet is to backup and re-format that filesystem.
  12. Don't understand what you mean but assuming you've copied from a user share to another, and not from a user share to a disk share or vice versa, if the data is missing not much you can do other than restore from a backups or use some file recovery util like UFS explorer.
  13. Copy the vdisk from the array back to cache replacing the old one.
  14. Parity2 also appears to be failing, disk3 looks OK, do you know if something was written to the emulated disk3 after it got disabled?
  15. What was the capacity of the other device?
×
×
  • Create New...