Page 1 of 1

One of three zpools imported on every boot

Posted: 24 Aug 2015 01:15
by turdburglar
I have three zpools. One is raidz1, one is raidz2, and the third is a simple 2-drive mirror. The raidz1 and mirror pools are fine, but the following appears in the history for the raidz2 pool every time the system is restarted:

Code: Select all

zpool import -d /dev -f -a
It started doing this after I upgraded to 10.2.0.2 - Prester (revision 1778) using the Web GUI. I find it strange that the other two pools don't do it as well. What can I do to stop this behavior?

Re: One of three zpools imported on every boot

Posted: 24 Aug 2015 07:09
by b0ssman
That import statement is normal for emebedded installs. Can you give us some more info about your system? Also a dmesg from boot would be helpful.


Sent from my iPhone using Tapatalk

Re: One of three zpools imported on every boot

Posted: 26 Aug 2015 10:26
by turdburglar
dmesg.boot:

Code: Select all

Copyright (c) 1992-2015 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.2-RELEASE #0 r286738M: Thu Aug 13 21:32:58 CEST 2015
    root@dev.nas4free.org:/usr/obj/nas4free/usr/src/sys/NAS4FREE-amd64 amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz (2666.67-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206c2  Family=0x6  Model=0x2c  Stepping=2
  Features=0x1fa3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,DTS,MMX,FXSR,SSE,SSE2,SS,HTT>
  Features2=0x80982201<SSE3,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,HV>
  AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant
Hypervisor: Origin = "VMwareVMware"
real memory  = 8589934592 (8192 MB)
avail memory = 8237092864 (7855 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <PTLTD  	 APIC  >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
random: <Software, Yarrow> initialized
cryptosoft0: <software crypto> on motherboard
acpi0: <INTEL 440BX> on motherboard
acpi0: Power Button (fixed)
Timecounter "HPET" frequency 14318180 Hz quality 950
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
isab0: <PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 UDMA33 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1060-0x106f at device 7.1 on pci0
ata0: <ATA channel> at channel 0 on atapci0
ata1: <ATA channel> at channel 1 on atapci0
pci0: <bridge> at device 7.3 (no driver attached)
vgapci0: <VGA-compatible display> port 0x1070-0x107f mem 0xec000000-0xefffffff,0xfe000000-0xfe7fffff irq 16 at device 15.0 on pci0
vgapci0: Boot video device
mpt0: <LSILogic 1030 Ultra4 Adapter> port 0x1400-0x14ff mem 0xfeba0000-0xfebbffff,0xfebc0000-0xfebdffff irq 17 at device 16.0 on pci0
mpt0: MPI Version=1.2.0.0
pcib2: <ACPI PCI-PCI bridge> at device 17.0 on pci0
pci2: <ACPI PCI bus> on pcib2
em0: <Intel(R) PRO/1000 Legacy Network Connection 1.0.6> port 0x2000-0x203f mem 0xfd5c0000-0xfd5dffff,0xfdff0000-0xfdffffff irq 18 at device 0.0 on pci2
em0: Ethernet address: 00:0c:29:be:6a:3e
pcib3: <ACPI PCI-PCI bridge> at device 21.0 on pci0
pci3: <ACPI PCI bus> on pcib3
mps0: <Avago Technologies (LSI) SAS2008> port 0x4000-0x40ff mem 0xfd4fc000-0xfd4fffff,0xfd480000-0xfd4bffff irq 18 at device 0.0 on pci3
mps0: Firmware: 15.00.00.00, Driver: 20.00.00.00-fbsd
mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
pcib4: <ACPI PCI-PCI bridge> at device 21.1 on pci0
pci4: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> at device 21.2 on pci0
pci5: <ACPI PCI bus> on pcib5
pcib6: <ACPI PCI-PCI bridge> at device 21.3 on pci0
pci6: <ACPI PCI bus> on pcib6
pcib7: <ACPI PCI-PCI bridge> at device 21.4 on pci0
pci7: <ACPI PCI bus> on pcib7
pcib8: <ACPI PCI-PCI bridge> at device 21.5 on pci0
pci8: <ACPI PCI bus> on pcib8
pcib9: <ACPI PCI-PCI bridge> at device 21.6 on pci0
pci9: <ACPI PCI bus> on pcib9
pcib10: <ACPI PCI-PCI bridge> at device 21.7 on pci0
pci10: <ACPI PCI bus> on pcib10
pcib11: <ACPI PCI-PCI bridge> at device 22.0 on pci0
pci11: <ACPI PCI bus> on pcib11
mps1: <Avago Technologies (LSI) SAS2008> port 0x5000-0x50ff mem 0xfd3fc000-0xfd3fffff,0xfd380000-0xfd3bffff irq 19 at device 0.0 on pci11
mps1: Firmware: 15.00.00.00, Driver: 20.00.00.00-fbsd
mps1: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
pcib12: <ACPI PCI-PCI bridge> at device 22.1 on pci0
pci12: <ACPI PCI bus> on pcib12
pcib13: <ACPI PCI-PCI bridge> at device 22.2 on pci0
pci13: <ACPI PCI bus> on pcib13
pcib14: <ACPI PCI-PCI bridge> at device 22.3 on pci0
pci14: <ACPI PCI bus> on pcib14
pcib15: <ACPI PCI-PCI bridge> at device 22.4 on pci0
pci15: <ACPI PCI bus> on pcib15
pcib16: <ACPI PCI-PCI bridge> at device 22.5 on pci0
pci16: <ACPI PCI bus> on pcib16
pcib17: <ACPI PCI-PCI bridge> at device 22.6 on pci0
pci17: <ACPI PCI bus> on pcib17
pcib18: <ACPI PCI-PCI bridge> at device 22.7 on pci0
pci18: <ACPI PCI bus> on pcib18
pcib19: <ACPI PCI-PCI bridge> at device 23.0 on pci0
pci19: <ACPI PCI bus> on pcib19
pcib20: <ACPI PCI-PCI bridge> at device 23.1 on pci0
pci20: <ACPI PCI bus> on pcib20
pcib21: <ACPI PCI-PCI bridge> at device 23.2 on pci0
pci21: <ACPI PCI bus> on pcib21
pcib22: <ACPI PCI-PCI bridge> at device 23.3 on pci0
pci22: <ACPI PCI bus> on pcib22
pcib23: <ACPI PCI-PCI bridge> at device 23.4 on pci0
pci23: <ACPI PCI bus> on pcib23
pcib24: <ACPI PCI-PCI bridge> at device 23.5 on pci0
pci24: <ACPI PCI bus> on pcib24
pcib25: <ACPI PCI-PCI bridge> at device 23.6 on pci0
pci25: <ACPI PCI bus> on pcib25
pcib26: <ACPI PCI-PCI bridge> at device 23.7 on pci0
pci26: <ACPI PCI bus> on pcib26
pcib27: <ACPI PCI-PCI bridge> at device 24.0 on pci0
pci27: <ACPI PCI bus> on pcib27
pcib28: <ACPI PCI-PCI bridge> at device 24.1 on pci0
pci28: <ACPI PCI bus> on pcib28
pcib29: <ACPI PCI-PCI bridge> at device 24.2 on pci0
pci29: <ACPI PCI bus> on pcib29
pcib30: <ACPI PCI-PCI bridge> at device 24.3 on pci0
pci30: <ACPI PCI bus> on pcib30
pcib31: <ACPI PCI-PCI bridge> at device 24.4 on pci0
pci31: <ACPI PCI bus> on pcib31
pcib32: <ACPI PCI-PCI bridge> at device 24.5 on pci0
pci32: <ACPI PCI bus> on pcib32
pcib33: <ACPI PCI-PCI bridge> at device 24.6 on pci0
pci33: <ACPI PCI bus> on pcib33
pcib34: <ACPI PCI-PCI bridge> at device 24.7 on pci0
pci34: <ACPI PCI bus> on pcib34
acpi_acad0: <AC Adapter> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
ppc0: <Parallel port> port 0x378-0x37b irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
qpi0: <QPI system bus> on motherboard
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xca000-0xcafff,0xdc000-0xdffff,0xe0000-0xe7fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
coretemp0: Tj(target) value 0 does not seem right.
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
coretemp1: Tj(target) value 0 does not seem right.
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
coretemp2: Tj(target) value 0 does not seem right.
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
coretemp3: Tj(target) value 0 does not seem right.
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 10.000 msec
iSCSI boot driver version 0.2.9
xmd version 0.4.4 by NAS4Free Project (experimental)
xmd: default blocklen 32KB, compression LZ4/LZ4HC, level 6
xmd0: Loaded preload cloop image </mfsroot.uzip> 17281024 bytes at 0xffffffff8211aa10 (128MB disk w/LZ4)
random: unblocking device.
mps0: SAS Address for SATA device = dc87721499c7caa8
mps1: SAS Address for SATA device = 8478a247a3c6f1ac
mps0: SAS Address for SATA device = db7d751499c6cc8b
mps1: SAS Address for SATA device = 8478a24988d8cdac
mps1: SAS Address for SATA device = a1993e20a3b09ca5
mps0: SAS Address for SATA device = 628a5b1499c6caa7
mps1: SAS Address for SATA device = a1993e20a3b29fa2
mps0: SAS Address for SATA device = de64761499c6cc8c
mps1: SAS Address from SATA device = 8478a247a3c6f1ac
mps0: SAS Address for SATA device = 84789f529adaf3b0
mps0: SAS Address for SATA device = 84789f549edfd9ac
mps1: SAS Address from SATA device = 8478a24988d8cdac
mps1: SAS Address from SATA device = a1993e20a3b09ca5
mps0: SAS Address for SATA device = 84789f4c83c3edac
mps1: SAS Address from SATA device = a1993e20a3b29fa2
mps0: SAS Address for SATA device = 84789f4ba5c7e4ac
mps0: SAS Address from SATA device = dc87721499c7caa8
mps0: SAS Address from SATA device = db7d751499c6cc8b
mps0: SAS Address from SATA device = 628a5b1499c6caa7
mps0: SAS Address from SATA device = de64761499c6cc8c
mps0: SAS Address from SATA device = 84789f529adaf3b0
mps0: SAS Address from SATA device = 84789f549edfd9ac
mps0: SAS Address from SATA device = 84789f4c83c3edac
mps0: SAS Address from SATA device = 84789f4ba5c7e4ac
cd0 at ata1 bus 0 scbus1 target 0 lun 0
cd0: <NECVMWar VMware IDE CDR10 1.00> Removable CD-ROM SCSI device
cd0: Serial Number 10000000000000000001
cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes)
cd0: Attempt to query device size failed: NOT READY, Medium not present
cd0: quirks=0x40<RETRY_BUSY>
da0 at mpt0 bus 0 scbus2 target 0 lun 0
da0: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device
da0: 320.000MB/s transfers (160.000MHz DT, offset 127, 16bit)
da0: Command Queueing enabled
da0: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C)
da0: quirks=0x40<RETRY_BUSY>
da1 at mps0 bus 0 scbus3 target 0 lun 0
da1: <ATA Hitachi HUA72302 A840> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number *            
da1: 600.000MB/s transfers
da1: Command Queueing enabled
da1: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C)
da2 at mps0 bus 0 scbus3 target 1 lun 0
da2: <ATA Hitachi HUA72302 A840> Fixed Direct Access SPC-4 SCSI device
da2: Serial Number *            
da2: 600.000MB/s transfers
da2: Command Queueing enabled
da2: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C)
da4 at mps0 bus 0 scbus3 target 3 lun 0
da4: <ATA Hitachi HUA72302 A840> Fixed Direct Access SPC-4 SCSI device
da4: Serial Number *            
da4: 600.000MB/s transfers
da4: Command Queueing enabled
da4: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C)
da3 at mps0 bus 0 scbus3 target 2 lun 0
da3: <ATA Hitachi HUA72302 A840> Fixed Direct Access SPC-4 SCSI device
da3: Serial Number *            
da3: 600.000MB/s transfers
da3: Command Queueing enabled
da3: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C)
da11 at mps1 bus 0 scbus4 target 2 lun 0
da11: <ATA WDC WD5003ABYX-0 1S02> Fixed Direct Access SPC-4 SCSI device
da11: Serial Number      WD-*
da11: 300.000MB/s transfers
da11: Command Queueing enabled
da11: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C)
da5 at mps0 bus 0 scbus3 target 4 lun 0
da5: <ATA Hitachi HUA72303 A6L0> Fixed Direct Access SPC-4 SCSI device
da5: Serial Number       *
da5: 600.000MB/s transfers
da5: Command Queueing enabled
da5: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C)
da12 at mps1 bus 0 scbus4 target 3 lun 0
da12: <ATA WDC WD5003ABYX-0 1S02> Fixed Direct Access SPC-4 SCSI device
da12: Serial Number      WD-*
da12: 300.000MB/s transfers
da12: Command Queueing enabled
da12: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C)
da6 at mps0 bus 0 scbus3 target 5 lun 0
da6: <ATA Hitachi HUA72303 A6L0> Fixed Direct Access SPC-4 SCSI device
da6: Serial Number       *
da6: 600.000MB/s transfers
da6: Command Queueing enabled
da6: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C)
da7 at mps0 bus 0 scbus3 target 6 lun 0
da7: <ATA Hitachi HUA72303 A6L0> Fixed Direct Access SPC-4 SCSI device
da7: Serial Number       *
da7: 600.000MB/s transfers
da7: Command Queueing enabled
da7: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C)
da8 at mps0 bus 0 scbus3 target 7 lun 0
da8: <ATA Hitachi HUA72303 A6L0> Fixed Direct Access SPC-4 SCSI device
da8: Serial Number       *
da8: 600.000MB/s transfers
da8: Command Queueing enabled
da8: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C)
da9 at mps1 bus 0 scbus4 target 0 lun 0
da9: <ATA Hitachi HUA72303 AA10> Fixed Direct Access SPC-4 SCSI device
da9: Serial Number       *
da9: 600.000MB/s transfers
da9: Command Queueing enabled
da9: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C)
da10 at mps1 bus 0 scbus4 target 1 lun 0
da10: <ATA Hitachi HUA72303 AA10> Fixed Direct Access SPC-4 SCSI device
da10: Serial Number       *
da10: 600.000MB/s transfers
da10: Command Queueing enabled
da10: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C)
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Trying to mount root from ufs:/dev/xmd0 []...
VMware memory control driver initialized
The system is a virtual machine on an ESXi host with two LSI SAS2008 HBAs using passthrough. I have read before that the import statements are normal, but I can't ignore it because the other two pools don't have it:

