New Vero 5 update/re-install problems

Help and Support Vero V
1

Just got my brand spanking new Vero 5 (thanks Sam for the help). So I connected everything, then connected power. Great! All’s well, so far. After running the welcome setups, it connected to my network fine. Restored my backed up settings from my old Vero4K+. And, finally, it was up and running great. Then I tried to get an update. It downloaded the files, then asked if I wanted to exit kodi, which I answered yes. Then the screen went blank. And stayed blank for a long time. I then connected to the Vero 5 from a desktop via ssh. Ok, did that ok, then reboot. It rebooted, started kodi, then brought up the home screen okay. But after a minute or so, I got the unhappy face. Connected via ssh again, rebooted, then the same thing. Unfortunately, I forgot to save to kodi logs. Sorry.

I decided to try to update manually via apt-get. Ran “apt-get dist-upgrade”, it downloaded files, then started to update. But it failed trying to update the vero-main package. I tried a few things to try to fix that, but still couldn’t get it done.

Next I decided to just re-install osmc. Got the osmc installer, installed on a micro sd, put the card into the vero 5, then power on. After waiting 60 seconds, it started copying files. Very briefy, I saw a message about a tar file being corrupted. It went by too fast for me. But finally I got a series of boot messages, the screen cleared, the finally I got three lines:

Waitiing for root filesystem device /dev/osmcroot
/dev/osmcroot: clean 34106/1875968 files, 356790/7494656 blocks
switch_root: can’t execute ‘/sbin/splash_early’: No such file or directory

Tried this all several times, with different flash drives (micro sd and usb flash) and with different tar files (auto file via osmc, then downloaded the latest from the website). But still the same. So I am giving up for the night.

Any ideas on what to do now?

TIA

ken

2

If a tar file is corrupted, it won’t work. Make sure you get a version that is not broken.
Eventually Sam @ Team will wake up and tell you what to do soon.

3

Did you see the installer come up and actually say reinstalling OSMC?

Sam

4

I see this:

60 wait
new screen: installing files
briefly (I think): install failed corrupted tar
message: Installation complete
new screen: boot messages, too fast to read.
new screen:
Waitiing for root filesystem device /dev/osmcroot
/dev/osmcroot: clean 34106/1875968 files, 356790/7494656 blocks
switch_root: can’t execute ‘/sbin/splash_early’: No such file or directory

Here is the contents of the install.log file from the usb after running the above:

Wed Jan 1 00:00:13 2020 Starting OSMC installer
Wed Jan 1 00:00:14 2020 Detecting device we are running on
Wed Jan 1 00:00:14 2020 Mounting boot filesystem
Wed Jan 1 00:00:14 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:14 2020 Using device->boot: /dev/mmcblk1p1 and FS: fat32
Wed Jan 1 00:00:14 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:14 2020 Using device->boot: /dev/sda1 and FS: fat32
Wed Jan 1 00:00:14 2020 Filesystem defined by /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:00:14 2020 Preseed file found, will attempt to parse
Wed Jan 1 00:00:14 2020 Found a definition for storage: nops
Wed Jan 1 00:01:17 2020 Creating root partition
Wed Jan 1 00:01:17 2020 Calling fmtpart for partition /dev/osmcroot and fstype ext4
Wed Jan 1 00:01:18 2020 Creating filesystem with 7494656 4k blocks and 1875968 inodes
Filesystem UUID: a623ac9c-5065-4427-b01c-77136dcee1ad
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:18 2020 From a root partition of /dev/osmcroot, I have deduced a base device of /dev/osmcroo
Wed Jan 1 00:01:18 2020 Mounting root
Wed Jan 1 00:01:18 2020 Trying to mount to MNT_ROOT (/mnt/root)
Wed Jan 1 00:01:18 2020 Using device->root: /dev/osmcroot
Wed Jan 1 00:01:18 2020 Extracting files to root filesystem
Wed Jan 1 00:01:18 2020 Starting extract process …
Wed Jan 1 00:01:18 2020 Extracting from /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:01:48 2020 Halting Install. Error message was: tar: corrupted data
Wed Jan 1 00:01:48 2020 Extraction of root filesystem completed
Wed Jan 1 00:01:48 2020 Configuring bootloader
Wed Jan 1 00:01:48 2020 Boot changed. Re-mounting the real /boot
Wed Jan 1 00:01:48 2020 Trying to unmount MNT_BOOT (/mnt/boot)
Wed Jan 1 00:01:48 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:01:48 2020 Using device->boot: /dev/sda1 and FS: fat32
Wed Jan 1 00:01:48 2020 Configuring bootloader: moving /boot to appropriate boot partition
Wed Jan 1 00:01:49 2020 Vero V family: bootloader to be flashed is u-boot.bin.sd.bin.device.signed
Wed Jan 1 00:01:49 2020 Configuring boot cmdline
Wed Jan 1 00:01:49 2020 Configuring /etc/fstab
Wed Jan 1 00:01:49 2020 Successful installation. Dumping log and rebooting system

The file name on the download page is: 2023.08.-1, although the actual file downloaded was OSMC_TGT_vero5_20230907.img.gz . The md5 listed on the download page did match the md5sum of the downloaded file.

ken

5

If the install shows a corrupted tarball I would try another USB or SD card.

Sam

1 Like
7

I have tried several, both sd and usb. Always the same.

I did look at the files on the usb drive after I ran osmcinstaller. The file system tarball opened fine. And, as I mentioned, the md5 sum from the disk image was correct.

Is it possible that both the usb port and the sd card slot are bad? Or maybe bad memory?

Just thinking.

ken

9

It could be problematic memory and that would be my hunch if you still have issues.

Just as a quick test: can you try the power supply from the Vero 4K + which you know to work well instead? You’ll obviously have to repeat the install

Sam

10

No luck. I tried several power supplies. Same thing.

ken

11

Okay. Finally success, although I am not sure why.

I first the entire install, starting with osmcinstaller on my usb (which I know is good), then inserted it into my Vero 5. Same result as before. Corrupted tar file.

So this time, I did the osmcinstaller as before. But then, before putting the usb into the vero 5, I mounted, the usb on my desktop, copied the filesystem.tar.xz to the desktop, then copied the tar file back onto the usb drive. I shouild mention that before that, I was able to open the tar file, on the usb drive, and open some of its contents with no problems. So apparently it isn’t obviously corrupted.

After overwriting the tar file on the usb drive, I ran through the install process in the vero 5. And it worked. I ran all through the initial config, changed the network setup, added my mysql connections, and kodi was running with no problems. I did have to connect to it via ssh to add nfs mounts into fstab. But, so far, so good.

Maybe someone else has any ideas why this process worked. I’ve got a working system for now, and am very :smiley:.

Thanks Sam for all of your help, and also a great product.

ken

12

That’s… very… weird.

Do you have some kind of antivirus software that might be doing something?

Or maybe something is occupying the mount and it can’t be written out fully (some caching) so that it seems fine on PC but the file on the mass media storage isn’t fully synced yet.