Bug 58580

Summary: After sysinstall, F2 fails; wrong device specified for /?
Product: Base System Reporter: Chris Pepper <pepper>
Component: i386Assignee: Remko Lodder <remko>
Status: Closed FIXED    
Severity: Affects Only Me CC: murray
Priority: Normal    
Version: 4.9-PRERELEASE   
Hardware: Any   
OS: Any   

Description Chris Pepper 2003-10-26 22:40:16 UTC
	After sysinstall for 4.9RC1-4.9RC4 (from posted ISOs), with our without installing BootMgr and/or setting the FreeBSD partition as active, F2 should boot FreeBSD but fails. Rather than loading the kernel from /, it immediately reboots.

	FWIW, sysinstall & BootMgr/BootEasy work properly from 4.5-RELEASE through 4.8-RELEASE & 4.8-20030801-snap.

	More history available on freebsd-stable@ under "FreeBSD 4.9 RC1 (i386) now available" & "Re: Final 4.9-RC (i386) available now, please help test.".

Fix: 

Unknown.
How-To-Repeat: 	Install FreeBSD 4.9RC1-4 on HP Pavilion 7915 with NTFS (XP) on partition 1 & FreeBSD on partition 2.

$ uname -a
FreeBSD guest.reppep.com 4.8-20030701-SNAP FreeBSD 4.8-20030701-SNAP #0: Sun Oct 26 09:07:55 GMT 2003     root@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/GENERIC  i386
$ cat /etc/fstab
# See the fstab(5) manual page for important information on automatic mounts
# of network filesystems before modifying this file.
#
# Device                Mountpoint      FStype  Options         Dump    Pass#
/dev/ad0s2b             none            swap    sw              0       0
/dev/ad0s2a             /               ufs     rw              1       1
/dev/ad0s1              /c              msdos   ro              0       0
/dev/ad0s2g             /home           ufs     rw              2       2
/dev/ad0s2f             /usr            ufs     rw              2       2
/dev/ad0s2e             /var            ufs     rw              2       2
/dev/acd0c              /cdrom          cd9660  ro,noauto       0       0
proc                    /proc           procfs  rw              0       0
Comment 1 Remko Lodder freebsd_committer freebsd_triage 2006-09-11 12:25:26 UTC
State Changed
From-To: open->feedback

Hello, 

Is this still a problem with more recent versions of FreeBSD? 


Comment 2 Remko Lodder freebsd_committer freebsd_triage 2006-09-11 12:25:26 UTC
Responsible Changed
From-To: freebsd-i386->remko

Grab the PR
Comment 3 Chris Pepper 2006-09-11 14:28:52 UTC
	No idea, and I don't currently have any active FreeBSD systems, sorry.


						Chris
-- 
Chris Pepper:               <http://www.reppep.com/~pepper/>
                             <http://www.reppep.com/weblog/pepper/>
Rockefeller University:     <http://www.rockefeller.edu/>
Comment 4 Remko Lodder freebsd_committer freebsd_triage 2006-09-11 14:51:28 UTC
State Changed
From-To: feedback->closed

The submitter no longer runs FreeBSD so he is unable to tell whether the 
problem is still persisting, close the PR with that reason, if someone 
has feedback, poke me please