What the problem that I am here for help is the server recently dropped off the network (as looking on the network in Windows file explorer) so I did a hard reset by flipping off the power switch on the power supply, then flipping it back on, but it still wouldn't connect. So after I waited a while it still would not connect, so I hooked up a monitor and saw that it didn't boot up, I just saw what is in the photo. so I flipped it off and back on again the same way, but still nothing.
So you lost network access over SMB / CIFS, and figured a hard reset was the best way to fix it? Was the web interface responding? What about ssh? What about the physical console on the server? There's many things I'd check before doing an unclean shutdown like that.
And if deduplication was enabled, then on startup after any unclean shutdown, the entire dedupe table MUST fit into RAM in order to access the pool. This is why dedupe with inadequate ram is dangerous. Any unclean shutdown and you've lost the data without adding ram. "inadequate" for dedupe can vary depending on the data being stored, but I've seen recommendations as high as 20GB per TB of disk. If you had 4TB of usable disk space, that's potentially 80GB of ram.
If you can bump the ram to 16, I'd try that. If that doesn't help, an option might be sending the drives off to someone who has a server with enough ram to actually import the pool.