Jump to content

Squid

Community Developer
  • Posts

    28,769
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. It would sound like the flash itself is pooched (unless there's a physical write-protect switch on it). I would transfer the registration https://wiki.unraid.net/Manual/Changing_The_Flash_Device
  2. You need to post your diagnostics with the drive installed Also, does the BIOS see the drive?
  3. There was another user who had similar problems with ZFS and using a docker folder instead of an image (Settings - Docker) fixed them up.
  4. A reboot in theory should fix the filesystem on the flash drive. But for best results it's always best to pull the drive after shutting down the server and attaching it to a Windows / Mac and running the file system checks on it.
  5. If you UPS goes into Overload (there's usually a very annoying alert they make in that circumstance) when the server is running full tilt then yes it's underpowered. With full load (say running a parity check while you're doing whatever else you do) what is the estimated time on battery when looking at the UPS settings?
  6. Yeah, I forgot to mention that if you're booting via UEFI then you have to temporarily switch to Legacy Mode (or just hit whatever function key to select the boot device on the fly) as Memtest only works on Legacy mode.
  7. You would need to post the diagnostics from the server (you can do it at the command prompt). If the entire system is crashed or what not, then not much you can do except turn on / reboot and the steps to figure out why begin.
  8. Highly unlikely the maintainer here is actually changing the source code. Rather he's pulling automatically from another source (the official repos?) and the container gets built and updated as things change. Most apps operate like this, which is why you pretty much never see any change logs for the container within CA.
  9. Yup, nothing can be done until the diagnostics are posted.
  10. Have you run a memtest? Also try disabling the overclock (ie: XMP) on the memory in the BIOS. Your RAM is 2133, not 3200 It also doesn't appear that there is a cable plugged into the ethernet port. Double check both ends.
  11. Something is tying up disk #1 preventing a shutdown (note that simply sitting at a command prompt with the current directory somewhere within /mnt/disk1 will cause this) Were they stopped or paused? (An issue was just identified where a paused VM would present this exact issue)
  12. I just installed it from CA and there's no problems. Was this plugin ever released prior to inclusion in CA (or with a different URL)?
  13. Try disabling bonding in settings - network settings. With only a single NIC it's pointless to have it enabled and it only adds another layer of complexity to the system. It also looks like you may have had issues in the past with the docker image filling up (you've set a 100G image file, which is extreme overkill for the vast majority of use cases -> you're only utilizing 14G of it). Have these issues been resolved?
  14. The official minimum for any of the 6.9+ releases is 2GB RAM. The functional minimum is 4GB. You're just not going to be able to use the OS with 1GB as anything more than a pure file server (if it works at all), so I don't really get why you would require a swapfile to begin with. This isn't a "software" issue, but rather a "hardware" issue. You're not meeting the minimum requirements.
  15. You're being bombed with advertisements for IPv6 addresses from DHCP. Don't know why, but wondering if static addresses being assigned won't help
  16. Something crashed (cache_dirs) on Feb 11th. Have you run a memtest from the boot menu recently?
  17. My bad I didn't realize it was 6.10+
  18. You should revert to a stock OS image and use the Vendor Reset driver in Apps instead
  19. Any chance you're logged in to a terminal and are sitting at /mnt/user/Movies as an example?
  20. This issue was replicated by Limetech and should hopefully we resolved for the next release. The general way that users found around it however was to switch the vdisk location from auto to instead being manual and pointing the folder directly at it.
  21. Have you tried doing the suggestion the message has? If still no go, post your diagnostics
  22. It actually should say with a backup schedule.
×
×
  • Create New...