Search results

LACP with layer 3/4 hashing is typically how most setups are configured.

It was an ebay 9300-8i LSI SAS3008 that came "preflashed" to IT mode. I tried upgrading the FW on the card and going back and forth to Raid mode and IT mode. It didn't make any difference. I worked on it for about a week at night before I swapped the same card to another working server and...

Oh yes, I figured it out. It was the SAS controller the whole time. I grabbed a new one and put it in and everything magically started working.

Bios mode works fine and after all the head scratching and lifecycle and bios up/downgrades I decided that I'd move onto another server. For the next 3 servers I had to flash the LSI 3008's into IT mode as they were not already done. Server #2 BIOS 2.17 Lifecycle 2.84.84.84.0 I did the install...

While I was scratching my head I decided to put the 730mini back into the server and I was going to create a raid setup in an attempt to rule out the LSI 3008 so while I was in there I found that there is an option to turn the disk into a non-raid disk. I'm assuming that there was some sort of...

Resetting the NVRAM and then going back and setting up the BIOS results in the same crash.

After flashing I get the boot animation and then the failure again. Going to clear the NVRAM but now but not sure it's going to help

I'm going to take a few moments and reflash the IT mode as these cards were not done by me and I'm going to see if that could also be the problem.

I just tested installing Debian 11.7 on a single drive with the default layout to ensure that there is nothing funky there. On the first boot it still failed so more digging is needed.

While I was waiting to write to a usb drive the server booted past the enumerating boot devices screen and errored out here. This is a different UEFI0004 Vr 00015 from the last time.

I've set up the bios on both working and nonworking machines with the same configuration. There is no error logs on the install and it completes and reboots. Once I get the firmware back to where the uefi bootloader will error out I will post an image.

Okay, let me preface this with I'm not new to Proxmox and I've run this on lots of Dell servers. I've also been working on this for a few days so I might have missed a step or two of the actual troubleshooting This issue is only for UEFI boot and not bios boot. The setup consists of an 11-node...

Something also to look at would be system IO. IPerf behaves differently than most network traffic where packets per second affect the Linux bridge and networking stack. You can increase the MTU by using Jumbo frames and also switch from Linux bridge to OVS and DDPK if your hardware nic supports...

Just remember that you get what you pay for and modules garden has been around alone time and while its expensive... it automation. So if your just starting off then just have whmcs email you when a customer places an order and then you can process it when you have time to manually deploy a...

Here are some of my thoughts. If you must use hard drives ensure that they are SAS not SATA and have 10K+ RPM's. 15K's are better. The faster you can spin the disk the more io it can handle. It still will not be much as HDDs are just slow. You would need to throw more HDD's to get better...

What directly relates to the slow chunk verification speed?

After the CPU has been upgraded. Uploaded 562 chunks in 5 seconds. Time per request: 8914 microseconds. TLS speed: 470.51 MB/s SHA256 speed: 265.23 MB/s Compression speed: 444.40 MB/s Decompress speed: 726.08 MB/s AES256/GCM speed: 788.28 MB/s Verify speed: 193.03 MB/s...

Here is my example company. It's an apartment management company that has 500 employees. 400 of them are leasing agents that constantly respond to issues from residents that live at their various locations. With everyone using one of the shared email services (Gmail, Yahoo, Outlook...etc.) you...

vmbr0 is my management interface and no VM assigned to that interface. vmbr1 is where all the VM's attach to. I never had any issue with OVS, it performed fine, but I got a wild hair one day and decided that why have an extra level of complication to my setup. So I removed it.

With PVE Linux bridges you have two scenarios that I will outline below. 1. Bridge Vlan aware - You're not tagging in the VM configuration inside of PVE, but applying the tag inside the OS networking. 2. Standard Bridge - You can tag with the VM configuration inside of PVE. This is the same way...