On 29/12/2021 23.11, Marc Chamberlin wrote:
On 12/29/21 11:17, Carlos E. R. wrote:
Post the partition table, done with "fdisk -l"
It smells of encryption, but I want to confirm.
Thanks again Carlos for your response, here you go... (I have troubles trying to figure out how to send a file with the fdisk info from a partially installed system! Gave up and used a Live OpenSuSE 15.2 USB stick and then had to figure out how to set up a Bluetooth connection (Bluetooth user interfaces/model is something I have never been able to grok, so it is a bumbling trial and error process for me!) /dev/sda is the USB stick with Live OpenSuSE. This doesn't show anything about the nearly 900 GiB unallocated partition on the SSD drive.
:-o :-?
I thought, while I had the live version of OpenSuSE up and running, I would try to use the YaST partitioner to set up the partitions for the new 15.3 system. No joy! Got slapped aside and told that the SSD device was busy and could not be altered. Anywise here you go -
Marc...
localhost:/home/linux # fdisk -l Disk /dev/loop0: 821.1 MiB, 860946432 bytes, 1681536 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
Disk /dev/loop1: 4.5 GiB, 4818206720 bytes, 9410560 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
Ok, that must be a thing from the live, ignore it.
The backup GPT table is not on the end of the device. This problem will be corrected by write. Disk /dev/nvme0n1: 953.9 GiB, 1024209543168 bytes, 2000409264 sectors Disk model: INTEL HBRPEKNX0203AH 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: B32172FB-2CEE-4E2C-B94B-46DAABE35591
Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 360937471 360370176 171.9G Microsoft basic data /dev/nvme0n1p4 1999337472 2000392191 1054720 515M Windows recovery environment
This an nvme "disk" of about 1TB. If I read it correctly, there is a large hole in it. There doesn't seem to be an bitlocker encrypted partition there, which is good. It should allow you to create partitions in that empty space.
Disk /dev/nvme1n1: 27.3 GiB, 29260513280 bytes, 57149440 sectors Disk model: INTEL HBRPEKNX0203AHO Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes
I have no idea what this is. Another SSD?
Disk /dev/sda: 57.8 GiB, 62026416128 bytes, 121145344 sectors Disk model: USB 3.1 FD 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: dos Disk identifier: 0xf727289d
Device Boot Start End Sectors Size Id Type /dev/sda1 * 64 1886035 1885972 920.9M cd unknown /dev/sda2 1886036 1916755 30720 15M ef EFI (FAT-12/16/32) /dev/sda3 1916928 121145343 119228416 56.9G 83 Linux
And the live. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)