Power outage wiped my node config, then more woes came

[Alexey]

@MarkFeuer

I didn’t receive a suspension email until 10 days later, today, but now I’ve gotten the email notice that I’ve been suspended on three different satellites.

Created an issue [storagenode] The email about suspension is coming only after check-in to satellite · Issue #4235 · storj/storj · GitHub

What's the point of sending the emails about node suspension?

The emailing system is not robust enough yet. We evaluating the other provider, it could be better than the current one.

@MarkFeuer

I’m trying to access my log file to see what went wrong so I can fix, but the text file is 7 gigabytes large and Notepad is saying it’s too big to open.

You can use PowerShell or cmd and CLI commands to search for needed strings.
For PowerShell:

sls "ERROR" "C:\Program Files\Storj\Storage Node\storagenode.log" | select -last 10

For cmd.exe (but there is no analogue of tail (bash) or select -last 10 (PowerShell))

findstr /c:"ERROR" "C:\Program Files\Storj\Storage Node\storagenode.log"

Or use WSL Ubuntu and use Linux commands from there. All disks will be automatically mounted under /mnt
Another way is to install msys2 or cygwin to use Linux commands too.

See also

Text editor to open big (giant, huge, large) text files

However, I would recommend to stop the service, archive the log and delete the source log, then start the service. This way you would not lost the previous logs and can keep it small.
You can also use a logrotate for Windows or some scripting like GitHub - AlexeyALeonov/storagenode_win_log_rotate: Windows GUI storagenode log rotation script (doesn't compatible with logrotate) (you need to modify the script for your case) and run it as an Administrator (requires rights to start/stop the service).