demonmaestro

Members
  • Posts

    418
  • Joined

  • Last visited

About demonmaestro

  • Birthday 11/13/1988

Converted

  • Gender
    Male
  • Location
    Conroe Texas

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

demonmaestro's Achievements

Enthusiast

Enthusiast (6/14)

4

Reputation

  1. After hours of messing with this trying to get it to work finally did. Question: Will the regular system(docker) (non cron version) scan and network check if using normal network and not the docker bridge?
  2. Good day, So I had noticed that the log file has gotten full. A bunch of suggestions was to just delete the old log files that I had done but the log file just fills back up. I'm not really seeing anything off the log button that would cause it to fill up. Even the "Fix Common Problems" app is suggesting me to post here. My uptime is only 185 days. Thank you for your time and help. tower-diagnostics-20220118-0930.zip
  3. When I go to set eth2 (along with eth3) to 802.3ad it still keeps reverting it to Active-backup
  4. That didn't work. tower-diagnostics-20210619-0224.zip
  5. Here you go. It's a brand new install. This has happened on a couple different Supermicro systems. Both with onboard NICS. tower-diagnostics-20210618-1942.zip
  6. I am trying this again on a fresh new install of 6.9.2 and still same issue on a brand new machine. Select 802.3ad and hit save. Once I hit save it will revert to active-backup. I've also notice that its saying the Interface Ethernet port 2 is down. but when I go to terminal and do a "ip a" its showing the eth2 and eth3 as up and showing the bond2 as up. The switch is also showing the connections as up and is configured for 802.3ad.
  7. Good day, So I had rebooted the machine multiple of times and it never did recreate it. I had went up to the DC and "reinstalled" the backup (6.8.3) that I had of the Thumb drive. everything was working as entended. I had then installed 6.9.1 and it broke the 802.3ad again and set it to active-backup. I had reverted back to 6.8.3 and things are back working. Thank you for responding John_M
  8. I had also noticed that its not putting a bond4 in the "ip a" list. Just as proof 6.9.1 is not good i downgraded to 6.8.3 and it worked\ at least the 802.3 but its still not setting it right in the actual networking config deleted the networking. then went in and reconfigured the networks. restarted. networking.cfg gone for good. rebooted. nothing This box is in a DC. Don't have local access. I do have IPMI to the box.
  9. I am having the same issues basically. So this is an OS issue.
  10. I am on 6.9.1, 802.3ad was working before upgrading. Now when I try to set it back to 802.3ad it will revert back to active-backup when I click on save
  11. Is there a way to vlan tag off the individual VMs instead of having to shut down the whole VM/Docker side of things just to add a vlan?
  12. Depending on your OS. you should be able to tag off your OS.
  13. Is there a way to have a pop up of some sort where when click stop array or shutdown and have VM/s running that it will tell you that "VM's are running. Are you sure?".?