From owner-freebsd-questions@FreeBSD.ORG Sat Sep 18 08:20:31 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8632D1065670 for ; Sat, 18 Sep 2010 08:20:31 +0000 (UTC) (envelope-from djr@pdconsec.net) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by mx1.freebsd.org (Postfix) with ESMTP id 077498FC16 for ; Sat, 18 Sep 2010 08:20:30 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEALERlEyWZcBC/2dsb2JhbACjI8BDhUAEhR6ICQoG Received: from goliath.pdconsec.net (HELO smtp.pdconsec.net) ([150.101.192.66]) by ipmail07.adl2.internode.on.net with SMTP; 18 Sep 2010 17:50:28 +0930 Received: from mail1.pdconsec.net ([192.168.1.41] helo=mail1.pdconsec.net) with IPv4:25 by smtp.pdconsec.net; 18 Sep 2010 18:20:27 +1000 Received: from smtp.pdconsec.net ([192.168.1.32] RDNS failed) by mail1.pdconsec.net with Microsoft SMTPSVC(6.0.3790.4675); Sat, 18 Sep 2010 18:19:13 +1000 Received: from [10.14.6.41] ([150.101.192.69] helo=[10.14.6.41]) with IPv4:10025 by smtp.pdconsec.net; 18 Sep 2010 18:20:26 +1000 Message-ID: <4C947600.9010201@pdconsec.net> Date: Sat, 18 Sep 2010 18:19:12 +1000 From: David Rawling User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3 MIME-Version: 1.0 To: "freebsd-questions@FreeBSD. ORG" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Sep 2010 08:19:13.0151 (UTC) FILETIME=[2D4D20F0:01CB570A] Subject: FreeBSD 8.1 - boot failures (upgrades and clean installs) - root FS corrupt? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Sep 2010 08:20:31 -0000 Hi all I'm striking some trouble attempting to upgrade (and also in building a clean replacement) for an existing 8.0-RELEASE-p3 system running in a virtual machine. The host is Hyper-V R2 and 8.0 has been just fine and dandy. Upgrades and installation generally appear to go fine - no error messages that I can see - but in each case on restarting the system I get only a black screen with a single hyphen on the second line, and the cursor flashing underneath it. Leaving the VM for many minutes does not improve matters - but a Ctrl+Alt+Del does restart it, so it's not "hung" per se. It just fails to start. This is the result of a clean installation: The VM configuration is simple enough - a 64GB disk on IDE 0/0, a DVD on IDE 1/0, an Intel 100Mbps network card (de0), 2 CPUs and 1GB of RAM. Booting the Fixit shell from the DVD - fdisk shows the disk partitioned, seemingly correctly. I've created partitions like so: ad0s1a = 2GB = / ad0s1b = 2GB = swap ad0s1d = 10GB = /var ad0s1e = 48GB = /usr ad0s1f = 2GB = /tmp Mounting them shows the root volume seemingly has data: Fixit# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0 39561 3051 900 77% / devfs 1 0 0 100% /dev /dev/acd0 2251930 2251930 0 100% /dist /dev/ad0s1a 2026030 272730 1591218 15% /mnt/root /dev/ad0s1d 10154158 194 9341632 0% /mnt/var /dev/ad0s1e 48745002 695558 44149844 2% /mnt/root Fixit# Yet the 15% of used space is ... well not used properly: Fixit# ls -la /mnt/root total 0 Fixit# fsck_ffs /dev/ad0s1a produces errors for many (all?) inodes - as if file writes were not properly completed / flushed. When fsck is completed, all contents are in lost+found as inode numbers. Any suggestions on debugging what's going on? I'd really like to be able to get current. Dave. -- David Rawling Principal Consultant PD Consulting And Security Mob: +61 412 135 513 Email: djr@pdconsec.net Please note that whilst we take all care, neither PD Consulting and Security nor the sender accepts any responsibility for viruses and it is your responsibility to scan for viruses. The contents are intended only for use by the addressee and may contain confidential and/or privileged material and any use by other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material.