NetBSD Problem Report #54141

From www@netbsd.org  Sun Apr 28 09:05:56 2019
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 832557A194
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 28 Apr 2019 09:05:56 +0000 (UTC)
Message-Id: <20190428090555.AB2D07A1AC@mollari.NetBSD.org>
Date: Sun, 28 Apr 2019 09:05:55 +0000 (UTC)
From: tr@vispaul.me
Reply-To: tr@vispaul.me
To: gnats-bugs@NetBSD.org
Subject: landisk boot.fs unable to find kernel
X-Send-Pr-Version: www-1.0

>Number:         54141
>Category:       port-sh3
>Synopsis:       landisk boot.fs unable to find kernel
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-sh3-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 28 09:10:00 +0000 2019
>Closed-Date:    Wed May 01 09:32:07 +0000 2019
>Last-Modified:  Wed May 01 09:32:07 +0000 2019
>Originator:     Travis Paul
>Release:        current as of Sat Apr 27 22:00:29
>Organization:
N/A
>Environment:
unable to boot and run `uname -a`
>Description:
Landisk (at least the boot.fs) is no longer booting, seems unable to find the kernel:

  NetBSD/landisk ustarfs Primary Bootstrap

  >> NetBSD/landisk Boot, Revision 1.0 (Sat Apr 27 22:00:29 UTC 2019)
  Press return to boot now, any other key for boot menu
  booting hd0a:netbsd - starting in 0
  9362892read section: Input/output error
  boot: hd0a:netbsd: Input/output error
  booting hd0a:netbsd.gz
  open netbsd.gz: No such file or directory 
  boot: hd0a:netbsd.gz: No such file or directory
  booting hd0a:netbsd.old - starting in 2

A current build from mid-March was working, re-tested NetbSD-8 and it boots as well.
>How-To-Repeat:
build or download landisk from current, write boot.fs to a Compact Flash card, attempt to boot.
>Fix:

This issue appears to have been caused by a bad CF Card. latest snapshots are working.

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->closed
State-Changed-By: tpaul@NetBSD.org
State-Changed-When: Wed, 01 May 2019 09:32:07 +0000
State-Changed-Why:
Latest builds working with a new CF Card.


>Unformatted:

Home	PR Database Search