Error Message meanings

DaveR · Post by **DaveR** » Sun Mar 02, 2008 10:43

Error Messages and what they mean

I'm compiling a list of the various error messages and what they actually mean, and how to fix what is causing the message. Please feel free to reply with any messages and their meanings etc and I will add them to this first post.

Front Panel Display Messages

Also see 'Booting Error Messages' below

Beyonwiz Onscreen Messages

HDD Not Initialized = HDD appears to be unformatted.
The BW will ask if you want to initialize the HDD. If this is the first time you've turned it on you may not be able to see the question box on the TV screen - Cycle through the A/V output choices by repeatedly 'pressing the TV-Out button and waiting a few seconds' until you get a picture onscreen.

HDD Check Has Failed = HDD has failed a disk check.
The BW will leave the HDD unmounted which may affect accessibility and reliability of other media devices. It will also disable timeshifting and prevent recording.

HDD Temporarily Not Available = HDD has failed to mount.
The BW will try a disk check and later attempt to mount the HDD again. It will also disable timeshifting and prevent recording.

HDD Missing = HDD has failed to be detected.
The BW will leave the HDD unmounted which may affect accessibility and reliability of other media devices. It will also disable timeshifting and prevent recording.

IceTV EPG Messages

Bad IceLink message received from the server = The IceTV Server is not recognising your account details.
This could be because:
- Your Ice username and/or password do not match (try entering them again)
- The IceTV server is playing up (contact IceTV)
- The IceTV server has blacklisted your account (contact IceTV)

Booting Error Messages

------------------- During Normal Booting ----------------

ERROR 0000 = Bootloader failure
Somehow flash is not accessible, bootloader is not loaded, or boot process failed.

E:BOOTING = System image on flash is corrupted
System halted. ( POWEROFF key can recycle power )

ERROR 0001 = System boot failure
Bootloader initiated boot up process but next boot process marking to Micom was not issued by system within 30 sec.

ERROR 0002 = System failure
System crashed loading main application.

ERROR 0003 = System failure
System crashed loading main application. ( stage 2 - in fact, end user will never see this error )

ERROR 0004 = System failure
System crashed while setting up system clock, or loading configuration files

ERROR 0022 = HDD check timed out
Initial HDD checking is initiated and it wasn't completed withing 240 seconds.

------------------- Errors not from Normal Booting ----------------

ERROR 0011 = [ Mass production stage error ]
System board replacement required if this error occurs outside the factory.

ERROR 0012 = [ Mass production stage error ]
System board replacement required if this error occurs outside the factory.

------------------- Errors while performing Firmware Recovery Process -------------------

E:NETWORK = Networking (wired) is not available
Check link status or please confirm that RemoteUpdate.exe app is running, appropriate personal firewall setup is done.

E:DOWNLOAD = Problem downloading firmware image from PC
Please confirm that RemoteUpdate.exe app is running, appropriate personal firewall setup is done.

E:FIRMWARE = Problem with image
Size too big / img header corruption / etc.

E:CHECKSUM = Checksum of firmware package is broken
Please download firmware again, from one of official download sites.

E:SYSTEMID = System ID mismatch
Maybe a firmware for different model.

E:WRITE = Error while writing image to flash ROM
If this error keeps appearing, system board should be replaced. ( maybe flash ROM chip replacement is sufficient. )

E:UNKNOWN = Undefined error
.

doodlebug73 · Post by **doodlebug73** » Thu Mar 13, 2008 20:11

Got a couple more for the list
E: NETWORK
E: CHECKSUM

prl · Post by **prl** » Thu Mar 13, 2008 21:13

doodlebug73 wrote:Got a couple more for the list
E: NETWORK
E: CHECKSUM

What context? E: CHECKSUM is possibly a corrupted firmware download if that's what's happening at the time.

doodlebug73 · Post by **doodlebug73** » Thu Mar 13, 2008 22:37

Redownloaded firmware ran the remote updater again got from WRT 1 to WRT 61/61
thought great its going to work then I get E: WRITE instead of update finished

Any other ideas before i book it in for a tech to look at

Gully · Post by **Gully** » Thu Mar 13, 2008 23:00

Any reason why you are using the Remote Updater?

doodlebug73 · Post by **doodlebug73** » Thu Mar 13, 2008 23:37

continual error messages of E: BOOTING
They recommended do this I Think

DaveR · Post by **DaveR** » Sun Mar 16, 2008 17:24

doodlebug73 wrote:Any other ideas before i book it in for a tech to look at

Sounds like the flash memory is faulty. Are you in Sydney? (or have I already asked you this?)

doodlebug73 · Post by **doodlebug73** » Sun Mar 16, 2008 21:58

No Sorry in SA, North of Adelaide in Gawler
Finally got the firmware update finished but it only said 60 instead of 61
But it still becomes no responsive freezing then back to E: Booting again
Think it will require a tech to inspect

DaveR · Post by **DaveR** » Sun Mar 16, 2008 23:56

doodlebug73 wrote:Think it will require a tech to inspect

