Jump to content

LordRaven

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About LordRaven

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. Hi, Just for anyone who has a similar issue to what I had. I had a disk being unmountable. Disk is a default format of xfs. After checking the disk, I found that it had a metadata corruption. The fix was in maintenance mode to run the xfs_repair with the -Lv option. The L is for force the zeroing of the log file on the disk. I know that the in the xfs_repair screen (https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#xfs_repairmention that it isn't one of the options we probably need, however this was the only way to fix my disk and allow it to be mountable again. Thanks, Raven
  2. Just wanted to throw this out as a solution if anyone has the same issue I had. I'd put in the Syncthing docker on my machine and using the bridge connection mapped 8080 in the docker to my towers 8082. Unfortunately, what happened was that the system was not able to connect to any of my other Syncthing instances on other devices no matter how much I put the ID's on the tower instance or on the remote instances. The issue turned out to be needing to have 8080 mapped from the docker to the tower instance. Once I did this, the mappings started coming through. I had not originally done this because I was running unmenu on port 8080. I had to edit the unmenu.conf file to change the port there and everything is now up.
  3. Checking on it later, it seems that when the system did an update with the latest pull from git hub, it changed the permissions on my directories back to read/execute rather than read/write/execute. This could be part of the reasons why I was having issues earlier.
  4. Regarding that, I think the screen you're talking about is the plex sign in screen. I'd guess that they'd be able to theoretically access your data if they signed in with an account. Probably the better option is to setup a VPN to your home network and access your data via that. I've done similar things in the past.
  5. Solved But a slightly different solution. It seems that the system was downloading okay which I had waited before, but the default directories were unwriteable. Changing them seems to have solved my issues.
  6. I've been trying to go via the WebUI. http://10.42.1.115:32400/web/index.html http://[[server Name]]:32400/web/index.html
  7. I have been trying to access via the local name and the ip address. I have tried launching from the docker as well, but no real luck.
  8. Okay, I thought that had to be done within the app similar to the plugin. I made the change and no real difference in terms of the UI.
  9. So far its a pretty vanilla setup, but here are the screenshots
  10. Hi, I'm trying to play with dockers a bit and have put in Plex and SickRage. Both seem to okay on the docker page, but when I try to go to the webpages, nothing is available and I'm told the page isn't available. I had also installed Apache earlier but removed it when experimenting with VirtualBox. I've tried it with the Network type tested as both Hosted and Bridged with no difference. Just as background in case it makes a difference, I had installed Plex previously but during my tests, I've tried disabling the plugin as well as uninstalling it. I've tried rebooting but again no change in anything. I've seen some other people with questions but I didn't see any responses, so if it has been answered, sorry about the repost. Thanks When needo's plex starts up, it downloads the updated plex application (which may take a bit depending upon what else is going on), and then it still takes a bit for plex to get itself up and running.
  11. You'll also need to set your Network connection within the VM to be either a home or work connection in order to allow others to remote into your machine.
  12. I'm currently trying this in Unraid 6b15. I've tried to do it via the Settings and via the telnet with no luck. I had a similar experience when I tried to do so in b14. I've limited my dns servers to only be the PDC.
  13. Playing with this a bit more, it seems to occur whenever any plg is placed in the plugins-errors directory. I copied a couple of different plg files as well as creating an empty file named test.plg. In all cases, this error occurs.
  14. Similar to a regular PC, depends on how much read/write you're expecting to do. If you're planning to use it as a boot disk and a data store on another virtual drive, you should be good to go.
  15. You probably wouldn't install it on your cache drive depending on how many instances you'll be creating. Easiest thing would be to create a virtual drive on your user share for each instance. Just remember as your vhd fills up it will grow to the max size that you allocate to it, but won't automatically shrink. You'll need to run scripts to defrag and then zero out the free space in order to shrink it.