Error Compressed data is corrupt

Can u discord me or text mate helping u via email may take months . I don't
often check email erplegend#9791 or ERPlegend#9791

On Mon, Jan 22, 2024, 8:51 AM Kevin Ryan <
<email address hidden>> wrote:

> New question #709068 on Cubic:
> https://answers.launchpad.net/cubic/+question/709068
>
> If I use cubic to add a single package (as a test), I am able to boot my
> laptop off of the USB drive created by dd from the resulting ISO
>
> However, when I add about 40 packages and compress using LZW compression,
> it will not boot using the resulting ISO, which has a filesize of
> 3,827,441,664.
>
> The packages are java 17, google chrome, and the following:
> apt-transport-https curl wget openssh-server net-tools
> tigervnc-standalone-server tigervnc-viewer apache2 lrzsz vim xdotool
> xclip expect xz-utils vsftpd winbind sendmail gitk p7zip p7zip-full dillo
> lynx qbittorrent libnss3 perl-tk xsel autossh parcellite python3-pip
> python-tk lm-sensors acpi inxi openvpn libssl-dev apt-transport-https
> ca-certificates curl software-properties-common
>
> I see messages like
>
> file '/boot/' not found
>
> then on the error screen
>
> Initramfs unpacking failed: 2STD-compressed data is corrupt
> Failed to execute /init (error -2)
> Kernel panic - not syncing: no working init found. Try passing init=
> option to kernal...
>
> HOWEVER the image does boot when I click "Test" to directly boot it into
> QEMU
>
> Why would it boot in QEMU but not from the USB drive created using dd?
> And how can I fix that?
>
>
>
> --
> You received this question notification because you are an answer
> contact for Cubic.
>

It's very simple and I can include as many packages as u desire and include
compile scripts and more what's important is that everything u change is
all compatible

On Mon, Jan 22, 2024, 8:51 AM Kevin Ryan <
<email address hidden>> wrote:

> New question #709068 on Cubic:
> https://answers.launchpad.net/cubic/+question/709068
>
> If I use cubic to add a single package (as a test), I am able to boot my
> laptop off of the USB drive created by dd from the resulting ISO
>
> However, when I add about 40 packages and compress using LZW compression,
> it will not boot using the resulting ISO, which has a filesize of
> 3,827,441,664.
>
> The packages are java 17, google chrome, and the following:
> apt-transport-https curl wget openssh-server net-tools
> tigervnc-standalone-server tigervnc-viewer apache2 lrzsz vim xdotool
> xclip expect xz-utils vsftpd winbind sendmail gitk p7zip p7zip-full dillo
> lynx qbittorrent libnss3 perl-tk xsel autossh parcellite python3-pip
> python-tk lm-sensors acpi inxi openvpn libssl-dev apt-transport-https
> ca-certificates curl software-properties-common
>
> I see messages like
>
> file '/boot/' not found
>
> then on the error screen
>
> Initramfs unpacking failed: 2STD-compressed data is corrupt
> Failed to execute /init (error -2)
> Kernel panic - not syncing: no working init found. Try passing init=
> option to kernal...
>
> HOWEVER the image does boot when I click "Test" to directly boot it into
> QEMU
>
> Why would it boot in QEMU but not from the USB drive created using dd?
> And how can I fix that?
>
>
>
> --
> You received this question notification because you are an answer
> contact for Cubic.
>

Also don't dd . This method makes that iso simple u can use belena etcher

On Mon, Jan 22, 2024, 8:51 AM Kevin Ryan <
<email address hidden>> wrote:

