CouchPawTayTow

Members
  • Posts

    48
  • Joined

  • Last visited

Everything posted by CouchPawTayTow

  1. Thanks for the info. NB: found your post - very helpful. Might try the same style (M.2 key) but in the 6-port config with the ASM1166 chip (and update it using this post). If no good, then will go back for a 5-port 585 key, as you suggest. Will report back once it arrives and tested.
  2. Found this one, but the reviews aren't great, and in the product details it says 'non-raid' - so not sure it would work? Found this also - looks like a mini SAS controller type-thing. But again, says non-raid - but not sure exactly what they means in context?
  3. Does yours have any activity LEDs in that light up? When mine is plugged in a booted, not only do the drives not show in unraid, but also there's no activity lights on it when the system boots, which makes me think it's DOA, as I feel like it should at least have a power indicator light (blue or something?)
  4. How do I do this, sorry? I had a quick forum hunt and looked though settings in UNRAID, but can't find where to change the loggin for a container
  5. I recently switched my hardware (motherboard is a B660-ITX ASROCK which has 4x SATA ports and I need 6+, i7-12700K, and compatible RAM). Everything boots and works as normal when I am using a PCIE SAS controller, but I want to use the PCIE for a little GPU for transcoding and other apps. Took out the SAS and put this little adapter in the M.2 slot - connected all the drives with same SATA cables but they're not registering in UNRAID (nor BIOS.) I've had a look through the forms and checked all the BIOS settings are as suggested, but still not dice. So I am either missing something in setting somewhere, the adapter is unsupported (I had a quick google, but I don't know what I'm looking for really in this regard), or it's just DOA and I need a replacement. Thanks for any help! NB: as nothing shows in BIOS, I assume diagnostics won't help, but attached just in case. tower-diagnostics-20240413-2307.zip
  6. I can't think of anything running on a schedule - much less an hourly one. Only think I can think of is rsync backup, but that only once a day, and doesn't touch appdata. Yes, deleted appdata for all containers and setup from scratch, so hopefully no carry-over config gremlins. When ghost is erroring, I can still connect with adminer using same credentials as ghost, so seems like MYSQL if still functioning
  7. Routinely/regularly, ghost will error 500 and loose connection to the MySQL database. Almost daily. Last night, I started from scratch. Fresh MySQL database (from CA) and fresh ghost (also from CA). No issues during setup. No database connections problems - connected and created database fine. I don't know what/why/how, but randomly it will just lose the ability to access (error connection refused) the database and give me an error 500 webpage on the blog page and on the dashboard I get the red banner 'ECONNREFUSED 192.168.1.99:3306' at the top of the 500 webpage. I can't decipher the logs to get any clues. Both containers look fine and are running. Any help would be appreciated. Ghost and MYSQL logs.zip tower-diagnostics-20240412-0926.zip
  8. I've skimmed through most of this thread and am having similar issues - GPU stats dashboard frozen. It's been a bit on/off - like it works for about 5 minutes after I updated to 6.12.9, but just stopped at some point and haven't been able to get it working since. Tried all the high-level trouble-shooting I've read in this thread - making sure it's the newest CA version, uninstall/reinstall, browser cache/cookies removed etc. Dashboard screens were take while I was playing a plex video that has used GPU trancoding in the past. GPU is just a little Quadro P1000. Have tried to attach as much as I could - hopefully enough there to help diagnose. NB: The CPU in this system is an i7-4790. The Processor widget on the dash recognises this correctly, so unsure why the GPU Stats widget is registering a Xeon E3-1200? Unless it's just the same tag of the E3 and 4th gen intels? tower-diagnostics-20240406-1412.zip cat tmp gpujson.txt intel_gpu_top -J -d pci slot=0000 00 02 0.txt timeout -k .500 .600 intel_gpu_top -J -s 250 -d pci slot=0000 00 02 0.txt dmesg grep i915.txt timeout -k .500 .400 intel_gpu_top -J -s 250.txt cat gpustat.cfg.txt nvidia-smi -q -x -g GPU-0bdaba85-62de-f0c2-97a7-0f305cdc625e.txt
  9. Yeah the USB thing is weird - definitely a PCIe card - headless server - only USB device connected is internal OS thumbdrive. As you and, @ich777 notes above, looks like its an unsuported card at best, or a faulty one at worst. #badbuy. Thanks for your time, effort, and help - sorry for the time-waste!
  10. Diag attached, apologies. Yeah, I was hoping it wouldn't be a bad card, but possible I guess re: not showing with lspci. I recall I had similar issues when I was trying to get my GPU working - system couldn't see it initially, but it eventually registered and works fine now, so hoping similar issue here re: drivers or something else. tower-diagnostics-20240115-1130.zip
  11. Sorry - my clumsily worded request - The DVB plugin says 'No Adapters found!'. ls -la /dev/dvb/ gives the same result as the image above - /bin/ls: cannot access '/dev/dvb/': No such file or directory.
  12. Hi All/@ich777 I picked up a similar card - WinTV-HVR-1265 - but am having the same problem as @bbotto90 re: attached image - the card isn't recognised by unraid (have tried in multiple free slots that work with other PCI-E card.) Dockers fail to start if adding the /dev/dvb to extra parameters and not seen when calling lspci. NB: running unraid 6.12.6 and the DVB plugin (kernel - 6.1.64-Unraid - doesn't see any adapters
  13. Trying to switch from Pterodactyl as it had some very slow startup times - wanted to see if puffer was any different or better. Haven't been able to find any walk-throughs or how-to's on setting up an ARK server with puffer, but I've had no luck. Can't figure it. Using the ark-docker template. Ports opened etc. So I click install - it goes through the motions - appears to do a full install of the app - and reports all went well. I then click start on the server and it quickly fails (interestingly I see it does create the game container, which then disappears as the server fails.) So this is the console - you can see the installation completes. I try to start it and it fails. Then I try to install again, and it reports it's installed - although I can't actually find the the game data... just the log and config files on the sever - then I try to start it again. I don't know what I don't know with all this - probably something simple, but I just need someone to point it out and how to fix Here are the log files.
  14. Did you get this working? Can you advise how?
  15. [SOLVED] - must have been a bad install. Re-install and seems to have righted it. My organizr (fresh install) keeps auto-refreshing every ~minute or so. Does't matter where I am in the GUI (NB: i don't have any tabs or homepage or anything set yet - just navgating around the settings menu), it'll auto-refresh/re-load and send me back to the default settings page - barely have enough time to find/change anything before it reload again.
  16. Yeah, I thought it might have been a hardware issue re: the PCIe slot, however the slot works with a GPU so I took it to mean the slot was fine. And the fact that the card works in another machine mean the card is fine. So it's a bit confusing. Regardless, I tested it in the other x16 slot and same result/no detection. There's a couple other slots on the board - couple x8s and a x4, I think. I don't know the stats, but would it even be worth using these re: any bottle-necking? I also skimmed through the DELL BISO and the BIOS level device configuration menu and couldn't see anything obvious there (granted, not sure what I was looking for.)
  17. Attached - thanks for your time on this NB: Satus re: Diag is: HDDs moved back to onboard SATA (as need to use the system still - everything working fine) and 9211-8i is installed, but nothing connected to it. tower-diagnostics-20230704-1757.zip
  18. Was using the 9211-8i (in IT mode) in an mITX intel system, using unraid. No issue with it - was plug&play. Recently moved to a Dell Precision T5610 Dual CPU workstation. Initially used the onboard SATA ports - everything fine - array and all data works fine - plug&play. But the board is a bit older, and some of the SATA ports are SATA2, so wanted to use the 9211-8i to mitigate any bottle-necking (and there's only 5 ports so wanted expandability. Plugged the card into a working (tested with a GPU first) PCIe slot - using same cable as was using in previous system, to connect all the same drives - but on boot I am presented with the array setup GUI and none of my drives are available to select. I tried everything back in the old system again, just to make sure the 9211-8i had coincidentally died, and it works fine in the other system. So I'm not sure what the issue is. I did try another cable as well, but the fact that it works with the original cable in the original system kind of rules it out as the issue. Have I missed something obvious here? I just expected it to work as it's a supported card and worked without any issues or need for any configuration in the other system etc. I had a quick google and couldn't find anything re: needing to enable/disable anything in the DELL BIOS, but maybe...? NB: don't have access to diagnostics at the minute as am off site - just wanted to get the ball rolling - but can post this evening if needed. Thanks! NB: Satus re: Diag is: HDDs moved back to onboard SATA (as need to use the system still - everything working fine) and 9211-8i is installed, but nothing connected to it. tower-diagnostics-20230704-1757.zip
  19. Apologies - by legacy, I meant the boot drive. Switched to the 470 driver and now it's recognising it. Cheers for your help!
  20. Hi, have a supported card (quadro K4000 - Latest Legacy GPU version (470.xx series): 470.182.03) that works and followed the instructions re: docker off/on/reboot etc. Card wasn't bound, but tried binding/rebooting then unbinding/rebooting just to be sure. Still the plug-in doesn't recognise it. "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running." Attached diagnotics (followed your steps from a post on the previous page of this thread re: uninstall/reboot/reinstall/reboot/c-state off/switched to legacy etc. tower-diagnostics-20230625-0009.zip
  21. Understandable! Thanks for the reply anyway. If you do any VR gaming, it's a pretty good revival of the original carrier command. Best played with 2+ other people (lots of things to manage) though. Flat screen experience isn't too bad either.
  22. Hi @ich777 - not sure of the protocol for making requests, but wondering if you might be able to make an app for Carrier Command 2 dedicated server. Wiki Info here there I could find. and the steam store page. Cheers!
  23. This did it, I think. I am now able to load up and play a mission! Intel® Core™ i7-4790 CPU @ 3.60GHz on a Gigabyte Technology Co., Ltd. Z87N-WIFI rev.2.0. So 64bit. No. Before adding the force x86 variable, I was not able to get past the mission loading spash screen. It would just lose connection and the server would crash. Seems like x86 is the only way to run it on my hardware. Thanks for the help!
  24. I've since made a little progress. Didn't change anything from the first time (besides credentials, I just set validate = true), just removed and reinstalled. It shows up in the ARMA launcher servers list - that's where I connected to it - it loads up all the way to the mission selection, but then it crashed when it gets to the next - mission loading - screen. And now I'm back to the same loop as before. Tried stop/start/restarting, but no dice. Doesn't appear to be a CPU lockup either. And again - no logs as the window just kill itself after a short time (which I assumed to mean the docker was stopping/restarting?).