Upgrade from 2.0.1 to 2.1.2 corrupted one of my boot environments
-
Hi,
I upgraded from 2.0.1 to 2.1.2, my system has two boot environments F1 and F2 after the first upgrade on F2 went fine (booted to F2)
I ran for a week and tested everything ….
Then I upgraded boot environment F1 from 2.0.1 to 2.1.2, but now the / or root fs wouldn't mount R/W and said it needed an fsck
At this point I had a good boot on F2 ( / on /dev/ad4s2a ) and a non-functional boot on F1 ( / on /dev/ad4s1a) obviously not what I want and I was loath to do a fresh install over both my working boot partitions.
So I tough dump/restore utilities alas pFsense seems to not deliver /sbin/restore or /sbin/mksnap_ffs both needed to clone onto another boot media.
#####################################
sometimes the XML config files are just not enough …
why is /sbin/restore and /sbin/mksnap_ffs missing ?
#####################################
Painful I had to download the ISO get the utilities I needed, then I was able to make a bootable USB with my configs and all my changes and notes
Okay I could have installed form scratch but that would have been excessive down time on my firewall and also if it all went south I wojuld be SOL.
Once I had a bootable USB thumb drive (yes all works when the SATA drive was pulled) that ran my firewall, I felt completely comfortable doing the following to fix the broken boot environment on my hard drive.
gpart show
df -kl
newfs -L rootfs -U /dev/ad4s1a
mount /dev/ad4s1a /mnt
cd /mnt
pwd
df -kl
dump -0Lauf - /dev/ad4s2a | restore -rf -
cd /mnt/etc#–-------------------------------------------------------------
update the /mnt/etc/fstab to BOOT the F1 clone
was /dev/ad4s2a for / and /dev/ad4s2b for swap
now /dev/ad4s1a for / and /dev/ad4s1b for swap
#---------------------------------------------------------------
vi /mnt/etc/fstab
cd /
umount /mntThe above (USB prep not shown - but I used the same dump/restore pipeline) took a bit of research but I had solid piece of mind the entire time and now I also have a working USB thumb (the best part all my notes and tweaks also copied over)
-
@Jon:
I upgraded from 2.0.1 to 2.1.2, my system has two boot environments F1 and F2 after the first upgrade on F2 went fine (booted to F2)
I ran for a week and tested everything ….
Then I upgraded boot environment F1 from 2.0.1 to 2.1.2, but now the / or root fs wouldn't mount R/W and said it needed an fsck
At this point I had a good boot on F2 ( / on /dev/ad4s2a ) and a non-functional boot on F1 ( / on /dev/ad4s1a) obviously not what I want and I was loath to do a fresh install over both my working boot partitions.
Why didn't you just duplicate the working F2 slice to F1 overwriting it? That can be done with a few clicks from the web interface.
-
Not running Nano? Looks like a custom install.
Steve
