hi
i created a ventoy image and put the manjaro iso on it as well as a few other distro’s. manjaro is the only that wont boot and i wonder if this error message means anything to anyone?
“mount: /run/miso/sfs/mhwdfs: fsconfig system call failed unable to read xattr index table” etc.
"failed to mount /dev/loop1
sh: cant access tty
and i get a input prompt [rootfs ´´]#
Did you check the Manjaro ISO for errors?
That’s annoying.
I had a bad morning - ended up at Grub and ended up with only a bootable Mint USB, so I had to grab Manjaro’s KDE ISO and dig out a spare 8GiB USB.
Maybe it’s worth just deleting everything and starting again - it seemed to work fine this morning.
sounds to me like a broken ISO.
I have my USB-SSD since many months with different distributions and update the frequently once a newer version is out.
Never had a problem with the Manjaro ISO. (apart from the fact, that secure boot need to be disabled after installation)
I agree with the general consensus. The Manjaro ISO is most likely damaged. Downloading a fresh ISO from the official download location might be prudent.
Before you download, you might wish to check your current ISO for consistency against the provided checksum file (see the download page) to verify the premise.
Regards.
On the chance that you might find it useful, I recently authored a Ventoy USB creation guide:
Assuming it’s the latest KDE .ISO, download the checksum to the same directory and run:
sha256sum -c manjaro-kde-24.2.1-241216-linux612.iso.sha256
You can also do this on the Ventoy USB itself.
the manjaro site says it should be e8cb6f9617593707bb7a96ccfc6051e4e3d25635e416cfdd5ae73e07fd1cd65f
i dont get that doing a check using ventoy on the iso. ive downloaded the iso on different computers now several times.
ventoy gives other numbers and mentions something about a .trash dir too.
refine the check to find out where it goes wrong:
Sorry, but, what?
If you are indeed using Plasma, you can right-click a downloaded ISO file in Dolphin, choose Properies and then the Checksum tab.
The checksum of the ISO will be determined, and you then compare it with the checksum of the respective downloaded ISO.
Always check that the checksums match. If they don’t, it usually means the ISO was damaged during download.
I don’t get what you’re trying to say. Ventoy is not on an ISO - A Ventoy USB is what you create to then drag your ISOs onto.
What is your point?
Did you check them for consistency each time?
Or, are you suggesting that simply because other ISOs downloaded seemingly without issue that this one should be fine too?
Murphy’s Law, dude. Always check the ISO.
We don’t remind you to do check it for amusement.
Regards.
How do you check the ISO against the checksum?
Would be new to me if you can do this with Ventoy.
You don’t “do it with Ventoy”.
The ISO is simply copied to the Ventoy device - it is (should be) an exact copy of the downloaded ISO.
… one copy is in the Download folder (whichever you choose that to be)
a copy of this is made onto the Ventoy device
It can be checked just the same way as the “original” downloaded file.
good quesrion
ventoy sometimes choke on the Manjaro ISO.
When it happens please use try the other option in ventoy.
We have two tools in the repo to fetch and verify the ISO
I know, that’s why i asked how “Ventoy gives other numbers”. With Ventoy only, you cannot checksum an ISO
Turns out in the .Trash folder there was a manjaro image, i deleted it and copied over the image from my pc to the flash drive root dir, then it worked. wierd wierd.
Not weird at all - ventoy scans for bootables on the disk - if it finds an iso - even in the .Trash it will display it - unlucky for you - it may have been a damaged ISO.
If you delete an ISO, depending on the OS you used it goes to the .trash folder. As Ventoy doesn’t know it the folder of deleted items, it simply scans and uses it.
If the ISO is broken it will not work. But at the end it’s not a Ventoy problem.
I have gotten into the habit to SHIFT-Delete files from my Ventoy disk, after if got confused why there are still entries in the boot menu for ISOs i’ve already deleted.
This goes then directly to trash and not in a (hidden) folder and doesn’t show up in the menu any longer.
Downloading Manjaro ISOs via bittorrent is another viable method. Torrent files are also linked on the official download page.
The way bittorrent works is such that damage to successfully completed files is exceptionally rare.
The ISO must have been damaged regardless of it being in Trash. Then copying an undamaged ISO to the Ventoy USB allowed the procedure to progress.
In this case the damage likely occurred while copying a file to the Ventoy USB. Perhaps the USB was removed prematurely, or there was some other temporary interruption, or perhaps the chosen USB was already damaged.
It’s difficult to say, with any certainty.
Marking your own post is not an appropriate Solution for others finding this topic. I have marked the first one that is.
Regards.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.