Running `brew cleanup testdisk`…
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`

I installed it on MacBook Apple Silicone.

I intended to work exclusively with /dev/sdb (the second drive attached to my MSI PC which has a complicated layout with GRUB2 installed) and I was using “fdisk“. I think it might be a great idea to have a lock option on “fdisk” to restrict the write/save things to a specific drive unless you know for sure where you are writing the new partition layout.

I had been working on a recovery operation for several hours – when I made my mistake. So I removed the USB disk drive and plugged in a spare device – 256 GB SAMSUNG.

I was able to install the PenDrive software on it. The PenDrive installation software only runs under Windows but the resulting PenDrive is then bootable and supports whatever you have installed (by a selection tree).

There is a wide selection of things you can install from the internet. So I installed “Hirens” and “LXLE” and I am now writing this using the LINUX LXLE installed on my PenDrive

I did the install using the “apt” admin toolset as LXLE supports the “apt” command set. The system was able to download the “universe” if it was not installed earlier.
It needed to run ‘apt update‘ before you could run ‘apt install testdisk‘.

Right now I’m using SeaMonkey to browse the internet. The terminal service is called “Sakura“. Testdisk is running Analysis and is up to about 20% in its search. If I lose the whole drive due to this big MISTAKE I will learn from it, and backup ALL the drives partition layouts before I start FIXING things.

In SUMMARY – it was my mistake on my machine while working on producing a PenDrive on that USB3.1 SAMSUNG 256GB.

The USB backup solution would have been “so easy” to recover – I lost time and I lost my pride, but I keep learning.

@Bob,

Thanks, corrected the command in the article..

To verify that Testdisk is installed and display more information by running the following dpkg command.

$ sudo dpkg-l testdisk

You need a space between dpkg and -l.