> New question #709068 on Cubic:
> https://answers.launchpad.net/cubic/+question/709068
>
> If I use cubic to add a single package (as a test), I am able to boot my
> laptop off of the USB drive created by dd from the resulting ISO
>
> However, when I add about 40 packages and compress using LZW compression,
> it will not boot using the resulting ISO, which has a filesize of
> 3,827,441,664.
>
> The packages are java 17, google chrome, and the following:
> apt-transport-https curl wget openssh-server net-tools
> tigervnc-standalone-server tigervnc-viewer apache2 lrzsz vim xdotool
> xclip expect xz-utils vsftpd winbind sendmail gitk p7zip p7zip-full dillo
> lynx qbittorrent libnss3 perl-tk xsel autossh parcellite python3-pip
> python-tk lm-sensors acpi inxi openvpn libssl-dev apt-transport-https
> ca-certificates curl software-properties-common
>
> I see messages like
>
> file '/boot/' not found
>
> then on the error screen
>
> Initramfs unpacking failed: 2STD-compressed data is corrupt
> Failed to execute /init (error -2)
> Kernel panic - not syncing: no working init found. Try passing init=
> option to kernal...
>
> HOWEVER the image does boot when I click "Test" to directly boot it into
> QEMU
>
> Why would it boot in QEMU but not from the USB drive created using dd?
> And how can I fix that?
>
>
>
> --
> You received this question notification because you are an answer
> contact for Cubic.
>

Also ONLY FACTOR THAT MATTERS .are u using a live image

On Mon, Jan 22, 2024, 8:51 AM Kevin Ryan <
<email address hidden>> wrote:

> New question #709068 on Cubic:
> https://answers.launchpad.net/cubic/+question/709068
>
> If I use cubic to add a single package (as a test), I am able to boot my
> laptop off of the USB drive created by dd from the resulting ISO
>
> However, when I add about 40 packages and compress using LZW compression,
> it will not boot using the resulting ISO, which has a filesize of
> 3,827,441,664.
>
> The packages are java 17, google chrome, and the following:
> apt-transport-https curl wget openssh-server net-tools
> tigervnc-standalone-server tigervnc-viewer apache2 lrzsz vim xdotool
> xclip expect xz-utils vsftpd winbind sendmail gitk p7zip p7zip-full dillo
> lynx qbittorrent libnss3 perl-tk xsel autossh parcellite python3-pip
> python-tk lm-sensors acpi inxi openvpn libssl-dev apt-transport-https
> ca-certificates curl software-properties-common
>
> I see messages like
>
> file '/boot/' not found
>
> then on the error screen
>
> Initramfs unpacking failed: 2STD-compressed data is corrupt
> Failed to execute /init (error -2)
> Kernel panic - not syncing: no working init found. Try passing init=
> option to kernal...
>
> HOWEVER the image does boot when I click "Test" to directly boot it into
> QEMU
>
> Why would it boot in QEMU but not from the USB drive created using dd?
> And how can I fix that?
>
>
>
> --
> You received this question notification because you are an answer
> contact for Cubic.
>

I wish I would check ur mail I don't mind solving it problem . Cubic was
designed to make it easy once I understood this everything was no different
than just using a os terminal only . But u can vnc and have a display

On Mon, Jan 22, 2024, 4:35 PM kenneth harris <
<email address hidden>> wrote:

> Question #709068 on Cubic changed:
> https://answers.launchpad.net/cubic/+question/709068
>
> kenneth harris proposed the following answer:
> Also don't dd . This method makes that iso simple u can use belena
> etcher
>
> On Mon, Jan 22, 2024, 8:51 AM Kevin Ryan <
> <email address hidden>> wrote:
>
> > New question #709068 on Cubic:
> > https://answers.launchpad.net/cubic/+question/709068
> >
> > If I use cubic to add a single package (as a test), I am able to boot my
> > laptop off of the USB drive created by dd from the resulting ISO
> >
> > However, when I add about 40 packages and compress using LZW compression,
> > it will not boot using the resulting ISO, which has a filesize of
> > 3,827,441,664.
> >
> > The packages are java 17, google chrome, and the following:
> > apt-transport-https curl wget openssh-server net-tools
> > tigervnc-standalone-server tigervnc-viewer apache2 lrzsz vim xdotool
> > xclip expect xz-utils vsftpd winbind sendmail gitk p7zip p7zip-full
> dillo
> > lynx qbittorrent libnss3 perl-tk xsel autossh parcellite python3-pip
> > python-tk lm-sensors acpi inxi openvpn libssl-dev apt-transport-https
> > ca-certificates curl software-properties-common
> >
> > I see messages like
> >
> > file '/boot/' not found
> >
> > then on the error screen
> >
> > Initramfs unpacking failed: 2STD-compressed data is corrupt
> > Failed to execute /init (error -2)
> > Kernel panic - not syncing: no working init found. Try passing init=
> > option to kernal...
> >
> > HOWEVER the image does boot when I click "Test" to directly boot it into
> > QEMU
> >
> > Why would it boot in QEMU but not from the USB drive created using dd?
> > And how can I fix that?
> >
> >
> >
> > --
> > You received this question notification because you are an answer
> > contact for Cubic.
> >
>
> --
> You received this question notification because you are an answer
> contact for Cubic.
>

