Cannot boot after successful 2.7.2 install - EFI partition problem?
-
@stephenw10 No, the drives are SAS 12Gb/s so they need to connect to the backplane which connects to a controller. Is there a known working controller that's compatible with a PowerEdge R630 that I could try?
-
Hmm, I would have expected that to work in some mode. Maybe it has a different controller firmware?
-
@stephenw10 No, it was updated to the latest controller firmware (25.5.9.0001) from the Dell website.
-
Cloud it be that this bug has popped up again?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230557 -
@mvikman said in Cannot boot after successful 2.7.2 install - EFI partition problem?:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230557
Doesn't seem exactly the same as that. There's no panic here.
Do you have a full boot log we can check?
-
@mvikman said in Cannot boot after successful 2.7.2 install - EFI partition problem?:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230557
I think it looks quite possible that it's this bug, even though it's closed. There is two drives (not one in RAID 0) so the panic isn't expected. I'll get the installer boot log and send it to you and @stephenw10 in case it helps. Is there a way to try this
hw.mfi.mrsas_enable="1"option with the pfSense installer? -
@User6buinf43 said in Cannot boot after successful 2.7.2 install - EFI partition problem?:
Is there a way to try this hw.mfi.mrsas_enable="1" option with the pfSense installer?
I was able to set this option by choosing "3. Escape to loader prompt" and using these commands:
set hw.mfi.mrsas_enable="1"
bootThe drives then showed up as da0 and da1 with the manufacturer/model displayed instead of just mfisyspd. Installation worked and it boots!
Still trying to find a way to get a boot log from the installer.
-
Nice! You can add that permanently as loader variable:
https://docs.netgate.com/pfsense/en/latest/config/advanced-tunables.html#managing-loader-tunables -
Thanks @stephenw10 and @mvikman!
-
@stephenw10 said in Cannot boot after successful 2.7.2 install - EFI partition problem?:
Hmm, seems like you're installing a ZFS mirror onto hardware mirrored drives.
Steve
From my knowledge, choosing “ZFS mirror” option in installer on hardware RAID0, RAID1 or RAID10 enabled on RAID controller - is not the source of any problem: installation proceed and FreeBSD+pfSense installed and working successfully.
I confirm this more than … may be 70+ times. -
@User6buinf43 said in Cannot boot after successful 2.7.2 install - EFI partition problem?:
@stephenw10 Thanks for the suggestion. The controller (PERC H730P) was in HBA mode. I tried changing it to RAID mode (without an array configured) but the result was the same. HBA mode seems like it should be presenting the drives without RAID involvement.
Because RAID or HBA controller’s mode is not the source of problem.
I don't see an AHCI option for the controller.
This setting ALVAYS are in BIOS/UEFI, neither in RAID controller’s side.
Could it be that the PERC H730P is incompatible with pfSense?
Definitely NO! H7XX and up totally compatible with FreeBSD 13 and up (and of coarse pfSense at the top of them).
-
@User6buinf43 said in Cannot boot after successful 2.7.2 install - EFI partition problem?:
@stephenw10 No, the drives are SAS 12Gb/s so they need to connect to the backplane which connects to a controller. Is there a known working controller that's compatible with a PowerEdge R630 that I could try?
Better to replace it on “TRUE HBA” controller, like LSI reflashed to IT-mode, when You make hardware upgrade next time.
Better to read TrueNAS user forum how to choosing right controller’s card exactly for Your server and HOW TO AVOID FAKES.Because TrueNAS like pfSense also are on the top if FreeBSD, all suggestions are more than relevant.
-
@User6buinf43 said in Cannot boot after successful 2.7.2 install - EFI partition problem?:
@stephenw10 I tried setting the Integrated RAID Controller to Disabled in the BIOS but the pfSense installer then gives the error "No disk(s) present to configure".
Exactly! Because motherboard’s BIOS/UEFI knows just nothing behind the RAID controller!
-
@User6buinf43 said in Cannot boot after successful 2.7.2 install - EFI partition problem?:
@stephenw10 No, the drives are SAS 12Gb/s so they need to connect to the backplane which connects to a controller. Is there a known working controller that's compatible with a PowerEdge R630 that I could try?
You need to know that on R360 also exist motherboard’s BUILT-IN RAID. (To activate it You need enter special code in appropriate section in BIOS/UEFI, or (not remember right now) hardware key).
So, in situation when Your hardware RAID dies, You may able to connect disks directly to built-in RAID (of coarse, in 80% cases, You would be need to reformat/initialize drive because internal controller not able to recognize system format on drive. But sometime depends on motherboard revision, buil-in controller ask You to import configuration from drive and booting successfully). -
@User6buinf43 said in Cannot boot after successful 2.7.2 install - EFI partition problem?:
@User6buinf43 said in Cannot boot after successful 2.7.2 install - EFI partition problem?:
Is there a way to try this hw.mfi.mrsas_enable="1" option with the pfSense installer?
I was able to set this option by choosing "3. Escape to loader prompt" and using these commands:
set hw.mfi.mrsas_enable="1"
bootThe drives then showed up as da0 and da1 with the manufacturer/model displayed instead of just mfisyspd. Installation worked and it boots!
Still trying to find a way to get a boot log from the installer.
So looks like this is FreeBSD installer not properly recognizing some hardware RAID controllers and loading MFI driver instead MRSAS.
Recently I have similar problem when CE (probable the Plus also) version, when installer not see VDRIVE at all if it was ZFS formatted. And installer able to see, choose and successfully installing pfSense on it and working w/o any issues ONLY WHEN RE-INITILIZE TGE SAME VDRIVE ON RAID CONTROLLER’S LEVEL (from it’s BIOS menu).
I wrote bug to pfSense bugzilla, but still no solution from pfSense DevTeam. (May be because this is mostly problem on FreeBSD side, not on pfSense. And the second - this issue not affect exactly pfSense’s hardware, , only users with bare metal DIY servers, so not have higher priority to resolving…).
