Installation fail with unsquashfs error

P

Prr0

New Member
Jan 13, 2024
4
0
1
Hi,

I'm trying to install proxmox 8.1-1 on a beelink ser6, but during the installation I receive the following error

command 'unsquashfs -f -dest /target -I /cdrom/pve-base.squashfs' failed with exit code 1 at /usr/share/perl5/Proxmox/Install.pm line 906

I try 7.x version but the installation fails during GUI loading

Any help?
 
Thanks @BobhWasatch I check SHA256SUM and match, I change to another usb stick and the same, I just download again burn it to a different usd stick and the same error
 
What FS? The one you select during installation doesn't matter at this stage as far as I know. If you mean the USB stick the ISO should be written directly to the USB stick without a filesystem. On Linux use "dd", on Windows Etcher or Rufus are suggested.

https://pve.proxmox.com/pve-docs/pve-admin-guide.html#installation_prepare_media

Did you follow the above procedure to prepare the USB? Are you sure it is large enough? I see that you tried different sticks, were they different brands? Some USB sticks seem to not work well as boot devices. Other than those things I'm kind of out of ideas.
 
I try to install ubuntu and fail too due efi error on partition #1, so I is not a proxmox installation issue, is something during the creation of the partitions that cant be created, am looking how can I erase the ssd to try again
 
It's trying to access the cdrom. I assume you are doing an install using a USB drive? I'm not sure why the installer is doing this. I had the same issue. I burned a DVD and the installation worked perfectly fine using the DVD.
 
Be aware of corrupted USB storage devices!

I ran in to this issue as I re-installed a test Proxmox 8.1-1 node today and found this thread.

Two days ago I did a first attempt to install a Proxmox 8.1-1 node. I used a 32 GB USB drive and used Rufus to create a bootable install drive. USB drive was working flawlessly. Only issue I ran in to was that graphical installation just returned a black screen, so installation had to be done in console mode. Deployed using ZFS RAID0 file system on a single NVME SSD.

Today It was time to do a maiden proxmox installation to get a clean start. Used the same USB drive as before but ran in to the error:
Code: 
command 'unsquashfs -f -dest /target -I /cdrom/pve-base.squashfs' failed with exit code 1 at /usr/share/perl5/Proxmox/Install.pm line 906

Googled around and found this thread,

Used my trusted USB drive and re-did the creation of bootable installer with a sha256-verified ISO file. But with same result.

Found an older thread mentioning that balenaEtcher was a more robust option for creating the installation media. Walked down that path, but still got the error. However, this time the installation console threw another error message indicating I/O error on my USB storage device.

Did a third attempt where I used another USB drive, created a bootable install USB using balenaEtcher, and crossed by fingers. This time it finally worked.

This just goes to show that there is no such thing as a trusted USB storage drive!
 
  • Like
Reactions: pyr8lab
I know this is a bit dated, but I thought I'd post my solution. I encountered this error when using a USB stick. I saw a solution to install 7.4 and then upgrade, which I did but I didn't want to stop there. I thought about it and saw some folks said to use a different or a new USB stick. I had a USB 3.0 HDD enclosure so I put in a 500GB SSD I had around (overkill I know) and wrote the 8.2 image to the HDD using the PI imager. It installed flawlessly. Same image as failed on the USB stick.
 
Hi folks,

TDLR: I ran into the same issue and solved by updating the bios and using using rufus instead of balena to prepare the usb drive.

I was about to install Proxmox VE 8.3-1 on a hp ProDesk 600 G2 Mini and ran into the same issue. Changing the FS from ext4 to xfs didn't work.
I have only one USB drive (which I'm only ever use if I'm installing an OS), have no optical drive in the machine nor do I have an USB - otical drive.

After a few tries I updated the BIOS on the machine (it had a version from 2019, the latest one is from 2022). Because I had format the pendrive for the BIOS update I had to recreate the install drive but this time just for the sake of trying I used rufus instead of balena. After these two changes the installation was successfull on the first try.

I don't know which one of the two changes made the trick or the combination of the two but hope it will help someone in the future.
 
You must log in or register to reply here.
Top Bottom