From owner-freebsd-questions@FreeBSD.ORG Fri Dec 11 06:39:09 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 7BEEA106566C for ; Fri, 11 Dec 2009 06:39:09 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 4EB548FC15 for ; Fri, 11 Dec 2009 06:39:09 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NIz9g-0005u9-O9 for freebsd-questions@freebsd.org; Thu, 10 Dec 2009 22:39:08 -0800 Message-ID: <26739396.post@talk.nabble.com> Date: Thu, 10 Dec 2009 22:39:08 -0800 (PST) From: Ivo Karabojkov To: freebsd-questions@freebsd.org In-Reply-To: <26706523.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ivo@kit-bg.com References: <26667339.post@talk.nabble.com> <26679927.post@talk.nabble.com> <20091208095732.GA64581@ei.bzerk.org> <26701709.post@talk.nabble.com> <20091208232158.f532a1bc.freebsd@edvax.de> <26706523.post@talk.nabble.com> Subject: Re: won't boot after 8.0-RELEASE upgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Dec 2009 06:39:09 -0000 Can someone give me a clue what went wrong in so described upgrade and what made Kernel 8.0 REL not to see either disklabel nor even partition of my gmirror? I need some advice prior starting upgrade process of the rest of my servers. As you see in my previous posts the problem is NOT in DD mode! Ivo Karabojkov wrote: > > As I guessed, I am using standard, not DD mode. Despite of this I was > unable to boot, and even more: FreeBSD 8.0 sysinstall did not find any > partitions neither on the (g)mirror, hardware RAID I described above or > any individual disks part of the RAID. I had to use FreeBSD 7.2 livefs to > copy my data after I formatted one of the disks with new 8.0 sysinstall. > I think this makes our problem totally unexplained. > As an example I'll show you my "unable to boot system with gmirror" fstab: > > # Device Mountpoint FStype Options Dump > Pass# > /dev/mirror/gm0s1b none swap sw 0 > 0 > /dev/mirror/gm0s1a / ufs rw 1 > 1 > /dev/mirror/gm0s1d /usr ufs rw 2 > 2 > /dev/mirror/gm0s1e /var ufs rw,acls 2 > 2 > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > > Something I've noticed: when formatting an entire disk with sysinstall > prior 7.0 its partition looks like this: > > Offset Size(ST) End Name PType Desc Subtype > Flags > > 0 63 62 - 12 unused 0 > 63 781417602 781417664 ad4s1 8 freebsd 165 > 781417665 2990 781420654 - 12 unused 0 > > When formatted with later versions of sysinstall it looks like this: > > Offset Size(ST) End Name PType Desc Subtype > Flags > > 0 63 62 - 12 unused 0 > 63 625142385 625142447 ad4s1 8 freebsd 165 > > I notice that the free part at the end is missing. My "hardware" raid, > described above in this thread, stores its metadata in the beginning of > the disk. Writes in the first sectors result in mirror break and the error > I wrote already. I know all of this because I did a lot of tests to help > all of you to find our problem out. > > I have to say that my problems occured with system initially installed > with FreeBSD 5 or 6. One system with single drive installed with 7.2 > (second example) upgraded with no problems. > > I hope my tests will help to find out what happens wit our older > "disklabelled" systems. > > > Polytropon wrote: >> >> On Tue, 8 Dec 2009 14:09:16 -0800 (PST), Ivo Karabojkov >> wrote: >>> So I'd like to know how >>> to distinguish mode of my current filesystems - is it standard or >>> dangerously dedicated? >> >> If you've first created a slice on the disk, and then >> partitions inside the slice, it's standard mode, e. g. >> >> ad0 a b d e f g >> { [ (/) (swap) (/tmp) (/var) (/usr) (/home) ] } >> s1 >> >> If you've omitted the slice, and created the partitions >> on the disk device itself, it's dangerosly dedicated mode, e. g. >> >> ad0 >> { (/) (swap) (/tmp) (/var) (/usr) (/home) } >> a b d e f g >> >> You can tell by the existence of ad0s1[adefg] vs. ad0[adefg] >> in /dev, or by trying to print the disks's slice table. >> >> >> >> -- >> 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-unsubscribe@freebsd.org" >> >> > > -- View this message in context: http://old.nabble.com/won%27t-boot-after-8.0-RELEASE-upgrade-tp26628661p26739396.html Sent from the freebsd-questions mailing list archive at Nabble.com.