IceBox boot error - Error in mount_sysroot

[Simon_G]

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

[IanL-S]

No idea what the problem could be.
Error in mount_sysroot: mount_common: Could not mount /flash/SYSTEM
Starting debugging shell for boot step: mount_sysroot... type exit to quit

Is a bit deceptive as the IceBox system files are on the first (small) partition on the SSD. But that does not help in solving the problem.

As you cannot boot the system, the only solution I can think of is to do a reinstallation of IceTV using a USB drive - this is the same process that is used when building a BYOB IceBox - see https://support.icetv.com.au/hc/en-us/articles/6591367595407-IceBox-BYOB-Installation-Links.


WARNING: This process will reformat the SSD so all your recordings will be lost. As you know how to take the SSD out and how to access the recordings, before you do the reinstallation copy the /recordings/ directory to your PC/MAC. Make sure that you include the /.backups/ subdirectory. The backup directory is a hidden directory (indicated by the "." character at the beginning of the name). Once you have reinstalled the operating system (including running the IceTV addon) reboot the system and copy the content of the /recordings/ directory back to the IceBox

[Simon_G]

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

[raymondjpg]

Anyway I managed the job, reassembled the IceBox and plugged it in and it just worked (thankfully).

Well done sorting that out with Daniel Hall. I haven't seen that reported before, and it occurred to me that it might be related to some SSD instability rather than the linux installation. If it happens again, that's where I'd be looking.

[Simon_G]

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.