Boot loader missing after upgrade

spittlbm

I just updated from 2.4.4 to 2.4.4_p1 via console. On reboot, I get "GRUB Loading stage2. Read Error"

No worries - I install GAG and load the appropriate partition. PFSense finishes patching. Life is good.

On a whim, I reboot it just to see if everything's fine. An ancient bootloader for EndianFW appears. I haven't used Endian in probably 5 years. I've fresh installed PFSense on these drives at least twice, probably 3x. So I have no idea why it's still there (other than I didn't wipe it properly).

This isn't a PFSense problem - it's a 'me' problem. Another round of GAG and PFSense is back up.

gpart show


=>        1  976773167  ada0  MBR  (466G)
          1  154256129     1  linux-raid  [active]  (74G)
  154256130  822511935     2  linux-raid  (392G)
  976768065       5103        - free -  (2.5M)

=>       63  976773105  ada1  MBR  (466G)
         63  976773105     1  freebsd  [active]  (466G)

=>        0  976773105  ada1s1  BSD  (466G)
          0         16          - free -  (8.0K)
         16  959995873       1  freebsd-ufs  (458G)
  959995889   16777216       2  freebsd-swap  (8.0G)

=>        1  976773167  diskid/DISK-WD-WCC2ECA43221  MBR  (466G)
          1  154256129                            1  linux-raid  [active]  (74G)
  154256130  822511935                            2  linux-raid  (392G)
  976768065       5103                               - free -  (2.5M)

so next I do a

df -h

Filesystem                     Size    Used   Avail Capacity  Mounted on
/dev/ufsid/553dbc1f09af6c8e    443G    8.4G    400G     2%    /
devfs                          1.0K    1.0K      0B   100%    /dev
/dev/md0                       3.4M    164K    3.0M     5%    /var/run
devfs                          1.0K    1.0K      0B   100%    /var/dhcpd/dev

I'm pretty sure I'm booted into ada0s2 and that there's something residual left in ada0s1. Since this is a headless, keyboardless setup, I need to get this fixed.

The mystical Google has suggested that gpart bootcode is the holy grail I'm after, but I thought I'd ask here for a more definitive answer before I break things more...

Thanks!

Gertjan

Hi,

Nuke the raid stuff - visit BIOS if needed.
Btw : nuking means re reinstalling ... take config backups