Jump to content

JorgeB

Moderators
  • Posts

    67,092
  • Joined

  • Last visited

  • Days Won

    703

Everything posted by JorgeB

  1. By using a different one, but controller would be last thing to try, cables and/or PSU are more likely, it can also be the backplane/expander.
  2. You'll likely get "unmountable: unsupported partition layout" on all data disks, solution it to rebuild one disk at a time so Unraid recreates the partition, you can confirm by unassigning one disk and checking that the emulated disk mounts correctly before rebuilding on top.
  3. Check/replace cables, can also be the PSU, you'll need to test one thing at a time to rule them out.
  4. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=537383
  5. You should update both if an update is available. Same model/firmware will much likely have the same issues.
  6. Run a long SMART test on both disks, but more likely a controller/connection/power problem
  7. Ideally we'd want the diags before rebooting to see what happened, but the disabled disk looks fine and errors on two disks at the same time suggest more a connection/power issue, so check/replace cables and rebuild.
  8. Cache files system is corrupt, best bet it's to reformat, if it keeps getting corrupt you might have an underlying hardware problem, also note that because of this bug cache pool is not redundant.
  9. That's a giant badge!! I though they were the typical size.
  10. It can, supports dual link. Then likely parity wasn't in sync.
  11. Yes, like mentioned the only acceptable number of errors during memtest is 0.
  12. If the array is started without a cache device Unraid "forgets" cache config, so now you just need to assign it back, note that if libvirt.img was also on cache there was a new one created on the array, since it's set to /mnt/user.
  13. Still not acceptable, make sure RAM is not overclocked, it's known to cause issues with some Ryzen systems.
  14. Try de tunables tester scrip, default tunables are not very good for larger arrays, also note that if you're using a single link between the HBA and the expander max speed will be around 90MB/s, usu dual link if possible. These usually mean parity is not in sync, unless you're getting disk errors, is this 1st parity check?
  15. There's a constant problem with the HBA, make sure it's well seated, sufficiently cooled and not a fake Sep 22 05:45:07 Tower kernel: mpt3sas_cm0: fault_state(0x6004)!
  16. https://forums.unraid.net/topic/59375-hp-proliant-workstation-unraid-information-thread/ Scroll down to the ACPI section.
  17. Bios update might also help, if none of those work likely only a new board will.
  18. You might be able to still copy the data normally form the pool, using Krusader or any other toll, if you can't then see the recovery options.
  19. At that time there was an unclean shutdown detected: Aug 26 22:53:33 husky emhttpd: unclean shutdown detected Like mentioned this detection happens at boot time, it doesn't have anything to do with an aborted or not aborted parity check.
  20. The same would happen with dual parity, but during a rebuild with single parity Unraid has no way of calculating missing data if there are errors on another disk, so some data on disk2 will be corrupt, unless by luck those sectors don't have data.
  21. Yeah, this is the actual bullshit answer from Crucial support, it was posted by a FreeNAS user with the same problem on their forum: Which begs the question, if it's so normal why don't other Crucial models have this issue?
  22. Cache filesystem is corrupt with a fatal problem, you'll need to backup data and re-format, some recovery options here if needed.
  23. Yes, but parity sync will re-start from the beginning.
×
×
  • Create New...