Re-install error

I am trying to reinstall osmc on my V and get the following error message.

img for root filesystem device /dev/osmcroot
/osmcroot: clean 31722/1875968 files, 30317/749464 blocks
ch_root: can’t execute ‘/sbin/splash_early’ : No such file or directory

If I remove the usb and reboot I get the following error

img for root filesystem device /dev/osmcroot
/osmcroot: recovering journel
/osmcroot: Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set)
/osmcroot: clean, 31749/1075960 files, 302273/7494656 blocks
ch_root: can’t execute ‘/sbin/splash_early’ : No such file or directory

I have tried 2 different usb stick, used the windows installer and the os/s installer, tried different versions of osmc for V and I get the same results each time. Only thing that changes is the block numbers.

Suggestions? Reason to reinstall, I used my 4k backup but could not get my harmony elite to connect even thoug it worked great on my 4k., so I thought it best to start from scratch.

Al

This could be a corrupt download. When prompted to whether to re-download the file you can select Yes.

I assume apart from the Harmony remote the system was otherwise working fine.

Can you show a screenshot of the contents of the USB stick after formatting? You should see the installer come up on the device.

Hi Sam,

  • I redownloaded the image when prompted on both my Windows and Mac
  • It worked fine except for the Harmony
  • see screenshot

I should have also mentioned that that I do get the install screen saying it is copying the files. There is a log file that gets written to the usb but I can’t upload it, I guess only jpg ares allowed. Here is a paste:

Wed Jan 1 00:00:14 2020 Starting OSMC installer
Wed Jan 1 00:00:15 2020 Detecting device we are running on
Wed Jan 1 00:00:15 2020 Mounting boot filesystem
Wed Jan 1 00:00:15 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:15 2020 Using device->boot: /dev/mmcblk1p1 and FS: fat32
Wed Jan 1 00:00:15 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:15 2020 Using device->boot: /dev/sda1 and FS: fat32
Wed Jan 1 00:00:15 2020 Filesystem defined by /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:00:15 2020 No preseed file was found
Wed Jan 1 00:01:18 2020 Creating root partition
Wed Jan 1 00:01:18 2020 Calling fmtpart for partition /dev/osmcroot and fstype ext4
Wed Jan 1 00:01:19 2020 Creating filesystem with 7494656 4k blocks and 1875968 inodes
Filesystem UUID: 37e7b28a-1515-4524-84ff-6d4b0bddee96
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:19 2020 From a root partition of /dev/osmcroot, I have deduced a base device of /dev/osmcroo
Wed Jan 1 00:01:19 2020 Mounting root
Wed Jan 1 00:01:19 2020 Trying to mount to MNT_ROOT (/mnt/root)
Wed Jan 1 00:01:19 2020 Using device->root: /dev/osmcroot
Wed Jan 1 00:01:19 2020 Extracting files to root filesystem
Wed Jan 1 00:01:19 2020 Starting extract process …
Wed Jan 1 00:01:19 2020 Extracting from /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:01:41 2020 Halting Install. Error message was: tar: corrupted data
Wed Jan 1 00:01:41 2020 Extraction of root filesystem completed
Wed Jan 1 00:01:41 2020 Configuring bootloader
Wed Jan 1 00:01:41 2020 Boot changed. Re-mounting the real /boot
Wed Jan 1 00:01:41 2020 Trying to unmount MNT_BOOT (/mnt/boot)
Wed Jan 1 00:01:41 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:01:41 2020 Using device->boot: /dev/sda1 and FS: fat32
Wed Jan 1 00:01:41 2020 Configuring bootloader: moving /boot to appropriate boot partition
Wed Jan 1 00:01:42 2020 Vero V family: bootloader to be flashed is u-boot.bin.sd.bin.device.signed
Wed Jan 1 00:01:42 2020 Configuring boot cmdline
Wed Jan 1 00:01:42 2020 Configuring /etc/fstab
Wed Jan 1 00:01:42 2020 Successful installation. Dumping log and rebooting system

