Can't read GPT disk in old notebook
I decided to bring my desktop hard disk with me on a trip. It is a 3TB disk on a USB enclosure. The notebook sees the hard disk but only sees one big partition but there are several partitions in that disk.
The notebook is old, but it does give me these options for BIOS setup: - Legacy - Native EFI (without CMS) - Hybrid EFI (with CMS) Neither of these fixes my problem. |
You don't say what tools you are using - or distro version.
Try parted from the CLI. |
My guess is that you have a 512/4096 translation problem either caused by the on board or USB controller. This was a recent thread but since you are going to reinstall the drive back into the desktop I would be reluctant to change anything.
https://www.linuxquestions.org/quest...on-4175618642/ |
Hmmm - that was a strange issue, but it was a filesystem resolution; the partitions could still be seen. This looks to be different.
|
Quote:
You need to give much more detail on your hardware and on your linux version used. |
Quote:
Code:
insmod part_gpt |
What file system is on your desktop drive, if it isn't a 'standard' Linux or DOS filesystem, you may need extra software to 'see' it. (raid - lvm - etc.)
|
Hi, original poster here. I am running Debian 9, aka Stretch. That disk is running as external via USB. No LVM. Here is some output:
Code:
# fdisk -l |
You should be using gdisk and cgdisk with a GPT disk as fdisk and cfdisk just show the single partition in the protective MBR. Older versions can't read GPT partition tables.
Code:
Device Boot Start End Sectors Size Id Type This partition just marks the disk as used for older partition tools such as older versions of fdisk and cfdisk. If you want to see the GPT partitions on this disk you need to use gdisk and cgdisk. |
Quote:
Code:
#> gdisk /dev/sdb Code:
cgdisk 1.0.1 |
uh oh.
"Creating new GPT entries." fdisk from Debian 9 should have been OK. Did this usb enclosure ever work as expected on any system? Pretty sure you will have to boot to uefi. The disk will have to be seen correctly in bios entry. uefi presents hardware to the system kind of unlike bios forces hardware on system. |
Quote:
Quote:
|
I too think it should but seems an odd output statement.
Then I get the feeling there may be some limit to the box?? (enclosure I meant edited) |
Quote:
I have found a couple of links that explain the problem with enclosures that only support 32-bit LBA which has a 2.2TB limit. Since GPT uses 64-bit LBA any such enclosures can't understand GPT. https://drbobtechblog.com/not-all-us...-need-to-know/ https://superuser.com/questions/3084...sb-hard-drives Quote:
|
So I got a new case, rated to be 8TB compatible, and now it works.
FYI, fdisk and cfdisk work just fine. Solved. |
All times are GMT -5. The time now is 04:40 PM. |