Code: Select all

History for 'tank1':
2015-01-25.22:32:28 zpool create -m /mnt/tank1 tank1 raidz1 /dev/da1 /dev/da2 /dev/da3 /dev/da4
2015-01-25.22:50:07 zfs receive tank1/z1

History for 'tank2':
2015-01-25.23:24:26 zpool create -m /mnt/tank2 tank2 raidz2 /dev/da5 /dev/da6 /dev/da7 /dev/da8 /dev/da9 /dev/da10
2015-01-25.23:42:28 zfs receive tank2/z2
2015-01-26.00:17:08 zpool import -d /dev -f -a
2015-08-14.17:32:58 zpool import -d /dev -f -a
2015-08-14.18:02:11 zpool import -d /dev -f -a
2015-08-14.20:57:10 zpool import -d /dev -f -a
2015-08-14.21:09:52 zpool import -d /dev -f -a
2015-08-14.22:19:39 zpool import -d /dev -f -a
2015-08-14.22:32:20 zpool import -d /dev -f -a
2015-08-14.22:43:00 zpool import -d /dev -f -a
2015-08-23.17:43:35 zpool import -d /dev -f -a
2015-08-23.17:49:47 zpool export tank2
2015-08-23.17:52:02 zpool import -d /dev -f -a
2015-08-23.17:55:43 zpool import -d /dev -f -a

