new 6.1 install will not boot
Derek Ragona
derek at computinginnovations.com
Wed Aug 23 15:34:38 UTC 2006
I have seen this happen where the kernel is not copied by sysinstall. I
booted the install CD but exited sysinstall to a shell prompt, mounted the
root partitiion and manually copied the kernel. You might give that a try.
-Derek
At 01:48 AM 8/23/2006, Perry Hutchison wrote:
> > Recommend you get a [bigger|second] disk if you can though,
> > or housecleaning will be a constant chore.
>
>I got it more or less working, although not completely set up, and
>then that 10GB disk died: click -- kerthunk -- click -- kerthunk
>continuously, even after cycling power, even with only the power
>connected :(
>
>After replacing it with a 160GB Hitachi, and reinstalling Windoze,
>Linux, and FreeBSD (in that order, as before), I seem to be back at
>square one -- FreeBSD won't boot -- but the details are different.
>Partition Commander now has:
>
> Ptn size ----- type ----- 1st sector # of sectors
> P0 250M FAT32 0x0B 63 514017
> P1 7M Linux ext2 0x83 514080 16065
> P2 41.99G Unix 0xA5 530145 88068330
> P3 85.75G Extended 0x0F 88598475 179831610
> L0 43.75G FAT32 0x0B 88598538 91763217
> L1 400M Linux swap 0x82 180361818 819252
> L2 41.60G Linux ext2 0x83 181181133 87248952
>
>Sysinstall had not commented about the geometry with the 10GB disk,
>but it did this time; and as suggested I let it do what it wanted.
>The Dell BIOS will not tell me what it thinks the geometry is -- it
>just says the drive is EIDE -- so I have no direct way of verifying
>sysinstall's geometry; however the first BIOS partition is a
>working FAT32 and per the instructions that "should" be enough for
>sysinstall to have gotten it right. (The second BIOS partition is
>a Linux /boot, which also works.)
>
>The install appeared to succeed, and the FreeBSD boot manager does
>successfully boot Windoze and Linux, but all attempts to boot FreeBSD
>from the hard disk fail.
>
>The following was transcribed by hand, so there might be some typos;
>and I've added some notes to the right of the lsdev output. I've
>also confirmed, using the loader's "ls", that there is no visible
>file named 'kernel' in the root directory, nor anywhere under /boot,
>/rescue, or /sbin. Where is it supposed to come from, and how do
>I get it where it needs to be without reinstalling the whole thing
>*yet again*?
>
>====================================================================
>
>
>F1 DOS
>F2 Linux
>F3 FreeBSD
>
>Default: F3
>
>BTX loader 1.00 BTX version is 1.01
>Consoles: internal video/keyboard
>BIOS drive A: is disk0
>BIOS drive C: is disk1
>BIOS 640kB/195584kB available memory
>acpi: bad RSDP checksum (210)
>
>FreeBSD/i386 bootstrap loader, Revision 1.1
>(root at opus.cse.buffalo.edu, Sun May 7 03:20:03 UTC 2006)
>Loading /boot/defaults/loader.conf
>Unable to load a kernel!
>/
>can't load 'kernel'
>
>Type '?' for a list of commands, 'help' for more detailed help.
>OK lsdev
>cd devices:
>disk devices:
> disk0: BIOS drive A:
> disk1: BIOS drive C:
> disk1s1: FAT32 # C:
> disk1s2: ext2fs # Linux /boot
> disk1s3a: FFS # FreeBSD /
> disk1s3b: swap
> disk1s3d: FFS # FreeBSD /var
> disk1s3e: FFS # FreeBSD /tmp
> disk1s3f: FFS # FreeBSD /usr
> disk1s4: Unknown fs: 0xf # contains FAT32 D:, Linux swap and /
>pxe devicde:
>OK
>_______________________________________________
>freebsd-questions at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
>MailScanner thanks transtec Computers for their support.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
More information about the freebsd-questions
mailing list