Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Simon_G

#1
I ran a check against the SSD and it came up fine, not sure how that can be. Anyway I suspect that the issue occurred when I was connecting a new smart TV as I was definitely fiddling around behind the IceBox. I wonder if I may have accidentally jiggled the power connection during the process. It seems unlikely but I can't put it down to anything else.
#2
Thanks for taking the time to reply.
I ended up raising a support request direct with IceTV and Daniel Hall has helped me sort this out. Turns out that the SYSTEM file had gotten corrupted somehow, being about 100MB smaller than it should have been. In the end I was able to download the current IceBox image and extract the SYSTEM file from it and copy it onto the drive from the IceBox. Sadly not quite as easy as it sounds, although not difficult if you are familiar enough with the Linux command prompt, which I am not, and are comfortable with pulling your IceBox apart and have the bits necessary to connect it's SSD to a Linux PC or laptop.
Anyway I managed the job, reassembled the IceBox and plugged it in and it just worked (thankfully).
Simon
#3
Getting Help / IceBox boot error - Error in mount_sysroot
November 04, 2025, 12:37:13 PM
A couple of days ago we finally upgraded to a smart TV but upon connecting the IceBox to the new TV it displayed the above message. I can't see how the two events are related but the IceBox is now unusable. I have had the SSD out and have verified that all of my recordings are still there so the issue seems to be confined to the OS only.
The full error message reads -

Error in mount_sysroot: mount_common: Could not mount /flash/SYSTEM
Starting debugging shell for boot step: mount_sysroot... type exit to quit

I plugged in a keyboard and typed exit which led to a whole lot of no file or directory messages. I've attached a photo of the messages. If anyone has any clues as to where to now I would very much appreciate hearing them.

Simon
#4
Thanks for the swift feedback. Glad to know that this issue is not unique to me. Disabling the screensaver sounds like a sensible and simple option.
Cheers,
Simon
#5
It is normal for the display to be dulled if the IceBox is not displaying live TV or is not playing a recording, and it has been idle (ie the remote has not been touched) for a fairly short period of time. Normally pressing a button on the remote wakes the display back up to full brightness. However I have had several instances of late where the display does not recover and in fact I have been able to change channels or play a recording and still not have it wake back up. Most annoyingly this happened mid program this evening when the recorded program that I was watching was paused for a few minutes. The only way I have found to get the thing working properly again is to restart the IceBox which, if you have a recording underway is a pain.
Has anyone else seen this problem or have a cure? This has only been a problem since the most recent update was installed.
#6
General / Re: Recording failures - unwritten extents
December 12, 2023, 02:58:15 PM
Thanks Daniel and IanL-S,
I'll email support as soon as my email is working again. I'm one of the unfortunates who is having their Internode email migrated to another company and email has only been working intermittently now for about the last fortnight, and today is an off day!!
#7
General / Recording failures - unwritten extents
December 10, 2023, 08:44:39 PM
I have a regular timed recording set up on my IceBox which worked fine for a while but now I most often get the error "[sector number] EXT4-fs (sda2): failed to convert unwritten extents to written extents - possible data loss!". At this point the unit stops working until it is restarted, ie press the button on the front of the unit. If it was supposed to be in the middle of a recording when I pick this up it will carry on recording as soon as the unit starts up. The other recordings all seem to be fine.
If anyone has any idea how to fix this I would be very pleased to hear it because at the moment I feel as though I have wasted my money, having bought this unit to replace and ageing and equally unreliable Beyonwiz DP-P2.
#8
Getting Help / Re: Channel scan
June 04, 2023, 05:43:01 PM
Great, thanks. That's done the job and found all of the channels now.
#9
Getting Help / Re: Channel scan
June 03, 2023, 10:17:12 AM
Thanks for the quick reply. What else will need to be set up again after a soft reset?
#10
Getting Help / Channel scan
June 03, 2023, 08:58:40 AM
Hi,
I've just set up a new Icebox but had some trouble with the antenna splitter and after the initial channel scan only ended up with channel 10 and it's subchannels. Having resolved the splitter issues how do I now initiate another channel scan? So far as I can see there does not seem to be an option for this in Kodi.
Thanks.