Squid

Community Developer
  • Posts

    28636
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. Not surprised. The flash drive got disconnect. Your best bet is to put it into a different USB controller on your board (IE: USB 2 <--> USB 3), and possibly change your boot order accordingly.
  2. https://forums.lime-technology.com/topic/46802-faq-for-unraid-v6/?page=2#comment-545988
  3. I'll save you the time. I posted thinking you were on the lsio flavour. On Binhex's libmediainfo is there, but the mediainfo command is not.
  4. docker exec -it radarr /bin/bash followed by mediainfo --Output=HTML /path/to/your/file.mkv Will out the results to the screen. To save it to a file, add to the end of the command > /path/To/WhereToSave/output.html Note that all paths are based on the container path you've specified within the template, not unRaid's normal paths.
  5. It means that some of the files within that share are currently sitting on the cache drive. Common and easy way for that to happen is to have the share being written to while use cache disk was set to only, yes, or prefer. And the subsequently switching the share to use cache no, but before mover ran. The fix is to change the setting to be use cache disk yes, run mover from the main tab, then switch it back. If there were no errors (ie: no files were in use), then it should now be fully protected.
  6. Post the xml file (/config/plugins/dockerMan/templates-user/my-{whateverYouNamedTheContainer} on the flash drive) after it fails to install To me, it appears that possibly you're using some weird characters within the password entry that's messing up everything (or the flash drive is pooched)
  7. You need to restore the backup (if made) of the libvirt.img file, which defaults to being stored in the system share.
  8. Ah I missed that emby is running as network mode host try switching it to bridge and try again. If it still doesn't work then you have to find out all the ports emby uses and assign them individually (or upgrade to 6.4 and assign emby a different IP address) Also, you pretty much never need to change the webui entry regardless of how you assign ports
  9. You're not the first. Hopefully @limetech will fix this behaviour on a future release.
  10. What was the format of those drives? unRaid supports XFS, BTRFS, and ReiserFS as data drives Probably not one of the aforementioned filesystems, then they will show as unmountable. Whatever you do do not hit FORMAT. Implies the format was NTFS. Unfortunately, the first thing unRaid does when it sees a drive assigned to the array is to set the partition start to be compatible with itself. Presumably, this wasn't how Windows had the partitioning set. You'll need to run some partition recovery software on your windows box to get the file(s) back No. unRaid is the cat's meow. But, without researching on how to add in drives with existing data, you've just caused some aggravation to yourself. Once you've recovered the partition information via a windows utility, what you want to do is (assuming you've never hit the Format button), is to get all the files off of one of the data drives onto another drive (or the second). Assign the drive as a data drive, format it. Then install the Unassigned Devices plugin to mount your drive full of data. Copy the data from the UD mounted drive to the blank drive. Wash, rinse, repeat.
  11. Squid

    Docker FAQ

    How do I install a second instance of an applications? There may be some use cases where you may wish to run a given application twice, with separate appdata settings, ports, etc. Assuming that the container runs as network type: Bridge, On the Apps Tab (you do have Community Applications installed don't you?), Go to Settings - Enable Reinstall Defaults Go to the Installed Apps section, Reinstall using default values the application you want to run another instance for Change the name of the application, along with assigning it different ports, paths (you may need to show advanced settings to see the appdata (/config) path) Hit Apply If the application runs as network type: Host, you will do all the same as above, but you will need to switch network type to be Bridge, and add in all of the applicable ports and reassign them as needed. (ie: check with the support thread and/or the project URL to determine which ports need to be defined Alternatively, (under either Bridge or Host network types), if you are running unRaid 6.4+, then you can also assign the new instance a different IP address and keep the ports the same (bridge mode), or not define them at all (host mode). But you will still have change the name of the application and set the appdata (/config folder) accordingly
  12. From CA, within the Installed Apps section, install Emby (but don't edit the existing installation -> reinstall using the default settings). Then change the name of the container, the applicable ports, and the applicable paths.
  13. No errors, just an up and reboot would imply Check for BIOS updates, especially if you're running VM's with passthrough Power Supply Mismatched RAM RAM not on the MB approved list Cooling issues Very excessive dust bunnies But, realistically, try googling for an updated Memtest, as the included one with unRaid is rather dated and doesn't actually catch all errors (make a live linux USB stick or something for Memtest)
  14. While probably very difficult to arrange, the more interesting information would be on the locally attached monitor (if you have one). Major PITA as you'd basically need a video camera pointed at it for hours on end. (unless you set up your phone or something to record, run your 6+ containers that cause it to shortly crash)
  15. Try this as a custom cron entry 0 5 * * 0 [[ $(date +%e) -le 7 ]] && Should run the backup first Sunday of every month @ 5am Nutshell is that that cron entry is every Sunday, but you're entering in a script also that checks if the Day is <= 7 and only then executes the script which I'm supplying Obviously not tested since its not the first week of August
  16. For the improper shutdown, increase the shutdown time before forcibly killing the container. This is a docker thing. Stopping a running container will always try to do it cleanly, with an adjustable timeout before its killed. If its doing some sort of task, then take your chances on keeping things running. "Open" file backup. Keep everything running. But then you also run the chance that the backup is incorrect because one file is in the middle of being written to, and another related file hasn't be written yet, etc etc. Open files on backups will always possibly result in indeterminate states on an ultimate restore that may or may not render the application non-functional. Up to you.
  17. IIRC photoshow is very slow with tons of pics. Compounded by your PI. But you should be asking these questions on Linux servers forum as detailed in the OP Sent from my LG-D852 using Tapatalk
  18. Strange because it's there in your screenshot Sent from my LG-D852 using Tapatalk
  19. Copy the config folder somewhere safe, then reformat, set unRaid back up and copy the config folder back. But, it appears that at least part of the config folder is corrupted (the config/plugins/dockerMan/templates-user folder) Not the end of the world if you have to completely redo the templates (would be basically reinstalling the applications, but your appdata wouldn't be affected), but it is a PITA But first thing to do is if there are any files with a zero byte length in that folder, delete them.
  20. Its looking at the root (/) folder of the docker container. Select input or output on that dialog you've got up.
  21. Squid

    Ram Purge?

    Maybe I'm thinking this wrong, but if the board does do that wouldn't the 4-40Watts savings be at ~1.3 Volts. Once that's all converted to the actual power draw at the outlet, you'd be saving a dollar at the end of the year. (Nice deal on a steak though )
  22. And after checking, look in /config/plugins/dockerMan/templates-user (and templates) if there are any zero byte files, delete them.
  23. Same error? If so, then your flash drive is corrupted. Toss it into a computer and check the file system on it.
  24. Its one of 3 things docker image completely full docker image corrupted cache drive corrupted and mounted read-only Posting your diagnostics would tell the story