treos33
-
Posts
22 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by treos33
-
-
Yup, flashdrive is cooked. Couldn't even run chkdsk. I was able to restore from a backup and access the web gui.
Thanks for the help!-
1
-
-
I restarted my machine while I was doing some network upgrades, replacing a switch and tidying wires. After restarting the server I can't get to the Web GUI. I can connect via SSH and local console. I can see that it's still getting an IP address (I think this mostly rules out my network changes as the cause). I started in safe mode and GUI safe mode with no luck. I grabbed the diagnostics (attached) via the command line and manually made a backup of the boot drive. I'm debating trying a new USB drive, but I wanted to check for any ideas here first.
-
On 2/10/2020 at 2:30 AM, coolspot said:
I just upgraded 6.8.2 and it looks like it broke my networking entirely ... I can no longer get an IP address even in GUI mode.
I successfully upgrade to 6.8.2 today. Not sure what has changed but it worked. Sorry Coolspot, I hope you figure something out soon!
-
Still hoping to get some help with this issue. I realize this was originally posted during the holiday madness so hopefully I can get a few more eyes on the issue now.
Again, I can't get an IP address when I upgrade to 6.8.0. I have no issues on 6.7.2. I have linked to some other issues above that seem to be very similar to mine.
-
Disabling bonding made no difference for me. I still couldn't get an IP address from DHCP with only one ethernet adapter configured.
Reverting back to 6.7.2 fixed the issue completely.
I did not try booting into GUI mode before reverting to 6.7.2.
-
Another similar issue:
This case and the one I found previously are both using Supermicro motherboards as well.
-
3 hours ago, gberg said:
I remember I had some DHCP issues a while back, then I disabled and then re-enabled bonding, and the issue seemed to be gone since I did that.
Ok, thanks. I'll try this after work today.
-
I'm having similar issues. I created a similar support topic but I'm not getting as much attention as you so I figured I'd try to consolidate here. My post:
Another very similar issue that has been posted recently:
The one thing we all have in common is that we have Supermicro motherboards.
-
My switch does support LACP. This exact configuration was working perfectly for months on 6.7.2.
-
1
-
-
Just wanted to say there seems to be another similar case here:
I'm still hoping to get some help with this. I'd prefer to use DHCP and let me router assign IP addresses if possible.
Thanks
-
After upgrading to 6.8.0 my server was unreachable on the webUI. I was able to connect to the CLI and noticed that the IP address was set to 169.254.234.11. I've gathered that this is an Automatic Private IP. I was able to connect to the webUI at this address and I saw on the network settings that the default gateway was set to "link".
I was able to change the network settings to use a static IP and manually define the gateway and DNS server. This seems to be working fine at the moment but I want to understand why this happened.
I'm not sure if it matters but my mobo has two ethernet ports and I have them configured in a bond. I didn't try removing the bond but this configuration was working perfectly in 6.7.2 for months. Lastly, I have a few different VLANS configured. When I assigned the static IP to my main interface, the IP of my first VLAN was then set to 169.254.234.11. I set all my vlans to static IPs and they're working fine now too.
tower-diagnostics-20191215-1943.zip
I've attached my diagnostics from before I started assigning static IPs. Let me know if there are any other details that would be helpful.
Thanks in advance!
-
So I finally figured out part of the mystery. Whenever I have my 4 port NIC (HP NC364T) installed, IOMMU gets disabled.
The next part of the mystery is why is this happening? I would like to use this NIC to passthrough to VMs at some point.
Also, I did update the bios to the most recent version but it made no difference with this behavior.
-
Yeah I can try that next. I'm on the same bios I tested Proxmox on and it's not exactly ancient.
-
This is as close as I can find to a manual.
Also forgot to mention I briefly had Proxmox installed on this box and I don't remember having any issues with IOMMU.
-
I'm trying to play around with a few VMs on a new machine but I can't enable IOMMU.
I've enabled VT-d and VT-x in bios. The only other virtualization option I see is Intel TXT which I have disabled.
I've attached a snip of my system info and my diagnostics.
Thanks!
Unassigned Devices Preclear - a utility to preclear disks before adding them to the array
in Plugin Support
Posted
I had the same issue. After preclearing one drive, I installed two more but was unable to preclear them. They showed "Starting..." forever. The log showed the initial script invoke line but nothing after that.
I don't know the cause but I was finally able to get started by uninstalling and reinstalling the plugin.