Bug #15534
open
pfSense’s installer not table to see ZFS-formatted internal drive
0%
Description
Brilliant pfSense DevTeam!
CONDITIONS
Installing pfSense CE 2.7.2-REL from USB-flash (Transcend 16Gb USB 2.0, image from Netgate servers, bootable usb created by Rufus) on a bare-metal server (Fujitsu Primergy RX300 S7, LSI RAID10 on PCI) as recovery operation to reinstall pfSense.
ISSUE
pfSense able to successfully reading previous config.xml file from internal disk (which are VDISK based on RAID) but CANNOT see internal disk (mfid0) when proceeding to install and choose “Auto ZFS” option and “stripe” option: ONLY BOOTABLE USB-drive (da0) ARE IN LIST available to choose.
But if re-initializing RAID (no matter “slow” or “fast” initialization used on RAID’s BIOS utility level), in the pfSense installer after “Auto ZFS” and “stripe” options, BOTH USB-FLASH AND RAID VDISK ARE IN LIST and available to choose.
So, there are some impossibility to pfSense’s installer to see previously ZFS-formatted drive.
How to fix this issue?
Updated by Christopher Cope 7 months ago
- Status changed from New to Duplicate
I originally misread the report. Please provide a step-by-step to reproduce this issue, so we can attempt to recreate it.
Testing locally and the installer is able to see previously ZFS formatted drives. Presumably the issue you are seeing is due to the RAID controller.
Updated by Sergei Shablovsky 7 months ago
Christopher Cope wrote in #note-1:
Thank You for answering!
I originally misread the report. Please provide a step-by-step to reproduce this issue, so we can attempt to recreate it.
0.
Download pfSense CE 2.7.2-REL from official Netgate public servers.
Make bootable USB-flash drive by Rufus (default settings).
1.
There is normally working pfSense server. We decided to reinstall pfSense from scratch.
So, saving config.xml and backup some extra config files (not directly involved in pfSense work, for example nano, trafshow, nvim, zsh,…).
2.
Doing hard reboot (no matter by pressing 5 from main “dumb” terminal menu and than choose “Normal reboot” or by short pressing “POWER” button on server).
3.
Choosing USB-flash drive as for booting from by server on-screen BIOS menu.
4.
pfSense loader started, and Agreement appear.
5.
Choose “Rescue Restore previous config”. Some messages appear on a short period of time at bottom of local screen, that indicate that config.xml successfully finds and copied to temporary place.
6.
Choose “Auto (ZFS)” option, proceed…
7.
Choose “stripe” option, proceed…
8.
ONLY BOOTABLE USB-DRIVE are in drives list!
Testing locally and the installer is able to see previously ZFS formatted drives. Presumably the issue you are seeing is due to the RAID controller.
RAID controller not to impact (please read my initial text carefully!) because AFTER HARDWARE LOW-LEVEL RE-INITIALISATION BY RAID the same(!) pfSense installer from the same(!) USB-flash drive -> LIST virtual drive (BSD system name “mfid0”) as available on STEP 8 above.
Updated by Sergei Shablovsky 7 months ago
Christopher Cope wrote in #note-1:
Testing locally and the installer is able to see previously ZFS formatted drives.
Please describe:
- Your bare metal server hardware config
- How You testing the issue?
Updated by Jordan G 6 months ago
latest version of the installer is able to see drives that are part of a ZFS pool, trying to install to them will present an error if you haven't previously run gmirror destroy swap in the rescue shell but they should be visible to the system unless they are behind some other controller.