Re: [bug-fdisk] terrible problem with fdisk on on GPT partition. help needed!!!

[Leslie P. Polzer]

Dear Xingtao Zhang,

thanks for writing. Unfortunatley your mail is not clear
on whether you have access to the data still or not.

If you still have access to the data then I suggest
backing it up to another device and then doing a fresh
partitioning of the current hard disk(s).

HTH,

  Leslie


> hi, all
>
> I have got a terrible problem now, I had used fdisk created 2 new
> partition on an GPT format partition of a sever,
>
> and that patition is an LVM partition. After fdisk finished, I realized
> things goes wrong.
>
> But the partition table had changed already.
>
> Could I get them back without data loss, the data is very important for
> me.
>
> The thing is the disk on my server is 7T, but just  1T is used(3 lvm
> partition ), So I use fdisk create another 2 partition.
>
>       1. b4 fdisk:
>       2. Â 
>       3. 255 heads, 63 sectors/track, 963658 cylinders, total 15481176192
> sectors
>       4. Units = sectors of 1 * 512 = 512 bytes
>       5. Sector size (logical/physical): 512 bytes / 512 bytes
>       6. I/O size (minimum/optimal): 512 bytes / 512 bytes
>       7. Disk identifier: 0x00000000
>       8. Â 
>       9.    Device Boot      Start         End      Blocks   Id
> Â System
>       10. /dev/sdb1 Â  Â  Â  Â  Â  Â 2048 Â  Â  Â 321535 Â  Â  Â 159744 Â  83
> Â Linux
>       11. /dev/sdb4 Â  Â  Â  Â  Â  Â  Â  1 Â  Â  Â  Â  Â  1 Â  Â  Â  Â  Â  0+
>  ee  GPT
>       12. Â 
>       13. Partition table entries are not in disk order
>       14. Â 
>       15. after fdisk:
>       16. Â 
>       17. Command (m for help): p
>       18. Â 
>       19. Disk /dev/sdb: 7926.4 GB, 7926362210304 bytes
>       20. 255 heads, 63 sectors/track, 963658 cylinders, total 15481176192
> sectors
>       21. Units = sectors of 1 * 512 = 512 bytes
>       22. Sector size (logical/physical): 512 bytes / 512 bytes
>       23. I/O size (minimum/optimal): 512 bytes / 512 bytes
>       24. Disk identifier: 0x00000000
>       25. Â 
>       26.    Device Boot      Start         End      Blocks   Id
> Â System
>       27. /dev/sdb1 Â  Â  Â  Â  Â  Â 2048 Â  Â  Â 321535 Â  Â  Â 159744 Â  83
> Â Linux
>       28. /dev/sdb2 Â  Â  Â  Â  Â 321536 Â 1996810239 Â  998244352 Â  83
> Â Linux
>       29. /dev/sdb3 Â  Â  Â 1996810240 Â 4294967294 Â 1149078527+ Â 83 Â Linux
>       30. /dev/sdb4 Â  Â  Â  Â  Â  Â  Â  1 Â  Â  Â  Â  Â  1 Â  Â  Â  Â  Â  0+
>  ee  GPT
>       31. Â 
>       32. Partition table entries are not in disk order
>
> before and after fdisk, the output of lsblk is the same.
>
>       1. # partprobe
>       2. # lsblk
>       3. NAME Â  Â  Â  Â  Â  Â  Â  Â  Â  MAJ:MIN RM Â  SIZE RO TYPE MOUNTPOINT
>       4. sda                      8:0    0  1000G  0 disk
>       5. sdb                      8:16   0   7.2T  0 disk
>       6. ├─sdb1                   8:17   0   156M  0 part 
> /boot
>       7. └─sdb2                   8:18   0   7.2T  0 part
>       8.   ├─system-home (dm-0) 253:0    0   600G  0 lvm  /home
>       9.   ├─system-root (dm-1) 253:1    0   400G  0 lvm  /
>       10.   └─system-swap (dm-2) 253:2    0     2G  0 lvm  [SWAP]
>       11. sr0                     11:0    1  1024M  0 rom  
>       12. wnobshost:/home/cmos # ls /dev/sdb*
>       13. /dev/sdb  /dev/sdb1  /dev/sdb2
> sdb3 and sdb4 does not  shown,  now all data can accessed. but I'm
> afraid of  it can not be booted .
>
> Is it possible to recover the GPT partition table back?
> What should I do now?
>
>
> Many many thanks!
>
> Br,
> Xingtao Zhang_______________________________________________
> Bug-fdisk mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-fdisk
>