Squid
-
Posts
28677 -
Joined
-
Last visited
-
Days Won
314
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by Squid
-
New installs or reinstalls using default values will give the pop up to select branch. Edits of existing installs will not.
-
You should run a Memtest from the boot menu if only to rule it out.
-
Shouldn't make any difference. But, you have to bear in mind that all paths anywhere in a script should be absolute, and not relative. That, and IIRC (would have to double check after work), but the scripts have slightly different /tmp folders that they execute from depending upon how its started.
-
Explain... Admittedly I have never checked what user a cron entry runs as though Sent from my LG-D852 using Tapatalk
-
Unraid doesn't support 32 bit binaries which based on the naming yours is If this is running within the docker container you may be able to execute it if you upgrade to 6.4 Sent from my LG-D852 using Tapatalk
-
Everything should run as root Sent from my LG-D852 using Tapatalk
-
@CHBMB is going to echo the same thing here: Don't ever, ever, ever do that. If you have Fix Common Problems plugin installed, in the same tools tab there is a "Docker Safe New Permissions Tool" that you should run instead if you ever feel that the permissions on the array are messed up for one reason or another.
-
did you rescan?
-
Since you were the first to use that particular term, allow me to state in non PC terms what I think is happening: I have no f*cking clue. The IT guys at my company have no f*cking clue either.
-
And is the BIOS reporting the correct amount of installed memory?
-
Not going to be what you want to hear, but what you wound up proving is that this issue that affects a handful of users is out of my control... And, in the process you also proved that my slight revamp for a possible fix to a problem I can't replicate won't work since the rm command locked up via a direct SSH connection. To be expected. The only thing that I can suggest is to keep plugging away at deleting the old backup sets, then switch to not using backup sets at all. Then the rm commands are never issued ever.
-
or this
-
Aug 21 00:31:53 Tower kernel: Your BIOS is broken; DMA routed to ISOCH DMAR unit but no TLB space. The trace is very early in the boot up, and may (or may not be) benign. BIOS update should hopefully fix you up.
-
These posts were from quite awhile ago and were basically guaranteed to fail and mess things up for you. You have to delete the docker.img and recreate it, then add in your previous apps in order to undo this.
-
/data has to be mapped exactly the same as it is on the download client. See the docker FAQ for ...aka linking containers. Sent from my LG-D852 using Tapatalk
-
Does this sound like a cable error
Squid replied to DJRon's topic in Storage Devices and Controllers
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. -
Biggies to avoid would be < > &
-
https://forums.lime-technology.com/topic/46802-faq-for-unraid-v6/?page=2#comment-545988
-
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.
-
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.
-
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.
-
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)
-
You need to restore the backup (if made) of the libvirt.img file, which defaults to being stored in the system share.
-
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
-
You're not the first. Hopefully @limetech will fix this behaviour on a future release.
