Jump to content


Photo

HD51 GSOD after flashing


  • Please log in to reply
22 replies to this topic

#1 Dream1975

  • Senior Member
  • 1,586 posts

+14
Neutral

Posted 6 May 2018 - 14:33

About a week ago I traded one of my HD2400's against a HD51 (someone I knew needed more than 2 tuners while I didn't but would like to be able to watch UHD, so good trade)

 

When I got the HD51 it had another image installed (don't know which as I flashed it immediately with OpenPLi)

 

When I flash it sometimes after startup it gives a GSOD (then when I pull the plug and it reboots no problem anymore untill the next reflash).

 

I found the following peculiar entries in the log (also enclosed)

 

<2>[  179.274814] EXT4-fs error (device mmcblk0p3): ext4_mb_generate_buddy:758: group 64, block bitmap and bg descriptor inconsistent: 8192 vs 4112 free clusters
<4>[  179.308718] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p3, blocknr = 1). There's a risk of filesystem corruption in case of system crash.
<2>[  196.270400] EXT4-fs error (device mmcblk0p3): ext4_mb_generate_buddy:758: group 48, block bitmap and bg descriptor inconsistent: 8192 vs 4112 free clusters
<2>[  196.284480] EXT4-fs error (device mmcblk0p3): ext4_mb_generate_buddy:758: group 49, block bitmap and bg descriptor inconsistent: 8192 vs 7934 free clusters
<4>[  196.439351] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p3, blocknr = 1). There's a risk of filesystem corruption in case of system crash.
<4>[  196.455121] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p3, blocknr = 1). There's a risk of filesystem corruption in case of system crash.

 

 

I already did install the latest bootloader (it had the old one) and off course a complete flash, but this message remains.
 
