LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Can't read GPT disk in old notebook (https://www.linuxquestions.org/questions/linux-hardware-18/cant-read-gpt-disk-in-old-notebook-4175618886/)

lucmove 12-03-2017 05:31 PM

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.

syg00 12-03-2017 06:00 PM

You don't say what tools you are using - or distro version.
Try parted from the CLI.

michaelk 12-03-2017 06:53 PM

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/

syg00 12-03-2017 07:31 PM

Hmmm - that was a strange issue, but it was a filesystem resolution; the partitions could still be seen. This looks to be different.

tofino_surfer 12-03-2017 07:53 PM

Quote:

The notebook is old, but it does give me these options for BIOS setup:
- Legacy
- Native EFI (without CMS)
- Hybrid EFI (with CMS)
If the notebook supports Native EFI then it can't be that old.

You need to give much more detail on your hardware and on your linux version used.

colorpurple21859 12-03-2017 07:56 PM

Quote:

The notebook sees the hard disk but only sees one big partition but there are several partitions in that disk.
If this at a grub prompt then
Code:

insmod part_gpt

fatmac 12-04-2017 06:17 AM

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.)

lucmove 12-04-2017 07:02 AM

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
(internal disk omitted)
Device    Boot Start        End    Sectors Size Id Type
/dev/sdb1          1 4294967295 4294967295  16T ee GPT

# cfdisk /dev/sdb
                                        Disk: /dev/sdb
                        Size: 2.7 TiB, 3000592977920 bytes, 732566645 sectors
                                Label: dos, identifier: 0x0255a6c8

    Device            Boot              Start              End          Sectors        Size        Id Type
>>  /dev/sdb1                                1        4294967295        4294967295        16T        ee GPT


tofino_surfer 12-04-2017 03:01 PM

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
/dev/sdb1          1 4294967295 4294967295  16T ee GPT

4294967295 X 512 = 2.199023255×10¹² = 2.2TB = 2TiB = 32 bit maximum size for MBR formatted disks
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.

lucmove 12-04-2017 03:39 PM

Quote:

Originally Posted by tofino_surfer (Post 5788790)
If you want to see the GPT partitions on this disk you need to use gdisk and cgdisk.

None of them is helping:

Code:

#> gdisk /dev/sdb
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: not present

Creating new GPT entries.

Command (? for help): q

Code:

cgdisk 1.0.1

                Disk Drive: /dev/sdb
              Size: 732566645, 2.7 TiB

Part. #    Size        Partition Type            Partition Name
----------------------------------------------------------------
            2.7 TiB    free space


jefro 12-05-2017 02:53 PM

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.

lucmove 12-05-2017 03:08 PM

Quote:

Originally Posted by jefro (Post 5789341)
uh oh.
"Creating new GPT entries."

I don't believe gdisk would make any changes to the disk without an express command and a confirmation.

Quote:

Originally Posted by jefro (Post 5789341)
Did this usb enclosure ever work as expected on any system?

Yes, but with a 1TB disk formatted with MBR.

jefro 12-05-2017 07:22 PM

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)

tofino_surfer 12-05-2017 08:27 PM

Quote:

Originally Posted by jefro View Post
Did this usb enclosure ever work as expected on any system?

Yes, but with a 1TB disk formatted with MBR.
It could be that it is the USB enclosure that is old and doesn't support GPT. In the original post the OP was claiming that the notebook was old but as it has native EFI it definitely supports GPT. The OP may need to get a newer USB enclosure.

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:

Some enclosures have a 2TiB limit, irrespective of the partition type. This is because the USB-SATA bridge IC's firmware can only address 32-bit LBAs. The firmware in newer enclosures can address the full 48 bits.

lucmove 12-08-2017 01:51 PM

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.