I received a new Vero 4k+ this week. On initial power up it failed during boot sequence. I don’t remember all the errors on the screen. The one I do remember was something like " failed to start systemctl status udisks-glue.service"
Today I downloaded and flashed the software again and now the device is crashing every time it boots up into OSMC during the Setup. Attempted to reset power and go through the setup window as quick as possible, but it still crashes even if I get completely through the process.
Unfortunately I didn’t take a picture of the post screen earlier in the week when I first unboxed. The only thing I can show now is a picture of it starting up, then it crashes in the menu to a blank screen on the tv. I was able to quickly setup the device, so I found it on my router. The web interface shows an alert popup on the bottom of the screen, but not long enough for me to grab a screen shot. It mentioned lost web socket or something similar.
Thu Jan 1 00:00:13 2015 Starting OSMC installer
Thu Jan 1 00:00:16 2015 Detecting device we are running on
Thu Jan 1 00:00:16 2015 Mounting boot filesystem
Thu Jan 1 00:00:16 2015 Trying to mount to MNT_BOOT (/mnt/boot)
Thu Jan 1 00:00:16 2015 Using device->boot: /dev/mmcblk1p1 and FS: fat32
Thu Jan 1 00:00:16 2015 Trying to mount to MNT_BOOT (/mnt/boot)
Thu Jan 1 00:00:16 2015 Using device->boot: /dev/sda1 and FS: fat32
Thu Jan 1 00:00:16 2015 No preseed file was found
Thu Jan 1 00:00:16 2015 Flash looks OK
Thu Jan 1 00:01:22 2015 Creating root partition
Thu Jan 1 00:01:23 2015 Calling fmtpart for partition /dev/vero-nand/root and fstype ext4
Thu Jan 1 00:01:26 2015 Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=2 blocks, Stripe width=1024 blocks
930240 inodes, 3716096 blocks
185804 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3808428032
114 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Thu Jan 1 00:01:26 2015 From a root partition of /dev/vero-nand/root, I have deduced a base device of /dev/vero-nand/roo
Thu Jan 1 00:01:26 2015 Mounting root
Thu Jan 1 00:01:26 2015 Trying to mount to MNT_ROOT (/mnt/root)
Thu Jan 1 00:01:26 2015 Using device->root: /dev/vero-nand/root
Thu Jan 1 00:01:26 2015 Extracting files to root filesystem
Thu Jan 1 00:01:26 2015 Starting extract progress…
Thu Jan 1 00:02:23 2015 Extraction of root filesystem completed
Thu Jan 1 00:02:23 2015 Configuring bootloader
Thu Jan 1 00:02:23 2015 Boot changed. Re-mounting the real /boot
Thu Jan 1 00:02:23 2015 Trying to unmount MNT_BOOT (/mnt/boot)
Thu Jan 1 00:02:23 2015 Using device->boot: /dev/sda1
Thu Jan 1 00:02:23 2015 Trying to mount to MNT_BOOT (/mnt/boot)
Thu Jan 1 00:02:23 2015 Using device->boot: /dev/sda1 and FS: fat32
Thu Jan 1 00:02:23 2015 Configuring bootloader: moving /boot to appropriate boot partition
Thu Jan 1 00:02:25 2015 Configuring boot cmdline
Thu Jan 1 00:02:25 2015 Configuring /etc/fstab
Thu Jan 1 00:02:25 2015 Successful installation. Dumping log and rebooting system
Keeping fingers crossed.
It could be just a issue with the display modes or it could be a power supply or worse a HW issue.
But using the december image might give us an idea
The cross is not lit up. It lights up red when power is originally connected then the LED shuts off. Connected via HDMI to AVR.
I thought it might be a video connection issue, but I was able to see the device on the network when powered on, but then it disappears after the display shuts off leading me to believe it is crashing.
Ok, was asking about the LED because if the Vero would shutdown it would lid up red again.
So I assume you say “shuts off” because of the TV going black and reporting no input?
Can you try to directly connect it to the TV for testing purpose?
I may have to wait till the AM so I don’t lose a hand stealing the remote again.
[Can’t reply again for 19hrs… should probably remove that limiter for support, but I will add that I wish I had a spare SD card around because I’d rather attempt that route over USB again.]
