Jump to content

JorgeB

Moderators
  • Posts

    67,863
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Anyone with this issue see if this helps: https://forums.unraid.net/topic/128696-after-611-no-longer-can-access-smb-via-network/?do=findComment&comment=1174207
  2. For some reason your hardware doesn't like the new kernel, try again when there's a newer release witha different kernel, hopefully it works.
  3. Looks like a driver issue, no attempt to load it, hopefully fixed in a future kernel
  4. Please post the diagnostics after a backup attempt.
  5. Emulated disk is mounting now, check that contents look correct, also look for a lost+found folder and any lost files inside.
  6. Run it again without -n, if it asks for it use -L
  7. Try rebooting, if the same check that the key is present.
  8. Please post the diagnostics with the controller installed in Unraid to see the device IDs.
  9. I'm trying to investigate this issue, but to me not yet clear cut it's a Samba problem, it's working correctly for most users and for example for @DrQone of two Windows 11 clients works while the other does not, so the problem might be Unraid but it also might be the non working client.
  10. I asked LT to add a quirk for that model anyway, it's just a matter of time for another user to be using the same model.
  11. True, maybe not the same issue them, @ich777any idea since you're the one who found those links?
  12. This you'd be your best bet, to see if it's finishing to boot or not.
  13. Could be, especially if it shares a splitter/cable with disk1.
  14. Kernel module is there but no driver in use, this suggests it's not loading, there should be more info in the log.
  15. Disk looks mostly OK, emulated disk is not mounting, so check filesystem on it first.
  16. You'd need to have existing checksums, or be using btrfs, you can still try to rebuild disk4 instead, either way there will likely be some corruption, but depending on how much changed in the array it might be less that this, if the disk is really bad. You can also try ddrescue instead.
  17. Since disk6 looks healthy and there's no parity anyway I would suggest doing a new config to re-enable it: Tools -> New Config -> Keep all assignments -> Apply Then start the array, of course the array will be unprotected until you add a new parity.
  18. Are you really still on v5? Also please post the diagnostics (assuming you are on v6).
  19. If its not detected with knwon good cables/port it suggests a drive problem, but still don't like the board not working in all AHCI mode, especially considering that those AMD chipsets have known issues when the controller is set to IDE.
  20. Just wait to see if Tom can add that quirk to the next release, he's already following this thread, so no need for anything else for now, and if he needs more info he will ask for it.
  21. 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?
  22. If I understood correctly one of the clients still works with v6.11?
  23. Looks like a board problem, swap parity with the disk1 using SATA1 and see if Unraid detects parity and not the other disk.
  24. Then it's not an iGPU problem, did you try Unraid v6.10.3 to see if there's any difference?
×
×
  • Create New...