Rescuing a GPT ZFS boot setup
Hey guys, 3 years ago I followed https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror for a FreeBSD 8.1 system (which has since been upgraded to 9.1). A couple days ago I had massive hardware failure, and wound up having to put the two drives into an entirely new PC system. Unfortunately I'm not able to get it to boot off the hard drives. It doesn't even show the FreeBSD bootloader menu it normally would. The BIOS sees both drives and it can boot off the 9.1 install/Live CD without any problems. In the LiveCD, I can see both drives partition tables (gpart show ..) and I can import the zpool (zpool import zroot), and see all my data. I just can't seem to boot from it. I tried rerunning the gpart bootcode commands on both drives (no errors), but no effect. It's also not beyond the realm of possibility I have some BIOS setting wrong, but the drives do show up in the POST and BIOS setting. Does anyone know how I can make my drives bootable again? Thanks. --Andy ___ 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: nfsd CPU usage?
On Sep 11, 2013, at 15:08, Lars Eggert l...@netapp.com wrote: Thanks, I will watch out for the MFC and test. I've been running for a day or so after the MFC, and CPU loads are WAY down. Plus, the cache issues I had haven't reappeared either. I need to bang on it some more, but for now it seems great. Lars signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Rescuing a GPT ZFS boot setup
19.09.2013 09:36, Andrew Moran wrote:
3 years ago I followed https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror
for a FreeBSD 8.1 system (which has since been upgraded to 9.1).A couple
days ago I had massive hardware failure, and wound up having to put the two
drives into an entirely new PC system.
Unfortunately I'm not able to get it to boot off the hard drives. It doesn't even show the FreeBSD
bootloader menu it normally would. The BIOS sees both drives and it can boot off the 9.1 install/Live CD
without any problems. In the LiveCD, I can see both drives partition tables (gpart show ..) and
I can import the zpool (zpool import zroot), and see all my data. I just can't seem to boot
from it. I tried rerunning the gpart bootcode commands on both drives (no errors), but no
effect.
It's also not beyond the realm of possibility I have some BIOS setting wrong,
but the drives do show up in the POST and BIOS setting.
Does anyone know how I can make my drives bootable again?
Maybe the machine is just too picky about partitioning scheme? Try this
black magic:
printf '\ny\n\n\n\ny\n\ny\n\n\n\n\ny\n' | fdisk -u ${YourDiskName}
--
Sphinx of black quartz, judge my vow.
___
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 9-Stable + Atom D510 Freeze
I have an Intel Atom D510 motherboard that is being used in my home router for the last several years. It started on FreeBSD 8-Stable and was recently upgraded to FreeBSD 9-Stable. Through the years I have observed spurious reboots when rebuilding ports, but never world or kernel. I have tried both schedulers in FreeBSD 8-Stable. I have also replaced memory, power supply and disk drives to attempt to isolate hardware from the equation. Last evening I had a complete freeze when rebuilding tshark. The keyboard was dead, screen display was frozen and no network access. I recovered by pressing the reset switch. As always, there are no log entries about panic or core dumps in the swap partition. My question to the group is whether FreeBSD is correctly identifying the number of CPU's on this motherboard. I see 4 listed in the top utility and it appears that code is being run on all 4. Are HT CPU's equal in performance to 'real' ones and should they participate fully in the task scheduler operation? Since my problem is very intermittant and non-reproducable, is it possible that code may try to exercise something in a HT core that should only be run on a 'real' one? My DMESG: Sep 18 20:50:19 mail kernel: Copyright (c) 1992-2013 The FreeBSD Project. Sep 18 20:50:19 mail kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Sep 18 20:50:19 mail kernel: The Regents of the University of California. All rights reserved. Sep 18 20:50:19 mail kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Sep 18 20:50:19 mail kernel: FreeBSD 9.2-PRERELEASE #2: Sat Sep 14 18:27:55 EDT 2013 Sep 18 20:50:19 mail kernel: root@x.x.x:/usr/obj/usr/src/sys/ROUTER amd64 Sep 18 20:50:19 mail kernel: gcc version 4.2.1 20070831 patched [FreeBSD] Sep 18 20:50:19 mail kernel: CPU: Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1662.72-MHz K8-class CPU) Sep 18 20:50:19 mail kernel: Origin = GenuineIntel Id = 0x106ca Family = 0x6 Model = 0x1c Stepping = 10 Sep 18 20:50:19 mail kernel: Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX, FXSR,SSE,SSE2,SS,HTT,TM,PBE Sep 18 20:50:19 mail kernel: Features2=0x40e31dSSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE Sep 18 20:50:19 mail kernel: AMD Features=0x20100800SYSCALL,NX,LM Sep 18 20:50:19 mail kernel: AMD Features2=0x1LAHF Sep 18 20:50:19 mail kernel: TSC: P-state invariant, performance statistics Sep 18 20:50:19 mail kernel: real memory = 1073741824 (1024 MB) Sep 18 20:50:19 mail kernel: avail memory = 1002127360 (955 MB) Sep 18 20:50:19 mail kernel: Event timer LAPIC quality 400 Sep 18 20:50:19 mail kernel: ACPI APIC Table: INTEL MOPNV10N Sep 18 20:50:19 mail kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs Sep 18 20:50:19 mail kernel: FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 HTT threads Sep 18 20:50:19 mail kernel: cpu0 (BSP): APIC ID: 0 Sep 18 20:50:19 mail kernel: cpu1 (AP/HT): APIC ID: 1 Sep 18 20:50:19 mail kernel: cpu2 (AP): APIC ID: 2 Sep 18 20:50:19 mail kernel: cpu3 (AP/HT): APIC ID: 3 Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ 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: Rescuing a GPT ZFS boot setup
Alas, that did not work. But it does look to be BIOS related.
I think this new system has a UEFI bios.
I just read from https://wiki.freebsd.org/UEFI:
* Partitions not seen. When using GPT, FreeBSD will create a protective
MBR. This MBR has one partition entry covering the whole disk. FreeBSD marks
this partition active. This causes at least some UEFI implementations to ignore
the GPT. To fix this the partition needs to be marked inactive.
* Filesystem not seen. FreeBSD's FAT32 code appears to sometimes create
filesystems that the UEFI code can't properly read. If the filesystem is small
enough, use FAT16 or FAT12 instead.
I think this may be my issue. But 9.1 LiveCD does boot and I can see the data
once booted, so there must be a way to fix the boot loader on the drive to work.
Is there a way for me to reinstall the MBR or boot partition on the drives to
make it boot up with this BIOS? :(
Thanks.
--Andy
From: Volodymyr Kostyrko c.kw...@gmail.com
To: Andrew Moran amo...@yahoo.com
Cc: freebsd-stable@freebsd.org freebsd-stable@freebsd.org
Sent: Thursday, September 19, 2013 12:51 AM
Subject: Re: Rescuing a GPT ZFS boot setup
19.09.2013 09:36, Andrew Moran wrote:
3 years ago I followed https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror
for a FreeBSD 8.1 system (which has since been upgraded to 9.1). A couple
days ago I had massive hardware failure, and wound up having to put the two
drives into an entirely new PC system.
Unfortunately I'm not able to get it to boot off the hard drives. It doesn't
even show the FreeBSD bootloader menu it normally would. The BIOS sees both
drives and it can boot off the 9.1 install/Live CD without any problems. In
the LiveCD, I can see both drives partition tables (gpart show ..) and I
can import the zpool (zpool import zroot), and see all my data. I just
can't seem to boot from it. I tried rerunning the gpart bootcode commands
on both drives (no errors), but no effect.
It's also not beyond the realm of possibility I have some BIOS setting wrong,
but the drives do show up in the POST and BIOS setting.
Does anyone know how I can make my drives bootable again?
Maybe the machine is just too picky about partitioning scheme? Try this
black magic:
printf '\ny\n\n\n\ny\n\ny\n\n\n\n\ny\n' | fdisk -u ${YourDiskName}
--
Sphinx of black quartz, judge my vow.
___
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: Rescuing a GPT ZFS boot setup
19.09.2013 16:43, Andrew Moran wrote: Alas, that did not work. But it does look to be BIOS related. I think this new system has a UEFI bios. I just read from https://wiki.freebsd.org/UEFI: * Partitions not seen. When using GPT, FreeBSD will create a protective MBR. This MBR has one partition entry covering the whole disk. FreeBSD marks this partition active. This causes at least some UEFI implementations to ignore the GPT. To fix this the partition needs to be marked inactive. * Filesystem not seen. FreeBSD's FAT32 code appears to sometimes create filesystems that the UEFI code can't properly read. If the filesystem is small enough, use FAT16 or FAT12 instead. I think this may be my issue. But 9.1 LiveCD does boot and I can see the data once booted, so there must be a way to fix the boot loader on the drive to work. Good catch. The fix landed in stable not so long ago (http://svnweb.freebsd.org/base?view=revisionrevision=255017) so you wouldn't find it in 9.2 either. Can you try this: gpart unset -a active ada0 -- Sphinx of black quartz, judge my vow. ___ 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
9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)
Hello, unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to this panic: panic: blockable sleep lock (sleep mutex) 16 @ /usr/local/share/deploy-tools/RELENG_9_2/src/sys/vm/uma_core.c:2553 cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper(c0a3d5bf,4c45522f,5f474e45,2f325f39,2f637273,...) at db_trace_self_wrapper+0x26/frame 0xf00709cc kdb_backtrace(c0a84539,1,c0a4124d,f0070a60,1,...) at kdb_backtrace+0x2a/frame 0xf0070a28 panic(c0a4124d,c0a73003,c09e67b9,c0a71b3c,9f9,...) at panic+0x16f/frame 0xf0070a54 witness_checkorder(c15a5788,9,c0a71b3c,9f9,0,...) at witness_checkorder+0xaa/frame 0xf0070aac _mtx_lock_flags(c15a5788,0,c0a71b3c,9f9,0,...) at _mtx_lock_flags+0xb1/frame 0xf0070ad8 uma_zfree_arg(c15a4a80,c7549320,c7549cb8,c7549320,c7549320,...) at uma_zfree_arg+0x59/frame 0xf0070b1c free(c7549320,c85d1680,c85cedce,2f7,c743b180,...) at free+0xd8/frame 0xf0070b40 dahdi_unregister_echocan_factory(c85ce60c,c0a36b31,108,0,c743b180,...) at dahdi_unregister_echocan_factory+0xbd/frame 0xf0070b60 dahdi_cleanup(0,f0070ba4,c06ded93,c743b180,1,...) at dahdi_cleanup+0x13/frame 0xf0070b7c _linux_module_modevent(c743b180,1,c85d10a0,108,0,...) at _linux_module_modevent+0x50/frame 0xf0070b88 module_unload(c743b180,c0a34a5c,284,292,2a7,...) at module_unload+0x43/frame 0xf0070ba4 linker_file_unload(c78e3000,0,c0a34a5c,2a7,0,...) at linker_file_unload+0x15e/frame 0xf0070bd4 linker_file_unload(c78e3200,0,c0a34a5c,449,c85a9000,...) at linker_file_unload+0x444/frame 0xf0070c04 kern_kldunload(c865b2f0,3,0,f0070cfc,c09bd39b,...) at kern_kldunload+0xd1/frame 0xf0070c30 sys_kldunloadf(c865b2f0,f0070ccc,c0a85bb4,c0a428ae,c0a87198,...) at sys_kldunloadf+0x2b/frame 0xf0070c44 syscall(f0070d08) at syscall+0x2bb/frame 0xf0070cfc Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf0070cfc --- syscall (444, FreeBSD ELF32, sys_kldunloadf), eip = 0x280c088b, esp = 0xbfbfd27c, ebp = 0xbfbfdac8 --- KDB: enter: panic –– Loading the wcb4xxp kernel module leads to some hundred of these: uma_zalloc_arg: zone 256 with the following non-sleepable locks held: exclusive sleep mutex registration_mutex (registration_mutex) r = 0 (0xc85e08ac) locked @ /usr/local/ports-wrktree/usr/ports/misc/dahdi-kmod26/work/dahdi-freebsd-2.6.1-r10738/bsd-kmod/dahdi/../../drivers/dahdi/dahdi-base.c:7296 KDB: stack backtrace: db_trace_self_wrapper(c0a3d5bf,64736265,362e322d,722d312e,33373031,...) at db_trace_self_wrapper+0x26/frame 0xf002e674 kdb_backtrace(c0730080,1,,c0c72e74,f002e720,...) at kdb_backtrace+0x2a/frame 0xf002e6d0 _witness_debugger(c0a40d44,f002e734,4,1,0,...) at _witness_debugger+0x25/frame 0xf002e6e8 witness_warn(5,0,c0a7210b,c0a667f3,f002e768,...) at witness_warn+0x20d/frame 0xf002e720 uma_zalloc_arg(c159d840,0,502,2,c861df34,...) at uma_zalloc_arg+0x34/frame 0xf002e780 malloc(ec,c0aafc2c,502,c84ace00,f002e7c4,...) at malloc+0x115/frame 0xf002e7a4 devfs_alloc(0,c852f5e0,f002e7e0,246,c85c60e0,...) at devfs_alloc+0x31/frame 0xf002e7c4 make_dev_credv(b,0,0,0,1a4,...) at make_dev_credv+0x38/frame 0xf002e7f8 make_dev(c85c60e0,b,0,0,1a4,...) at make_dev+0x4a/frame 0xf002e824 _dahdi_assign_span(1,0,c85c3dce,1c80,0,...) at _dahdi_assign_span+0x39e/frame 0xf002e860 dahdi_register_device(c70ccac0,c861800c,4,0,3,...) at dahdi_register_device+0xd0/frame 0xf002e884 b4xxp_register(c8618000,c85a4970,c861801c,2,c0ab808c,...) at b4xxp_register+0x367/frame 0xf002e8b4 b4xxp_device_attach(c7164900,c74a685c,c0ab808c,c0a3c75f,8003,...) at b4xxp_device_attach+0x141/frame 0xf002e8e0 device_attach(c7164900,4,c0a3c5e7,aa5) at device_attach+0x3c3/frame 0xf002e920 device_probe_and_attach(c7164900,c715fa00,f002e954,c6e51a00,1,...) at device_probe_and_attach+0x4e/frame 0xf002e93c pci_driver_added(c7164980,c85a49c0,c0ab7e5c,c85a49c0,c745e180,...) at pci_driver_added+0xe6/frame 0xf002e964 devclass_driver_added(c85a49c0,c0ac7088,101,0,c85a4a0c,...) at devclass_driver_added+0x74/frame 0xf002e988 devclass_add_driver(c6e96e00,c85a49c0,7fff,c85a4f40,c85a49f4,...) at devclass_add_driver+0x156/frame 0xf002e9a8 driver_module_handler(c74da680,0,c85a49f4,75,c06b82d1,...) at driver_module_handler+0x85/frame 0xf002e9d4 module_register_init(c85a4a0c,0,c0a34a5c,e9,0,...) at module_register_init+0xa7/frame 0xf002e9fc linker_load_module(0,f002ec0c,c0a34a5c,40e,0,...) at linker_load_module+0xa36/frame 0xf002ebec kern_kldload(c852f5e0,c748f400,f002ec34,0,c8525000,...) at kern_kldload+0xca/frame 0xf002ec1c sys_kldload(c852f5e0,f002eccc,c0a85bb4,c0a4214f,c0a87198,...) at sys_kldload+0x74/frame 0xf002ec44 syscall(f002ed08) at syscall+0x2bb/frame 0xf002ecfc Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xf002ecfc --- syscall (304, FreeBSD ELF32, sys_kldload), eip = 0x280c24ab, esp = 0xbfbfd92c, ebp = 0xbfbfde18 --- uma_zalloc_arg: zone 16 with the following non-sleepable locks held: exclusive sleep mutex registration_mutex (registration_mutex) r = 0 (0xc85e08ac) locked @
Re: Rescuing a GPT ZFS boot setup
On Sep 19, 2013, at 6:58 AM, Volodymyr Kostyrko c.kw...@gmail.com wrote: 19.09.2013 16:43, Andrew Moran wrote: Alas, that did not work. But it does look to be BIOS related. I think this new system has a UEFI bios. I just read from https://wiki.freebsd.org/UEFI: * Partitions not seen. When using GPT, FreeBSD will create a protective MBR. This MBR has one partition entry covering the whole disk. FreeBSD marks this partition active. This causes at least some UEFI implementations to ignore the GPT. To fix this the partition needs to be marked inactive. * Filesystem not seen. FreeBSD's FAT32 code appears to sometimes create filesystems that the UEFI code can't properly read. If the filesystem is small enough, use FAT16 or FAT12 instead. I think this may be my issue. But 9.1 LiveCD does boot and I can see the data once booted, so there must be a way to fix the boot loader on the drive to work. Good catch. The fix landed in stable not so long ago (http://svnweb.freebsd.org/base?view=revisionrevision=255017) so you wouldn't find it in 9.2 either. Can you try this: gpart unset -a active ada0 It says 'active' is an invalid attribute. This matches what gpart mangpage says under ATTRIBUTES .. it doesn't list 'active' as an attribute for the GPT partition scheme (but it does for other schemes).I did try to unset 'bootme' but that did not help either. Do I need the newer version of gpart to be able to unset or set it? --Andy ___ 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
9.2 or 10.0 and txz packages
Is there a plan to have repo for files, used by pkgng on upcomming releases? Best regards Zoran ___ 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: Rescuing a GPT ZFS boot setup
Andy Moran wrote this message on Thu, Sep 19, 2013 at 08:12 -0700: On Sep 19, 2013, at 6:58 AM, Volodymyr Kostyrko c.kw...@gmail.com wrote: 19.09.2013 16:43, Andrew Moran wrote: Alas, that did not work. But it does look to be BIOS related. I think this new system has a UEFI bios. I just read from https://wiki.freebsd.org/UEFI: * Partitions not seen. When using GPT, FreeBSD will create a protective MBR. This MBR has one partition entry covering the whole disk. FreeBSD marks this partition active. This causes at least some UEFI implementations to ignore the GPT. To fix this the partition needs to be marked inactive. * Filesystem not seen. FreeBSD's FAT32 code appears to sometimes create filesystems that the UEFI code can't properly read. If the filesystem is small enough, use FAT16 or FAT12 instead. I think this may be my issue. But 9.1 LiveCD does boot and I can see the data once booted, so there must be a way to fix the boot loader on the drive to work. Good catch. The fix landed in stable not so long ago (http://svnweb.freebsd.org/base?view=revisionrevision=255017) so you wouldn't find it in 9.2 either. Can you try this: gpart unset -a active ada0 It says 'active' is an invalid attribute. This matches what gpart mangpage says under ATTRIBUTES .. it doesn't list 'active' as an attribute for the GPT partition scheme (but it does for other schemes).I did try to unset 'bootme' but that did not help either. Do I need the newer version of gpart to be able to unset or set it? You could try the new 10-ALPHA1 LiveCD to unset it.. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ 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: 9.2 or 10.0 and txz packages
Zoran Kolic wrote: Is there a plan to have repo for files, used by pkgng on upcomming releases? If you mean that 10.0-RELEASE will come with a PKGNG-style package repository, then yes. 9.2-RELEASE will most likely still use the old-style pkg_* format, so if you want to use PKGNG with that you'll have to either build your own repository from ports or use someone else's repository. For example, my 9.1-RELEASE/amd64 repository is publicly available and people have also reported success with PC-BSD's repository. Hope this helps, Fonz -- I'm not completely useless, I can be used as a bad example. pgpIgD4rWR8YM.pgp Description: PGP signature
Re: 9.2 or 10.0 and txz packages
On 19/09/2013 17:04, Zoran Kolic wrote:
Is there a plan to have repo for files, used by
pkgng on upcomming releases?
Yes, and the implementation of that plan is advancing well. Hardware is
up and running, and the build system is pretty much ready to go. Most
of the action at the moment is about reducing the number of ports that
fail to build with clang, plus coping with a number of new shared
libraries which will be in the 10.x base system but that come from the
ports for 9.x or older.
If you want to try it out:
% cat /usr/local/etc/pkg/repos/pkg-test.conf
---
pkg-test:
URL: http://pkg-test.freebsd.org/pkg-test-${ABI}/latest
ENABLED: YES
MIRROR_TYPE: SRV
It's not in regular full production updating mode yet, and obviously
it's under a temporary URL for testing purposes, but it does have a
reasonably complete and fairly recent set of packages for amd64/i386
8.x, 9,x or 10.x.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
How goes the 9.2 release?
Building up some servers with 9.1 (latest patch level), but want to switch to 9.2 ASAP if it is solid. How goes the build? Remaining TODOs? Estimated release date? ___ 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: How goes the 9.2 release?
On Thu, Sep 19, 2013 at 06:13:10PM -0600, Brett Glass wrote: Building up some servers with 9.1 (latest patch level), but want to switch to 9.2 ASAP if it is solid. How goes the build? Remaining TODOs? Estimated release date? It should be done within the week. We're finishing up the release notes, and wrapping up some additional release-specific items. The re@ team is going to be more vocal about the status of releases when we slip behind schedule. Sorry that nothing was explicitly announced, as far as the status. Glen pgpk_h__eQrnB.pgp Description: PGP signature
Re: nfsd CPU usage?
On Sep 19, 2013, at 2:50 AM, Eggert, Lars l...@netapp.com wrote: On Sep 11, 2013, at 15:08, Lars Eggert l...@netapp.com wrote: Thanks, I will watch out for the MFC and test. I've been running for a day or so after the MFC, and CPU loads are WAY down. Plus, the cache issues I had haven't reappeared either. I need to bang on it some more, but for now it seems great. Lars has this issue been brought to re@ for inclusion in 9.2 ? --- Mark saad | mark.s...@longcount.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: Rescuing a GPT ZFS boot setup
On Sep 19, 2013, at 9:28 AM, John-Mark Gurney j...@funkthat.com wrote: Andy Moran wrote this message on Thu, Sep 19, 2013 at 08:12 -0700: On Sep 19, 2013, at 6:58 AM, Volodymyr Kostyrko c.kw...@gmail.com wrote: 19.09.2013 16:43, Andrew Moran wrote: Alas, that did not work. But it does look to be BIOS related. I think this new system has a UEFI bios. I just read from https://wiki.freebsd.org/UEFI: * Partitions not seen. When using GPT, FreeBSD will create a protective MBR. This MBR has one partition entry covering the whole disk. FreeBSD marks this partition active. This causes at least some UEFI implementations to ignore the GPT. To fix this the partition needs to be marked inactive. * Filesystem not seen. FreeBSD's FAT32 code appears to sometimes create filesystems that the UEFI code can't properly read. If the filesystem is small enough, use FAT16 or FAT12 instead. I think this may be my issue. But 9.1 LiveCD does boot and I can see the data once booted, so there must be a way to fix the boot loader on the drive to work. Good catch. The fix landed in stable not so long ago (http://svnweb.freebsd.org/base?view=revisionrevision=255017) so you wouldn't find it in 9.2 either. Can you try this: gpart unset -a active ada0 It says 'active' is an invalid attribute. This matches what gpart mangpage says under ATTRIBUTES .. it doesn't list 'active' as an attribute for the GPT partition scheme (but it does for other schemes).I did try to unset 'bootme' but that did not help either. Do I need the newer version of gpart to be able to unset or set it? You could try the new 10-ALPHA1 LiveCD to unset it.. -- WIth the 10-ALPHA2 LiveCD, I get: gpart: attrib 'active': Device not configured I can set/unset the bootme attribute and I can do: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i ada0 But neither seems to get me out of my jam -- the UEFI doesn't seem to see it as a bootable disk. :( --Andy ___ 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: Rescuing a GPT ZFS boot setup
Another thought: since the LiveCDs can see my ZFS root pool, would it be possible to create a CD or memstick image just for the boot loader that then boots the OS of the hard drive? --Andy ___ 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: Rescuing a GPT ZFS boot setup
On 20.09.2013 06:34, Andy Moran wrote: WIth the 10-ALPHA2 LiveCD, I get: gpart: attrib 'active': Device not configured GPT partitions don't have active attribute. You should omit -i argument. Just run `gpart unset -a active ada0`. -- WBR, Andrey V. Elsukov -- WBR, Andrey V. Elsukov ___ 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