History for 'tank3':
2015-01-26.00:02:45 zpool create -m /mnt/tank3 tank3 mirror /dev/da11 /dev/da12
2015-01-26.00:10:56 zfs receive tank3/vol2

Re: One of three zpools imported on every boot

Posted: 26 Aug 2015 18:07
by b0ssman
please read
https://forums.freenas.org/index.php?th ... ine.12484/

can you try it without virtualization?

Re: One of three zpools imported on every boot

Posted: 28 Aug 2015 22:26
by turdburglar
I understand the caution against using virtual disks and other aspects of virtualization; however, N4F/ZFS is directly in control of the HBAs in my use case (VT-d). It's server-grade hardware with ECC memory. This, of course, can't guarantee nothing will ever go wrong (but this same guarantee obviously can't be made for bare-metal installations either).

I should note that this wasn't happening while I was on 9.3.0.2.1310; it only started after upgrading to 10.2. Since I have other things happening on the server, it will probably be a while before I can test it without virtualization; however, I don't see how it being a VM would make any difference. Any other suggestions?

Re: One of three zpools imported on every boot

Posted: 29 Aug 2015 13:46
by daoyama
Do you use full installation?
early version use /boot/zfs/zpool.cache but later don't use it.
check /boot/zfs/zpool.cache or /cf/boot/zfs/zpool.cache on your system.

One of three zpools imported on every boot

Posted: 16 Sep 2015 11:15
by Parkcomm
In fact you may have both and if they are out of sync it might explain the import.

Code: Select all

zdb -C -U /cf/boot/zfs/zpool.cache
zdb -C -U /boot/zfs/zpool.cache
Sent from my foam - stupid auto correct.