drive/partition totally missing after errant diskpart clean

I think like other folks who've come here, I have a relatively similar issue: I wanted to wipe a flash drive (in my case, because the 16GB drive had been formatted on mac os, so it didn't work w/ windows), went to diskpart, selected what appeared to be the small flash drive and did "clean." This for whatever reason instead made my 2TB "file install" drive disappear.

The reason I created a new thread is because I haven't seen my case elsewhere: I've actually lost the drive letter, the partition, and any sign that the drive exists. it no longer appears in device manager, in my bios boot menu, and so on. It DOES appear when I boot via the MiniTool Power Data Recovery Boot Loader (as in, when I boot that executable from a flash drive)--and not within that MiniTool's Windows version, nor within EaseUS Partition Master. Same goes for Testdisk; when I load that, it only shows my Windows system drive (along with any USB stick I have inserted), not the 2TB drive.

I thankfully had all important files on my 2TB drive backed up, so losing them wouldn't be the end of the world. But now I can't even use the drive! I would love some help figuring out what exactly I did and how to at least access the drive again, if not recover any/all of its 2TB of data. I only did "clean," not "clean full," so my hope is the drive's data (which is apparently not being touched by computer, since it doesn't exist) has been sitting unperturbed for the past few hours while I've been wondering what the heck is going on.

I'm happy to send screenshots or other info as needed/requested. I'm relatively knowledgable about computers, but clearly I'm not a genius, since I dabbled with diskpart :-0 and would probably benefit from some ELI5 (explain like I'm 5) help. I have Hiren's Boot CD ready to do tests/etc, but I don't wanna start messing w/ that when I'm unsure which of its apps, if any, would be of use.

THANK YOU IN ADVANCE!

UPDATE: After unplugging and replugging the drive with different cables, it was recognized by Windows again. I booted straight into testdisk, let it run a deep analysis, then simply booted back into Windows and had the drive back. Perhaps an electrical or connection issue happened when the "clean" command was issued. Unsure what happened. Will leave this up for anyone else who runs into my exact twist on the issue. Thanks, all.