Boot & Uncorrectable parity/CRC errors

[MD389]

Hey all,

I just recently picked up a Vnopn J3160 system to replace my previous Untangle virtual firewall appliance. I've installed 4GB of RAM and an older 128GB mSATA Samsung SSD that I had available.

I've been trying to evaluate OPNsense as it seems like a good combination of the things I like about Untangle (reporting, UI & ease of use) but also has the extra power and control that pfSense offers. I originally had pfSense installed and running for about a week to iron out any hardware issues. I installed OPNsense 19.7 last night but ran into an issue that has me stumped.

Installation appears to have gone through without any issue and was able to complete the initial configuration wizard, upon updating the system to the latest kernel & packages then rebooting the console starts to report a bunch of CAM status: Uncorrectable parity/CRC errors on ada0. Based on a little google-foo people have solved this with reseating or replacing SATA cables / enclosures so I removed, cleaned and reinstalled SSD into slot but errors still returned.

The strangest part though is if I shutdown/reboot the system once it starts reporting the errors it will not boot from the SSD anymore and BIOS/UEFI will not accept it as a valid boot media and I need to reinstall via USB again, almost as if the install has been corrupted. I was able to run a quick and extended SMART test on the drive and it reported back no errors.

I will reinstall again tonight to grab screenshots of CAM error messages & SMART results and also test if the problems present themselves with a base install of 19.7 with no upgrades.

Has anyone else seen / heard of problem like this?

Thanks

** UPDATE **

Looks like the faults might all come down to the SSD. Installed to a USB drive for testing and system is not reporting any issues. Will need to do some further testing to see if the drive is actually faulty or if something in OPNsense/FreeBSD just doesn't like this model of SSD.

Have new SSD on the way.

[pirin]

Hi,

I have exactly the same problem. Did you resolve it?

[Supermule]

Using the orrect image to install from??