From owner-freebsd-sparc64@FreeBSD.ORG Mon Jul 1 18:49:42 2013 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AD2C06FE; Mon, 1 Jul 2013 18:49:42 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200::ae25]) by mx1.freebsd.org (Postfix) with ESMTP id 786011B58; Mon, 1 Jul 2013 18:49:42 +0000 (UTC) Received: from zalamar.mm-corp.net (static-66-16-13-46.dsl.cavtel.net [66.16.13.46]) (authenticated bits=0) by mail.distal.com (8.14.3/8.14.3) with ESMTP id r61IneOT011845 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 1 Jul 2013 14:49:41 -0400 (EDT) From: Chris Ross Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Problems booting into ZFS on recent stable/9 Date: Mon, 1 Jul 2013 14:49:35 -0400 Message-Id: <951F81F6-5301-4DF4-8822-0567FDABA4DB@distal.com> To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) Cc: freebsd-sparc64@freebsd.org X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jul 2013 18:49:42 -0000 I had a sparc64 (Netra X1) running a stable/9 from late March 2013. = Actually, the kernel may've been a bit newer than that as I was working = with folks to diagnose and repair some Netra-X1 specific issues. But, = ZFS worked fine. I have two pools, zroot as a RAID1 (using equally = sized partitions at the front of two large disks), and a zdata that is a = large pool of the remaining space of both disks concatenated together. After installing a kernel from a build of [yesterday's] stable/9 = today, I now get a failure when trying to boot, which can be seen at the = end of this clip from the end of the boot messages below. Is anyone aware of a change in recent months that might've caused = this, or have any idea what I may've done wrong? In google'ing I've = seen a few posts talking about ways to import the zfs pool to adjust the = cache file, but I'm not sure if that is or isn't my problem. I don't = think I did anything specific with configuring cache files for either = pool. Thoughts are welcome. I don't have physical access to the machine for = quite a few more hours, but when I do should be able to net-boot into = the earlier freebsd stable/9 that I originally installed onto this host, = and can try a few more things. - Chris atapci0: port = 0x10200-0x10207,0x10218-0x1021b,0x10210-0x10217,0x10208-0x1020b,0x10220-0x= 1022f at device 13.0 on pci0 atapci0: using PIO transfers above 137GB as workaround for 48bit DMA = access bug, expect reduced performance ata2: at channel 0 on atapci0 ata3: at channel 1 on atapci0 rtc0: at port 0x70-0x71 on isa0 uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 43 on isa0 uart0: console (9600,n,8,1) uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 43 on isa0 ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is = present; to enable, add "vfs.zfs.prefetch_disable=3D0" to = /boot/loader.conf. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounter "tick" frequency 500000000 Hz quality 1000 Event timer "tick" frequency 500000000 Hz quality 1000 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 Root mount waiting for: usbus0 ugen0.1: at usbus0 uhub0: on = usbus0 uhub0: 2 ports with 2 removable, self powered Trying to mount root from zfs:zroot []... Mounting from zfs:zroot failed with error 2. Loader variables: vfs.root.mountfrom=3Dzfs:zroot