From owner-freebsd-questions@FreeBSD.ORG Fri Oct 23 05:27:14 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09483106566B for ; Fri, 23 Oct 2009 05:27:14 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id BD8868FC13 for ; Fri, 23 Oct 2009 05:27:13 +0000 (UTC) Received: from r55.edvax.de (port-92-195-71-245.dynamic.qsc.de [92.195.71.245]) by mx01.qsc.de (Postfix) with ESMTP id 9446C28; Fri, 23 Oct 2009 07:27:12 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id n9N5RB3A001560; Fri, 23 Oct 2009 07:27:11 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Fri, 23 Oct 2009 07:27:11 +0200 From: Polytropon To: Steve Franks Message-Id: <20091023072711.f627df21.freebsd@edvax.de> In-Reply-To: <539c60b90910221548l217d6590madd0ef9dc68b95f1@mail.gmail.com> References: <539c60b90910221548l217d6590madd0ef9dc68b95f1@mail.gmail.com> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Mailing List Subject: Re: ad0 mountable after sysinstall, but invalid from boot mgr / mbr (7.2-R) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Oct 2009 05:27:14 -0000 On Thu, 22 Oct 2009 15:48:01 -0700, Steve Franks wrote: > So, I jump back to the liveFS disk, thinking sysinstall zorked the > disk, but I can mount the disk (ad0s1d) just fine, and see the > contents of /mnt/boot/kernel and see /mnt/boot/loader* (never seen a > file with a * in the name, but the one on /boot has a * after > loader too). The root partition should be /dev/ad0s1a, not ad0s1d. If it is, specify another boot device for the loader. Check the examples for "rootdisk" in /boot/defaults/loader.conf. Never seen a * after (not in) a file name? It is possible that the * in /mnt/boot/loader is printed by the ls command which has the ability to indicate file types with suffixes (* for executables, @ for symlinks, / for directories etc.); check if ls has been aliased for the shell on the live file system, e. g. % which ls ls: aliased to ls -FG See "man ls" for more details. Look, same here: % ls /boot/loader /boot/loader* By the way, the output here is colored, but I can't make the mail message show this. :-) I have setenv'd LSCOLORS with this value: % echo $LSCOLORS ExGxdxdxCxDxDxBxBxegeg It only works on color capable terminals, of course. So don't mind the *, it's completely normal and intended. According to your booting problem, check if partitions have been created correctly, and if not, and if you have the time, start again and create correct partitions, e. g. /dev/ad0s1a on / /dev/ad0s1b as swap /dev/ad0s1c isn't touched at all ("whole slice") /dev/ad0s1d on /tmp /dev/ad0s1e on /var /dev/ad0s1f on /usr /dev/ad0s1g on /home or whatever layout you prefer. As I mentioned before, make sure that the booting partition / is a, not d. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...