Jump to content

JorgeB

Moderators
  • Posts

    67,572
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Some have successfully used UFS explorer. I did make a request for that, but It won't mess up parity, you'd need to stop or wait for the rebuild to end, do a new config to re-enable disk7 and disable disk4 and repeat the rebuild, you should recover 100% of the data (if done before changing any data in the array).
  2. If it happens again grab and post the diagnostics before rebooting.
  3. Unraid can do it one disk at a time, ZFS can't, if using mirrors you might be able to remove the top-level vdev (if you have enough space in the reaming one), won't be able to remove raidz vdevs.
  4. This is somewhat normal but usually only last for a couple of seconds, it can last much longer with large amounts of RAM, you can decrease the amount of RAM used for write cache, 20% free RAM is the default. Also look into enabling turbo write for the initial load, it should go much faster.
  5. That's not the problem, check that sleep/hibernation is disable in the VM.
  6. Please post the diagnostics: Tools -> Diagnostics
  7. Please post the diagnostics: Tools -> Diagnostics
  8. Not likely, several possible reasons for that, start with booting in safe mode and see if shutdown works normally.
  9. Flash drive dropped offline, try a different port/controller (USB 2.0 preferred), if it keeps happening try a different flash drive.
  10. One them starts with Macvlan call traces, those are usually the result of having dockers with a custom IP address, see below and if that doesn't help they are still probably LAN related so try to simplify your network config as much as possible.
  11. Not sure if UD supports optical drives, but the place to ask is below:
  12. It failed, so the disk should be replaced.
  13. Yes, but the VM will be in a crash consistent state, since it wasn't shutdown at the time of the backup.
  14. There's something mounting disk1 before the array: Jan 17 17:06:58 MirinServer kernel: XFS (sde1): Mounting V5 Filesystem Jan 17 17:06:58 MirinServer emhttpd: shcmd (3): /usr/local/emhttp/webGui/scripts/update_access Jan 17 17:06:58 MirinServer sshd[1887]: Received signal 15; terminating. Jan 17 17:06:59 MirinServer kernel: XFS (sde1): Ending clean mount Then it cant be mounted again: Jan 17 17:07:05 MirinServer kernel: XFS (md1): Filesystem has duplicate UUID eb78e917-4f51-464e-8114-d251dc7845f5 - can't mount
  15. Please start your own thread, also attach the syslog/diags instead of pasting.
  16. Macvlan call traces are usually the result of having dockers with a custom IP address, more info here:
  17. It's logged as an actual disk error, but it might be intermittent, run an extended SMART test
  18. That's expected, unless you have dual parity. The best chance of recovering would be to force disable disk4 and rebuilt it again, but if you moved the data from the old disk it's too late now.
  19. If you haven't yet try a different port on the cable, or a new cable if available, also check power.
  20. Try the IPMI plugin instead, should be able to get all temps.
  21. Check the share split level, it will override allocation method, also there needs to be an appropriate minimum free space set.
×
×
  • Create New...