NetBSD Problem Report #53253
From www@NetBSD.org Wed May 2 15:42:24 2018
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
by mollari.NetBSD.org (Postfix) with ESMTPS id DB1AE7A110
for <gnats-bugs@gnats.NetBSD.org>; Wed, 2 May 2018 15:42:24 +0000 (UTC)
Message-Id: <20180502154223.DFAAD7A26A@mollari.NetBSD.org>
Date: Wed, 2 May 2018 15:42:23 +0000 (UTC)
From: tobiasu@tmux.org
Reply-To: tobiasu@tmux.org
To: gnats-bugs@NetBSD.org
Subject: miniroot installation fails with "Bad path" on Ultra 60
X-Send-Pr-Version: www-1.0
>Number: 53253
>Category: port-sparc64
>Synopsis: miniroot installation fails with "Bad path" on Ultra 60
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: port-sparc64-maintainer
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed May 02 15:45:00 +0000 2018
>Closed-Date: Thu May 03 10:50:28 +0000 2018
>Last-Modified: Thu May 03 11:00:01 +0000 2018
>Originator: Tobias Ulmer
>Release: netbsd-8 201805020210Z
>Organization:
>Environment:
>Description:
Attempted installation using http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201805020210Z/sparc64/installation/miniroot/miniroot.fs.gz
Bootblock aborts with "Bad path":
screen not found.
Can't open input device.
Keyboard not present. Using ttya for input and output.
(2 X UltraSPARC-II 450MHz), No Keyboard
OpenBoot 3.23, 2048 MB memory installed, Serial #13190093.
Ethernet address 8:0:20:c9:43:cd, Host ID: 80c943cd.
Boot device: disk File and args:
NetBSD IEEE 1275 Multi-FS Bootblock
Version $NetBSD: bootblk.fth,v 1.15 2015/08/20 05:40:08 dholland Exp $
.Bad path
Fast Data Access MMU Miss
{0} ok .s
Empty
{0} ok .registers
Normal Alternate MMU Vector
0: 0 0 0 0
1: 0 1 fffd26c0 7ed
2: f0000000 f00090a4 f0000000 f0000000
3: fffe0000 fffe0000 0 9bf6f6f463fbffeb
4: ffffffffffffffff 0 0 4000
5: f003c9cc fffe6f30 f 163b5953deebe5c9
6: fffefeb0 4415001600 fffe0000 e
7: fffeefd8 4e 68 f00569c0
%PC f0009ca4 %nPC f0009ca8
%TBA f0000000 %CCR 88 XCC:Nzvc ICC:Nzvc
{0} ok
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-sparc64/53253: miniroot installation fails with "Bad path"
on Ultra 60
Date: Wed, 2 May 2018 18:20:19 +0200
How did you extract the image and what boot command did you use?
The message means the file system is corrupted and /boot can not be read,
so most likely something went wrong when you wrote miniroot.fs to the disk.
Martin
State-Changed-From-To: open->closed
State-Changed-By: martin@NetBSD.org
State-Changed-When: Thu, 03 May 2018 10:50:28 +0000
State-Changed-Why:
Image works, other things went wrong on first try
From: Martin Husemann <martin@duskware.de>
To: Tobias Ulmer <tobiasu@tmux.org>
Cc: gnats-bugs@NetBSD.org
Subject: Re: port-sparc64/53253: miniroot installation fails with "Bad path"
on Ultra 60
Date: Thu, 3 May 2018 12:49:15 +0200
On Thu, May 03, 2018 at 11:25:38AM +0200, Tobias Ulmer wrote:
> I did dd the image to the live disk and then power cycled the machine in
> order to not overwrite things. However it seems I got unlucky. It worked
> the second time.
Glad it worked now!
Typical usage would be to write it to a swap partiton (after unconfiguring
swap), but you boot output did not mention "disk:b" or similar.
Martin
From: Tobias Ulmer <tobiasu@tmux.org>
To: gnats-bugs@NetBSD.org
Cc: port-sparc64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Subject: Re: port-sparc64/53253: miniroot installation fails with "Bad path"
on Ultra 60
Date: Thu, 3 May 2018 11:25:38 +0200
On Wed, May 02, 2018 at 04:25:01PM +0000, Martin Husemann wrote:
> The following reply was made to PR port-sparc64/53253; it has been noted by GNATS.
>
> From: Martin Husemann <martin@duskware.de>
> To: gnats-bugs@NetBSD.org
> Cc:
> Subject: Re: port-sparc64/53253: miniroot installation fails with "Bad path"
> on Ultra 60
> Date: Wed, 2 May 2018 18:20:19 +0200
>
> How did you extract the image and what boot command did you use?
>
> The message means the file system is corrupted and /boot can not be read,
> so most likely something went wrong when you wrote miniroot.fs to the disk.
>
> Martin
>
I did dd the image to the live disk and then power cycled the machine in
order to not overwrite things. However it seems I got unlucky. It worked
the second time.
My mistake, sorry :)
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.