NetBSD Problem Report #51330

From www@NetBSD.org  Sat Jul  9 19:34:51 2016
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 "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id E61817A210
	for <gnats-bugs@gnats.NetBSD.org>; Sat,  9 Jul 2016 19:34:50 +0000 (UTC)
Message-Id: <20160709193449.BDA4F7AB3D@mollari.NetBSD.org>
Date: Sat,  9 Jul 2016 19:34:49 +0000 (UTC)
From: venture37@geeklan.co.uk
Reply-To: venture37@geeklan.co.uk
To: gnats-bugs@NetBSD.org
Subject: Unable to install onto CF card despite kernel detecting it as wd0
X-Send-Pr-Version: www-1.0

>Number:         51330
>Category:       port-hpcarm
>Synopsis:       Unable to install onto CF card despite kernel detecting it as wd0
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-hpcarm-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jul 09 19:35:00 +0000 2016
>Last-Modified:  Sun Jul 10 22:20:01 +0000 2016
>Originator:     Sevan Janiyan
>Release:        HEAD
>Organization:
>Environment:
>Description:
Attempting to install from the latest HEAD snapshot on a Jornada 720 fails, sysinst reports no disk is detected & disklabel wd0 reports that /dev/rwd0 is not configured.
The kernel does detect the CF card as wd0 & I've successfully wiped the card using dd whilst booted in this environment.
System / CF card is ok because I was able to install the latest STABLE snapshot without issue.
>How-To-Repeat:
Attempt to install a latest snapshot of HEAD on a Jornada 720
>Fix:

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-hpcarm/51330: Unable to install onto CF card despite kernel detecting it as wd0
Date: Sun, 10 Jul 2016 09:24:32 +0200

 On Sat, Jul 09, 2016 at 07:35:00PM +0000, venture37@geeklan.co.uk wrote:

 > Attempting to install from the latest HEAD snapshot on a Jornada 720
 > fails, sysinst reports no disk is detected & disklabel wd0 reports that
 > /dev/rwd0 is not configured.

 Can you check where /dev/rwd0 (the symlink) points to? And if it properly
 points to the raw disk raw device, whether the device node has the
 correct minor/major?

 The symlink has only recently been introduced, and I had not expected
 it to be used anywhere during installation.

 Martin

From: Sevan Janiyan <venture37@geeklan.co.uk>
To: gnats-bugs@NetBSD.org, port-hpcarm-maintainer@netbsd.org,
 gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc: 
Subject: Re: port-hpcarm/51330: Unable to install onto CF card despite kernel
 detecting it as wd0
Date: Sun, 10 Jul 2016 16:36:17 +0100

 Hi Martin,

 On 10/07/2016 08:25, Martin Husemann wrote:
 >  Can you check where /dev/rwd0 (the symlink) points to? And if it properly
 >  points to the raw disk raw device, whether the device node has the
 >  correct minor/major?
 >  
 >  The symlink has only recently been introduced, and I had not expected
 >  it to be used anywhere during installation.

 I don't see a symlink, on todays snapshot, it's a character special file.
 ls -lo /dev/rwd0 reports
 crw-r----- 1 root operator - 16, 2 Jul 10 11:14 /dev/rwd0



 Sevan

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-hpcarm/51330: Unable to install onto CF card despite kernel
 detecting it as wd0
Date: Sun, 10 Jul 2016 22:19:33 +0000

 On Sun, Jul 10, 2016 at 03:40:01PM +0000, Sevan Janiyan wrote:
  > On 10/07/2016 08:25, Martin Husemann wrote:
  > >  Can you check where /dev/rwd0 (the symlink) points to? And if it properly
  > >  points to the raw disk raw device, whether the device node has the
  > >  correct minor/major?
  > >  
  > >  The symlink has only recently been introduced, and I had not expected
  > >  it to be used anywhere during installation.
  >  
  >  I don't see a symlink, on todays snapshot, it's a character special file.
  >  ls -lo /dev/rwd0 reports
  >  crw-r----- 1 root operator - 16, 2 Jul 10 11:14 /dev/rwd0

 That should be the same as rwd0c... also try disklabel /dev/rwd0c
 explicitly (or /dev/rwd0d if this is a d-partition port and the above
 device is thereby wrong, which I don't know offhand) to help sort out
 confounding factors.

 -- 
 David A. Holland
 dholland@netbsd.org

Home	PR Database Search