Sponsored Content
Top Forums UNIX for Advanced & Expert Users Can't boot FreeBSD after successful installation. Post 303036730 by vectrum on Tuesday 9th of July 2019 12:42:16 PM
Old 07-09-2019
Can't boot FreeBSD after successful installation.

This is a cross post as I haven't got any solution and I'm badly in need of one.

I've installed Slackware 14.2 in /dev/sda1 and x86Solaris 10 U6 in /dev/sda3 (sda2 is Linux swap)and boot menu was Solaris grub but, later deleted Solaris partition and installed FreeBSD12 (for i386) on the same partition.

I created separate partitions for /boot (1G), / (1G), /var (2G), /tmp (1G), swap (3G) and / (23G) in FreeBSD and the installation was seemed to be OK as there was no error msg.

But FreeBSD couldn't boot so I had to use Slack's installation disc to boot slack and used lilo -v to add slack in lilo table. Here lilo throws the following errors:

Quote:
Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda1
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/slack.bmp
Calling map_insert_file

Boot image: /boot/vmlinuz -> vmlinuz-huge-smp-4.4.172-smp
Added Linux *

Boot other: /dev/sda3, on /dev/sda, loader CHAIN
Added FreeBSD

Writing boot sector.
/boot/boot.0801 exists - no boot sector backup copy made.
One warning was issued.
I also make /dev/sda1 as active in lilo using fdisk with a command. Now there are two partitions are marked active, /dev/sda1 for slack and /dev/sda3 for FreeBSD.

In lilo boot menu the following error message appears when FreeBSD is selected.

Quote:
FreeBSD/x86 boot
Default: 0:ad(0,a)/boot/loader
boot: loader: not a config directory

FreeBSD/x86 boot
Default: 0:ad(0,a)/boot/loader
boot: _ <*here cursor blinks*>
I think it comes from a leftover of Solaris' grub but I'm not sure.

Here is the lilo.conf entry for slack and freebsd:

Quote:
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
# Linux bootable partition config ends
other=/dev/sda3
table=/dev/sda
label=FreeBSD
I use 486 with 1.5G memory and 180G ide type HDD.

How will I be able to boot FreeBSD?

P.S FreeBSD 4x to 8x installation was much much better. Nowadays everything seems to be foreign.

Last edited by vectrum; 07-09-2019 at 01:57 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how do u remove a messed up freebsd boot installation?

i messed up while installing freebsd into a dual os wannabe system. Now, how do i del it( so i wouldn't get prompted to choose freebsd during boot?)so that i could try installing a different flavour of linux? cheers:eek: (1 Reply)
Discussion started by: coffeecoolers
1 Replies

2. UNIX for Advanced & Expert Users

snort installation on freebsd issues

i'm following the, "How to setup and secure Snort, MySQL and Acid on FreeBSD 4.6 Release" off of the snort.org website. in the documentation it says snort should be installed through the following: ----- make -DWITH_MYSQL -DWITH_FLEXRESP ; make install ----- later it says to do the... (13 Replies)
Discussion started by: xyyz
13 Replies

3. BSD

Reduce boot-time delay on FreeBSD?

Say for instance, I would like to reduce the delay/waiting time for the boot-time menu from 10 seconds to 5 seconds, how would I go about doing it? From what I've been able to find, entering "autoboot 5" into the right file would take care of that for me, but the man pages are unclear as to... (1 Reply)
Discussion started by: DownSouthMoe
1 Replies

4. UNIX for Dummies Questions & Answers

Wi0 d-link DWL-510 installation on freebsd

hello, i have a problem installing a d-link dwl-510 wireless network card on freebsd 4.8 first, i already successfully installed a dwl- 500 (which is a pcmcia card in a pci card) by adding just a few simple lines to my /etc/rc.conf pccard_enable="YES" pccard_mem="DEFAULT"... (0 Replies)
Discussion started by: termiEEE
0 Replies

5. BSD

FreeBSD / KDE installation woes...

Forgive the newbie question. I've been trying to install FreeBSD 5.4 on a new AMD64 based box at work today, and I started running into problems. Maybe some background is appropriate? Here goes... I've finished the first stage of development of a model in C++ which simulates airflow through a... (1 Reply)
Discussion started by: ForestryJim
1 Replies

6. Linux

freeBSD installation

why is my new freeBSD hanging at setting up hostname each time I plug in the network cable i use host name like X.ng I intend to configure it as a gateway (2 Replies)
Discussion started by: AkinOkin
2 Replies

7. BSD

FreeBSD Installation problems

Hi all, I'm new to the world of Unix/Linux (though not to computing in general) and I'm having a few issues installing FreeBSD (v6.2). Firstly, I realise that it's not the most user-friendly of distros, especially for newbies, but it's what I'm required to install so unfortunately I have to... (2 Replies)
Discussion started by: Techmonkey
2 Replies

8. Windows & DOS: Issues & Discussions

How do I remove FreeBSD to boot from Windows CD?

Just got free laptop w/FreeBSD. Won't boot from CD, only boots into FreeBsd. I need to install Windows, what do I do?:( (6 Replies)
Discussion started by: laforg
6 Replies

9. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

10. BSD

An installation script on freeBSD

Hello So i got my hands on some freebsd iso, installed it in a qcow2 image and installled git and bash. So far, so good. Git repositry retireved install script executed files got copied files have exec flag files are in $PATH / found by which / bash-completion works But still,... (3 Replies)
Discussion started by: sea
3 Replies
LILOCONFIG(8)						     liloconfig documentation						     LILOCONFIG(8)

NAME
liloconfig - create new lilo.conf file (with diskid and uuid) SYNOPSIS
liloconfig [-h] [-v] [-f] [lilo.conf] DESCRIPTION
liloconfig is an simple program for creating a new lilo.conf file. After creating the new configuration file you must execute '/sbin/lilo'. liloconfig use the lilo.example.conf file as template. In the final lilo.conf file you find many useful comments for custom changes. OPTIONS
-h Print a brief help. -v Print verbose messages. -f Force overriding existing lilo.conf. EXAMPLES
Lines in the configuration file /etc/lilo.conf: ### LILO global section ### #large-memory lba32 boot = /dev/sda map = /boot/map install = menu menu-scheme = Wb:Yr:Wb:Wb prompt timeout = 100 vga = normal #default = Linux ### LILO per-image section ### #boot = /dev/sda boot = /dev/disk/by-id/ata-SAMSUNG_SV1604N_S01FJ10X999999 image = /boot/vmlinuz-2.6.32-5book-686 label = "Linux" #root = /dev/sda1 root = "UUID=18843936-00f9-4df0-a373-000d05a5dd44" read-only # restricted # alias = 1 # optional initrd = /boot/initrd.img-2.6.32-5book-686 image = /boot/vmlinuz-2.6.32-5-686 label = "Linux Old" #root = /dev/sda1 root = "UUID=18843936-00f9-4df0-a373-000d05a5dd44" read-only # restricted # alias = 2 # optional initrd = /boot/initrd.img-2.6.32-5-686 COPYRIGHT and LICENSE Copyright (C) 2011 Joachim Wiedorn This script is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. On Debian systems, the complete text of the GNU General Public License version 2 can be found in `/usr/share/common-licenses/GPL-2'. AUTHOR
lilconfig was written by Joachim Wiedorn. This manual page was written by Joachim Wiedorn <ad_debian at joonet.de> for the Debian project (and may be used by others). SEE ALSO
lilo(8), update-lilo(8), lilo-uuid-diskid(8) 23.1 2011-03-20 LILOCONFIG(8)
All times are GMT -4. The time now is 01:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy