Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,737

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    How did you run xfs_repair? Correct way is starting the array in maintenance mode then use the GUI or in the CLI (and since the problem is with disk4) type: xfs_repair -v /dev/md4
  2. JorgeB
    Depends on and how many dockers you have.
  3. JorgeB

    VM problem

    JorgeB replied to Mrobert's topic in General Support

    Not seeing any issue in the logs, try rebooting in safe mode and post new diags if it still doesn't work.
  4. JorgeB
    Those are normal.
  5. JorgeB
    It would also work.
  6. JorgeB
  7. JorgeB
    https://forums.unraid.net/topic/103938-69x-lsi-controllers-ironwolf-disks-disabling-summary-fix/?do=getNewComment
  8. JorgeB
    Correct, if the problem is serious enough it's easily caught, but even 48H without errors is no guarantee, still as close as you can get to rule that out.
  9. JorgeB
    Nothing that I can think of for now, good to run a stress test like a parity/read check when you have all the disks connected.
  10. JorgeB
    Looks fine now.
  11. JorgeB
    Yep, just boot needs to be in CSM/legacy mode, memtest that comes with Unraid won't work with UEFI boot.
  12. JorgeB
    You can reset the array to keep just the remaining good drives (tools -> new config), then start the array to begin a parity sync.
  13. JorgeB
    One thing I forgot to mention, if this issue started after an Unraid it should mount normally if you go back to the previous release, and this way easier to backup.
  14. JorgeB
    Yes. Yep, nothing to lose. Re-format. Yes, as long as everything is successfully copied.
  15. JorgeB
    No, devices are tracked by serial number.
  16. JorgeB
    That's expected, once a disk gets disabled it needs to be rebuilt, as long as the emulated disk is mounting and contents look correct you can rebuild on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  17. JorgeB
    Parity couldn't help with filesystem corruption anyway, please post diagnostics after array start.
  18. JorgeB
    That's a good idea, looks more like a hardware issue.
  19. JorgeB
    Enable the syslog server and post that after a crash, it may help showing what the problem is.
  20. JorgeB
    Yes, it's on purpose, they only auto-start after first boot.
  21. JorgeB
    Try updating to v6.10-rc2, some kernel/hardware combinations can sometimes have some issues.
  22. JorgeB
    Cache filesystem is going read-only: Jan 3 10:15:06 Utopia kernel: BTRFS: error (device nvme1n1p1) in cleanup_transaction:1942: errno=-28 No space left Jan 3 10:15:06 Utopia kernel: BTRFS info (device nvme1n1p1): forced readonly Likely from getting out of space before, best bet it to backup and re-format the pool, you should never completely fill up a COW filesystem like btrfs or zfs.
  23. JorgeB
    Try disabling Bluetooth in the board BIOS.
  24. JorgeB
    Logs are spammed with errors related to an unassigned NTFS device, because of that there are several hours missing.
  25. JorgeB
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=972660
×
×
  • Create New...