djvj

Members
  • Posts

    55
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • URL
    http://www.rlauncher.com

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

djvj's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. Satisfactory just made a change to require a parameter sent to steamcmd to stay on the experimental brance. I don't see an ability to do that in the docker settings. How can I sent something like -steambeta to steamcmd? I tried setting this for the game parameters, but doesn't look like those are for steamcmd -beta experimental See more info here: https://satisfactory.fandom.com/wiki/Dedicated_servers#Experimental_Branch_Selection https://github.com/wolveix/satisfactory-server/pull/93
  2. Trying to Install TinyMM and when I launch it I get this error: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='TinyMM' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'USER_ID'='0' -e 'TZ'='America/NewYork' -e 'DISPLAY_HEIGHT'='1380' -e 'DISPLAY_WIDTH'='1200' -e 'PUID'='99' -e 'GUID'='100' -e 'UMASK'='000' -p '5801:5800/tcp' -p '5901:5900/tcp' -v '/mnt/user/Movies/':'/media/Movies':'rw' -v '/mnt/user/TV/':'/media/TV':'rw' -v '/mnt/user/TV2/':'/media/TV2':'rw' -v '/mnt/cache/appdata/TinyMM':'/config':'rw' 'coolasice1999/tmm:latest' 0ff7265bc2d05bc18c8d0deb00e671610d10a8398fc4fbaebb77c7505a4a4b2d Docker log won't show anything as it won't launch yet to start a log. I feel like I'm missing something simple, just can't see what. Compared to other docker settings, everything looks ok.. Anyone have an idea?
  3. Just purchased a new 14TB WD Element drive and I've read others preclear before shucking. I just tried doing the same so I don't ruin the warranty in case it's a bad drive but when I start it, the script just gets stuck on Starting... I'm on unraid 6.9.2 and all plugins are updated. Is there something I need to do to get this to work?
  4. Thanks for explaining the differences. root@Storinator:/mnt/user/domains/Windows 7# du -h 49G . root@Storinator:/mnt/user/domains/Windows 7# du -h --apparent-size 51G . My concern isn't the actual usage of the VMs, it's the discrepancy of my cache disk size vs free space and figuring out where that free space is being used up. In this case, it isn't the Windows 7 VM alone using up that much space. I have 100GB worth of VM disk usage among a few VMs. This still leaves 380 of 480GB left. DU only shows 246GB used which 84 of that says its from domains. 480 - 246 (from DU) = 234GB is somewhere and I don't know where! For instance on Windows, I could just look at the properties of a folder and find it's exact usage, amount of files/folders/etc. Then trace out where my space is being used up. Then decide is I need to move it to another drive, delete, etc. If I can't trust DU command because cache is btrfs, what can I trust to figuring this out?
  5. Thank you. I have a win7 VM, but that still shows 50GB vdisk size and has never changed. This isn't what's been taking up more and more space gradually then. Your guide is more for win8/10. I tried for win7 but defrag found 0% defragmentation. If the Unraid GUI is correct, then what tool can I use to show the correct space usage on each folder so I can find the culprit?
  6. I have 2 identical SSD drives in my cache pool in Raid-1. GUI showing they are full, but over CLI, they are not. Using UnRaid v6.8.3 Why is this happening and how can I go about fixing it? Tried searching and I find threads on this issue with drives are not identical. root@Storinator:/mnt/cache# du -h -d 1 /mnt/cache 60G /mnt/cache/docker 84G /mnt/cache/domains 6.1G /mnt/cache/isos 1.0G /mnt/cache/system 96G /mnt/cache/appdata 0 /mnt/cache/downloads 171M /mnt/cache/.PhAzE-Common 246G /mnt/cache
  7. When trying to delete large files, like multiple gigabyte files, they won't delete. But when I delete smaller files, they delete fine. I'm not sure what the cutoff is between the 2, but I'll try a 14GB file, and nothing happens when I try to delete it. A small txt file, and no problem, deletes fine. Permissions on everything are all 777. When I used the other krusader docker, I never had this issue. I only recently switch to this flavor because the other gave me too many issues. How can I figure out what's causing this?
  8. Same here, no cursor on VM windows 7, tried in IE and Chrome. Can't find a fix anywhere!
  9. Thanks so much, this worked! Just saved me a lot of money for no reason. Unraid booted so much faster as well from not having all the timeouts.
  10. Oh ok I can try that. Did something break on the 6.7.x with Marvell-based controllers? My only idea I could think of was to try another usb stick with the older unraid version on it to see if it could communicate with the controller properly. Thank you!
  11. Was running 6.6.7 for last 100 days, updated to 6.7.2 just now and none of my drives show up. I recorded a video of the boot messages and I'm getting some new lines I've never seen before regarding my rocketraid 750, which is what all the drives are on. Not sure what to do. Tried a different PCI slot and tried hard powering down and get same thing. Only thing I did was updated unraid and reboot.
  12. Hello, just installed this docker and the log dumps this right after installation was complete. It keeps dumping it every few seconds and have no access to server or anything yet since it never actually started: Start Logitech Media Server... Can't call method "log" on an undefined value at /usr/share/squeezeboxserver/CPAN/Log/Log4perl/Appender.pm line 189. [19-06-04 22:40:57.0311] main::init (387) Starting Logitech Media Server (v7.9.2, 1555406898, Tue Apr 16 11:48:46 CEST 2019) perl 5.022001 - x86_64-linux-gnu-thread-multi [19-06-04 22:40:57.1204] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table [19-06-04 22:40:57.1308] Slim::Schema::forceCommit (2147) Warning: Trying to commit transactions before DB is initialized! [19-06-04 22:40:57.1844] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table [19-06-04 22:40:57.1948] Slim::Schema::forceCommit (2147) Warning: Trying to commit transactions before DB is initialized! [19-06-04 22:40:57.3892] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table [19-06-04 22:40:57.4000] Slim::Schema::forceCommit (2147) Warning: Trying to commit transactions before DB is initialized! It's been doing this for about 10 minutes, so didn't think it was still creating a db or anything. All settings in the docker template used were default. Ok nevermind. Restarting the docker seems to have fixed it. Hopes this helps if anyone else gets this error.
  13. I figured it wasn't the drives, but replacing an $800 controller is a much more costly venture, I'd rather it be bad drives. It's been working fine since 2014. Was the only one I could find that supported all the ports I needed. Possibly one of the ports failed then. I'll reboot and test. Thank you.
  14. storinator-diagnostics-20190401-1020.zip Here you go.