22.04 not installing

[vanadiumboy]

The file that I have is
kubuntu-22.04.1-desktop-amd64.iso
I think I downloaded it a year ago.

I burned it to DVD-RW and installed it.
Previous version of Kubuntu would not install from DVD (21.10, 21.04). We reported the bug and I guess they fixed it in 22.04.
20.04 and 22.04 can be installed from DVD.

As for your question about size, my ISO file is
3,767,502,848 Bytes

As to your question about fitting a 3.5 GB file on a 4.7 GB DVD.... DVDs don’t have 4.7 GB because they divide by 1000 instead of dividing by 1024.
In reality, the size of a DVD is 4.38 GB. Some people get their panties in a twist and insist on inserting an i in the GB and calling that gigigobo.
Your file should fit.

BTW, your 1 TB HDD is actually 0.93 GB.

[arsivci]

Friday 28th.
I fear I still have problems! I have now purchased a box of Verbatim DVD-R discs labeled 4.7Gb 16xspeeed 120min. Back home used K3B to burn the original downloaded .iso file onto one of those blank discs. To my bafflement it stopped at the same point as did my previous attempt on to a 3.5Gb disc with a Write Error message. When I use Dolphin to see what I have got on that DVD (I am calling it 'Failed' for an identity) I am given only the one file name - Kubuntu 22.04 LTS amd64 - but also 'free space 0b of 3.5Gb (100% used)'. That is absurd! How can a 7.4 capacity disc be full at 3.5Gb?

It is normal; that's the difference of burning as opposed to copying a CD.

I am going back to get a better grasp on this SHA business but in the meantime has anyone else tried downloading 22.04 (some must have, surely)? If so, from which source and what size was the resultant .iso file please? I would happily follow someone else's lead!

This is the address to download:
https://cdimage.ubuntu.com/kubuntu/r....04.1/release/

I assume your pc is UEFI capable.

[MarkS]

Once you figure out how to SHA256 the download, I would download the LTS .iso to your hard drive and use Smart Disk Creator on your USB stick. Then enter your BIOS and set the USB stick to the 1st option to boot from.

[Keith Sayers]

Friday 28th.
I fear I still have problems! I have now purchased a box of Verbatim DVD-R discs labeled 4.7Gb 16xspeeed 120min. Back home used K3B to burn the original downloaded .iso file onto one of those blank discs. To my bafflement it stopped at the same point as did my previous attempt on to a 3.5Gb disc with a Write Error message. When I use Dolphin to see what I have got on that DVD (I am calling it 'Failed' for an identity) I am given only the one file name - Kubuntu 22.04 LTS amd64 - but also 'free space 0b of 3.5Gb (100% used)'. That is absurd! How can a 7.4 capacity disc be full at 3.5Gb?

Tracking back further to my original download (the usb stick I call Lily) I get the file name 'kubuntu-22.04.1-desktop-amd64.iso' and then 'size is 3.5Gb' - yet the stick itself is labeled 16Gb and Dolphin tells me it has 11Gb free. In other words the download has terminated at just the capacity of the DVD onto which I intended to burn it, left 11Gb unused, and a shortfall of 1.5Gb. That cannot be coincidence, surely? Lily could not know what my next step would be!

I am going back to get a better grasp on this SHA business but in the meantime has anyone else tried downloading 22.04 (some must have, surely)? If so, from which source and what size was the resultant .iso file please? I would happily follow someone else's lead!

In passing is there any significance in the original being an ISO9669 file system? From online I got only that it is the standard format for CDs and DVDs. From K3b I got a notification that 'The file you are about to add to the project is an IS 9660 image. As such it can be burned to a medium directly since it already contains a file system' - I opted to 'Burn the image directly' - would that have been correct?

[claydoh]

Glad you are doing well!
My wife has been doing lollipop work over near Bendoura, She hasn't mentioned any allergies as of yet. I do need to save enough $$$ for the visa fees etc so I can finally test my own sinuses personally

With USB boot disks, you just point the software to the ISO to where it is located directly on your hard drive, and the destination will be the USB stick (4Gb or larger). No need to move the ISO anywhere. It will actually work a little better/faster if you leave the ISO on your hard drive.

