Jump to content


Photo

Update rootfs on Vu+ Solo 4K


  • Please log in to reply
43 replies to this topic

#1 ims

  • PLi® Core member
  • 12,261 posts

+188
Excellent

Posted 20 January 2020 - 12:50

Does exist some solution how repair box, when flash VU box finishing on "Update rootfs" ?


Edited by ims, 20 January 2020 - 12:51.

Kdo nic nedělá, nic nezkazí!

Re: Update rootfs on Vu+ Solo 4K #2 Dimitrij

  • PLi® Core member
  • 7,118 posts

+233
Excellent

Posted 20 January 2020 - 14:45

1)When  receiver is loaded, use ofgwrite.

2)When the inscription appears on the display, the image is found, slightly remove and insert the flash drive back.


Lunix3-4K/VU+solo4k(thanks guys to gisclub.tv)


Re: Update rootfs on Vu+ Solo 4K #3 ims

  • PLi® Core member
  • 12,261 posts

+188
Excellent

Posted 20 January 2020 - 15:06

It is not my machine - I can forward this notes ... But I think, that ad 2) they tried it - no success

and for ad1) - it is not possible connect to box, when it is in "update rootfs"

 


Kdo nic nedělá, nic nezkazí!

Re: Update rootfs on Vu+ Solo 4K #4 Dimitrij

  • PLi® Core member
  • 7,118 posts

+233
Excellent

Posted 20 January 2020 - 15:31

"update rootfs"

This new openPli image?


Lunix3-4K/VU+solo4k(thanks guys to gisclub.tv)


Re: Update rootfs on Vu+ Solo 4K #5 ims

  • PLi® Core member
  • 12,261 posts

+188
Excellent

Posted 20 January 2020 - 15:36

"update rootfs"

This new openPli image?

I must know it what image it is ...  why ?


Edited by ims, 20 January 2020 - 15:38.

Kdo nic nedělá, nic nezkazí!

Re: Update rootfs on Vu+ Solo 4K #6 ims

  • PLi® Core member
  • 12,261 posts

+188
Excellent

Posted 20 January 2020 - 15:45

Btw - could you put here ofgwrite for vu+ solo 4k (it seems, they will need it for manual run from usb) ?

 

 

last info: some old PLi, tried fix it with PLi 7.2 now.


Edited by ims, 20 January 2020 - 15:49.

Kdo nic nedělá, nic nezkazí!

Re: Update rootfs on Vu+ Solo 4K #7 ims

  • PLi® Core member
  • 12,261 posts

+188
Excellent

Posted 20 January 2020 - 16:34

I have limited remote account to box. Tried ofgwrite (from duo4k) with -r -k:

 

Using /dev/mcblk0p1 as kernel device

rootfs (dev/mmcblk0) is on different device than current rootfs(). Maybe wrong device selected. -> Aborting

 

 
 
 

 

 

 
 
 

 


Kdo nic nedělá, nic nezkazí!

Re: Update rootfs on Vu+ Solo 4K #8 ims

  • PLi® Core member
  • 12,261 posts

+188
Excellent

Posted 20 January 2020 - 17:16

This is as fdisk -l

 

 

# fdisk -l

Disk /dev/mtdblock0: 2 MB, 2097152 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 65536 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/mtdblock2: 0 MB, 65536 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock2 doesn't contain a valid partition table

Disk /dev/mtdblock3: 0 MB, 65536 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock3 doesn't contain a valid partition table

Disk /dev/mtdblock4: 4 MB, 4194304 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock4 doesn't contain a valid partition table
Found valid GPT with protective MBR; using GPT

Disk /dev/mmcblk0: 7634944 sectors, 7456K
Logical sector size: 512
Disk identifier (GUID): 9a0b2167-db88-440b-877d-b61f2581ac5c
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7634910

Number  Start (sector)    End (sector)  Size       Code  Name
   1            8192           40959       32768   0700  kernel
   2           40960           73727       32768   0700  initrd
   3           73728           77823        4096   0700  splash
   4           77824         7626751       7372K   0700  rootfs

Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/mmcblk0boot0 doesn't contain a valid partition table

