error when adding PC-BSD via chainloader

Bug #1098885 reported by Mark Benavides on 2013-01-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Grub Customizer
Daniel Richter

Bug Description

Greetings! I get the following error when attempting to add PC-BSD via chainloader using Grub Customizer 3.0.2:

File | New | Chainloader

An error immediately appears:

please Inform the author about this problem. The following information could be helpful:

exception '15ParserException'
 with message 'parsing failed - RegEx not matched'
 in /home/mark/Downloads/grub-customizer-3.0.2/src/lib/ContentParser/Chainloader.cpp:45

My choices are 'quit' or 'continue (risk of data loss)'


#1: My OS's: Win7.64, LMDE (and both appear/work just fine, and reside on my first HDD). PC-BSD CAN be booted if I select to boot from HDD2 at boot (via BIOS) so I know it functions correctly, too.

#2: I VERIFIED the path (/home/mark/yada exists)

#3: I'm TRYING TO add the following via File/New/Chainloader:


echo "Adding Custom PC-BSD system" >&2
cat << EOF
menuentry "PC-BSD_Unix_KDE" {
set root=(hd2,1)
chainloader +1



Thank you! Other than this slight snafu, I LOVE the product!

Please relabel as "user error" when chainloading PC-BSD <G>. I purged grub-customizer and grub, reinstalled grub2 (LMDE) to start from a clean slate and properly edited /etc/grub.d/40_custom, then reinstalled grub-customizer-3.0.4.

my /etc/grub.d/40_custom is:

exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'PC-BSD 9.1(64) (on /dev/sdc1) (hd1,1)'{
    set root='(hd1,1)'
    chainloader +1


Sorry for the late answer. Seems like launchpad changed bug notification :-(

Seems like problem is fixed. So I'll close the bug.

Changed in grub-customizer:
status: New → Invalid
assignee: nobody → Daniel Richter (danielrichter2007)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers