0

I extracted two disks from a laptop after it went kaput:

  • a 2.5 SATA hdd (NTFS + ext4 data partitions),
  • a SATA M.2 (mostly ext4 partitions, this had the boot and root partitions).

Then I purchased two USB bays and installed the disks in them, but when connecting them via USB, I see no partitions (I'm running Linux). They were formatted and used in the laptop (still Linux), so I'm surprised no partition is visible. It's also suspicious that both disks are unreadable.

I think GPT was being used, and I'm no expert on GPT, but I wonder if this behavior is expected or not. My plan is to try and recover the partition table on both disks, but given they both contain some important data, I'm reluctant to perform any destructive action on them.

Is this expected behavior? If yes, what's the best way to proceed? If no, what could be the likely causes?

EDIT #1

Here some info after the very insightful comments:

  • /dev/sda is the 2.5" SATA hdd
  • /dev/sdb is the SATA M.2 sdd

ran fdisk -l on both devices:

# fdisk -l /dev/sda
fdisk: cannot open /dev/sda: Input/output error

# fdisk -l /dev/sdb
Disk /dev/sdb: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: FE202x Series
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes

Indeed, dmesg spits out a few errors related to sda:

[ 2248.918967] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 2248.937039] scsi host3: uas_eh_device_reset_handler success
[ 2249.401881] sd 3:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=92s
[ 2249.401914] sd 3:0:0:0: [sda] tag#27 Sense Key : Aborted Command [current]
[ 2249.401920] sd 3:0:0:0: [sda] tag#27 Add. Sense: No additional sense information
[ 2249.401928] sd 3:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 2249.401936] blk_update_request: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2249.401950] Buffer I/O error on dev sda, logical block 0, async page read
ARDVL
  • 101

0 Answers0