mrjimi16

The server is on my home network, so I shouldn't be going through the VPN with that, though, I'll be honest, I'm not 100% clear where that starts. I do know that the issue is the VPN itself, not being connected through the VPN, I'm assuming that there is some sort of preliminary framework it sets up for when I connect to one of the servers. Again, I'll be honest, I don't know all that much what a firewall is doing. I look through the Avast settings and it seems to just be a filter for what kinds of protocols are allowed to pass through from what area. Still, it just doesn't make sense to me that I would tell Avast to allow all connections from a range of IPs and yet it doesn't do that.

Okay guys. I think I figured something out. I recently installed the Newshosting VPN on my PC. It was the only change software wise that I have made in any capacity in the past month or so, so I closed it and immediately I got a much quicker response time on the webgui, though still a bit slow. As derMeister suggested, I also did the thing with Avast's firewall and though it didn't help before I closed the VPN, after I closed the VPN I tried turning off the firewall and everything works as normal. That isn't a solution of course, not having a firewall up, but it's something. unRAID is running in safe mode (or at least it says it is, both my Folding@home and Plex dockers are still running), but hopefully the improvements transfer over into a normal boot. I'd really like some help now figuring out how to make the firewall not do this. I can deal with turning off the VPN anytime I need to do something, but I don't like the idea of having my firewall off. Also, just to be clear, the box "allow all connections with friends when in private mode" is checked and the IP of my server is within one of the ranges listed, as derMeister suggested.

Did what you said, but I'm still getting the same problems. I don't think it took, my Plex server is up and I can stream music from it. Is there a graphical change in safe mode? Is the webgui even active in safe mode?

Okay, so I got the diagnostics file. As I had said before, everything is mostly just super slow to load, except for a few times when the network connectivity just stops. I was able to download the diagnostics thing from tools/diagnostics in the webgui. So that's here. I'm not 100% sure what the specs are, and I'm not sure exactly how to find out. Again, with plugins, I'm not sure exactly what is there, and I didn't add anything new before this started. I know I have Plex as a docker, I don't think there is anything else that auto starts. No VMs, unRAID version 6.3.2 (can't believe I forgot to put that in). Anyway, I did check to see if I could access files this time before doing anything else, and yes, I was able to. I also verified that the Plex docker was working, though I didn't play any videos or music. Tried to do something else in the webgui and I lost the ability to connect to the server again. Also, not sure how to boot into safe mode, the board doesn't have video and I don't have a graphics card to put in. Is there a way to schedule it on a reboot? throne-diagnostics-20170418-1831.zip

When I try to access the webgui, it "loads" but not all of the images are loaded in the tables and stuff on the main screen. My array is started, and just before posting this I could navigate through Windows explorer in all of the folders (didn't try to open any files) but when I tried to capture the syslog file (with cp /var/log/syslog /boot) I lost that ability and my PuTTY session timed out. So, I'm thinking maybe something hardware related, but I was hoping it wasn't. If anyone has any idea if there are any software related things that might cause this, I'd love to hear them.

I've got the biggest smile on my face right now. You were right, it was a BIOS setting. I had figured as much as well, as you say the intuitive thing after an update is settings being reset, it had just been so long I wasn't sure what all settings I had changed (and which ones had been adjusted back when I used this build as my PC). Turns out the IOMMU controller was disabled and needed to be enabled. Doesn't make much sense to me, as far as I know IOMMU is VM related, but I shall not complain (especially since this all started because I wanted to VM retropie to play around with it until my Raspberry Pi gets here (which was itself stupid apparently given incompatible architectures and stuff)). Thanks for all the help everyone!

Finally managed to get back on this, the disk tool thing didn't work, same IP and drive label issues persist. I'm starting to think it might be the drive itself. Does that make any sense?

I've disabled the all the boot options that aren't the UNRAID drive (including the UEFI one). I've changed a setting that had UEFI or Legacy to legacy, I forget the exact title. Same issues with IP. Any other ideas?

So I stupidly upgraded the motherboard BIOS when it turns out I didn't need to. Let's not talk about that. As far as I can tell, it went smoothly, no error messages or anything and the system posts and goes to the unRAID booting up process. The problem is that suddenly the DHCP process thing couldn't get an IP address, even though I have it set up for a static address (which I would have assumed bypasses that process, obviously not). So I'm doing some troubleshooting and stuff, and then suddenly I get issues where it can't find the boot disk ("waiting for /dev/disk/by-label/UNRAID (will check for 30 seconds)" error message). I saw someone say that meant that the boot drive was corrupted in some way, so I backed up the thing, reformatted and repasted in my build, make_bootable.bat, issue persists (presumably there is something in there that is causing the problem, but I can't figure it out). I'd really rather not have to redo everything, I'm kind of a hands off person, once I got it the way I wanted it three months ago, I have almost not touched it. I have no idea what kinds of settings I had set. I have since reverted the BIOS to the old firmware, which, yeah, was probably stupid too, it was a long shot that didn't work out. The only idea I have left is that there may be some settings in the BIOS that got reset in the changing I did there but I wouldn't know what to change because, as I said earlier, I have no idea what the settings were changed to to begin with. Okay, after typing the above, I figured I would do the diagnostics thing cuz maybe that would help, and the by-label thing didn't show up. IP issue is still there. It is actually weirder now, my router shows that the MAC associated with my server has an IP (different to the static one I set up), but ifconfig still shows no IP and I can't ping the one the router shows from my desktop. And hey, now I try to get the diagnostics file off of the boot drive and its completely corrupted. Redo that again and the by-label thing is back, but now IP is getting an address at the same not static one I set as before. Still can't ping either way (even managed the would-be infinite pinging because I forgot about that). What a comedy of errors. I have no idea what to do now. Kudos to anyone that actually read all of this.

I have no idea what I did to fix it, but it works now. I changed the install back to 6.1.9, that did nothing, as far as I could tell, if anything it made it worse as I was unable to get an ip address at all. I re-terminated the ethernet cable that I was using, that did nothing. I went in the BIOS and saw that two of the SATA ports were in IDE mode, I remember seeing that as a bad thing to do, so I changed them to SATA. Maybe that was the issue, I don't see why that would cause a problem with networking, but whatever. I also used two different USB devices, the one that I am using now is newest one I have, but it was having the same issues as before, so I don't think it was the USB drive. Anyway, crisis averted.

I am running 6.2.0 beta19. Any attempt to reach the web gui times out, whether it be ip or tower. Looking on my router's page, I can see that one of the DHCP clients is called "Tower" and has the same ip that the server is reporting, so I assume that is fine. Still I cannot even ping the system over the network, I get, seemingly randomly either time outs or "Destination host unreachable." Does this sound like a network issue? This server is connected directly to the router, and the computer I am trying to access the server on is connected to a switch which is connected to the router. I wouldn't think that is a problem, but originally, the server wasn't getting an ip when connected to the switch. That is itself weird, because I have another server connected to the switch which is just fine (though I did originally connect that straight to the router). That server is running 6.1.9 (it's not mine, I wanted to have fun with the bleeding edge on my server, yay, fun!). While I wait for you guys to think of something I'll probably try connecting my computer to the router as well, and then if that doesn't work I'll try directly connecting them. One more thing, could someone tell me what broadcast is in the ifconfig readout? Normally when I see three ip address looking numbers the third is a default gateway, but the last number here is 255 and my router is the usual 1. So I'm probably wrong. EDIT: Turns out they were already both on the router...

