RE: Problems booting into ZFS on recent stable/9
Hi Cris, Do you still have the following file: /boot/zfs/zpool.cache ? I guess that with the kernel upgrade you have just replaced that :) This is the file that you can create with: zpool set cachefile=/boot/zfs/zpool.cache Regards, Ivailo Tanusheff -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Chris Ross Sent: Monday, July 01, 2013 9:50 PM To: freebsd-stable@freebsd.org Cc: freebsd-spar...@freebsd.org Subject: Problems booting into ZFS on recent stable/9 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-0x1022f 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=0" to /boot/loader.conf. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounter "tick" frequency 5 Hz quality 1000 Event timer "tick" frequency 5 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=zfs:zroot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems booting into ZFS on recent stable/9
On Jul 1, 2013, at 22:30 , Chris Ross wrote: > Maybe I messed something up in the kernel I was building. Let me drop back > to a GENERIC > from the same stable/9 and see if that will boot. I just have to figure out > how to get it onto the > disks. :-) User error. Thanks, Gary. I took too many things out of my kernel, I'm sure. I loaded a GENERIC from the same sources and it came up fine. I'll adjust my kernel config and try again, but it's definitely not a FreeBSD problem. Sorry for the noise. - Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems booting into ZFS on recent stable/9
On Mon Jul 1 19:51:45 UTC 2013, Gary Palmer wrote: > What is the interface that the disk(s) that ZFS are on? If it's the > AcerLabs ATA controller, then there are no disks found. There is an > earlier ATA bus (at a guess from the fact ata2 and ata3 are shown above), > however I don't see any disks detected. Normally ATA and SCSI/SAS disks > are probed asynchronously near the end of the boot and that appears > to be missing Right you are. That's likely the core of the problem, then. On my netboot of an older kernel, I see more at the end as you describe: atapci0: port 0x10200-0x10207,0x10218-0x1021b,0x10210-0x10217,0x10208-0x1020b,0x10220-0x1022f 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 nexus0: type unknown (no driver attached) 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=0" to /boot/loader.conf. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounter "tick" frequency 5 Hz quality 1000 Event timer "tick" frequency 5 Hz quality 1000 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 ugen0.1: at usbus0 uhub0: on usbus0 ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: ATA-7 device ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytesuhub0: 2 ports with 2 removable, self powered) ada0: 308921MB (632672208 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ata3 bus 0 scbus1 target 0 lun 0 ada1: ATA-7 device ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada1: 308921MB (632672208 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad1 GEOM_MIRROR: Device mirror/gswap launched (2/2). Trying to mount root from nfs: []... dc0: link state changed to UP Maybe I messed something up in the kernel I was building. Let me drop back to a GENERIC from the same stable/9 and see if that will boot. I just have to figure out how to get it onto the disks. :-) - Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems booting into ZFS on recent stable/9
On Mon, Jul 01, 2013 at 02:49:35PM -0400, Chris Ross wrote: > > 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-0x1022f > 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=0" to /boot/loader.conf. > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > Timecounter "tick" frequency 5 Hz quality 1000 > Event timer "tick" frequency 5 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=zfs:zroot What is the interface that the disk(s) that ZFS are on? If it's the AcerLabs ATA controller, then there are no disks found. There is an earlier ATA bus (at a guess from the fact ata2 and ata3 are shown above), however I don't see any disks detected. Normally ATA and SCSI/SAS disks are probed asynchronously near the end of the boot and that appears to be missing Gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Problems booting into ZFS on recent stable/9
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-0x1022f 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=0" to /boot/loader.conf. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounter "tick" frequency 5 Hz quality 1000 Event timer "tick" frequency 5 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=zfs:zroot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
