Tygerial

Well here I am again with a 9207-8i from The Art of Server, and I'm hitting the same wall again. I get a solid orange dram light when the system tries to boot with the card installed. Any other thoughts out there?

Thanks @JorgeB! I did forget to mention that I had found a similar thread and did try the tape trick to no avail as well. The card has the LSI branding and the darker/glossy pcb (Not shown in the listing pictures) so I thought it might be real, but at this rate of a few days frustration I think I'll return it and buy from The Art of Server. Thanks again!!

I recently bought an LSI 9207-8i, and when trying to install it onto my server I discovered the whole machine won't boot with the card installed. I'm running 7.0 on a an AMD 9900x. My MSI mobo has an up to date bios, and the LSI card works when plugged into my windows machine and shows as in IT mode with version 20.00.06 firmware on it. The system not only won't boot, but won't let me into the bios with the card installed, and instead just boot loops. I get a flashing green light on the LSI card, and the first couple boots I see the VRAM light on the mobo flash, but eventually that light stops flashing as it continues looping. Anyone have any thoughts on this? I'm starting to get the feeling the card is bad or a fake, and I might just return it to buy one for The Art of Server instead. Card: https://www.amazon.com/dp/B0BXPWJLM6?ref=ppx_yo2ov_dt_b_fed_asin_title Mobo: MSI Pro X870-P

Did you ever resolve this? I am experiencing the same symptoms with the same model card right now.

Hey sorry, I think I actually ended up doing this a while back and it resolved my issue. I appended all my VLANs I might access the docker from into the LAN_NETWORK variable to have the docker allow traffic from those vlans. Thanks for reaching out again though! Not sure why I just now got the notification about you responding though...

I'm having about the same issue. I upgraded my main server, and then reused the old case/mobo/cpu/ram to build a second server. This second server can last anywhere from 20 minutes to 3 or 4 hours before almost rebooting itself and never fully rebooting. Likewise logs don't look outrageous, and the RAM cleared a test. That being said the server wont stay up in safe mode or even in the built in memtest it crashes. I would lean hardware but this gear has run 100% rock solid for 3 years which is when I bough it for my first server, so that makes me hesitant to say hardware is the issue. What further is confusing is I built the machine the 14th, and it ran fine until the 20th when the crashes started happening. Diagnostic is from this morning after most recent crash, syslog is the active syslog at time of most recent crash. The crash took place at 01:10 while the syslog ends at 00:01. anna-diagnostics-20250222-0922.zip syslog-previous

Okay this is gonna sound dumb but might apply? Is your desktop on the same VLAN as the server/docker? If not, follow FAQ Q32 here: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Turns out it doesn't matter if you have firewall rules set up to properly allow traffic across the VLANs, you have to append both the server/docker vlan AND the Dekstop vlan in the config of the qbit docker to be able to hit the WebUI.

Yes sorry over LAN is correct. hardwired from local desktop all the way to the server.

I am using chrome by default, but Edge doesn't produce any different results. I don't get any specific error trying to hit the page, just a forever loading screen until it fails eventually. I am using IP:8080 through both the unraid gui and manually typing, neither makes a difference. I did recently swap my networking gear out for a full Ubiquiti set, but am hesitant to assume a firewall issue when all my other dockers such as radarr/sonarr are working fine as they were before. I tried to Telnet to verify the port functionality but that never connected either, but I could hit other binhex dockers with it too.

Bumping my issue. Sorry if not allowed.

I have a multitude of dockers running on my server (mostly binhex torrent dockers), and after months of working fine I have had 1 specific docker just quit working for gui access. It's a qbittorrent docker and I can tell it is still doing everything else, but I just can't hit the gui anymore. No config changes, no duplicates on ports used, and I have done everything from reboot the docker, to remove the docker and pull down a new image, to doing a full server build upgrade from 6.12.11 -> 6.12.14 with nothing giving gui access back. supervisord.log Command.txt

I have a multitude of dockers running on my server, and after months of working fine I have had 1 specific docker just quit working for gui access. It's a qbittorrent docker and I can tell it is still doing everything else, but I just can't hit the gui anymore. No config changes, no duplicates on ports used, and I have done everything from reboot the docker, to remove the docker and pull down a new image, to doing a full server build upgrade from 6.12.11 -> 6.12.14 with nothing giving gui access back. Any thoughts other than building a whole new container?