Install With Windows exe yields only 46 GB storage, not 128 or 256 GB

#1

I tried several times on different computers to install Endless OS 6.0 using the exe file inside Windows 11. I choose 256 GB, but after installation, I get a notification that there’s only about 600 MB of storage space left of about 46 GB. The OS seems to boot and run OK, but I can’t install anything new due to no storage space. I’ve tried choosing 128 GB too with the same result.

I’ve read that after installation, you can’t increase the size of the storage…have to uninstall Endless and reinstall. But if I do, I get the same ~46 GB storage, not 128 or 256 as selected.

Is this a bug or do I need to do something else to achieve 128 or 256 GB storage?

#2

This is a bug.

Endless OS is installed by writing a disk image directly to disk – or in the case of the Windows tool, a virtual disk backed by a file in your C: drive. The first time you boot Endless OS, the OS partition is meant to be automatically resized to fill the disk you installed it to.

It sounds like this is not working as expected on dual-boot systems. Please could you get a diagnostic file from within Endless OS, following the instructions below, and attach it here?

You should also have a number of files named Endless Installer (date).log in the same directory as the endless-installer.exe file you used to install. Could you attach one of those here too, please, ideally from the last time you installed?

#3

OK, I’ve created the diagnostic file: eos-diagnostic-240524_121817_UTC-0400.txt (655.1 KB)

And here’s the latest log from Windows:
EndlessInstaller20240522_16_18_21.log (56.4 KB)

#4

Hey Will, I posted the log files on the web site but have seen no response to them.

#5

Sorry – I was on vacation on Monday & Tuesday so I’m only just back at my desk today.

From this section of the diagnostic file, I can see that the partition was resized to fill the available space; but the filesystem on the partition was not resized:

/org/freedesktop/UDisks2/block_devices/loop0p3:
  […]
  org.freedesktop.UDisks2.Filesystem:
    […]
    Size:               45275414528
  org.freedesktop.UDisks2.Partition:
    […]
    Size:               137371827712
    […]

So something went wrong with the eos-firstboot script that is supposed to do this.

I am curious what you see if you run the following command in a terminal window:

sudo /sbin/eos-firstboot
#6

OK, after running that command in a terminal, it
looks like it’s now showing 137.9 GB total; 43.9 GB used; 90.6
GB free using “properties” of the partition. I tried to take a
screenshot of the screens, but I couldn’t make any of the
screenshot programs work correctly.

    I also created a bootable flash drive using

Etcher. It boots just fine, but when I try to install EOS, it
errors out on reformatting.

    I also downloaded the VirtualBox VM and it works

quite well in a couple of my desktops.

Thanks for your help.

Dan

#7

Thanks. It’s a little surprising that this didn’t happen automatically but I couldn’t figure out why from the logs. I’ll open a ticket to look into this.

You can press the PrintScreen key on your keyboard, or click the camera icon in the system menu (right-hand side of the top bar), to access a built-in screenshot tool.

Oh no! Do you have any further details about the error?

#8

OK, I just tried it on another laptop, HP 840 G1
with 500 GB SATA old HDD. I took a screenshot, but your forum
won’t accept images. It says “Oops, something went wrong.
error reading image: Error reading from file: input/output
error” I copied the debug txt file and have attached it here.
Hope this helps.

  I really like EOS, but if I can't install it on a computer, it

isn’t worth much to me or the friends in education I’m trying to
show it to.

Dan

eos-diagnostics-240525_052952_UTC-0400.txt (675 KB)

#9

We’re about 5 levels of debugging deep here, but: the forum should accept screenshots. What kind of file are you attaching (PNG?) and what error do you see when you try to?

