2.4.4 p2 pfsense wds500g2x0c install fails

admins

Hi
I wanted to install pfsense 2.4.4 on a WD NVMe wds500g2x0c with zfs.
Thw wizard sees the disk. After the ZFS Configuration the shell displays:
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
kern.geom.part.mbr.enforce_chs: 0 -> 0
nvme0: resetting controller

After this message the installation hangs. Has anyone a solution?

thx
admins

jimp

Exactly which options did you pick for ZFS in the installer?

First, try one of the other ZFS layout options, specifically try GPT and not MBR or BIOS.

Check the BIOS for boot options as well, it may need to be on UEFI.

If that fails, have you tried using UFS?

It's also possible that support for that drive/controller isn't great in FreeBSD 11.2. We should have some pfSense 2.5.0 alpha snapshots soon based on FreeBSD 12.x you can try if nothing else works. I wouldn't run that in production any time soon, though.

admins

For everyone who want to use this m.2 ssd: dont use it. the driver is buggy. ufs crashes and zfs crashes.
I've checked now with different layout options: panic an crashes.
Thx jimp for your help. I need to use an other m.2 disk.

regards
adminst

jimp

I don't have an NVMe disk in hardware running pfSense, but I am using a Samsung 970 EVO 500GB - NVMe PCIe M.2 2280 SSD (MZ-V7E500BW) in a FreeBSD 12.0 box and it's perfect.

A Former User

I know this is old thread, but I wanted to provide information in case anyone runs into it also. Similar error to OP and similar resolution... (although this is with the latest release 2.5.0)

I am setting up a refreshed pfSense box and using a quite old but little used Samsung 830 series 128GB SSD. It is a dell version that was removed from a laptop a good 7 years ago but didn't see much use except for test installations of Windows 10.

During setup, I read the documentation which steered you towards ZFS, especially on UEFI modern gear, so I did that and left the default ZFS setup options selected. When executing the final Yes, it would attempt to do:

kern.geom.part.mbr.enforce_chs:

but then nothing, and eventually the screen would keep popping up with:

ahcich1 timeout on slot x port x, a bunch of "SEND_FPDMA_QUEUED DATA SET MANAGEMENT" and just repeating timeouts.

I then thought, let's try an old rusty spindle HDD and sure enough, that kern.geom command went right through and started copying files right away and no problems. Finger beginning to be pointed at the Samsung 830 (or its firmware) I then grabbed another SSD from my parts drawer, this time, an Intel X25-V 40GB (yeah.. old!), and tested another ZFS install and it too blew through without a drama.

so similar resolution to the guy above, a different SSD seems to work, which makes me think its a firmware issue with the SSD perhaps (and 830 is very old series, so I'm not surprised to be honest...but i was trying to re-purpose some old gear so as to not waste resources!)