From owner-freebsd-current@FreeBSD.ORG Sun Dec 8 17:31:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A4B0537 for ; Sun, 8 Dec 2013 17:31:40 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B5A5F11C1 for ; Sun, 8 Dec 2013 17:31:39 +0000 (UTC) Received: from ASUS ([89.217.100.79]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MFu0Y-1Vkk750gR4-00Er6c for ; Sun, 08 Dec 2013 18:31:37 +0100 From: "Stefan Hegnauer" To: Subject: nanobsd / dd problem? Date: Sun, 8 Dec 2013 18:31:36 +0100 Message-ID: <000001cef43b$591c7c90$0b5575b0$@hegnauer@gmx.ch> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac70O1iHdH6sc8CUTd+WE4nGFBizXw== Content-Language: de-ch X-Provags-ID: V03:K0:eDX1SLwdNi8ApP6W+u1oYg1MUc/4Ja0jQqxnWKRblUykdoQHfZ9 xBRPiQpUqVZVrw3Fd4oKGlclQY1W6e11AMJ21NajluLIXbWQ+XS255WwbZw7UkUzAA2w1h0 xKYsKbacqmGq6rfQNy+2rB8oG8qQ6l3SYXO4CUC+Vm1JXa9lhR4D5V53DEBHJEYhw1QQqe9 iptYRC63Cl96auJ4DQV1Q== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Dec 2013 17:31:40 -0000 Hi, I am using freebsd-current (FreeBSD BUILDMASTER 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r259095: Sun Dec 8 10:20:40 CET 2013 root@BUILDMASTER:/usr/obj/usr/src/sys/ASUS i386) in a VirtualBox as a build machine for nanobsd images to be used on pc-engines.ch alix boards. The only difference to GENERIC is the inclusion of 'march=geode' and disabling of most debugging switches (malloc, Witness etc). Worked like a charm in the past. Since late summer - sorry, no exact date / svn revision - nanobsd.sh fails at the last stage when building the disk image, e.g. with ... 00:00:25 ### log: /usr/obj/nanobsd.alixpf//_.di # Looking a bit closer it seems that dd(1) returns with an I/O error whenever the input is a file created with mdconfig(8): # dd if=/dev/zero of=somebackingfile bs=1k count=5k # mdconfig -f somebackingfile -u md0 # newfs -U /dev/md0 # dd if=/dev/md0 of=/dev/null dd: /dev/md0: Input/output error 10241+0 records in 10241+0 records out 5243392 bytes transferred in 3.240345 secs (1618159 bytes/sec) The outputfile in nanobsd.sh seems to be error-free. Anyone else seen similar behaviour? How to proceed/fix it? Thanks Stefan