The failure presents as "SYSTEM STUCK" after choosing the UEFI booting usb drive, which means it's not showing either Unraid Booting Menu nor rows of logs in terminal. As what I have met when I updated from unraid 6 to unraid 7, consider it as a booting media failure.

I managed to shutdown the server and backuped the files from the usb drive, then tried methods in BOOTING FAILURE page from https://docs.unraid.net/unraid-os/troubleshooting/common-issues/boot-and-startup-failures/

1. Use a USB 2.0 port for the boot device if possible (when booting from USB). It's generally more reliable and less prone to issues than USB 3.0.

   [I used another usb3.0 drive with valid GUID]

2. Check your BIOS/UEFI settings to ensure that the Unraid boot device is set as the primary boot target.

   [UEFI checked]

3. Inspect the boot device for any physical or logical errors on a Windows or macOS computer.

   [Cleared]

4. Re-extract the Unraid release bz* files onto the boot volume to prevent any potential corruption.

   [Tried, not working]

5. Rebuild boot media by starting with a clean Unraid copy, then restore your config folder.

   [I backed up the files from the corrupted drive, and downloaded a new unraid 7.3.1 archive. After exracting the files to the new drive, I then REPLACED the /config folder with the BACKED-UP one.

   This time, it boots

   

   

   HOWEVER when it comes to the GUI, the firefox says it is unable to connect. I even tried "ip addr" and confirmed im using the right ip address.

   

   ]

6. Try booting in Safe Mode to check for any plugin-related problems.

7. Test with new boot media and perform a clean Unraid installation. This helps determine if there are issues with the server hardware.

8. If necessary, transfer your license to a new boot device.

At this stage, i don't know what to do. Should I create a new unraid 7.3.1 boot drive? or how should I solve this "Not Booting WebGUI"?

Boot is not finishing; does it work with a stock install? If yes, it would suggest a problem with the current config, if that is the case you can restore just the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

Update to 7.3.0 went ok, but update to 7.3.1 had issues. The system wouldn't reboot or shutdown from the web gui so I tried the restart button on the device, on boot there seemd to be nothing, pinging the ip address just got timeout. Followed with a hard shutdown and reboot, still seemed to be nothing, then the web gui came back to life after using the reset button on the case again. But now there are no containers in docker or config files for them in app data, but the frigate media files are still visible in shares. Now to reistall the containers and copy over the Frigate config file from note+.

Should I risk moving to internal boot?

I wouldn't move before figuring out what is causing the current issues.