Jump to content

JorgeB

Moderators
  • Posts

    67,852
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Strange that all 3 disks had the same name "ARC-1222-VOL", not sure how that worked, I have no experience with Areca controllers, but no extra disks are being found, assuming they are connected they are not being passed-trough by the controller, you'd need to use the controller BIOS to pass-trough/initialize the disks, this might or not delete the data on the disks, though depending exactly on what's deleted it could still be possible to rebuild them one at a time.
  2. Your server doesn't have a NIC that use the tg3 driver, so it wouldn't be affected, also since v6.10.3 that issue is resolved for all servers, update to v6.10.3, enable the syslog server and post that after a crash.
  3. Docker image can also grow with time, use only what you really need.
  4. OK... but can you do that to test?
  5. Same from Please don't double post about the same thing.
  6. I see now, unfortunately there's nothing logged, could be this issue:
  7. Click on the link for instructions: syslog server
  8. Negative Ghost Rider, that syslog starts over after every reboot, syslog server might be able to catch what's crashing the server, if it's not hardware related.
  9. Not practical, you'd need to unassign cache to be able to mount with UD and even worse the configured paths would not be the same, if you had for example /mnt/cache/appdata or /mnt/user/appdata you'd need to change it to /mnt/disks/UD_label/appdata It does, you'd need to unassign the disk but would be able to mount it read-only with UD, of course there are no shares, it would be disk by disk.
  10. Copy the vdisk with cp --sparse=always /source /dest This will make it as small as possible, though it will grow with time if it's not trimmed.
  11. It could if it's not being trimmed, but not sure how to do that for Ubuntu VM, you could move the vdisk to the array temporarily to see if that is the problem., if it isn't start moving the other stuff, something is using that space, could be due to fragmented extents.
  12. If you have a Windows VM make sure the vdisk is being trimmed: https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606
  13. Sep 19 23:36:23 Coruscant kernel: XFS (md7): Internal error rec.ir_free != frec->ir_free || rec.ir_freecount != frec->ir_freecount at line 1558 of file fs/xfs/libxfs/xfs_ialloc.c. Caller xfs_dialloc_ag_update_inobt+0xd0/0x121 [xfs] Check filesystem on disk7.
  14. Do you know the time it last crashed? Not seeing anything relevant in the syslog.
  15. Enable turbo write and tranfer directly to the array, do you get the same or better speeds?
  16. On your Windows PC got to control panel - credentials and delete all stored credentials for the Unraid server, then reboot Windows and try again.
  17. No, you need to cancel or wait for it to end.
  18. See if you can download the complete diagnostics, if not get the syslog at least: cp /var/log/syslog /boot/syslog.txt
  19. Enable the syslog server and post that after a crash.
  20. Could just be some compatibility issue between the NIC and the board.
  21. There's nothing logged, assumed you followed the general Ryzen recommendations linked above there's likely some hardware issue, one more 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 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.
×
×
  • Create New...