Garland.Joseph97

Everything is working normally. The non working port was due to a noncompatible SFP. I swapped it and now both appear to be working. Thank you for the help everyone!

@JorgeB I added it wrong the first time, made this change and now (1) port is showing up in network settings. but the port is down. I'll go check my cables in the morning. hypeserver-diagnostics-20240207-2246.zip

Good call, here is my latest diag. The device is still showing up in the systems devices list, but nothing in network settings. hypeserver-diagnostics-20240207-0719.zip

@JorgeB Just tried that and no luck unfortunately

Hello, Just wanted to piggyback on this thread. I'm having the same issue with a x520-DA2. It shows up in the device list, but nothing shown on the network page. hypeserver-diagnostics-20240205-1951.zip

That was definitely the problem, I swapped those shares to a different drive and am able to write. Any suggestions for moving the content from the system share? I don't think it can be done with mover

One Update, I can't write files to any of the default shares. Just failed an attempt to put some isos in the iso share

I've attached the diagnostic zip if it will help hypeserver-diagnostics-20230910-1448.zip

Hello, I've had pretty good success with the docker interface until today. WhenI try to create a new container I get the error in quotes below. I've got other container running and there is other data in the appdata share. I've got ~5tb available on the relevant array/drives. Any suggestions would be much appreciated. I've tried to add a folder to appdata via: Krusader, CLI, and in windows with SMB. "docker: Error response from daemon: error while creating mount source path '/mnt/user/appdata/jellyseerr': mkdir /mnt/user/appdata/jellyseerr: no medium found."