Jump to content

JorgeB

Moderators
  • Posts

    67,871
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Try booting a different OS to rule out hardware issues, like Ubuntu or even Windows.
  2. Does it coincide with the logged lsof general protection faults? Stop all dockers and start enabling one by one, might help find the culprit.
  3. What was updated? Unraid itself is not updated automatically.
  4. It's the first Ryzen 7000 i see with Unraid, no idea if it's stable or not with current kernel, boot in safe mode and leave docker/VM services divisibled for for now, if it still crashes like that there might be issues with the hardware or kernel support.
  5. Disk dropped and reconnected again with a different identifier, could be power/connection problem, you should also update both HBAs firmware since it's quite old.
  6. Since it doesn't look like a disk problem there won't be anything on SMART showing that, it's normal if it's a power/connection issue.
  7. Read SMART Thresholds failed: scsi error medium or hardware error (serious) Try swapping cables with a different disk but looks like it's a goner.
  8. It's not logged as a disk problem and SMART looks OK ,so most likely a power/connection issue, but wait for the SMART test result to confirm.
  9. I believe nothing is written until you start changing settings.
  10. Syslog starts over after every boot, enable the syslog server and post that after a crash.
  11. When Unraid need to force an unclean shutdown it saves the diags in the flash drive, logs folder, that should show what the problem was.
  12. Try with v6.10.3, in case it doesn't like the newer kernel, if the same try blacklisting the iGPU from loading, there have been some stability issues with that driver.
  13. That means Unraid had to force the shutdown, i.e., the set timeouts were not enough.
  14. Negative, just re-assign disk1 and start the array to begin rebuilding.
  15. Connect the flash to a PC and run chkdsk on it.
  16. See if you can access the server locally on the console, if yes grab the diagnostics.
  17. Parity swap won't work for this, array would need to be valid with the smaller parity.
  18. You'd need to get small disk, cannot be smaller than the old disk was but also cannot be larger than parity, to test if the emulate disk mounts you can even used a bad/failing disk, as long as it's detected for the initial config it's enough, then if you want to rebuild you'll need a good one of course.
  19. Nothing obvious logged, 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 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.
  20. You are using a release candidate, update to v6.11.0 final.
×
×
  • Create New...