Yep. If I was you and I was able to bring it back to life I'd be forever worried that it might go again in the future (now that I'm sure it's hardware related).

janilxx · Post by **janilxx** » Wed May 21, 2008 17:36

While using Remote Updater:
E:DOWNLOAD - maybe because PC's firewall did not allow sending FW file to BW
E:NETWORK - Maybe because PC's firewall was waiting me to use "allow Remote Updater to send data" button and I was too late?
E:SYSTEMID - Wrong sysid in FW file(?)

doodlebug73 · Post by **doodlebug73** » Wed May 21, 2008 22:06

Yes it went back to beyonwiz
Replaced the motherboard i think?
Came back all good
been working fine for little while now put the latest firmware on
Thanks to the techs for a fairly quick repair

prl · Post by **prl** » Tue Sep 28, 2010 10:32

Hi Dave?. Would it be possible to post the flashing front LED error codes that are used by the DP-Lite and Lite i against their corresponding alphanumeric error codes?

For the "ERROR nn" codes that come from the watchdog timers in /etc/rc.sysinit, my DP-Lite i seems to alternate between 4 short flashes, then nn long flashes, repeating until powerdown. Does the older plain DP-Lite use different indications? Are their differences between boot loader versions or the front panel microcontroller firmware versions?

It's easy to test the "ERROR nn" codes on the Lite using the Beyonwiz's micomparam program, but it's not so clear for the other error messages.

It would have been handy to have this information in this discussion.

peteru · Post by **peteru** » Tue Sep 28, 2010 16:15

prl wrote:Are their differences between boot loader versions or the front panel microcontroller firmware versions?

Careful there Peter. The spelling and grammar police will come after you.

madmax · Post by **madmax** » Tue Sep 28, 2010 16:38

peteru wrote:
prl wrote:Are their differences between boot loader versions or the front panel microcontroller firmware versions?
Careful there Peter. The spelling and grammar police will come after you.

Ha! I knew he'd slip up one day......

prl · Post by **prl** » Tue Sep 28, 2010 17:16

madmax wrote:
peteru wrote:
prl wrote:Are their differences between boot loader versions or the front panel microcontroller firmware versions?
Careful there Peter. The spelling and grammar police will come after you.
Ha! I knew he'd slip up one day......

Damn! Struck low by a treacherous homophone!

Gully · Post by **Gully** » Tue Sep 28, 2010 20:22

Well maybe Peter was just trying to acknowledge that different boot loader versions will have their own differences.

prl · Post by **prl** » Tue Oct 05, 2010 12:10

prl wrote:
madmax wrote:
peteru wrote:
prl wrote:Are their differences between boot loader versions or the front panel microcontroller firmware versions?
Careful there Peter. The spelling and grammar police will come after you.
Ha! I knew he'd slip up one day......
Damn! Struck low by a treacherous homophone!

I was most pleased to discover quite accidentally that there's a name for the phenomenon of language pedants being caught out this way

IanSav · Post by **IanSav** » Tue Oct 05, 2010 12:16

Hi Peter,

What is even better is the fact that the name was created by an Australian! (In a Victorian publication.

)

Regards,
Ian.

alfons · Post by **alfons** » Mon Oct 18, 2010 09:38

Can anyone decipher this message for me? It appears in the Wizilla log when I click on a file in the list. When this message appears afte clicking on a file, I cannot delte, move or copy it. Other files in the same list that do not exhibit the message can be deleted, copied or moved.

(Time & Date) - Episode image set - No matching tvlogo '#none.bmp' found

Thanks
Alfons

Gully · Post by **Gully** » Mon Oct 18, 2010 10:29

alfons wrote:Can anyone decipher this message for me? It appears in the Wizilla log when I click on a file in the list. When this message appears afte clicking on a file, I cannot delte, move or copy it. Other files in the same list that do not exhibit the message can be deleted, copied or moved.

(Time & Date) - Episode image set - No matching tvlogo '#none.bmp' found

Thanks
Alfons

This topic is for Wiz error messages. You would be better posting in one of the Wizilla topics.

prl · Post by **prl** » Thu Nov 04, 2010 13:53

prl wrote:
prl wrote:
madmax wrote:
peteru wrote:
prl wrote:Are their differences between boot loader versions or the front panel microcontroller firmware versions?
Careful there Peter. The spelling and grammar police will come after you.
Ha! I knew he'd slip up one day......
Damn! Struck low by a treacherous homophone!
I was most pleased to discover quite accidentally that there's a name for the phenomenon of language pedants being caught out this way

Continuing this rather old thread hijacking, I give you the following orthography curmudgeon's ditty, courtesy of Column 8 in the SMH. Sung to the tune of I've got a Little List, from Gilbert and Sullivan's Mikado, though if you couldn't work that out yourself, you probably don't know the tune anyway

I must say that I do like C8's suggestion of an office of Lord High Punctuator.

SouthPark · Post by **SouthPark** » Fri Jan 27, 2012 22:36

