I download both the full ISO and the net install ISO yesterday and neither will finish installing. Yesterday I attempted to install from the net install ISO and it got to 23% and sat there. Today I attempted the full ISO install and it got to 50% and just sat there. With my hardware there should be no issue with either installing. Any thoughts on what might be happening? I currently have Garuda installed so I’m providing the inxi from it. Thanks
I have an even earlier problem; I can’t even make a bootable usb stick.
danw58@danw58:~$ sudo usb-creator-gtk
xorriso 1.5.6 : RockRidge filesystem manipulator, libburnia project.
xorriso : NOTE : Loading ISO image tree from LBA 0
xorriso : UPDATE : 4857 nodes read in 1 seconds
xorriso : NOTE : Detected El-Torito boot information which currently is set to be discarded
Drive current: -dev '/home/danw58/Downloads/zip/openSUSE-twd/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20240520-Media.iso'
Drive access : shared:readonly
Media current: stdio file, overwriteable
Media status : is written , is appendable
Boot record : El Torito , MBR isohybrid cyl-align-off
Media summary: 1 session, 2190029 data blocks, 4277m data, 2459g free
Volume id : 'openSUSE-Tumbleweed-DVD-x86_64'
xorriso : FAILURE : Cannot determine attributes of (ISO) source file '/.disk/info' : No such file or directory
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
xorriso 1.5.6 : RockRidge filesystem manipulator, libburnia project.
xorriso : NOTE : Loading ISO image tree from LBA 0
xorriso : UPDATE : 4857 nodes read in 1 seconds
xorriso : NOTE : Detected El-Torito boot information which currently is set to be discarded
Drive current: -dev '/home/danw58/Downloads/zip/openSUSE-twd/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20240520-Media.iso'
Drive access : shared:readonly
Media current: stdio file, overwriteable
Media status : is written , is appendable
Boot record : El Torito , MBR isohybrid cyl-align-off
Media summary: 1 session, 2190029 data blocks, 4277m data, 2459g free
Volume id : 'openSUSE-Tumbleweed-DVD-x86_64'
xorriso : FAILURE : Cannot determine attributes of (ISO) source file '/.disk/mini-info' : No such file or directory
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
danw58@danw58:~$
And it did the same thing whether it was the full cd iso, or the network install.
It is better to open an own thread as you have a completely different problem.
But the issue is clear. You are using a tool which is not suitable to dump an ISO to an USB stick (other than *buntu). The package description for usb-creator-gtk (*buntu only) is clear:
Startup Disk Creator converts a USB key or SD card into a volume from which you
can start up and run Ubuntu. You can also store files and settings in any space
left over.
The program also works for Debian, or any other Debian-based OS for which you
have a CD or .iso image.
This package contains the GTK+ client frontend.
openSUSE is a rpm based distribution. Debian and *buntu are deb based distributions.
I’m sorry; I’m new here, and the system doesn’t let me post a new topic.
Nothing but problems, punished just for being new; I’m at the end of the line; GL drivers from AMD for Ubuntu 24.04 will take possibly months; I destroyed my machine with arcane driver install commands and had to reinstall the OS; but I had the plan to try tumbleweed and I hear driver updates are less of a problem with it, but I try to burn a usb stick with tumbleweed’s image but the tool from Ubuntu doesn’t work. Found a video on how to install SUSE that recommends etch from balena, so I downloaded their AppImage and I don’t know what to do with the file, so I download their .deb package but apt install gives me an error…
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
balena-etcher : Depends: gconf-service but it is not installable
Depends: gconf2 but it is not installable
Depends: libgconf-2-4 but it is not installable
E: Unable to correct problems, you have held broken packages.
If an admin could move my posts to a new topic it would be great; this punishment of not letting people post a new thread when they are new is very cruel and probably ineffective. People probably register to the forum precisely when they are desperate to ask something.
Lol, I should have searched for a simpler explanation.
Well, in the meantime I got my etcher problem sorted out; it installed fine on my old laptop, with Ubuntu 22.04. So now I’m going to try and boot off the usb stick and install SUSE.
EDIT: Nope, it didn’t work. It ignores the usb and boots right into Ubuntu.
Anyways, I will start a new topic.
If it helps anyone I have not cleared the partition of the files that were installed, so by right there should be a log that has info on what was happening. Just need instructions on finding them so I can post them.
There is also Ventoy which should have on issue with any OpenSUSE ISO. I know cause I’ve installed Tumbleweed in the pass from a Ventoy key without issue.
I would suggest it is a OpenSUSE issue and not a Ventoy issue. It’s amazing that when a ISO doesn’t work proper;ly with Ventoy they manage to fix Ventoy so it does. Since OpenSUSE ISO consistantly don’t like to work with Ventoy it suggest that the design of the particular ISO is the issue and not Ventoy.
Understanding the base problem is really important. Ventoy added arbitrary boot parameters to the installer and not openSUSE. That means Ventoy altered the kernel command line parameters which prevented sucessful operation of the OS. I recommend to search bugzilla and forum and to read the provided links. The “fix” of Ventoy was to remove these wrong parameters (added by Ventoy) after users complained about Ventoy breaking installations.
It can easily be seen (documented in issues and bugreports) that Ventoy added boot parameters like
rdinit=/vtoy/vtoy
VTOY_LINUX_REMOUNT
In other words, Ventoy alters the installation media. That is why responsible devs warn before the use of Ventoy.
If you insist to use it, you can do it. It is your system and your sacurity. But don’t advertise it here.
openSUSE is easy Most Linuxes need special change to boot from USB. openSUSE is boot ready simply do a clean unchanged binary copy to the device, NOT a partition on the device direct to the device.
I simply use cp others recommend dd. Generally GUI Linux copiers modify the iso code thus breaking openSUSE, Some do offer a dd mode but that is usually not obvious
@CummingCowGirl Well then best do your due diligence on using a third party product…
Compare the output of the distribution images with fdisk -l some.iso but as @gogalthorp indicated a simple dd if=/path/to/downloaded.iso of=/dev/sd<X> bs=4M status=progress && sync should work.
My point was and is that they install from Ventoy and once installed run as intended by the OS’s devs. Not wanting your OS to work with a tool that makes things easier for your users screams our way or the highway.
@CummingCowGirl The way I see it adding a third party tool has the potential to compromise security, can you use secure boot with a current/unrevoked certificate.
You can but you need to trust the Ventoy, at least temporary. But as you are going to use it anyway I guess it does not pose additional security risk. secure . Ventoy
Of course, it does require user to understand what’s going on. It is no more plug and play.
