Jump to content

JorgeB

Moderators
  • Posts

    67,779
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Nope, it should wake up after pressing any key, you can disable console blanking by adding setterm -blank 0 to /boot/config/go and rebooting.
  2. I think I remember seeing the same thing when connecting from a server running an older release, but since it still worked didn't though much about it, it should go away once you update the backup server.
  3. Not much point in backing up the docker image, appdata on the other hand should be, you can also change the docker image path to e.g. /mnt/disk4/docker.img instead of /mnt/user/docker.img, this way it won't create a new image if the old one is temporarily unavailable.
  4. Not that I know of, other than using a different model board, ideally Intel based.
  5. It does, check the board BIOS for the SEL (system event log), there might be more info there, including the affected DIMM.
  6. I stay logged for days, AFAIK there's no setting for auto logoff.
  7. Correct, and it's already in IT mode, which is the default for that model. Yes. You can connect the HBA to any of the ports, it works like a switch.
  8. Docker image is showing a very low transid, this means it was recently created, like today or yesterday tops, assuming appdata is still there you can just re-add the dockers using CA, or if you think there could be another image somewhere else you can search for one: find /mnt -name docker.img
  9. Please post the diagnostics.
  10. May 11 15:36:33 Apollon kernel: BTRFS error (device nvme0n1p1): super_num_devices 1 mismatch with num_devices 1 found here The superblock is corrupt, and the other pool member is way out of sync, though that's expected if it dropped offline earlier, you can try a backup superblock to see if it works, stop the array, type: btrfs-select-super -s 1 /dev/nvme0n1p1 Then reboot and post new diags.
  11. Changed Status to Closed Changed Priority to Other
  12. Recycle bin is not part of stock Unraid, please use the existing plugin support thread:
  13. The main issue is that USB devices can be prone to disconnects and they are usually also not the best at error handling, but this is a general recommendation, some USB bridges work well enough, though performance is usually also not as good, not the max transfer rates, assuming USB 3.x, but the IOPS and latency.
  14. 1. It's fine 2. Yes 3. Don't know, someone else should be able to answer 4. Yes, as long as it's formatted with a filesystem support by the UD plugin 5. Yes P.S. USB drives are not recommend for array/pool usage, but they can be used.
  15. Problems with the onboard SATA controller, quite common with some Ryzen boards, look for a BIOS update or use an add-on controller.
  16. To be honest the surprise for me is that is was working before, as far as I remember spin down is known to not work with most RAID controllers, including Areca.
  17. Please use the existing docker support thread:
  18. May 10 09:09:41 Tower sshd[6744]: Closing connection to 192.168.1.172 port 55313 May 10 12:52:04 Tower kernel: BTRFS info (device nvme0n1p1): found 14 extents, stage: update data pointers Nothing logged at the time of the crash, since you're using an iGPU it could be this issue, which unfortunately doesn't leave anything logged: https://forums.unraid.net/bug-reports/prereleases/69x-610x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-r1674/?do=getNewComment&d=2&id=1674
  19. I agree, problem IMHO is finding a sensible default, for user shares I would use around 50GB, for pools it's more complicated, maybe 2% pool size but with a 10GB minimum and a 50GB max.
×
×
  • Create New...