Jump to content

JorgeB

Moderators
  • Posts

    67,880
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Are you sure the NVMe is dead? It might just have dropped, if you want us to take a look post the diagnostics.
  2. Adaptec controller crashed: Nov 4 13:16:18 Tower kernel: aacraid: Host bus reset request. SCSI hang ? Nov 4 13:16:18 Tower kernel: aacraid 0000:09:00.0: Adapter health - -3 Nov 4 13:16:18 Tower kernel: aacraid 0000:09:00.0: outstanding cmd: midlevel-8 Nov 4 13:16:18 Tower kernel: aacraid 0000:09:00.0: outstanding cmd: lowlevel-0 Nov 4 13:16:18 Tower kernel: aacraid 0000:09:00.0: outstanding cmd: error handler-0 Nov 4 13:16:18 Tower kernel: aacraid 0000:09:00.0: outstanding cmd: firmware-1 Nov 4 13:16:18 Tower kernel: aacraid 0000:09:00.0: outstanding cmd: kernel-0 Nov 4 13:16:18 Tower kernel: aacraid 0000:09:00.0: Controller reset type is 3 Nov 4 13:16:18 Tower kernel: aacraid 0000:09:00.0: Issuing IOP reset Nov 4 13:17:33 Tower kernel: aacraid 0000:09:00.0: IOP reset failed Nov 4 13:17:33 Tower kernel: aacraid 0000:09:00.0: ARC Reset attempt failed Start by rebooting and post new diags after array start.
  3. Don't see any logged docker start attempt, did you try rebooting?
  4. Mainly not indicating a file path, this is how it looks when it's data: Oct 6 09:30:20 Test kernel: BTRFS warning (device md1): checksum error at logical 8981135360 on dev /dev/md1, sector 18000032, root 5, inode 266, offset 739328000, length 4096, links 1 (path: ISOS/Windows.10.ISO) Oct 6 09:30:20 Test kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 0, flush 0, corrupt 330, gen 0
  5. That suggests the problem is with metadata, in that case best to backup everything you can and re-format the pool.
  6. You can enable repair but at least some blocks will not be repairable.
  7. You can do it using the GUI, click on cache and scroll down.
  8. IIRC one of my server did this if I started with a new Unraid install, if I have the time during the weekend I'll see if I can find anything that helps.
  9. Unfortunately there's nothing relevant logged that I can see, this usually suggest a hardware problem, one thing you can try is to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a while, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  10. Try replacing the flash drive.
  11. Balance aborted because it found some data corruption, run a scrub then look for the affected files in the syslog, delete/restore from backups those and run another balance.
  12. This sometimes happens with some hardware combinations, unfortunately not yet clear why, try connecting the Mellanox in a different PCI slot if available, also change something in the network setting so that that network.cfg gets recreated, then delete it again and reboot.
  13. Make sure there no other stale windows opened to the GUI, other than that not really sure what could cause this.
  14. If it's a different drive there won't be a SMART report, but looks like the other one was also failing.
  15. Nginx is having memory issues, do you have a browser window opened on an Android device? They are known to cause issues if left open when the device is sleeping.
  16. Nov 3 19:11:41 Tower emhttpd: unclean shutdown detected Some sync errors are normal after an unclean shutdown, just correct them.
  17. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480419 If it's a device failure you just need to replace it. You must use the 'degraded' mount option: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
×
×
  • Create New...