Canceling BIOS Data Wipe Process

Hello!

So I am having an issue with my Dell G3 3590 native HDD. My laptop configuration has both m.2 SSD and  SATA 1000GB HDD (SSD used for Windows 10 OS and HDD for all the other stuff).

Lately I did a mistake hard shutting down my PC when it was in both processes of cancellation of deleting a program and preparing to restart Windows 10. The restart process was kind of stuck on a Windows 10 logo for an hour so I only had an option of hard reboot.

After that, there was nothing but a Dell logo and Windows reparation tool getting ready for another hour. I had to hard shut down it again.

After that, I checked BIOS if my hard drives were OK. Both SSD and HDD were identified in BIOS, but I eventually figured out that  Windows 10 would run ONLY if SATA 0 and SATA 1 controllers were disabled inside of BIOS settings. That's how I knew it was an HDD problem. I even tried to put up a fresh Windows 10 with USB boot, but even USB boot didn't load until I disable SATA controllers manually.

After that, I initiated BIOS Maintenance Data Wipe function since I didn't really care about the data and just wanted to set both disks to defaults (hoping it would fix the HDD). Now it has been running for at least 24 hours straight (looping at "Starting to erase internal SATA devices" moving bar), which is quite long even for the 1000GB HDD.

I also cannot hear HDD actually working, there's no needle scratching sound inside the laptop, which is familiar (at least at minimum level) even for a brand new laptop. It just goes silent.

My question is: is there a way to cancel looped Data Wipe process except a hard shutdown? I'm afraid to make another hard shutdown since I think it may damage the whole hardware system, not only the HDD, turning my whole PC into paperweight. I don't even care about HDD anymore, I'll just go buy another one. I only care if the system would be safe so I can put a fresh Windows 10 installation on SSD after all.

Once again, I'm pretty sure it's an HDD issue, not the SATA controllers because BIOS could've identify HDD perfectly.

Thank you so much for any help!