Integrity check can't find specified file. lmde-7-cinnamon-64bit.iso

jjconstr

Active Member
Joined
Feb 8, 2020
Messages
113
Reaction score
45
Credits
646
Hi, Ive been away for a number of years and now wanting to get Linux up and running on an older machine. I'm using a Asus Vivobook laptop with Win11 and current updates. I've downloaded the above named iso, both the SHA256 files, not copied, but right clicked and "saved as". Using GNUPG windows installer I opened a Powershell window and typed the hashfile command. The iso couldn't be found and other errors were listed, all in red. I think snips would be appropriate here to show what is happening. Tell me if I'm
wrong, please. Screenshot 2025-10-28 184823.pngScreenshot 2025-10-29 023557.png

I'm wondering if the the error referencing the word "and" is related to the folder path which has spaces before and after that word. Dad and Mom is a user name I put in when I got the laptop. I saw in the beginner tutorials there should be no spaces in user names. I dont know how it got to be a folder name.

Something I read mentioned distros that had built in verifiers. Does that mean verification can be done
after installation? Even when they're not built in?

Years ago, I couldn't get the verification to work so I installed without verifying. Problems did come up. I don't want that again.
 
Last edited:


Hi, Ive been away for a number of years and now wanting to get Linux up and running on an older machine. I'm using a Asus Vivobook laptop with Win11 and current updates. I've downloaded the above named iso, both the SHA256 files, not copied, but right clicked and "saved as". Using GNUPG windows installer I opened a Powershell window and typed the hashfile command. The iso couldn't be found and other errors were listed, all in red. I think snips would be appropriate here to show what is happening. Tell me if I'm
wrong, please.View attachment 28391View attachment 28394

I'm wondering if the the error referencing the word "and" is related to the folder path which has spaces before and after that word. Dad and Mom is a user name I put in when I got the laptop. I saw in the beginner tutorials there should be no spaces in user names. I dont know how it got to be a folder name.

Something I read mentioned distros that had built in verifiers. Does that mean verification can be done
after installation? Even when they're not built in?

Years ago, I couldn't get the verification to work so I installed without verifying. Problems did come up. I don't want that again.

Install on Windows gtkhash and you can verify the ISO of lmde-7-cinnamon
 
Problem is path, you're not in correct path currently. You're on system32 folder, you probably need to cd to Downloads folder or wherever you downloaded

"cd C:\Users\yourname\Downloads\" then check :)
 
Problem is path, you're not in correct path currently. You're on system32 folder, you probably need to cd to Downloads folder or wherever you downloaded

Thank you! cd\ worked. Then gnupg gave output for sha1. That didn't match. Can it be asked for sha256?

Build instructions in Gnupg said it is dependent on 5 related packages I have not downloaded them. Is that needed?

Thank you in advance.

View attachment 28402
 
You can use SHA256, it's common. For other checks I can't help, I usually only check checksum and that's it.
 
Build instructions in Gnupg
Using GNUPG windows installer
There is gpg4win:

File sha256sum.txt contains sha256 so with PS you can:
Bash:
(Get-FileHash -Algorithm sha256 <"path/to/filename">).Hash -eq <"sha256 hash string">

Note the quotes, they're needed for paths or strings with spaces.
You can avoid CLI with gpg4win, just use Kleopatra to import key and verify sums.
 
The problem also was that i left off part of the command specifying sha256. Verification was successful after correcting that.
I used balena etcher to burn, maybe not the right word, the mint iso to stick drive. Seemed to go well until checking properties. The drive had only 4 MB on it and had capacity of 4 MB. Any ideas?
 
Did you format or otherwise clean the usb stick before using balena ? if you did, how did you go about doing that ?

Just for the record, when using balena or rufus to burn an .iso to a usb stick there is really no need to format or clean it before. Balena or rufus will both take care of that automatically

If the properties of the usb stick are only showng 4MB .....there is something wrong there......either the stick or the burning failed in some way.

I have a stick here which has a capacity of 16GB when empty....and it has LMDE7 on it and shows 3GB on it currently. It also shows 0 bytes free space...which is normal after burning an .iso to a usb stick

It also shows its capacity as being 3.0GB
 
Last edited:
1761892853684.png
 
As my colleagues have said, this is normal behaviour when you put any bootable application/program on a USB drive, no matter how big the drive is, if the ISO is 3GB then that is all that will show, the only exception is if you are making a multi bootable drive with Ventoy or similar
 


Follow Linux.org


Top