May 25 05:29:48 endless kernel: SQUASHFS error: zlib decompression failed, data probably corrupt
May 25 05:29:48 endless kernel: SQUASHFS error: Failed to read block 0x114becf1e: -5
May 25 05:29:48 endless kernel: SQUASHFS error: zlib decompression failed, data probably corrupt
May 25 05:29:48 endless kernel: SQUASHFS error: Failed to read block 0x114becf1e: -5
May 25 05:29:48 endless kernel: I/O error, dev loop1, sector 10400768 op 0x0:(READ) flags 0x80700 phys_seg 53 prio class 2
May 25 05:29:48 endless kernel: SQUASHFS error: zlib decompression failed, data probably corrupt
May 25 05:29:48 endless kernel: SQUASHFS error: Failed to read block 0x114becf1e: -5
May 25 05:29:48 endless kernel: I/O error, dev loop1, sector 10401792 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
May 25 05:29:48 endless kernel: Buffer I/O error on dev loop1, logical block 5200896, async page read
May 25 05:29:48 endless kernel: SQUASHFS error: zlib decompression failed, data probably corrupt
May 25 05:29:48 endless kernel: SQUASHFS error: Failed to read block 0x114becf1e: -5
May 25 05:29:48 endless kernel: I/O error, dev loop1, sector 10401794 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
May 25 05:29:48 endless kernel: Buffer I/O error on dev loop1, logical block 5200897, async page read
May 25 05:29:48 endless kernel: SQUASHFS error: zlib decompression failed, data probably corrupt
May 25 05:29:48 endless kernel: SQUASHFS error: Failed to read block 0x114becf1e: -5
May 25 05:29:48 endless kernel: I/O error, dev loop1, sector 10401796 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
May 25 05:29:48 endless kernel: Buffer I/O error on dev loop1, logical block 5200898, async page read
May 25 05:29:48 endless gnome-image-ins[2932]: gis_scribe_subtask_cb: tee failed: error reading image: Error reading from file: Input/output error
May 25 05:29:48 endless kernel: SQUASHFS error: zlib decompression failed, data probably corrupt
May 25 05:29:48 endless kernel: SQUASHFS error: Failed to read block 0x114becf1e: -5
May 25 05:29:48 endless kernel: I/O error, dev loop1, sector 10401798 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
May 25 05:29:48 endless kernel: Buffer I/O error on dev loop1, logical block 5200899, async page read

Either your USB drive or (less likely) the ISO download is defective. You could try a different USB drive, or verifying the SHA256sum of the ISO.

#10

I increased your trust level on this forum, which might make it possible for you to attach more interesting files.

#11

I tried to attach a (jpg) file; can’t remember the
exact words, but it said it couldn’t accept image files.

    I've looked all over and I can't find any checksum

info on the EOS website. Send it to me and I’ll check my ISO
download. I used bit torrent to d/l.

Dan

#12

https://images-dl.endlessm.com/release/6.0.0/eos-amd64-amd64/en/eos-eos6.0-amd64-amd64.240514-082543.en.iso.sha256

#13

But given you used BitTorrent to download the ISO, my money is on the USB drive, because the BitTorrent protocol includes checksumming the downloaded data.

#14

Copy I downloaded:
a45d0bdf070c940db4f65fabeee7040916a1fc0d6d42b33b7f1faf7b05bc2665

    Link you sent:

03a23cd0fdcc2092aa377914dd50b0d08af7c36bcbe7c29f7c8597389ff3a024

    It boots and operates from the flash drive OK it

seems, just won’t install. Please verify the link you sent
checksum is correct. I’ll d/l it again and run checksum if the
“03a…” is correct.

#15

If the file you downloaded is called eos-eos6.0-amd64-amd64.240514-082543.en.iso then the checksum I sent you is correct

#16

Yes, that’s the file name. I’ll d/l it again
with HTTP this time.

#17

Well, this time with HTTP (using uGet) d/l, the
SHA256 checksum is:
ccf95353c9ba9dd68ae86f75bbc5a4b9f3222d48d6b8bff3ba665de0c9171741

Way weird!! Any suggestions?

#18

What URL are you fetching with uGet?

Does it tell you which mirror you downloaded from?

What is the file size, in bytes?

#19

Actually, uGet stalled at 99% on the first
download and I didn’t notice it. I retried the download and now
the checksum matches. I’ll put it on the flash drive later
today and try to install. I’ll let you know how it goes.

#20

Used Etcher to make a bootable USB stick on a PNY 64 GB drive. It boots and now the installation goes w/o a hitch. Thanks for your help.