Vero V Upgrade to 2025.03-1 went wrong, also error during USB install

Hi all,
I am a long time user of the Vero 4K and the Vero V, using the V as my main, i alway had to update via cli (sudo apt-get update and sudo apt-get dist-upgrade) since the update via my-osmc skin always stays on downloading update for hours.
No problem to update via cli, until now.

Ran the 2 commands, rebooted and spalsh screen stayed on the S905x4 logo, could nog get in via ssh.

Next best thing, download the image and install via USB, but on both the 2025.10-1 and 2025.03-1 i get an error after initial installation:

This is the install.log which is on the usb:
Wed Jan 1 00:00:12 2020 Starting OSMC installer
Wed Jan 1 00:00:13 2020 Detecting device we are running on
Wed Jan 1 00:00:13 2020 Mounting boot filesystem
Wed Jan 1 00:00:13 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:13 2020 Using device->boot: /dev/mmcblk1p1 and FS: fat32
Wed Jan 1 00:00:13 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:13 2020 Using device->boot: /dev/sda1 and FS: fat32
Wed Jan 1 00:00:13 2020 Filesystem defined by /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:00:13 2020 No preseed file was found
Wed Jan 1 00:01:16 2020 Creating root partition
Wed Jan 1 00:01:16 2020 Calling fmtpart for partition /dev/osmcroot and fstype ext4
Wed Jan 1 00:01:17 2020 Creating filesystem with 7494656 4k blocks and 1875968 inodes
Filesystem UUID: 5e573dd5-af93-4ff4-875e-2426ad476853
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Allocating group tables: 0/229 done
Writing inode tables: 0/229 done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: 0/229 done

Wed Jan 1 00:01:17 2020 From a root partition of /dev/osmcroot, I have deduced a base device of /dev/osmcroo
Wed Jan 1 00:01:17 2020 Mounting root
Wed Jan 1 00:01:17 2020 Trying to mount to MNT_ROOT (/mnt/root)
Wed Jan 1 00:01:17 2020 Using device->root: /dev/osmcroot
Wed Jan 1 00:01:17 2020 Extracting files to root filesystem
Wed Jan 1 00:01:17 2020 Starting extract process …
Wed Jan 1 00:01:17 2020 Extracting from /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:01:37 2020 Halting Install. Error message was: tar: corrupted data
Wed Jan 1 00:01:38 2020 Extraction of root filesystem completed
Wed Jan 1 00:01:38 2020 Configuring bootloader
Wed Jan 1 00:01:38 2020 Boot changed. Re-mounting the real /boot
Wed Jan 1 00:01:38 2020 Trying to unmount MNT_BOOT (/mnt/boot)
Wed Jan 1 00:01:38 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:01:38 2020 Using device->boot: /dev/sda1 and FS: fat32
Wed Jan 1 00:01:38 2020 Configuring bootloader: moving /boot to appropriate boot partition
Wed Jan 1 00:01:38 2020 Vero V family: bootloader to be flashed is u-boot.bin.sd.bin.device.signed
Wed Jan 1 00:01:38 2020 Configuring boot cmdline
Wed Jan 1 00:01:38 2020 Configuring /etc/fstab
Wed Jan 1 00:01:38 2020 Successful installation. Dumping log and rebooting system

Used the windows osmc-installer to download to 2 images, also downloaded the 2 images and used option the use the local build, so all 4 ways give the same error.

Used both USB ports, also tried balena etcher to write image to usb, tried 3 different usd drives.
Sooo…i am out of options on my side…HELPPPPP :rofl:

Can you give me the checksums of the images you downloaded?

Sam

Both match as far as i can see…

rozz@uPower:~/Downloads$ md5sum OSMC_TGT_vero5_20250303.img.gz
b9d01f9fe8da82c0dfc39bb49cf29c5e OSMC_TGT_vero5_20250303.img.gz

rozz@uPower:~/Downloads$ md5sum OSMC_TGT_vero5_20241104.img.gz
7fd501da3075ce0a49a8889c087df907 OSMC_TGT_vero5_20241104.img.gz

UPDATE:
Using the Linux usb installer also gives the same error.

UPDATE 2:
Also tried the 2024.08-1, same error.

@sam_nazarko I have created a support ticket, or do you have anything more i could test or try?
I updated my other Vero 4k without any problems, so nearly 100% sure the problem lies with my Vero V and not any kind of image/install usb.

How many USB devices have you tried?
Have you tried an SD-card?

Thanks for the reminder @JimKnopf, i tried it just now and the installs goes through OK!!!

Stupid i did not think of that myself.
Setting it all up as we speak.

This thread can be “closed”

2 Likes