Solved GEOM: ada6: the secondary GPT header is not in the last LBA.

V

Vossy

Hi All,

I've received this message in my 'daily security run output' email.

The drives have just been installed and have no data on them as of yet. So I can do what ever to fix them.

kernel log messages
Code: 
+GEOM: ada6: the secondary GPT header is not in the last LBA.
+GEOM: ada7: the secondary GPT header is not in the last LBA.
+GEOM: ada8: the secondary GPT header is not in the last LBA.[/I]

Code: 
root@Bob:/ # dmesg | grep -i geom
GEOM: ada6: the secondary GPT header is not in the last LBA.
GEOM: ada7: the secondary GPT header is not in the last LBA.
GEOM: ada8: the secondary GPT header is not in the last LBA.
GEOM: ada9: the secondary GPT header is not in the last LBA.
GEOM: ada6: the secondary GPT header is not in the last LBA.
GEOM: ada7: the secondary GPT header is not in the last LBA.
GEOM: ada9: the secondary GPT header is not in the last LBA.
GEOM: ada8: the secondary GPT header is not in the last LBA.
GEOM: ada6: the secondary GPT header is not in the last LBA.
GEOM: ada7: the secondary GPT header is not in the last LBA.
GEOM: ada8: the secondary GPT header is not in the last LBA.

Code: 
root@Bob:/ # diskinfo -v ada6
ada6
        512             # sectorsize
        1000204886016   # mediasize in bytes (932G)
        1953525168      # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        1938021         # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        WD-WCASJ0305505 # Disk ident.
        Not_Zoned       # Zone Mode
Can any one help?
 
See if gpart recover ada6 fixes things.

Code: 
     recover       Recover a corrupt partition's scheme metadata on the geom
                   geom.  See the section entitled RECOVERING below for the
                   additional information.

                   Additional options include:

                   -f flags    Additional operational flags.  See the section
                               entitled OPERATIONAL FLAGS below for a
                               discussion about its use.
See gpart(8) for more info.

On what controller are these drives connected? I know some RAID controllers tend to write their metadata to the end of the disk and could potentially overwrite the GPT info.
 
Thanks for the info, however

Code: 
root@Bob:/ # gpart recover ada6
gpart: arg0 'ada6': Invalid argument

How is best to find out the controller information? Can i find it in dmesg
 
Does gpart show ada6 work? Are these disks really unused? Unused, as in, no partition tables. In that case it may just be some left-over data lingering about that causes the error message.
 
Code: 
root@Bob:/ # gpart show ada6
gpart: No such geom: ada6.

I guessing they are unused based on the above...

Should i create a pool with them and just add a few things? Would this remove / fix the problem?

or do they require a format or something along those lines?
 
If you're going to use ZFS you won't need partition tables. But it's probably best to clear the first and last couple of sectors of the disks, just to silence the messages. This will probably also do the trick:
Code: 
gpart create -s gpt ada6
gpart destroy ada6
It creates a proper partition table, then destroys it. Afterwards there shouldn't be an error anymore. If that doesn't work you can always use dd(1) to zero out the first and last couple of sectors.
 
Looks like all is fixed now SirDice

After a reboot my
Dmesg has cleared up. So i would assume all is well. I shall see what happens when i get my email tonight.

You are the master!

Thank you for your time and effort.
 
You must log in or register to reply here.
Back
Top