Jump to content

JorgeB

Moderators
  • Posts

    61,692
  • Joined

  • Last visited

  • Days Won

    650

Everything posted by JorgeB

  1. Due to all the fs errors recommend reformatting, or you will likely run into issues again soon.
  2. No assuming you've only copied the bz* files. Those suggest previous flash drive issues, better to format and recreate, backup before.
  3. Delete/rename /boot/config/network.cfg and network-rules.cfg and reboot, settings will go back to default, which is a bond with all NICs and DHCP.
  4. Check filesystem on disk12, are you sure disk13 had a filesystem before? No valid filesystem is being detected, and even forcing xfs doesn't work meaning it's not xfs, or it's not there any more.
  5. Syslog is lost after every reboot, if it happens again either get the syslog at least before rebooting, if the full diags are not possible, or enable the syslog server and post that.
  6. No, you only need to assign disk5 as parity, assuming the other ones are correctly assigned.
  7. It won't delete anything, as long as you don't format the pool after start if it doesn't mount, as for recovering depends on the situation.
  8. You can do a read-only check, but even if nothing is detected it might happen again.
  9. Recommend swapping/replacing cables/slot to rule that out if it happens again to the same disk.
  10. Unfortunately there's nothing relevant logged, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, 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.
  11. Should be, start the array in normal mode.
  12. That sounds more like it, and normal for the disk size.
  13. Never seen that error before, suggest backing up and recreating the filesystem.
  14. It's basically the same if there are no or few sync errors, much slower if there are many, in that case cancel and do a sync.
  15. Make sure it's using a USB 2.0 port, if you want to replace it: https://wiki.unraid.net/Manual/Changing_The_Flash_Device#Overview
  16. I though you meant after rebooting, old syslog does show what look like flash drive problems.
  17. New config might work or not depending on the enclosures used, some USB enclosures don't have a transparent USB bridge, i.e. the data will be completely different without it. This would be an issue, parity2 is calculated in a different way, so they are not interchangeable.
  18. Emulated Disk1 mounted, if contents look correct you can rebuild on top, after that's done repeat for the remaining unmountable disks, one at a time.
  19. You must have or the array disks wound not be green, this might make recovery more difficult, but do another new config, keep all assignments, then check "parity is already valid" and "maintenance mode" then start the array, then stop array, unassign disk1 and start array, in normal mode now, then post new diags.
  20. Did you start the array after the new config?
  21. That will work, just don't add it a s new disk without doing a new config since it would be wiped. Yep.
×
×
  • Create New...