11 replies to this topic

[smith]

Good morning,

 

I have three Zgemma H9 Combos and this week I've been upgrading them all to Open PLi 8.1, it went well for two of them but the third box would not go into recovery mode or allow for the flash of a recovery unless I disconnected the internal drive. It is strange because one of the other boxes has an identical Samsung 500Gb internal drive and does not exhibit this issue when going through either recovery process.

 

However this particular box is one of the earlier one's and I seem to remember the Open PLi team provided me with a script to get the drive mounted correctly. The main issue was that the drive wouldn't go to sleep, which was explained to me as a box hardware issue, the script was a workaround. Its worked fine ever since, but I vaguely remember the mount didn't look quite right to me.

 

Is there a way of checking what is causing this issue?

 

 

Thanks

[Dimitrij]

enigma2-plugin-extensions-hddsleep as workaround.

[smith]

 

enigma2-plugin-extensions-hddsleep as workaround.

 

 

Yes that does work and the HDD is functioning correctly.

 

My issue is that when I try and force Recovery using Remote button during power on, the box locks up at the splash screen. I then have to open up the box, disconnect the HDD to make it boot into recovery mode. The same thing happens when I try and flash a recovery image, it locks at the splash screen until I disconnect the internal drive.

 

So it looks like it is trying to boot from the internal HDD, can this be inhibited?

 

Thanks.

[Pr2]

How do you format your internal HDD?
Do you format it from within the STB or do you format it on PC before installing it?

[smith]

How do you format your internal HDD?
Do you format it from within the STB or do you format it on PC before installing it?

 

It would have been formatted in an Enigma 2 box, either a Dreambox but more probably an Xtrend 8500. I've read that the mounted drives have flags assigned to determine features like whether the drive is 'removable' and thought there might be a 'bootable' flag that could be set?    

[Pr2]

I just want to be sure that the HDD was formated in extX format and not in NTFS or FAT32.

Some bootloader get stuck when a NTFS drive is attached.

[smith]

I've run dmesg, nothing obvious to me in this section:-

 

mmc0: new HS400 MMC card at address 0001

mmcblk0: mmc0:0001 8GTF4R 7.28 GiB

mmcblk0boot0: mmc0:0001 8GTF4R partition 1 4.00 MiB

mmcblk0boot1: mmc0:0001 8GTF4R partition 2 4.00 MiB

mmcblk0rpmb: mmc0:0001 8GTF4R partition 3 512 KiB

 mmcblk0: p1(fastboot) p2(bootargs) p3(recovery) p4(bootoptions) p5(deviceinfo) p6(baseparam) p7(pqparam) p8(logo) p9(fastplay) p10(kernel) p11(trustedcore) p12(misc) p13(system) p14(vendor) p15(e2tv) p16(cache) p17(private) p18(securestore) p19(linuxkernel1) p20(linuxkernel2) p21(linuxkernel3) p22(linuxkernel4) p23(userdata)

f9820000.himciv200.SD: eMMC/MMC/SD Device NOT detected!

usb 1-2.2: new full-speed USB device number 3 using ehci-platform

usb 1-2.3: new high-speed USB device number 4 using ehci-platform

ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

ata1.00: ATA-8: SAMSUNG HM500JI, 2AC101C4, max UDMA/133

ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)

ata1.00: configured for UDMA/133

scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HM500JI  01C4 PQ: 0 ANSI: 5

sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00

sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

 sda: sda1

sd 0:0:0:0: [sda] Attached SCSI removable disk

 

 

 

 

sda1 also mentioned here:-

 

EXT4-fs (sda1): recovery complete

EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

[Dimitrij]

As option...

Re-install recovery.

[twol]

Why flash recovery image? Why don‘t you just use flashimage to get to 8.1 or whatever

[smith]

Good Morning,

 

Apologies for re-opening this thread again but it is probably the most relevant. I re-flashed my troublesome H9 Combo to v9.0 and again had to disconnect the HDD to get to the recovery menu despite re-installing the recovery last time - is it worth updating to v9.0 Recovery? Anyway after the re-flash and whilst setting up the new image, I normally install the hddsleep plugin but noticed it is no longer in the feed. Is this plugin no longer necessary for this box? I vaguely remember there was something specific to this box relating to the Hisilicon chipset, so has it been fixed in v9.0? I haven't noticed the disk permanently spinning and it does seem to respond to changes in the HDD standby time settings in the HDD setup menu. Running the command confirms it is in standby.

 

root@h9combo:~# hdparm -C /dev/sda

 

/dev/sda:

 drive state is:  standby 

[Dimitrij]

What version of recovery do you currently have?

The recovery has not been updated for 3-4 years(SRCDATE = "20201123").

Edited by Dimitrij, 24 January 2024 - 17:16.

[smith]

What version of recovery do you currently have?

The recovery has not been updated for 3-4 years(SRCDATE = "20201123").

 

It would have been updated when I flashed v8.1 when I had this trouble last time - is there a command to check it? Hopefully I won't need it in future as I've tried that 'Flash Image' selection from the main menu on another box and it worked really well, I'm very impressed. I've had trouble with it in the past hence the need to resort to USB Sticks!