Adding to the list, but unclear about the meaning : seen on dp-p2 - 'Access Error', and 'Temporarily Not Accessible'. Conditions I encountered these particular errors - refer to :
http://www.beyonwiz.com.au/phpbb2/viewtopic.php?t=6952

That just describes the particular conditions where these messages popped up for my case. It doesn't at all mean that these messages are unique to those particular conditions.

prl · Post by **prl** » Sat Jan 28, 2012 10:25

This topic is about Beyonwiz front panel error messages rather than popup errors.

The fact that some of the error popups could be much improved is a long-standing issue. In the beta forum, I've periodically extracted error message strings from the wizdvp app and its error message file and suggested improvements to the clarity, grammar and spelling of error messages. That was an effort initiated by the Beyonwiz engineering team who asked on the beta forum for such improvements, though I'm not sure whether too many of my suggestions have been taken up recently. I'll revisit this if & when the Beyonwiz firmware is in beta again.

As for error messages like "Access Error" and "Temporarily Not Accessible", they could definitely be more informative about the reasons for the errors, but it's hard to make concrete suggestions, because of the lack of knowledge outside Beyonwiz enginnering about the exact circumstances of the error messages.

SouthPark · Post by **SouthPark** » Sat Jan 28, 2012 11:53

prl wrote:This topic is about Beyonwiz front panel error messages rather than popup errors.

The original post clearly has a section that says 'onscreen messages'. Thanks for the rest of the comments though. Appreciated.

prl · Post by **prl** » Sat Jan 28, 2012 12:41

SouthPark wrote:
prl wrote:This topic is about Beyonwiz front panel error messages rather than popup errors.
The original post clearly has a section that says 'onscreen messages'. Thanks for the rest of the comments though. Appreciated.

True, I didn't notice that section. A comprehensive list of the error messages would be quite large, though.

thewally · Post by **thewally** » Tue May 06, 2014 10:04

The first post says:
ERROR 0003 = System failure
System crashed loading main application. ( stage 2 - in fact, end user will never see this error )

So what do i do if I DO see this error?
Occasionally I get it and have to reboot a dozen times till it turns on correctly.
I have upgraded to PSU and HDD, all works well apart from this occasional oddity.

Cheryl · Post by **Cheryl** » Sun Dec 07, 2014 09:18

Hi All, just wondering if anyone can help me, I've a FV-L1 model normally works ok has a few pain in the neck habits but I can live with them. Unfortunately this morning it wouldn't work, flashing on its screen is "E booting". I turned it off then back on, it came up with. "Error 0003" Turned it off again (if in doubt turn it off is my motto). And it's back to E booting! My husband is ready to E boot it out the window, so if anyone can help I'd very much appreciate it. Thanks

prl · Post by **prl** » Sun Dec 07, 2014 09:40

Cheryl wrote:Hi All, just wondering if anyone can help me, I've a FV-L1 model normally works ok has a few pain in the neck habits but I can live with them. Unfortunately this morning it wouldn't work, flashing on its screen is "E booting". I turned it off then back on, it came up with. "Error 0003" Turned it off again (if in doubt turn it off is my motto). And it's back to E booting! My husband is ready to E boot it out the window, so if anyone can help I'd very much appreciate it. Thanks

There's a list of error messages with explanations in the Beyonwiz web pages (in the Guides tab).

Both these errors indicate that the system is failing at a pretty fundamental level - E:Booting indicates that the flash memory where the firmware is stored can't be read, or can't be read properly. Error 3 indicates that the system has started up, but the main application that runs the PVR has crashed early on. The errors page says "This error should never be seen by end users".

The problem could be a failed/failing flash memory, or an indication of a failing power supply (IIRC the flash is quite sensitive to its power going out of spec).

Contact Beyonwiz support, or forum user Warkus (Mark). Warkus has a strong reputation on the board for fixing Beyonwizes (though I've never used his services myself), especially power supplies, quicker and less expensively than Beyonwiz

Cheryl · Post by **Cheryl** » Sun Dec 07, 2014 16:09

Thanks Peter, I left it turned off for a few hours and decided to try it again and it's working, don't know how long for. My husband has a habit of pushing all the buttons on the remote if things don't work quick enough, so I'm assuming he had it confused. Anyway cheers for your reply.
Cheryl

prl · Post by **prl** » Sun Dec 07, 2014 17:50

Cheryl wrote:... My husband has a habit of pushing all the buttons on the remote if things don't work quick enough, so I'm assuming he had it confused. ...

That's very unlikely to be causing those errors.

peteru · Post by **peteru** » Sun Dec 07, 2014 21:09

Get it repaired by either Warkus or Beyonwiz ASAP. The fact that turning it off for a while and then back on made it work again is a sure sign of a failing power supply. Running with a failing power supply for any significant amount of time is almost certain to cause irreparable damage to the unit.

Error Message meanings

Error Message meanings

Message in Wizilla log

Re: Message in Wizilla log

Re: Error Message meanings

Re: Error Message meanings

Re: Error Message meanings

Re: Error Message meanings

Re: Error Message meanings

Re: Error Message meanings

About the Forum

About the Forum

Join us