Personally, I have sometimes had issues with the USB Creator tool in the past, though it usually works for most people most of the time.
If you are still having issues booting, and you have set your computer to boot from USB, you might try an alternative tool,
I like this one: Etcher
It does not need installation - just extract the file from the zip, click to run, and is simple and easy to use, and it has always worked for me.

[Keith Sayers]

I have diagnosed my problem and am reprimanding myself for not thinking of it sooner. The 3.5GB DVD I am using for that intermediate stage is not big enough to hold the expanded .iso file - though it must be 'only just' because now I do get it opened its size is 3,767,502,848.

So I tried the Startup Disk Creator route - which initially would not let 'Lily' (the USB stick containing the .iso file - I name my drives for easy reference) be the source file - but put it into the destination box.

I then copied the .iso into its own folder on the hard drive but found it had to be in the Downloads folder for Startup Disc Creator to find it. That succeeded and I had another USB ('Lucy') containing the expanded file.

Then to the boot menu where set both 'USB Boot' and 'Boot USB Devices First' to <ENABLED>

But I could not then boot from Lucy :
PXE-E61 : Media test failure, check cable
PXE-M0F : Exiting Intel boot agent
No bootable device - insert boot disc and press any key
- but there was no response to the keyboard.

Booted from the hard drive, went into Partition Manager, found the type for Lucy was ISO9660 - something new to me - set the mount point for Lucy to '/' and the flag to 'boot' but could not give it a name. But still the same failure.

Also tried K3b which gave me a choice of source files of which one was the .iso file I needed but when I chose that I got 'File not found'.

My obvious next step is to buy some larger DVDs and try again via K3b but I would be interested in any comments on my experience with the Startup Disc Creator.

>I hope you are recovering well, Keith!!
Yes, thank you, it was eventually diagnosed to have been hay fever - something else new to me - but for weeks now Canberra weather has been nothing but rain, therefore more growth (to which the weeds in my garden can attest) and more pollen .....

[Snowhog]

Be careful there to check the actual SHA256SUMS for the actual iso image file you linked to
https://cdimage.ubuntu.com/kubuntu/j...-live/current/
The SHA256SUM you list is not the one for the image you linked to, though the correct one is easily found on the landing page.
It isn't even the correct one for the official 22.04.1 release iso
https://kubuntu.org/alternative-downloads/

Well, it was the correct SHA256SUM for the image I linked to at the time I made the post. The page I linked to was for Kubuntu "Daily-Live" images for amd-64. And of course, when the daily image is updated, the SHA256SUM is also going to change. Sorry 'bout that!

The important take away is to verify the download against the checksum immediately after the download is finished.

[claydoh]

Sorry to be slow coming back to this - I have been laid out by a virus. However I have now been back to then Australian National Library (who have a much faster download) and taken another download from www.kubuntu.org) onto a USB stick, brought that home and on it run sha256sum. The result :
1b03afb1e89bb52ff6264a97d5308ccc330e629af87ee03ee1 6d8552c2f511de kubuntu-22.04.1-desktop-amd64.iso
- which differs from that quoted above by Snowhog. Presumably that means I have a faulty download?. I will try again from the https://cdimage.ubuntu.com/kubuntu/j...-live/current/ suggested by Snowhog. (There is a proverb somewhere about patience.)

I hope you are recovering well, Keith!!

The sha256sum is actually correct, so you are OK there
This page has the correct sums for your ISO
https://kubuntu.org/alternative-downloads/

[claydoh]

Well, that very well could be that the shasum256 you cited here, is for Ubuntu 22.04.1. If you downloaded the Kubuntu 22.04.1 ISO, its shasum256 is going to be different.

Download for Kubuntu 22.04.1 LTS: https://cdimage.ubuntu.com/kubuntu/j...-live/current/
SHASUM256 for Kubuntu 22.04.1 LTS: 7e057f14b4c5aa2cf8052b3a990d49d0bea83e704dabace2cd 483064c45badf8 *jammy-desktop-amd64.iso

Be careful there to check the actual SHA256SUMS for the actual iso image file you linked to
https://cdimage.ubuntu.com/kubuntu/j...-live/current/
The SHA256SUM you list is not the one for the image you linked to, though the correct one is easily found on the landing page.
It isn't even the correct one for the official 22.04.1 release iso
https://kubuntu.org/alternative-downloads/


