Seeing GPT error in startup log. Is this cause for concern?

Status
Not open for further replies.

oRAirwolf

Explorer
Joined
Dec 6, 2016
Messages
55
I am seeing the following in the startup logs when I first boot my FreeNAS server:

Code:
GEOM: da0: the secondary GPT header is not in the last LBA.
GEOM: da1: the secondary GPT header is not in the last LBA.


Here is dmesg.today:

Code:
Copyright (c) 1992-2017 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 11.0-STABLE #0 r321665+25fe8ba8d06(freenas/11.0-stable): Mon Sep 25 06:24:11 UTC 2017
	root@gauntlet:/freenas-11-releng/freenas/_BE/objs/freenas-11-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0)
CPU: Intel(R) Xeon(R) CPU E5-2407 0 @ 2.20GHz (2200.05-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206d7  Family=0x6  Model=0x2d  Stepping=7
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x1fbee3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  XSAVE Features=0x1<XSAVEOPT>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 35165044736 (33536 MB)
avail memory = 33259270144 (31718 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <DELL   PE_SC3  >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ioapic1: Changing APIC ID to 1
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 32-55 on motherboard
random: entropy device external interface
kbd1 at kbdmux0
nexus0
cryptosoft0: <software crypto> on motherboard
aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
padlock0: No ACE support.
acpi0: <DELL PE_SC3> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x7f irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x5f irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
Event timer "HPET4" frequency 14318180 Hz quality 440
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff numa-domain 0 on acpi0
pci0: <ACPI PCI bus> numa-domain 0 on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 53 at device 1.0 numa-domain 0 on pci0
pci1: <ACPI PCI bus> numa-domain 0 on pcib1
mps0: <Avago Technologies (LSI) SAS2008> port 0xfc00-0xfcff mem 0xdcff0000-0xdcffffff,0xdcf80000-0xdcfbffff irq 34 at device 0.0 numa-domain 0 on pci1
mps0: Firmware: 20.00.07.00, Driver: 21.01.00.00-fbsd
mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
pcib2: <ACPI PCI-PCI bridge> irq 53 at device 1.1 numa-domain 0 on pci0
pci2: <ACPI PCI bus> numa-domain 0 on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 53 at device 3.0 numa-domain 0 on pci0
pci3: <ACPI PCI bus> numa-domain 0 on pcib3
pcib4: <PCI-PCI bridge> irq 16 at device 17.0 numa-domain 0 on pci0
pci4: <PCI bus> numa-domain 0 on pcib4
pci0: <simple comms> at device 22.0 (no driver attached)
pci0: <simple comms> at device 22.1 (no driver attached)
ehci0: <Intel Patsburg USB 2.0 controller> mem 0xdf8fe000-0xdf8fe3ff irq 23 at device 26.0 numa-domain 0 on pci0
usbus0: EHCI version 1.0
usbus0 numa-domain 0 on ehci0
pcib5: <ACPI PCI-PCI bridge> at device 28.0 numa-domain 0 on pci0
pci5: <ACPI PCI bus> numa-domain 0 on pcib5
pcib6: <ACPI PCI-PCI bridge> irq 16 at device 28.4 numa-domain 0 on pci0
pci6: <ACPI PCI bus> numa-domain 0 on pcib6
bge0: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd94a0000-0xd94affff,0xd94b0000-0xd94bffff,0xd94c0000-0xd94cffff irq 16 at device 0.0 numa-domain 0 on pci6
bge0: APE FW version: NCSI v1.4.14.0
bge0: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus0: <MII bus> numa-domain 0 on bge0
brgphy0: <BCM5720C 1000BASE-T media interface> PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge0: Using defaults for TSO: 65518/35/2048
bge0: Ethernet address: f8:bc:12:44:47:c4
bge1: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd94d0000-0xd94dffff,0xd94e0000-0xd94effff,0xd94f0000-0xd94fffff irq 17 at device 0.1 numa-domain 0 on pci6
bge1: APE FW version: NCSI v1.4.14.0
bge1: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus1: <MII bus> numa-domain 0 on bge1
brgphy1: <BCM5720C 1000BASE-T media interface> PHY 2 on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge1: Using defaults for TSO: 65518/35/2048
bge1: Ethernet address: f8:bc:12:44:47:c6
pcib7: <ACPI PCI-PCI bridge> at device 28.6 numa-domain 0 on pci0
pci7: <ACPI PCI bus> numa-domain 0 on pcib7
ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.1.13-k> mem 0xd9000000-0xd91fffff,0xd93fc000-0xd93fffff irq 18 at device 0.0 numa-domain 0 on pci7
ix0: Using MSIX interrupts with 5 vectors
ix0: Ethernet address: a0:36:9f:1e:30:6a
ix0: PCI Express Bus: Speed 5.0GT/s Width x1
pcib8: <ACPI PCI-PCI bridge> irq 19 at device 28.7 numa-domain 0 on pci0
pci8: <ACPI PCI bus> numa-domain 0 on pcib8
pcib9: <PCI-PCI bridge> at device 0.0 numa-domain 0 on pci8
pci9: <PCI bus> numa-domain 0 on pcib9
pcib10: <PCI-PCI bridge> at device 0.0 numa-domain 0 on pci9
pci10: <PCI bus> numa-domain 0 on pcib10
pcib11: <PCI-PCI bridge> at device 0.0 numa-domain 0 on pci10
pci11: <PCI bus> numa-domain 0 on pcib11
vgapci0: <VGA-compatible display> mem 0xd8000000-0xd8ffffff,0xdeffc000-0xdeffffff,0xde000000-0xde7fffff irq 19 at device 0.0 numa-domain 0 on pci11
vgapci0: Boot video device
pcib12: <PCI-PCI bridge> at device 1.0 numa-domain 0 on pci9
pci12: <PCI bus> numa-domain 0 on pcib12
ehci1: <Intel Patsburg USB 2.0 controller> mem 0xdf8ff000-0xdf8ff3ff irq 22 at device 29.0 numa-domain 0 on pci0
usbus1: EHCI version 1.0
usbus1 numa-domain 0 on ehci1
pcib13: <PCI-PCI bridge> at device 30.0 numa-domain 0 on pci0
pci13: <PCI bus> numa-domain 0 on pcib13
isab0: <PCI-ISA bridge> at device 31.0 numa-domain 0 on pci0
isa0: <ISA bus> numa-domain 0 on isab0
atapci0: <Intel Patsburg SATA600 controller> port 0xecd0-0xecd7,0xecf0-0xecf3,0xecd8-0xecdf,0xecf4-0xecf7,0xec90-0xec9f,0xeca0-0xecaf irq 20 at device 31.2 numa-domain 0 on pci0
ata2: <ATA channel> at channel 0 on atapci0
ata3: <ATA channel> at channel 1 on atapci0
atapci1: <Intel Patsburg SATA300 controller> port 0xece0-0xece7,0xecf8-0xecfb,0xece8-0xecef,0xecfc-0xecff,0xecb0-0xecbf,0xecc0-0xeccf irq 21 at device 31.5 numa-domain 0 on pci0
ata4: <ATA channel> at channel 0 on atapci1
ata5: <ATA channel> at channel 1 on atapci1
pcib14: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
pci14: <ACPI PCI bus> numa-domain 0 on pcib14
pci14: <dasp, performance counters> at device 14.1 (no driver attached)
pci14: <dasp, performance counters> at device 19.1 (no driver attached)
pci14: <dasp, performance counters> at device 19.4 (no driver attached)
pci14: <dasp, performance counters> at device 19.5 (no driver attached)
pcib15: <ACPI Host-PCI bridge> on acpi0
pci15: <ACPI PCI bus> on pcib15
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
ichwd0: <Intel Patsburg watchdog timer> on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8800-0xc97ff,0xec000-0xeffff 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
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001600
device_attach: est0 attach returned 6
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001600
device_attach: est1 attach returned 6
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001600
device_attach: est2 attach returned 6
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1fdd00001600
device_attach: est3 attach returned 6
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
freenas_sysctl: adding account.
freenas_sysctl: adding directoryservice.
freenas_sysctl: adding middlewared.
freenas_sysctl: adding network.
freenas_sysctl: adding services.
ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
nvme cam probe device init
usbus0: 480Mbps High Speed USB v2.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: <Intel EHCI root HUB> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
ugen1.1: <Intel EHCI root HUB> at usbus1
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
_mapping_process_dpm_pg0: conflict in mapping table for device 4
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
ugen0.2: <vendor 0x8087 product 0x0024> at usbus0
uhub2 numa-domain 0 on uhub0
uhub2: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus0
ugen1.2: <vendor 0x8087 product 0x0024> at usbus1
uhub3 numa-domain 0 on uhub1
uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus1
mps0: SAS Address for SATA device = 4f313f5ec98db379
mps0: SAS Address from SATA device = 4f313f5ec98db379
mps0: SAS Address for SATA device = d14c2b4dc5b2a95c
mps0: SAS Address from SATA device = d14c2b4dc5b2a95c
mps0: SAS Address for SATA device = dc4b214b9db98d84
mps0: SAS Address from SATA device = dc4b214b9db98d84
mps0: SAS Address for SATA device = 3855355fc98e9c7f
mps0: SAS Address from SATA device = 3855355fc98e9c7f
mps0: SAS Address for SATA device = 3d552a5fc98e9c7f
mps0: SAS Address from SATA device = 3d552a5fc98e9c7f
mps0: SAS Address for SATA device = de363f4b9db08e75
mps0: SAS Address from SATA device = de363f4b9db08e75
mps0: SAS Address for SATA device = 35313f5ec98db37b
mps0: SAS Address from SATA device = 35313f5ec98db37b
mps0: SAS Address for SATA device = 4848415fc98e9c7f
mps0: SAS Address from SATA device = 4848415fc98e9c7f
uhub2: 6 ports with 6 removable, self powered
uhub3: 8 ports with 8 removable, self powered
ugen0.3: <no manufacturer Gadget USB HUB> at usbus0
uhub4 numa-domain 0 on uhub2
uhub4: <no manufacturer Gadget USB HUB, class 9/0, rev 2.00/0.00, addr 3> on usbus0
uhub4: 6 ports with 6 removable, self powered
ugen0.4: <Avocent KeyboardMouse Function> at usbus0
ukbd0 numa-domain 0 on uhub4
ukbd0: <Keyboard> on usbus0
kbd0 at ukbd0
ada0 at ata4 bus 0 scbus3 target 0 lun 0
ada0: <SPCC Solid State Disk S9FM02.8> ACS-3 ATA SATA 3.x device
ada0: Serial Number C44207660BEE03064355
ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada0: 57241MB (117231408 512 byte sectors)
ada1 at ata5 bus 0 scbus4 target 0 lun 0
ada1: <SPCC Solid State Disk S9FM02.8> ACS-3 ATA SATA 3.x device
ada1: Serial Number C44207660BEE03064288
ada1: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada1: 57241MB (117231408 512 byte sectors)
da0 at mps0 bus 0 scbus0 target 0 lun 0
da0: <ATA WDC WD80EFZX-68U 0A83> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number VJGPK6NX
da0: 600.000MB/s transfers
da0: Command Queueing enabled
da0: 7630885MB (15628053168 512 byte sectors)
da1 at mps0 bus 0 scbus0 target 5 lun 0
da1: <ATA WDC WD80EZZX-11C 0A03> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number VLJ3MVAY
da1: 600.000MB/s transfers
da1: Command Queueing enabled
da1: 7630885MB (15628053168 512 byte sectors)
da2 at mps0 bus 0 scbus0 target 6 lun 0
da2: <ATA WDC WD80EMAZ-00W 0A83> Fixed Direct Access SPC-4 SCSI device
da2: Serial Number 7SGYXV8C
da2: 600.000MB/s transfers
da2: Command Queueing enabled
da2: 7630885MB (15628053168 512 byte sectors)
da3 at mps0 bus 0 scbus0 target 7 lun 0
da3: <ATA WDC WD80EFZX-68U 0A83> Fixed Direct Access SPC-4 SCSI device
da3: Serial Number VK0V4ZDY
da3: 600.000MB/s transfers
da3: Command Queueing enabled
da3: 7630885MB (15628053168 512 byte sectors)
da4 at mps0 bus 0 scbus0 target 8 lun 0
da4: <ATA WDC WD80EFZX-68U 0A83> Fixed Direct Access SPC-4 SCSI device
da4: Serial Number VK0V9Z9Y
da4: 600.000MB/s transfers
da4: Command Queueing enabled
da4: 7630885MB (15628053168 512 byte sectors)
da5 at mps0 bus 0 scbus0 target 9 lun 0
da5: <ATA WDC WD80EMAZ-00W 0A83> Fixed Direct Access SPC-4 SCSI device
da5: Serial Number 7JHJZAVC
da5: 600.000MB/s transfers
da5: Command Queueing enabled
da5: 7630885MB (15628053168 512 byte sectors)
da6 at mps0 bus 0 scbus0 target 10 lun 0
da6: <ATA WDC WD80EFZX-68U 0A83> Fixed Direct Access SPC-4 SCSI device
da6: Serial Number VJGR16NX
da6: 600.000MB/s transfers
da6: Command Queueing enabled
da6: 7630885MB (15628053168 512 byte sectors)
da7 at mps0 bus 0 scbus0 target 11 lun 0
da7: <ATA WDC WD80EFZX-68U 0A83> Fixed Direct Access SPC-4 SCSI device
da7: Serial Number VK0VDMPY
da7: 600.000MB/s transfers
da7: Command Queueing enabled
da7: 7630885MB (15628053168 512 byte sectors)
random: unblocking device.
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1100025064 Hz quality 1000
Trying to mount root from zfs:freenas-boot/ROOT/11.0-U4 []...
GEOM: da2: the secondary GPT header is not in the last LBA.
GEOM: da5: the secondary GPT header is not in the last LBA.
GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
ipmi0: <IPMI System Interface> on isa0
ipmi0: KCS mode found at io 0xca8 alignment 0x4 on isa
ipmi0: IPMI device rev. 1, firmware rev. 2.50, version 2.0
ipmi0: Number of channels 6
ipmi0: Attached watchdog
hwpmc: SOFT/16/64/0x67<INT,USR,SYS,REA,WRI> TSC/1/64/0x20<REA> IAP/8/48/0x3ff<INT,USR,SYS,EDG,THR,REA,WRI,INV,QUA,PRC> IAF/3/48/0x67<INT,USR,SYS,REA,WRI>
bge0: link state changed to DOWN
bge0: link state changed to UP
ums0 numa-domain 0 on uhub4
ums0: <Mouse> on usbus0
ums0: 3 buttons and [Z] coordinates ID=0
ums1 numa-domain 0 on uhub4
ums1: <Mouse REL> on usbus0
ums1: 3 buttons and [XYZ] coordinates ID=0
ix0: link state changed to UP
GEOM_ELI: Device da0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:	 Crypto: hardware
GEOM_ELI: Device da3p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:	 Crypto: hardware
GEOM_ELI: Device da4p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:	 Crypto: hardware
GEOM_ELI: Device da6p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:	 Crypto: hardware
GEOM_ELI: Device da7p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:	 Crypto: hardware
GEOM_ELI: Device da1p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:	 Crypto: hardware
nfsd: can't register svc name
ix0: link state changed to DOWN
ix0: link state changed to UP
ix0: link state changed to DOWN
ix0: link state changed to UP
ix0: link state changed to DOWN
ix0: link state changed to UP
ix0: link state changed to DOWN
ix0: link state changed to UP
ix0: link state changed to DOWN
ix0: link state changed to UP
ix0: link state changed to DOWN
ix0: link state changed to UP
ix0: link state changed to DOWN
ix0: link state changed to UP


Screenshot: https://i.imgur.com/oVTUUeO.png

I believe this is for the boot drives that are in a ZFS mirror that was created by the guided installer, but I am not 100% sure on this. Is this something I should be concerned about? I am happy to provide any additional information.
 
Last edited:

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
I believe this is for the boot drives that are in a ZFS mirror that was created by the guided installer, but I am not 100% sure on this. Is this something I should be concerned about? I am happy to provide any additional information.
No, these are your boot devices:
Code:
ada0 at ata4 bus 0 scbus3 target 0 lun 0
ada0: <SPCC Solid State Disk S9FM02.8> ACS-3 ATA SATA 3.x device
ada0: Serial Number C44207660BEE03064355
ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada0: 57241MB (117231408 512 byte sectors)
ada1 at ata5 bus 0 scbus4 target 0 lun 0
ada1: <SPCC Solid State Disk S9FM02.8> ACS-3 ATA SATA 3.x device
ada1: Serial Number C44207660BEE03064288
ada1: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada1: 57241MB (117231408 512 byte sectors)

You have another error on these two disks
Code:
GEOM: da2: the secondary GPT header is not in the last LBA.
GEOM: da5: the secondary GPT header is not in the last LBA.

In your particular system, the data disks are numbered da0 to da7 and I can't say why these disks are giving you a problem.
Have you replaced or added disks recently?
 

oRAirwolf

Explorer
Joined
Dec 6, 2016
Messages
55
No, these are your boot devices:
Code:
ada0 at ata4 bus 0 scbus3 target 0 lun 0
ada0: <SPCC Solid State Disk S9FM02.8> ACS-3 ATA SATA 3.x device
ada0: Serial Number C44207660BEE03064355
ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada0: 57241MB (117231408 512 byte sectors)
ada1 at ata5 bus 0 scbus4 target 0 lun 0
ada1: <SPCC Solid State Disk S9FM02.8> ACS-3 ATA SATA 3.x device
ada1: Serial Number C44207660BEE03064288
ada1: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada1: 57241MB (117231408 512 byte sectors)

You have another error on these two disks
Code:
GEOM: da2: the secondary GPT header is not in the last LBA.
GEOM: da5: the secondary GPT header is not in the last LBA.

In your particular system, the data disks are numbered da0 to da7 and I can't say why these disks are giving you a problem.
Have you replaced or added disks recently?

Now that you mention it, I did just add 2 new drives that were shucked from WD Easystore 8TB enclosures. I haven't done anything with them yet because I was waiting on that zpool expansion feature to be added and just expand my current pool by 2 drives. I am a fool for not realizing this, but I assume this is from those drives being formatted in NTFS/exFAT.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
Now that you mention it, I did just add 2 new drives that were shucked from WD Easystore 8TB enclosures. I haven't done anything with them yet because I was waiting on that zpool expansion feature to be added and just expand my current pool by 2 drives. I am a fool for not realizing this, but I assume this is from those drives being formatted in NTFS/exFAT.
I did a second look through the code listing you gave and I bet that the drive numbers were changed after a reboot. What was listed as da2 and da5 were probably the same drives that were listed as da0 and da1.
if you run the disk burn-in on those two drives, it will remove all the factory data and you shouldn't get this error any more.
Do you have the link to that script?
 

oRAirwolf

Explorer
Joined
Dec 6, 2016
Messages
55
I did a second look through the code listing you gave and I bet that the drive numbers were changed after a reboot. What was listed as da2 and da5 were probably the same drives that were listed as da0 and da1.
if you run the disk burn-in on those two drives, it will remove all the factory data and you shouldn't get this error any more.
Do you have the link to that script?

I created a new zpool with the 2 drives and the error is not showing up when I boot up anymore. I really appreciate your help with that.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
I created a new zpool with the 2 drives and the error is not showing up when I boot up anymore. I really appreciate your help with that.
Sure. I am happy I could help.
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Sometimes enclosures, like RAID systems, put metadata at the end of a disk and then pretend that metadata space is not available. The secondary GPT is then written to what it thinks is the end of the disk. Move the drive to something that isn't pretending, and it looks wrong. The other thing that can do this is binary copying disks. Don't do that with GPT disks.
 
Status
Not open for further replies.
Top