Re: problem after installkernel going from 9.0 to CURRENT

2012-12-31 Thread Robert Huff

On 12/30/2012 7:11 PM, Robert Huff wrote:


It indicates
that the / partition cannot be mounted to continue booting.
Maybe you can interrupt at the boot loader and examine the
mount source for /, or manually set it to be ada0p1?


 I'll try that.


OK - I'm at the part of loader2(?) where it shows:

OK

and wants something of the form

disk partitionpath to bootable kernel

However, the sample format for the partition is

0:ad(0,a)

How do I specify a GPT partition?



Robert Huff


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


problem after installkernel going from 9.0 to CURRENT

2012-12-30 Thread Robert Huff

Situation:
	One of my boxes failed, and for various reasons it became easier to 
just scrub and rebuild it.

1) Using BSDinstall, I created the first disk:

ada0p1  freebsd-boot128k
ada0p2  freebsd-swap4g
ada0p3  freebsd-ufs 25g

2) Installed off the CD, got it up and running, everything was good.
3) Like it's predecessor, this wants to run CURRENT.
Used csup (tag=.) to update the source tree as of midnight last night.
4) Built world - OK.
Build kernel - OK.
Ran mergemaster - OK.
Installed kernel - OK.
	5) On rebooting, the loader(??) claims to not be able to find a 
bootable partition - i.e. I get a screen that ends in mountpoint   .

Providing the presumptive value by hand returns error 19.
	6) Boot using installation CD and use gpart show to double check 
device names and partitions; everything looks good.

7) Try normal booting again, no go.

	This is my first time installing to a GPT partitioned system, and I 
have (obviously) failed to grok something.  I checked src/UPDATING and 
found nothing which covered this.

What is it, and how do I fix it?


Respectfully,


Robert Huff
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: problem after installkernel going from 9.0 to CURRENT

2012-12-30 Thread Polytropon
On Sun, 30 Dec 2012 17:26:40 -0500, Robert Huff wrote:
   Used csup (tag=.) to update the source tree as of midnight last night.

This seems to be discouraged today. Instead svn should be used.


   5) On rebooting, the loader(??) claims to not be able to find a 
 bootable partition - i.e. I get a screen that ends in mountpoint   .

Are you sure this isn't the mountroot prompt? It indicates
that the / partition cannot be mounted to continue booting.
Maybe you can interrupt at the boot loader and examine the
mount source for /, or manually set it to be ada0p1?



 Providing the presumptive value by hand returns error 19.

No root partition, probably. :-)



   This is my first time installing to a GPT partitioned system, and I 
 have (obviously) failed to grok something.  I checked src/UPDATING and 
 found nothing which covered this.

That's why _I_ prefer old-fashioned MBR partitioning with
sysinstall which has never failed me. :-)



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: problem after installkernel going from 9.0 to CURRENT

2012-12-30 Thread Robert Huff

On 12/30/2012 6:24 PM, Polytropon wrote:


Used csup (tag=.) to update the source tree as of midnight last night.


This seems to be discouraged today. Instead svn should be used.


	I'm using this for ports, will convert for source ... probably in the 
next round after I deal with this.



5) On rebooting, the loader(??) claims to not be able to find a
bootable partition - i.e. I get a screen that ends in mountpoint   .


Are you sure this isn't the mountroot prompt?


Right you are; sorry, typing from memory on a different system.


It indicates
that the / partition cannot be mounted to continue booting.
Maybe you can interrupt at the boot loader and examine the
mount source for /, or manually set it to be ada0p1?


I'll try that.


Providing the presumptive value by hand returns error 19.


No root partition, probably. :-)


Duh.  :-)


That's why _I_ prefer old-fashioned MBR partitioning with
sysinstall which has never failed me. :-)


	There's something to be said for that.  On the other hand, GPT is the 
rising tide and one has to learn to swim sometimes.



Robert Huff



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org