Note that your ISO url leads to a daily build. NOT the release iso, though the physical content is probably identical, or close enough. It has its own SHA256SUM which of course will be completely different to other Iso builds (the one on Kubuntu's downloads page, for example)

[Keith Sayers]

Sorry to be slow coming back to this - I have been laid out by a virus. However I have now been back to then Australian National Library (who have a much faster download) and taken another download from www.kubuntu.org) onto a USB stick, brought that home and on it run sha256sum. The result :
1b03afb1e89bb52ff6264a97d5308ccc330e629af87ee03ee1 6d8552c2f511de kubuntu-22.04.1-desktop-amd64.iso
- which differs from that quoted above by Snowhog. Presumably that means I have a faulty download?. I will try again from the https://cdimage.ubuntu.com/kubuntu/j...-live/current/ suggested by Snowhog. (There is a proverb somewhere about patience.)

[Snowhog]

Progress? I am picking my way slowly through this and have copied the two lines from http://releases.ubuntu.com/jammy/SHA256SUMS - the upper of which is for desktop - and run SHA256 in Konsole against the .iso file I have downloaded. The result from that latter bears no resemblance to the former.

Well, that very well could be that the shasum256 you cited here, is for Ubuntu 22.04.1. If you downloaded the Kubuntu 22.04.1 ISO, its shasum256 is going to be different.

Download for Kubuntu 22.04.1 LTS: https://cdimage.ubuntu.com/kubuntu/j...-live/current/
SHASUM256 for Kubuntu 22.04.1 LTS: 7e057f14b4c5aa2cf8052b3a990d49d0bea83e704dabace2cd 483064c45badf8 *jammy-desktop-amd64.iso

[Keith Sayers]

Progress? I am picking my way slowly through this and have copied the two lines from http://releases.ubuntu.com/jammy/SHA256SUMS - the upper of which is for desktop - and run SHA256 in Konsole against the .iso file I have downloaded. The result from that latter bears no resemblance to the former. I will do another download .....

[kc1di]

Wondering does the live session boot and run without problems? If it does please go to the system setting page (found on the panel next to the Menu button.) Under system Administration click on About this system and when that page comes up click on show more information. What does it show for processor , ram and graphics card?

[oshunluvr]

First of all, you need to ensure you have a good download. The file size is not an solid indicator that the file is OK, just that the file you have is the same size as the source. A corruption may not be revealed by file size. You MUST do a checksum validation after download.

I suggest not writing the ISO to anything at all. GRUB can boot directly to an ISO. A GRUB USB stick isn't too hard to build. I have one and it boots to 6 different ISO I carry with me for work - clonezilla, gparted live, a live distro, etc.

If your computer boots now using GRUB it's even easier. Copy the verified ISO to some place GRUB can access it - like the grub folder - and put a stanza in grub.cfg that puts the ISO in the GRUB menu so you can boot it. To add it to GRUB, put this in /etc/grub.d/40_custom:

menuentry 'Latest ISO download' --class iso {
set isofile="/iso/latest.iso"
loopback loop (hd1,2)$isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile noprompt noeject
initrd (loop)/casper/initrd.lz
}

Set 40_custom file as executable. Then run sudo update-grub.

In my example above, I have a folder name "/iso" on drive "hd1" and partition "2"
The hard drive is the second drive (GRUB counts drives starting with 0) and the partition is 2 (because for some reason GRUB counts partitions starting at 1 - go figure)
The ISO file name is "latest.iso" - obviously this would be whatever filename you use. I did it this way because I could easily add a new ISO to the /iso folder and just rename it to "latest" so I didn't have to keep updating GRUB.

Here some community info on the process: https://help.ubuntu.com/community/Gr...SO_Menuentries
Here's some examples of different ISO types and the required menus entries: https://help.ubuntu.com/community/Gr...OBoot/Examples

My example entry above boots any *buntu ISO no problem. If you go the the first link above, note there's a lot of "what if" stuff on there you can safely ignore.

[Keith Sayers]

Thank you all - I am digesting all this.