On Sun 03 Dec 2017 at 21:27:20 (-0800), David Christensen wrote: > On 12/03/17 21:17, David Christensen wrote: > >But, it was not a total loss -- I can now dissect the SSD. > > More info: > > # lsblk /dev/sda > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 0 14.9G 0 disk > |-sda1 8:1 0 953M 0 part > `-sda2 8:2 0 4.7G 0 part > > # parted /dev/sda u s p free > Model: ATA SAMSUNG SSD UM41 (scsi) > Disk /dev/sda: 31277232s > Sector size (logical/physical): 512B/512B > Partition Table: gpt > Disk Flags: > > Number Start End Size File system Name Flags > 34s 2047s 2014s Free Space > 1 2048s 1953791s 1951744s fat32 ESP boot, esp > 2 1953792s 11718655s 9764864s stretch lvm > 11718656s 31277198s 19558543s Free Space > > > Are there any other commands that readers might find interesting > (before I wipe the SSD)?
I recently reformatted a disk thus: puck: GPT-style, master Part # filesys size code rôle puck - 1007KiB partition tables and alignment space puck01 - 3MiB EF02 bios-boot for Grub (bios_grub flag) puck02 FAT32 496MiB EF00 EFI (boot flag) puck03 ext2 500MiB 8300 /boot (unencrypted) … which gdisk shows as Number Start (sector) End (sector) Size Code Name 1 2048 8191 3.0 MiB EF02 BIOS boot partition 2 8192 1023999 496.0 MiB EF00 EFI System 3 1024000 2047999 500.0 MiB 8300 Linux filesystem … Is the absence of a partition like puck01 on your disk a significant factor in your failure to install grub? ie where's grub going to place itself? Cheers, David.
