#Cgsecurity.org testdisk Pc#

Vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0ĭevice-2: AMD Turks HDMI Audio V: 3.3 Mesa 21.2.6 compat-v: 3.1 direct render: Yesĭevice-1: Intel 7 Series/C216 Family High Definition Audio Unloaded: fbdev,modesetting,vesa compositor: marco v: 1.26.0 Topology: Quad Core model: Intel Core i5-3570 bits: 64 type: MCPĪrch: Ivy Bridge rev: 9 L2 cache: 6144 KiBįlags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27138 Mobo: Hewlett-Packard model: 3399 serial: UEFI: Hewlett-Packard

#Cgsecurity.org testdisk Pc#

Product: HP Compaq Elite 8300 Touch All-in-One PC v: N/A serial: If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:' I have also received 'Found a gpt partition table in /dev/sdb'Īnd 'The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. I have tried a few different things and found different errorsįrom fdisk I got 'Partition 1 does not start on physical sector boundary.'

I'm not sure what to do next to fix the issue, I've done some reading but I can't find the exact solution. I downloaded the Hirens Boot CD and used it to run a scan and it has about 5% damaged sectors. I rebooted the computer to try something else and on reboot the drive was no longer mountable. The scan got stuck at around 67% and I closed the terminal window to restart it. I'm not that tech savvy so I'm not entirely sure exactly what that process is, and I think it may be the cause of what's happening now. As of yesterday, I ran a bad sectors scan with -wsv command.

The drive had been working well until just a few months ago after updating to Mate 20.3, it started running a little bit slower and over the past 2-3 months got progressively worse.