VessRaid 1840i w/ Fedora 24 fdisk shows The backup GPT table is corrupt, but the primary appears OK,

  • 361 Views
  • Last Post 24 November 2016
Rob Kudyba posted this 22 November 2016

We are running Fedora 24 w/ a VessRAID 1840i and we are seeing these errors from the file system:

 fdisk -l

The backup GPT table is corrupt, but the primary appears OK, so that will be used.

Disk /dev/sdc: 10.9 TiB, 11999999164416 bytes, 23437498368 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disklabel type: gpt

Disk identifier: 50A8A779-6283-407D-9381-DF6F9872CC33

 

 gdisk /dev/sdc1

GPT fdisk (gdisk) version 1.0.1

 

Warning! Read error 22; strange behavior now likely!

Partition table scan:

  MBR: not present

  BSD: not present

  APM: not present

  GPT: not present

 

Creating new GPT entries.

 

Command (? for help): >

b back up GPT data to a file

c change a partition's name

d delete a partition

i show detailed information on a partition

l list known partition types

n add a new partition

o create a new empty GUID partition table (GPT)

p print the partition table

q quit without saving changes

r recovery and transformation options (experts only)

s sort partitions

t change a partition's type code

v verify disk

w write table to disk and exit

x extra functionality (experts only)

? print this menu

 

Command (? for help): v

 

No problems found. 23437496220 free sectors (10.9 TiB) available in 1

segments, the largest of which is 23437496220 (10.9 TiB) in size.

 

Running fsck I get this:

fsck  /dev/sdc1

fsck from util-linux 2.28.2

e2fsck 1.42.13 (17-May-2015)

/dev/sdc1: clean, 4555342/366211072 files, 634306700/2929687035 blocks

Is there any other utility that I can run to fix this error?

Thanks so much.

Raghuraman Kannan posted this 24 November 2016

Hi Rob,

You can use any 3rd party softwares to repair the File System .  Please be aware that you have to purchase it before you can repair the Volume and also check if it is compatible with your Operating System.

If you have the back up of the data, then formatting the volume and restoring it would be the easiest way to fix these issues.

Let us know if you have any questions.

Regards,

Raghu

 

 

Close