SystemRescueCD Download Bug

I was going to post an issue on Github but saw it was required to post here first:

In OMV-Extras, kernel tab, the "Install SystemRescue" functionality does not download a valid ISO due to redirects (I believe it's actually downloading a 60K HTML page of the page it ends up on) which led to hours of wasted time trying to figure out why GRUB wouldn't launch into it with an "invalid file system" error. The file ends up getting saved with the correct filename and the GRUB entry is created as well, perhaps some better error checking or MD5 comparison should occur as a final step here to ensure a valid ISO is downloaded?

Here's the output of the "Install SystemRescue" popup which should be pretty self-explanatory to the redirects that are being followed:

https://osdn.net/projects/systemrescuecd/storage/releases/7.01/systemrescue-7.01-amd64.iso
Resolving osdn.net (osdn.net)... 52.89.195.186, 34.208.152.22
Connecting to osdn.net (osdn.net)|52.89.195.186|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://osdn.net/projects/systemrescuecd/ [following]
--2021-03-10 11:17:25--  https://osdn.net/projects/systemrescuecd/
Reusing existing connection to osdn.net:443.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/boot/systemrescue-7.01-amd64.iso’

     0K .......... .......... .......... .......... .......... 1.52M
    50K ......                                                 45.6M=0.03s

2021-03-10 11:17:25 (1.72 MB/s) - ‘/boot/systemrescue-7.01-amd64.iso’ saved [58182]

Zitat

Hours? Why not just post on the forum after the first five mins?

Well it wasn't at all evident that this was an issue with the SystemRescue process/ISO as GRUB was telling me that I had an "unknown filesystem" and to "load the kernel first" so I went down that rabbit hole of figuring out what else was wrong with my system (as there were other issues I was trying to fix which neccessitated the use of SystemRescue in the first place).

Zitat von ryecoaaron

You should've just used gparted live then. It is almost as good as SystemRescue for recovering.

Needed SSH unfortunately, but thanks for addressing this. Just didn't want others to experience this when they're already in need of SystemRescue and in some state of disrepair as the root issue was quite elusive (as everything looks normal at a high level).