what is storage mmcblk0p3 (as it wasn't reset with the bootloader or image flash) and how can I solve the dirty metadata buffer?

Attached Files


Mutant HD2400, OpenPLi RC, 2x DVB-C & 2x DVB-S

Mutant HD51, OpenPLi RC, 1x DVB-C & 1x DVB-S

Wavefrontier T55 (Astra 1,2,3 en HB)

Smartcards Ziggo (Irdeto) and CDS (Seca) on Oscam

 


Re: HD51 GSOD after flashing #2 WanWizard

  • Forum Moderator
    PLi® Core member
  • 39,831 posts

+616
Excellent

Posted 6 May 2018 - 14:36

It is your rootfs:

kernelcmdline=root=/dev/mmcblk0p3 rw rootwait hd51_4.boxmode=1 brcm_cma=440M@328M brcm_cma=192M@768M console=ttyS0,115200

Many answers to your question can be found in our new and improved wiki.

Currently in active use: HD2400 (4xS2)VU+Duo2 (3xS2)VU+Zero, Edision OS mini+, ET10000 (4xS2)

For testing purposes: XP1000Formuler F1 (2xS2)Miraclebox Premium Micro (S2+C/T),  ET7500 (S2)ET8500 (S2), Zgemma H2.H (S2+C)Zgemma H5.2TC (S2+C/T), SAB TripleAlpha (S2+C/T), Galaxy 4K (FBC), VU Zero 4K, Edision OS nino 


Re: HD51 GSOD after flashing #3 Dream1975

  • Senior Member
  • 1,586 posts

+14
Neutral

Posted 6 May 2018 - 14:40

What is rootfs exactly, and can it be fixed (for example with some kind of chkdisk command or something)?


Edited by Dream1975, 6 May 2018 - 14:40.

Mutant HD2400, OpenPLi RC, 2x DVB-C & 2x DVB-S

Mutant HD51, OpenPLi RC, 1x DVB-C & 1x DVB-S

Wavefrontier T55 (Astra 1,2,3 en HB)

Smartcards Ziggo (Irdeto) and CDS (Seca) on Oscam

 


Re: HD51 GSOD after flashing #4 WanWizard

  • Forum Moderator
    PLi® Core member
  • 39,831 posts

+616
Excellent

Posted 6 May 2018 - 14:47

rootfs is the root filesystem, the filesystem mounted on /.

 

If it is ext4, you should be able to check it. However, as you say it happens after every flash, many something else is going on, perhaps related to the multiboot capability of the box.

 

Perhaps someone with such a box can comment?


Many answers to your question can be found in our new and improved wiki.

Currently in active use: HD2400 (4xS2)VU+Duo2 (3xS2)VU+Zero, Edision OS mini+, ET10000 (4xS2)

For testing purposes: XP1000Formuler F1 (2xS2)Miraclebox Premium Micro (S2+C/T),  ET7500 (S2)ET8500 (S2), Zgemma H2.H (S2+C)Zgemma H5.2TC (S2+C/T), SAB TripleAlpha (S2+C/T), Galaxy 4K (FBC), VU Zero 4K, Edision OS nino 


Re: HD51 GSOD after flashing #5 Dream1975

  • Senior Member
  • 1,586 posts

+14
Neutral

Posted 6 May 2018 - 14:53

I read on the internet fsck is the utility to check, but when I type fsck in the command line i get "-sh: fsck: not found"

 

So it's probably not in the image. If someone can give me some pointers (my Linux knowledge is very basic) that would be very helpfull


Mutant HD2400, OpenPLi RC, 2x DVB-C & 2x DVB-S

Mutant HD51, OpenPLi RC, 1x DVB-C & 1x DVB-S

Wavefrontier T55 (Astra 1,2,3 en HB)

Smartcards Ziggo (Irdeto) and CDS (Seca) on Oscam

 


Re: HD51 GSOD after flashing #6 twol

  • Senior Member
  • 134 posts

+2
Neutral

Posted 6 May 2018 - 15:01

On a usb flash of the HD51, I have always found that the Emmc partitions are rebuilt, removing any previous images.
The Emmc should be initialised on a clean usb flash with a boot partition and 4 kernel & root partition pairs (plus swap with some other images) - so usually 9 partitions on the Emmc.

Re: HD51 GSOD after flashing #7 Dream1975

  • Senior Member
  • 1,586 posts

+14
Neutral

Posted 6 May 2018 - 15:04

I did flash several times the last days using the usb image (not the multiboot one as I only use one image). But this error remains consistently present


Mutant HD2400, OpenPLi RC, 2x DVB-C & 2x DVB-S

Mutant HD51, OpenPLi RC, 1x DVB-C & 1x DVB-S

Wavefrontier T55 (Astra 1,2,3 en HB)

Smartcards Ziggo (Irdeto) and CDS (Seca) on Oscam

 


Re: HD51 GSOD after flashing #8 betacentauri

  • PLi® Core member
  • 3,981 posts

+198
Excellent

Posted 6 May 2018 - 15:04

It’s not easy to explain and it happens because of the way the image is build (the image which can be flashed via USB stick! Not the multiboot image).
In short the build server creates an ext4 filesystem image (a file which contains a filesystem). Afterwards this image file is cut at the end. This cutting deletes some filesystem informations (eg superblock copies). That’s why the error is shown.
A filesystem check isn’t easy to execute as the root filesystem has to be unmounted before the check. It’s possible to unmount a root filesystem, but it’s very difficult and you need extra hardware.
But you can either install a second PLi image in another multiboot slot and use this (flashing via ofgwrite don’t corrupts the filesystem) or install what ever image in slot 2 and do a filesystem check of the first root filesystem when the 2. image is running.
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: HD51 GSOD after flashing #9 Dream1975

  • Senior Member
  • 1,586 posts

+14
Neutral

Posted 6 May 2018 - 15:21

Ok, so if I understand correctly I can use an image in the second slot and use it to check the filesystem of the first slot (or keep using it as the image in the second slot doesn't have a cut off like the usb image). But when I then would flash an usb image again the error would again show up when using the first slot (because of the cutting of the image file).


Edited by Dream1975, 6 May 2018 - 15:22.

Mutant HD2400, OpenPLi RC, 2x DVB-C & 2x DVB-S

Mutant HD51, OpenPLi RC, 1x DVB-C & 1x DVB-S

Wavefrontier T55 (Astra 1,2,3 en HB)

Smartcards Ziggo (Irdeto) and CDS (Seca) on Oscam

 


Re: HD51 GSOD after flashing #10 WanWizard

  • Forum Moderator
    PLi® Core member
  • 39,831 posts

+616
Excellent

Posted 6 May 2018 - 15:24

Yes.


Many answers to your question can be found in our new and improved wiki.

Currently in active use: HD2400 (4xS2)VU+Duo2 (3xS2)VU+Zero, Edision OS mini+, ET10000 (4xS2)

For testing purposes: XP1000Formuler F1 (2xS2)Miraclebox Premium Micro (S2+C/T),  ET7500 (S2)ET8500 (S2), Zgemma H2.H (S2+C)Zgemma H5.2TC (S2+C/T), SAB TripleAlpha (S2+C/T), Galaxy 4K (FBC), VU Zero 4K, Edision OS nino 


Re: HD51 GSOD after flashing #11 Dream1975

  • Senior Member
  • 1,586 posts

+14
Neutral

Posted 6 May 2018 - 15:45

I understand now, thanks for clearing it up (this is my first receiver with multiboot capabilities, so it is all new to me).

 

I shall read myself a little bit more into multiboot and how it works. Maybe a good idea to also have a wikipage for it.


Edited by Dream1975, 6 May 2018 - 15:47.

Mutant HD2400, OpenPLi RC, 2x DVB-C & 2x DVB-S

Mutant HD51, OpenPLi RC, 1x DVB-C & 1x DVB-S

Wavefrontier T55 (Astra 1,2,3 en HB)

Smartcards Ziggo (Irdeto) and CDS (Seca) on Oscam

 


Re: HD51 GSOD after flashing #12 betacentauri

  • PLi® Core member
  • 3,981 posts

+198
Excellent

Posted 6 May 2018 - 16:04

Not all multiboot capable boxes have this problem. Eg the Gigablue boxes use different mechanism and don’t have this problem.
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: HD51 GSOD after flashing #13 twol

  • Senior Member
  • 134 posts

+2
Neutral

Posted 6 May 2018 - 20:15

Not all multiboot capable boxes have this problem. Eg the Gigablue boxes use different mechanism and don’t have this problem.

..... but to clarify, if he “multiboot“ flashed the 1st slot (which uses ofgwrite), this would clear the problem?

Also, I was surprised recently, as I had to usb flash my gbuhd4k, and the image obviously updated the 1st slot, but left the original images in slots 2 &3 .....

Re: HD51 GSOD after flashing #14 WanWizard

  • Forum Moderator
    PLi® Core member
  • 39,831 posts

+616
Excellent

Posted 6 May 2018 - 20:17

Yes, I would say so.

 

A standard image flash always flashes the first slot.


Many answers to your question can be found in our new and improved wiki.

Currently in active use: HD2400 (4xS2)VU+Duo2 (3xS2)VU+Zero, Edision OS mini+, ET10000 (4xS2)

For testing purposes: XP1000Formuler F1 (2xS2)Miraclebox Premium Micro (S2+C/T),  ET7500 (S2)ET8500 (S2), Zgemma H2.H (S2+C)Zgemma H5.2TC (S2+C/T), SAB TripleAlpha (S2+C/T), Galaxy 4K (FBC), VU Zero 4K, Edision OS nino 


Re: HD51 GSOD after flashing #15 betacentauri

  • PLi® Core member
  • 3,981 posts

+198
Excellent

Posted 6 May 2018 - 22:23

Flashing a multiboot image into first slot don’t fix the problem. Ofgwrite (the used flashing tool) don’t formats a already formatted partition. It deletes all content after stopping (almost) all processes and unpacks the rootfs.tar.bz2 into the empty partition.
Maybe I should consider to format the partition. Or write a little tool which can do the filesystem check (also for the running slot).
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: HD51 GSOD after flashing #16 betacentauri

  • PLi® Core member
  • 3,981 posts

+198
Excellent

Posted 6 May 2018 - 22:28

Ah, yes. As said Gigablue USB flashing mechanism works differently and only overwrites first slot. But it’s also not perfect at the moment. Don’t try to start an image in slot2/3 if no image is installed there! You will get trouble to get the box booting slot 1 again.
@Wanwizard: Unfortunately USB flashing of an hd51, vs1500,... box erases all slots.
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: HD51 GSOD after flashing #17 littlesat

  • PLi® Core member
  • 44,039 posts

+442
Excellent

Posted 7 May 2018 - 06:50

Yes usb flashiing of hd51 etc. Deleted all slots... that is why the flashing of these boxes takes so long... you can also power on/off these boxes to increase that speed,
The user interface of multiboot checks if an enigma2 binary is available in an image and also checks the image name so I expect that you cannot reboot to an empty slot when there is no image inside
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W Thanks to Henksat

Re: HD51 GSOD after flashing #18 twol

  • Senior Member
  • 134 posts

+2
Neutral

Posted 7 May 2018 - 08:18

Flashing a multiboot image into first slot don’t fix the problem. Ofgwrite (the used flashing tool) don’t formats a already formatted partition. It deletes all content after stopping (almost) all processes and unpacks the rootfs.tar.bz2 into the empty partition.
Maybe I should consider to format the partition. Or write a little tool which can do the filesystem check (also for the running slot).

Like the idea of a tool to do a filesystem check, but I guess then if errors you need to re format as well or can the filesystem check also do the repairs?

Edited by twol, 7 May 2018 - 08:18.


Re: HD51 GSOD after flashing #19 pieterg

  • PLi® Core member
  • 32,733 posts

+244
Excellent

Posted 7 May 2018 - 10:20

NOTE: even though you see these messages in dmesg, most likely they are not related to the e2 crash.
Everybody does have these ext3 warnings (because of the reasons explained above) as far as we know they have never caused e2 to crash.

Re: HD51 GSOD after flashing #20 arn354

  • Senior Member
  • 124 posts

+10
Neutral

Posted 7 May 2018 - 10:24

 Don’t try to start an image in slot2/3 if no image is installed there! You will get trouble to get the box booting slot 1 again.
 

 

see attachment

Attached Files


Edited by arn354, 7 May 2018 - 10:25.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users