Disk /dev/sda: 1031 MB, 1031798784 bytes
32 heads, 62 sectors/track, 1015 cylinders
Units = cylinders of 1984 * 512 = 1015808 bytes


Kdo nic nedělá, nic nezkazí!

Re: Update rootfs on Vu+ Solo 4K #9 Dimitrij

  • PLi® Core member
  • 7,118 posts

+233
Excellent

Posted 20 January 2020 - 17:47

I must know it what image it is ...  why ?

 

Maybe it's spoiled backup.


Lunix3-4K/VU+solo4k(thanks guys to gisclub.tv)


Re: Update rootfs on Vu+ Solo 4K #10 Dimitrij

  • PLi® Core member
  • 7,118 posts

+233
Excellent

Posted 20 January 2020 - 18:06

ofgwrite arm


Lunix3-4K/VU+solo4k(thanks guys to gisclub.tv)


Re: Update rootfs on Vu+ Solo 4K #11 betacentauri

  • PLi® Core member
  • 6,290 posts

+276
Excellent

Posted 20 January 2020 - 21:02

What is the output of?

cat /proc/cmdline

This should include this:

root=/dev/mmcblk0p4

Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Update rootfs on Vu+ Solo 4K #12 betacentauri

  • PLi® Core member
  • 6,290 posts

+276
Excellent

Posted 20 January 2020 - 21:08

If

root=/dev/mmcblk0p4

is missing, the user has most likely flashed a wrong kernel.

cmdline should look like this:

https://github.com/v..._defconfig#L533

 

If it is present in cmdline, what does "mount" show? And also please post dmesg output.


Edited by betacentauri, 20 January 2020 - 21:09.

Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Update rootfs on Vu+ Solo 4K #13 ims

  • PLi® Core member
  • 12,261 posts

+188
Excellent

Posted 20 January 2020 - 21:51

I will know it tomorrow - it's not my box, never saw this box. I can try it remotely only (from my PC with way: TV<->TV<->telnet).

I must run ofgwrite from usb, because on box it is missing.


Kdo nic nedělá, nic nezkazí!

Re: Update rootfs on Vu+ Solo 4K #14 betacentauri

  • PLi® Core member
  • 6,290 posts

+276
Excellent

Posted 20 January 2020 - 23:59

Maybe some kind of multiboot was installed. Afaik some guys have build something for this box.
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Update rootfs on Vu+ Solo 4K #15 ims

  • PLi® Core member
  • 12,261 posts

+188
Excellent

Posted 21 January 2020 - 07:54

cat /proc/cmdline is empty line.

 

Weird:

# cat /proc/version
Linux version 3.14.28-1.10 (gdhan@Notebook) (gcc version 4.8.4 20141110 (prerelease) (Broadcom stbgcc-4.8-1.2) ) #4 SMP
Wed Feb 8 20:33:57 KST 2017

 

 
 

Edited by ims, 21 January 2020 - 07:57.

Kdo nic nedělá, nic nezkazí!

Re: Update rootfs on Vu+ Solo 4K #16 betacentauri

  • PLi® Core member
  • 6,290 posts

+276
Excellent

Posted 21 January 2020 - 17:29

From your PM I see:

Found mountpoint for rootfs file: /mnt/usb/sda1

The empty cmdline is also not ok and not normal.

Both imply that some kind of multiboot mechanism was installed by the user. I heard that that was available for solo4k, but I never used or really saw it.

 

If the user has detached the USB stick / HDD(/mnt/usb/sda1), he should attach it again. If root is still present on that stick/hdd, box should work properly again.

 

If that's not possible, please post output of "mount". Is the /dev/mmcblk0p4 used for rootfs?

Please don't do it yet. My idea would be to flash a proper kernel (from OpenPLi). The kernel will use /dev/mmcblk0p4 as rootfs. It works if really a rootfs is available on /dev/mmcblk0p4. If not, we might have a bigger problem than before. So better wait and think twice before bricking the box.