Can you access the GUI if you connect directly (like ethernet from your computer to your server)? I am hardly an expert, but that is what I would do just to make sure that the issue is with unRAID and not your network setup. I know when I set mine up I couldn't connect using http://tower but I could with my server's IP. I figure while you are waiting for people that know what they are talking about, that might be something to do. If nothing else, and assuming it is a network issue, you can do some setup while you wait for them as well.

So this is probably a stupid question, I realize this straight up. My new computer case can only take a slim drive, and all the drives I currently have are 5.25 inch drives. I find myself wondering if it is possible to pass through a disk drive from an unRAID server. The way I would think to try first would be to just create a disk share for that drive, but I don't even know whether the OS supports disk drives like that and, honestly, I can't see why it would to begin with (servers not tending to be computers that people mess with much once set up). I can't check this yet because my server is not yet built and the only other server I have done with unRAID is my parents, which is a fair distance away. Any thoughts?

Welp. Changing systems worked. As thanks for your simple and "I should have thought of that" solution, I will tell you of the stupid thing I did while trying it out. So I set up my old computer that I never use anymore since my only other system uses SteamOS at the moment. My monitor has DVI and VGA and a button on the front that allows you to switch between the two; it is useful in these kinds of situations. So, I get it booted up, having to wait forever because the thing is 6 or 7 years old. I get to the command prompt and hit a key. Nothing happens. Now I am perplexed. What the hell is going on, this computer can't be that bad. Well, many minutes go by, I have already typed out a response revealing how this isn't working and I guess I will need to buy a new flash drive when I decide I will give it one last try. So I go through all of it again, making sure to hit lots of keys because maybe that will help. Same result. How sad. I switch back to send the reply and what do I see at the end of my post, but this: "bkjhsdfrbjkvbdfr ,jkmnvdswrb w drvkbjnu jkn,sbfkbj " I was using the wrong keyboard. Switched back, used the correct keyboard and voila! Success. I thank you again for your help. But don't go too far, I will probably need it again, if this story is anything to go by.

Pretty simple really, title says it all. Specifically, the command prompt seems to hang after it shows this: U:\syslinux\syslinux.exe -maf U: and the cursor moves to the next line and blinks menacingly. After this I cannot type anything. The first time this happened I left it overnight, but the next morning it was still hung up here. The drive is the SanDisk Cruzer Fit, 8GB, that is suggested on the Hardware Recommendations page. The volume label is showing as UNRAID, I (quick) formatted it to FAT32, allocation size of 4KB, ran the command prompt as administrator. I'm doing all of this on Windows 7 if that helps. As far as I can tell, I am doing everything right, but hopefully I'm not and you fine people can reveal it to me. I don't really want to have to buy another drive and that is pretty much the only idea I have right now.