The USB boot worked when created with Balena Etcher! So I wonder why the dd command didn't work.

It was most likely due to partition type dd isn't really recommended if
doing gpt partition . It's more for mbr as it's a more a one way dynamic

On Tue, Jan 23, 2024, 7:57 AM Kevin Ryan <
<email address hidden>> wrote:

> Question #709068 on Cubic changed:
> https://answers.launchpad.net/cubic/+question/709068
>
> Status: Answered => Solved
>
> Kevin Ryan confirmed that the question is solved:
> The USB boot worked when created with Balena Etcher! So I wonder why
> the dd command didn't work.
>
> --
> You received this question notification because you are an answer
> contact for Cubic.
>

The error message "Compressed data is corrupt" indicates that there is an issue with the compressed (archive) file you are trying to open or extract. This error commonly occurs when attempting to access files within a compressed archive that have become damaged or corrupted.

To address this issue, you can try the following steps:

1. **Re-download the Compressed File:**
   If possible, re-download the compressed file from the original source. The file may have been corrupted during the download process.

2. **Use a Different Extraction Tool:**
   Try using a different compression/extraction tool to open the file. Popular tools include WinRAR, 7-Zip, or WinZip. Sometimes, a different tool may handle the corruption better.

3. **Repair the Compressed File:**
   Some compression tools have built-in features to repair damaged archives. Check if your tool has an option to repair or extract despite errors.

4. **Check for File Corruption:**
   Verify if the original file is corrupted by checking its source. If possible, obtain an uncorrupted version.

5. **Use Command-Line Tools:**
   You can try using command-line tools like `unzip` or `tar` to extract the contents. These tools may provide more detailed error messages that can help diagnose the issue.

6. **Contact the Source:**
   If the compressed file is from a specific source, consider reaching out to them for assistance. They may be able to provide a valid, uncorrupted file or offer guidance on resolving the issue.

If none of these solutions work, it's possible that the compressed file is irreparably damaged, and you may need to seek an alternative source or obtain a new, uncorrupted version. CHECK:https://www.supreme-cars.uk/best-taxis-in-high-wycombe/

My point is that I believe there was not really a problem with corrupt data unless it was due to the dd command, because the same image works fine in QEMU

Na mostly likely ur image is fine but like I said dd is more supported for
mbr partitioning which is used less often today . My original attempts
involved another tool but it would only work using dd and only worked for
mbr gpd was not registering so when I tried cubic the only thing I had to
figure out was the installer side to it so my iso could be flashed and a
person can using calamares installer to install

On Wed, Jan 24, 2024, 7:00 AM Kevin Ryan <
<email address hidden>> wrote:

> Question #709068 on Cubic changed:
> https://answers.launchpad.net/cubic/+question/709068
>
> Status: Solved => Open
>
> Kevin Ryan is still having a problem:
> My point is that I believe there was not really a problem with corrupt
> data unless it was due to the dd command, because the same image works
> fine in QEMU
>
> --
> You received this question notification because you are an answer
> contact for Cubic.
>