From owner-freebsd-questions@FreeBSD.ORG Mon Aug 25 12:55:00 2014 Return-Path: Delivered-To: questions@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 5234858E for ; Mon, 25 Aug 2014 12:55:00 +0000 (UTC) Received: from server1.shellworld.net (shellworld.net [69.60.117.94]) by mx1.freebsd.org (Postfix) with ESMTP id 2BA54381E for ; Mon, 25 Aug 2014 12:54:59 +0000 (UTC) Received: from server1.shellworld.net (localhost [127.0.0.1]) by server1.shellworld.net (Postfix) with ESMTP id EC6B6228B7 for ; Mon, 25 Aug 2014 08:54:52 -0400 (EDT) To: "questions@freebsd.org" Subject: Re: Has the Procedure for Regenerating A FreeBSD Installation Disk Changed? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <73807.1408971292.1@server1.shellworld.net> Date: Mon, 25 Aug 2014 07:54:52 -0500 From: "Martin G. McCormick" Message-Id: <20140825125452.EC6B6228B7@server1.shellworld.net> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2014 12:55:00 -0000 Roland Smith writes: > Could it be that your filesystem is full? > > Although I don't have FreeBSD-9.1-RELEASE-amd64-disc1.iso around, I tried > the > tar command with FreeBSD-10.0-RELEASE-amd64-disc1.iso and that unpacks > just > fine. An excellent question so I tried the exact same procedure on another FreeBSD9 system and got precisely the same results down to the outputs of the two attempts comparing perfectly. I think I should try FreeBSD-10.0-RELEASE-amd64-disc1.iso to see what happens. I really need to use 9.1 since this is a replacement for a FreeBSD9.1 system that is failing, but it might indicate what other part of the process is going wrong.