Date: Fri, 11 Apr 2014 22:23:55 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: Chris H <bsd-lists@bsdforge.com> Cc: FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: Unable to mount the root fs on stable/8 r264339, GENERIC kernel, with MBR, FreeBSD slice, and UFS volume labels Message-ID: <alpine.BSF.2.00.1404112158360.9102@mail.fig.ol.no> In-Reply-To: <e44e0e1edb39d8db3be2a3db1d9b3f77.authenticated@ultimatedns.net> References: <alpine.BSF.2.00.1404111820160.9102@mail.fig.ol.no> <e44e0e1edb39d8db3be2a3db1d9b3f77.authenticated@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 11 Apr 2014 10:04-0700, Chris H wrote:
> > Hi,
> >
> > I have a couple of uncritical systems running stable/8 r258344.
> > Hardware is Dell OptiPlex GX260, BIOS A09, which is the latest rev.
> >
> > The r264339 GENERIC kernel are unable to mount the root fs from the
> > hard drive using MBR, FreeBSD slice, and UFS volume labels.
>
> You didn't indicate where it won't mount the drives from. Is this from
> the releng_8 install media. In other words, When booting the install
> media, the installer can't find the drive(s)? Or is it something else?
> When you're presented with the problem, what's the output of ls /dev
> do any of ad0* da0* show up? If so, what's the output from
> gpart list ad0s1 and the likes?
It's when the kernel attempts to mount the root fs from the hard
drive during startup.
Booting the old kernel, r258344 from November 19th, 2013, works as
expected.
Typing ? at the mountroot> prompt presented by the new and faulty
kernel reveals acd0 and ad0 as GEOM managed disk devices. The kernel
printed a few lines or so above the mountroot> prompt that it
perfectly detected the ad0 harddrive.
The latest kernel simply can't find /dev/ufs/root nor /dev/ad0s1a.
Here's the output from various commands:
trond@amanda:~>uname -a
FreeBSD amanda.[withheld] 8.4-STABLE FreeBSD 8.4-STABLE #0 r258344: Tue Nov 19 21:33:39 CET 2013 root@amanda.[withheld]:/usr/obj/usr/src/sys/AMANDA i386
trond@amanda:~>gpart show ad0
=> 63 976773105 ad0 MBR (465G)
63 976773105 1 freebsd [active] (465G)
trond@amanda:~>bsdlabel ad0s1
# /dev/ad0s1:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 2097152 0 4.2BSD 0 0 0
b: 4194304 2097152 swap
c: 976773105 0 unused 0 0 # "raw" part, don't edit
d: 2097152 6291456 4.2BSD 0 0 0
e: 8388608 8388608 4.2BSD 0 0 0
f: 4194304 16777216 4.2BSD 0 0 0
g: 41943040 20971520 4.2BSD 0 0 0
h: 913858545 62914560 4.2BSD 0 0 0
trond@amanda:~>df -ah
Filesystem Size Used Avail Capacity Mounted on
/dev/ufs/root 989M 215M 694M 24% /
devfs 1.0k 1.0k 0B 100% /dev
/dev/ufs/home 3.9G 694M 2.9G 19% /home
/dev/ufs/tmp 989M 7.1M 903M 1% /tmp
/dev/ufs/usr 19G 8.2G 9.7G 46% /usr
/dev/ufs/var 2G 326M 1.5G 18% /var
/dev/ufs/amandahd0 422G 6.0k 422G 0% /var/spool/amanda/hd0
procfs 4.0k 4.0k 0B 100% /proc
linprocfs 4.0k 4.0k 0B 100% /usr/compat/linux/proc
linsysfs 4.0k 4.0k 0B 100% /usr/compat/linux/sys
The results are the same on the spare system.
There I first wiped the harddrive clean, by booting from the
8.0-RELEASE dvd1, ran dd if=/dev/zero of=/dev/ad0 bs=128M, before I
installed 8.0-RELEASE. I then transferred an up-to-date working copy
of stable/8 to the spare system. Next, I compiled world and the
GENERIC kernel, without any hassle. I performed make installkernel and
rebooted.
The boot loader managed its way through the maze, read /etc/fstab and
found the entry for the root filesystem. The new GENERIC kernel,
however, simply can't understand what to do with:
vfs.root.mountfrom="ufs:/dev/ufs/root"
vfs.root.mountfrom.options="rw"
as presented by the boot loader. Mind you, the boot loader hasn't been
replaced yet. Maybe that's the whole issue, however weird it sounds.
/boot/loader.conf is empty btw.
I'm doing a similar attempt in VirtualBox at home as I write this.
There I began with 8.4-RELEASE, and are currently compiling stable/8
r264351.
I'll later try in VBox, 8.4-R -> stable/8 with GPT + UFS, using GPT
labels, just to rule out UFS labels.
> > r258344 obviously can.
> >
> > I even tried regular device names like /dev/ad0s1a in /etc/fstab, and
> > at the mountroot> prompt, i.e. ufs:/dev/ad0s1a. The kernel still
> > cannot mount the root fs.
> >
> > The new kernel (r264339) does recognize the ad0 harddrive, and ad0 is
> > listed as one of the GEOM managed disk devices; acd0 being the other
> > one.
> >
> > Do I need to load additional geom modules, or is it a genuine bug?
> >
> > I have recreated the same conditions on a spare GX260, yes, I have
> > plenty of them.
> >
> > In addition there was some problems with the USB subsystem, so I
> > disabled USB in the BIOS for now. USB is not essential for any of my
> > systems.
> >
> > Maybe it's time to leave stable/8 and enter stable/10 or stable/9.
> > I'll try to compile stable/9 on the spare system, and see how it
> > fares.
> >
> > Any thoughts regarding the problem mounting the root fs?
--
+-------------------------------+------------------------------------+
| Vennlig hilsen, | Best regards, |
| Trond Endrestøl, | Trond Endrestøl, |
| IT-ansvarlig, | System administrator, |
| Fagskolen Innlandet, | Gjøvik Technical College, Norway, |
| tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, |
| sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. |
+-------------------------------+------------------------------------+
From owner-freebsd-stable@FreeBSD.ORG Fri Apr 11 21:24:45 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id CEB0D1A8
for <freebsd-stable@freebsd.org>; Fri, 11 Apr 2014 21:24:45 +0000 (UTC)
Received: from forward1l.mail.yandex.net (forward1l.mail.yandex.net
[IPv6:2a02:6b8:0:1819::1])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "forwards.mail.yandex.net",
Issuer "Certum Level IV CA" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 825C01FC3
for <freebsd-stable@freebsd.org>; Fri, 11 Apr 2014 21:24:45 +0000 (UTC)
Received: from smtp19.mail.yandex.net (smtp19.mail.yandex.net [95.108.252.19])
by forward1l.mail.yandex.net (Yandex) with ESMTP id 934461520DC7;
Sat, 12 Apr 2014 01:24:41 +0400 (MSK)
Received: from smtp19.mail.yandex.net (localhost [127.0.0.1])
by smtp19.mail.yandex.net (Yandex) with ESMTP id 2E348BE00AB;
Sat, 12 Apr 2014 01:24:41 +0400 (MSK)
Received: from 84.201.164.29-vpn.dhcp.yndx.net
(84.201.164.29-vpn.dhcp.yndx.net [84.201.164.29])
by smtp19.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id tEVSmwAicd-OeFW8Rv0;
Sat, 12 Apr 2014 01:24:40 +0400
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(Client certificate not present)
X-Yandex-Uniq: cbe88aa5-df3d-4774-8db1-47cf5f6f89ec
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
t=1397251480; bh=ZwRL1XHbtGvffqV2QDE2ir0jmoElz4j/F31J4B/9j+Y=;
h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:
References:In-Reply-To:X-Enigmail-Version:Content-Type:
Content-Transfer-Encoding;
b=m8Y1CeICqgtMQM+HCpm+kb3xD1PJLMy/K3Fwq0S8dLT4OMLbTYKYtNQ4lTCUvddKs
P87Yf2uNgOoeu7SGUjwnVFHiTwZamzQbMSxeWuJzYOyD7yCvyv4Laykgppwt/XfzR1
zG3RDiL0x7aW83VjAwAoGvgzsWFdAaWkJGXhGfmU=
Authentication-Results: smtp19.mail.yandex.net; dkim=pass header.i=@yandex.ru
Message-ID: <53485D65.9020803@yandex.ru>
Date: Sat, 12 Apr 2014 01:23:49 +0400
From: "Andrey V. Elsukov" <bu7cher@yandex.ru>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Trond_Endrest=F8l?=
<Trond.Endrestol@fagskolen.gjovik.no>, Chris H <bsd-lists@bsdforge.com>
Subject: Re: Unable to mount the root fs on stable/8 r264339, GENERIC
kernel, with MBR, FreeBSD slice, and UFS volume labels
References: <alpine.BSF.2.00.1404111820160.9102@mail.fig.ol.no>
<e44e0e1edb39d8db3be2a3db1d9b3f77.authenticated@ultimatedns.net>
<alpine.BSF.2.00.1404112158360.9102@mail.fig.ol.no>
In-Reply-To: <alpine.BSF.2.00.1404112158360.9102@mail.fig.ol.no>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: FreeBSD stable <freebsd-stable@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>;
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 21:24:45 -0000
On 12.04.2014 00:23, Trond Endrestøl wrote:
>>> r258344 obviously can.
>>>
>>> I even tried regular device names like /dev/ad0s1a in /etc/fstab, and
>>> at the mountroot> prompt, i.e. ufs:/dev/ad0s1a. The kernel still
>>> cannot mount the root fs.
>>>
>>> The new kernel (r264339) does recognize the ad0 harddrive, and ad0 is
>>> listed as one of the GEOM managed disk devices; acd0 being the other
>>> one.
Did you do some changes in the kernel config?
Does the loader detects all the partitions? (lsdev in loader prompt)
--
WBR, Andrey V. Elsukov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1404112158360.9102>