I have removed the Vero V and reconnected my Vero 4k for the time being, hopefully a fix can be found.

Cheers, Al

This means that the installation media is corrupted. As a result, the installation is failing.

Do you have a microSD card at hand?
Otherwise I can provide you with an alternative method to reinstall OSMC using a low level format.

Sam

Sam,

Not really sure how 2 (now 3) different usb sticks and using 2 different operating systems that the usb media is corrupted, however I dug out an old macbook with a sd slot, loaded it and “VOILA”. Gonna have to make note of this for the future. Can’t thank you enough! ! ! !

On to the next adventure.

Cheers, Al

2 Likes

That’s very strange. Did you use something like a USB Hub (common denominator) between the machines?

Glad this is solved. But I’d still like to know a bit more information to work out what’s going on here. If you’re able could you show me a couple of pictures of the USB drives you used? The only ones I know that will definitely cause problems are the old Sandisk Cruzers.

Cheers

Sam

Yeah strange indeed, no hub on either machine, straight into the usb on the pc and usb-c adapter on the Mac.
Again thanks for all the help.

Hahaha, one was a Sandisk Cruzer - 4GB and the other was a Transcend - 8GB and the last one was a nondescript brand (rebrand).

Al

Did you use both drives in the same port on the device, if so, which one (blue or black)?

Also, thanks for this report

Wed Jan 1 00:01:19 2020 Extracting from /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:01:41 2020 Halting Install. Error message was: tar: corrupted data
Wed Jan 1 00:01:41 2020 Extraction of root filesystem completed

The install should’ve halted and not continued. I need to check why it continued. You should’ve been given an error message and it halted. It wouldn’t have left you in any better state, but wouldn’t have given you the illusion that an installation had completed successfully.

The log is very useful, so many thanks.

I used the blue probably 5-6 times and the black only 2.

Al

Thanks for getting back to me promptly.

Odd.

I’m re-imaging via USB all the time here; hence why I found out that old Cruzers are no good.

I am just glad you are up and running now.

In the near future we intend to have a way to reinstall OSMC without any PC or installation media at all.

Sam

Hi Sam,
Hate to be back here but here I am.
Like Paul Cordingley’s threaad (did not want to hijack it) after I got a successful reload with the micro sd I was getting constant video freezing with the audio continuing until I would get the sad face and I would have to unplug the power and reboot. All the saved movies and shows play fine on my 4k+ so I can’t see that as an issue. I disconnected my external usb hdd and just let the Vero V sit and it would still lock up.
I Went to re-install via micro sd (new Kingston) and a new usb drive and now I get the same error in the install log file (see below) as before. Now I can’t install period, every media I try comes up that the data is corrupt. I have tried creating the install on my Windows 11 pc, my Macbook Air and my old Macbook Pro each time saying to download the new image.
I am truly baffled by this and need some help.
Thanks, Al

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 No preseed file was found
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: 8489eb4a-cda8-420b-9b68-d0f4c0589ac5
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:39 2020 Halting Install. Error message was: tar: corrupted data

How is the hard drive powered?

  • The hdd is powered by external power supplied by Seagate, it can not even run without the power.
  • It crashed even when I had the usb drive disconnected.
  • As mentioned above, I can’t install period now either via usb or microsd
    I am mystified as to why I can not reinstall without a tar error. I have downloaded a “new” image each time it asks, on 3 different computers.

Al

I should have mentioned that all these files (and drive) worked flawlessly on my Vero 4k+ and still do when I reconnect it. My main reason of updating to the new V was to get usb 3 and somewhat faster transfer speeds from my pc to the Vero.
My wife is picking me up another new microsd card and usb thumb drive while she is out and about today and will try them once she gets home. The microsd I used was a brand new Kingston and only used once for the last install that worked a few days back. Not I get a corrupt tar file.
Al

Let me know how it goes