View Single Post
  #3   (View Single Post)  
Old 21st November 2013
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,131
Default

You could try booting a FreeBSD 9.2 installation CD/DVD or USB stick and see whether # gpart show shows any meaningful info. If it does you can mount your FreeBSD partition(s) on /tmp. If you succeed in mounting you should save or backup the data and configuration stuff before attempting to fix the booting issue.

For the commands to fix the booting see the Warren Block's http://www.wonkity.com/~wblock/docs/...d_standard_mbr and/or the EXAMPLES section of gpart(8).

From that manual page (9.2 version):
Code:
Create an MBR scheme on ada0, then create a 30GB-sized FreeBSD slice,
     mark it active and install the boot0 boot manager:

	   /sbin/gpart create -s MBR ada0
	   /sbin/gpart add -t freebsd -s 30G ada0
	   /sbin/gpart set -a active -i 1 ada0
	   /sbin/gpart bootcode -b /boot/boot0 ada0

     Now create a BSD scheme (BSD label) with space for up to 20 partitions:

	   /sbin/gpart create -s BSD -n 20 ada0s1

     Create a 1GB-sized UFS partition and a 4GB-sized swap partition:

	   /sbin/gpart add -t freebsd-ufs -s 1G ada0s1
	   /sbin/gpart add -t freebsd-swap -s 4G ada0s1

     Install bootstrap code for the BSD label:

	   /sbin/gpart bootcode -b /boot/boot ada0s1
Make sure you use the correct FreeBSD disk device name and slice designators
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote