You mean doing "ls -l" in a booted Linux?
Accessing the disk from within Linux is not the problem.
I installed Linux(Ubuntu/Manjaro/Arch) some times to this disk and all wents good. But at boot time grub2 is not be able to detect/connect to the installed system.
Grub2 itself does not provide "ls -l", right?
Your guess goes in the direction of a problem with 48Bit-LBA it seems, but this was included in the BIOSes around the year 2002, I think?
This AMI BIOS is from the year 2010(Build-date).
In case of (hd0,msdos1)(Ubuntu) it helped to install it in the first partition.
But the rest of the HDD should be adressable by the BIOS and Grub2, too, I expect.
Booting by SuperGrub2Disk 2.04rc1 even does not show (hd0,msdos5).
Only when I load the additional drivers(experimental) I can show (usb5a,msdos5) and list its contents.
But I can not boot it, but this may be a other problem cause at first it detects a device hd111 and then can not find it.
Gesendet: Donnerstag, 18. Juli 2019 um 14:42 Uhr
Von: "Vladimir 'phcoder' Serbinenko" <address@hidden>
An: "Peter Littmann" <address@hidden>
Betreff: Re: grub does not detect partition 4 and 5 on new USB-WD My Passport 1TB
try "ls -l" to see how much of disk BIOS sees. My guess is that it
cuts it at 128GiB. I'd recommend putting everything need for boot at
the beginning of the disk
On Mon, Jul 15, 2019 at 6:32 PM Peter Littmann <address@hidden> wrote:
> I have a old BIOS (build date 04/01/2010) and connected a new USB-WD Passport 1TB harddisk.
> Grub 2.02 does only detect: (hd0,msdos1), (hd0,msdos2) and (hd0,msdos3)
> But not (hd0,msdos4) (Extended) and (hd0,msdos5) (ext4 with Arch-Installation).
> The addressing should be handled by 48Bit-LBA.
> What can be the reason and how to solve this?