ls: /mnt/udisk/system*.up: No such file or directory
The system can't find any file called system(anything).up in the /mnt/udisk directory.
/mnt/udisk seems to be the directory where your system expects to find firmware upgrade files. When you put your USB stick on the scope, the contents of the USB stick should appear in that directory.
It doesn't find any file callled "system(probably a number or reference).up", which would be the firmware
update. * is a wildcard that means "anything".
So probably your USB stick doesn't have any FW update file. It could be that the system doesn't take your USB but I think you would get a mount error should that be the case. Having the complete output from teraterm/putty would help. Maybe your USB stick is too big (>4 GB) or is not FAT32 formatted. But I think probably that firmware upgrade file just is not there.
Using teraterm/putty you could give this command
ls /mnt/udisk
This should return a list with the files/directories under /mnt/udisk. Maybe your system*.up file is under a directory or still compressed or...
I don't know what. It should be on the first level of your USB stick
I think you probably don't have any linux experience and screwed some command or some procedure step. Please follow the instructions found in this post:
https://www.eevblog.com/forum/repair/voltcraft-dso-1102d/msg2036896/#msg2036896These are the instructions that Blindelinx followed. He also claimed not having any linux experience. Please note that these instructions, as Blindelinx said, seem to be using a not-so-good firmware update file. You have to use the original firmware from Hantek instead as he did. Probably having that original firmware update systemXXXXXX.up in the first level of a good USB stick is all that is needed.
Please note that if you screw some command and give instead a command that will delete, say, anything, linux will not ask "Are you sure?" before executing that screwed up command. So be careful, and, if not sure you can do it, please go to the dealer.
If your system is able to return a "file not found" error it means that Linux is running so you'll have a functional oscilloscope as soon as a good firmware update is loaded into it.
Good luck