Jump to content

Squid

Community Developer
 View Profile  See their activity

  • Posts

    28,770

  • Joined

  • Last visited

  • Days Won

    314

 Content Type 

Everything posted by Squid

  1. Squid
    Did you just change the name of your server from "Tower" to be "Treadstone"? Can you reboot, Go to 192.168.140.2 (don't use the server name), start the array normally, and then wait a couple of minutes, and then post a set of diagnostics Also, do all your switches etc support Jumbo Frames?
  2. Squid
    Advanced View
  3. Squid
    You can click on it and select acknowledge. If another error happens in the future it will turn back to be a thumbs down
  4. Squid
    It's usually accessible via the network share flash
  5. Squid
    Probably not the answer you're looking for, but have you tried removing those lines at the end which you've added?
  6. Squid
    You should probably post in the relevant support thread for Plex (click it's icon and select support), and include the docker run command
  7. Squid
    Not the proper way to run file system repairs. By accessing the drive directly, you've invalidated parity. The proper way to run file system checks is via starting the array in maintenance mode and then xfs_repair /dev/mdX
  8. Squid
    Can't comment on whether it's needed or not, but the reason you're getting permission denied is that due to security, no file stored on the flashdrive is directly executable anymore. You have to copy the file somewhere else (say /tmp) and then execute it from there.
  9. Squid
    Net time frame is the same. My philosophy is that since the only time a disk gets disabled is when a write to it fails. At that point, the write gets reflected in the parity system. Because of that, as far as I'm concerned, the data on the drive is technically invalid since it was never updated to reflect that write, but since parity was, you're better off rebuilding the drive itself instead of doing a new config and rebuilding parity. The write itself though may have been meaningless, so you're probably ok...
  10. Squid
    Stop the array, set disk 9 to be not installed. Start the array, stop the array. Set disk 9 back to what it's supposed to be. Start the array. The system will rebuild the contents of disk 9
  11. Squid
    If you grab your Docker Run Command then the actual error will show up there.
  12. Squid
    No. Settings - Docker - Enable Docker: No
  13. Squid
    I'm assuming that they're mini-sas connectors, so yes.
  14. Squid
    Not necessarily your problem, but it looks like you've got 3x Marvel based HBA controllers. These tend to be very problematic and ideally should get replaced with LSI based ones.
  15. Squid
  16. Squid
    The video was probably based upon binhex's flavour of the app. But, instead of adding another path (which is probably what the video showed), you hit "Show More Settings", then modified an existing path (the /config) which means that you stored all of the appdata for the app within /mnt (which will wind up being in RAM) If you want to simply things, then you can simply change the /media mapping from its default of /mnt/user to instead be /mnt
  17. Squid
    won't warn you about usage or anything, but to see how much an app has consumed of network, docker stats
  18. Squid
  19. Squid
    The problem is that you've set the host path for /config to be /mnt While it's fixable, I'd suggest uninstalling this, then installing binhex-krusader. Accept the defaults and ADD another path mapping of /mnt/disks to /UNASSIGNED
  20. Squid
    All scripts log to their own log file which can be viewed / downloaded
  21. Squid
    Post the entire diagnostics zip file
  22. Squid
    The link is how to get the docker run command to post here
  23. Squid
    For some reason, certain combinations of hardware will issue an mce when initializing the CPU's. That's what happening with yours, and isn't anything to worry about.
  24. Squid
    No. That's emailed directly to LT
  25. Squid
    Debug Mode: false
×
×
  • Create New...