On Tue, Nov 30, 2021 at 03:25:30PM -0700, Theo de Raadt wrote: > Chris Bennett <cpb_m...@bennettconstruction.us> wrote: > > > After looking over the list, it looks like many SSD's have compatibility > > problems, so I'm just going to switch over to a spinning drive. > > That is news to us. >
I am also more than a little shocked by this. >From amd64 7.0 -current floppy img: OpenBSD 7.0-current Ramdisk #129 Tue Nov 30 11:03 Supermicro X11SSD-F cpu0 Intel Xeon E3-1270 v6 3.80Ghz ------------ >From an auto-installed FreeBSD 12.x by the company: Samsung SSD 860 Pro 256GB RVM01B6Q ACS-4 ATA SATA 3.x device ------------ Back to OpenBSD, amd64 shows sd0 as the floppy img i386 (7.0 release) does not mention sd0 at all I could not get network up at all under either OpenBSD or FreeBSD (zero experience with FreeBSD). However, I did get an error I have never seen before. When they (supposedly) changed boxes, I kept the same /29 IP block. I accidentally assigned the static IP addresses to em0 instead of em1. Then I added it correctly to em1. STDERR constantly repeated that I had assigned the same IP to both. Bringing both down stopped the error. However, I did not touch igb0 (em0) under FreeBSD. After changing igb1 (em1) to the correct address, I got the same error in FreeBSD. Huh? The company refuses to change the SSD to the spinning drive, but I can add it as a second drive. This was a special offer, so I can't complain. I looked at the specials again. All are only with this drive. I am at a complete loss here about what's going on. I specifically grabbed this to be able to run -current OpenBSD. I previously ran this exact type of box with this company before with a 1TB drive. So I have used this IPMI before. -- Frustrated, Chris Bennett