But maybe with proper kernel, USB flashing works again....


Edited by betacentauri, 21 January 2020 - 17:29.

Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Update rootfs on Vu+ Solo 4K #17 ims

  • PLi® Core member
  • 12,261 posts

+188
Excellent

Posted 21 January 2020 - 18:26

I'll have the box at home tomorrow afternoon - I will see more.
 


Kdo nic nedělá, nic nezkazí!

Re: Update rootfs on Vu+ Solo 4K #18 Dimitrij

  • PLi® Core member
  • 7,118 posts

+233
Excellent

Posted 21 January 2020 - 18:29

Just unplug all flash drives / disks and the receiver will boot from flash memory, then set the image in a standard way.


Lunix3-4K/VU+solo4k(thanks guys to gisclub.tv)


Re: Update rootfs on Vu+ Solo 4K #19 betacentauri

  • PLi® Core member
  • 6,290 posts

+276
Excellent

Posted 21 January 2020 - 18:40

I think it’s not OpenMultiboot as that uses normal kernels. Here a custom kernel is used as far as I can see.
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Update rootfs on Vu+ Solo 4K #20 ims

  • PLi® Core member
  • 12,261 posts

+188
Excellent

Posted 22 January 2020 - 20:10

@betacentauri - box is home - what all you need to know ?

# mount
rootfs on / type rootfs (rw,size=108460k,nr_inodes=27115)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
none on /dev type devtmpfs (rw,relatime,size=108460k,nr_inodes=27115,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
tmpfs on /tmp type tmpfs (rw,relatime)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime)
/dev/sda1 on /mnt/usb/sda1 type vfat (rw,sync,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

# cat /etc/fstab
/dev/sda1                    /                   auto      defaults         1 1
/dev/sda2                    swap                swap      noauto           0 0
/dev/sda3                    /opt                auto      defaults         1 2
/dev/sda4                    /data               auto      defaults         1 3

 

# ls -l /
drwxrwxr-x    2 root     root          3340 Feb  8  2017 bin
drwxrwxr-x    2 root     root            40 Feb  8  2017 data
drwxr-xr-x    8 root     root         13480 Jan  1 00:00 dev
drwxrwxr-x    5 root     root           560 Feb  8  2017 etc
lrwxrwxrwx    1 root     root            11 Feb  8  2017 init -> bin/busybox
drwxrwxr-x    5 root     root          1120 Feb  8  2017 lib
lrwxrwxrwx    1 root     root            11 Feb  8  2017 linuxrc -> bin/busybox
drwxrwxr-x    6 root     root           120 Feb  8  2017 mnt
drwxrwxr-x    2 root     root            40 Feb  8  2017 opt
dr-xr-xr-x   68 root     root             0 Jan  1 00:00 proc
drwxrwxr-x    2 root     root            40 Feb  8  2017 root
drwxrwxr-x    2 root     root          1080 Feb  8  2017 sbin
dr-xr-xr-x   12 root     root             0 Jan  1 00:00 sys
drwxrwxrwt    2 root     root           100 Jan  1 00:00 tmp
drwxrwxr-x    3 root     root            60 Feb  8  2017 usr
drwxrwxr-x    5 root     root           100 Feb  8  2017 var

# ls -l /mnt
drwxrwxr-x    2 root     root            40 Feb  8  2017 flash
drwxrwxr-x    2 root     root            40 Feb  8  2017 hd
drwxrwxr-x    2 root     root            40 Feb  8  2017 nfs
drwxrwxr-x    3 root     root            60 Jan  1 00:00 usb

usb flash is as sda1

# ls -l /mnt/usb
drwxrwxrwx   19 root     root          4096 Jan  1 00:00 sda1

 

# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                  108460      7464    100996   7% /
none                    108460         0    108460   0% /dev
tmpfs                   118668        12    118656   0% /tmp
shm                     118668         0    118668   0% /dev/shm
/dev/sda1              7892964   2498752   5394212  32% /mnt/usb/sda1

 

 


Kdo nic nedělá, nic nezkazí!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users