[FIXED] Avalon URGENT ISSUE: both of my avalon do not work any more

[Bogart]

You might also try the firmware update.

[1715456899]

1715456899

[1715456899]

1715456899

[1715456899]

1715456899

[1715456899]

1715456899

[1715456899]

1715456899

[BCbitcoin]

How about open the case and upload some pictures to see if there's something obvious?

[libertybuck]

You might also try the firmware update.

Ok. I have emailed them for latest firmware.

[Aseras]

Did you change anything? Is there free space?

[cedivad]

Crashed within one second each one another from 2 different locations and also certainly with 2 different running times... Dosent make any freaking sense. How far way where the locations from each other?

Since that its a "modular design" and that you get a bus error, have you tried disconnecting some of the modules and boot with only one or 2 module?

Maybe the pool sent a "share of death" that killed your hardware. How funny would that be? (Sorry for the joke)

[debianlinux]

And the remaining window fro GPU mining got some fraction wider. Good thing I didn't turn off back in October when they told me the sky was falling.

[Jaw3bmasters]

This is what happens when ya forgot to update.....

[goxed]

If I am not mistaken a Bus error is the same as a Segmentation fault.

http://software.intel.com/en-us/articles/determining-root-cause-of-sigsegv-or-sigbus-errors

[nathanrees19]

Code:

 [2013-03-02 04:02:40] New block: 00fb4966084a69b4... diff 18.4E                    
Bus error

18.4E is 18.4 * 10^18. This also happens to be the maximum value of a 64 bit unsigned int. That is not the correct difficulty.

The bus error suggests an attempt to read from memory outside the real range.

Both of these point to some kind of memory corruption issue, which is either a cgminer bug (not very likely) or a bug in the avalon driver (quite likely). (A hardware error on the control board is also possible, but unlikely on two independent devices.)

[Bogart]

Did issue begin when the difficulty recently readjusted, perhaps?

You might try mining on testnet and see if that behaves any differently.

I'm not sure how much a pool hides the network difficulty from a miner.  cgminer somehow seems to always know the network difficulty and display it for me regardless of what pool I use.

[testerx]

Sounds like a software or network issue since it's unlikely that both units would simultaneously have hardware failure.  I'd drag it over to a friends place or something and see if it works on their network, update the firmware, reset it to whatever defaults it has, etc.

[Korbman]

Sounds like a software or network issue since it's unlikely that both units would simultaneously have hardware failure.  I'd drag it over to a friends place or something and see if it works on their network, update the firmware, reset it to whatever defaults it has, etc.

This is my thought as well...near simultaneous failures from the hardware generally (at least in the SysAdmin world) rules out hardware errors (though it's possible). Have any recent updates been applied (intentionally or not), can any other pools be reached, or have any networking changes occurred (not being in China, I don't know how much they'd limit connections for Bitcoin)?

Just some food for thought. I'll think about it for a bit, though I'm sure there are dozens of capable minds in this community that can far surpass mine. I'm curious to see what BitSyncom comes back with.

[foo]

Did issue begin when the difficulty recently readjusted, perhaps?

Bingo! Seems to me that OP's problems started exactly then. If that is the case then jgarzik's Avalon should also have b0rked, unless the new firmware fixed something.

[libertybuck]

Did issue begin when the difficulty recently readjusted, perhaps?

Bingo! Seems to me that OP's problems started exactly then. If that is the case then jgarzik's Avalon should also have b0rked, unless the new firmware fixed something.

I did not adjust anything recently.  For btcguild it is 32. For ozco it is -1 (means dynamic).

[libertybuck]

Did you change anything?

No. I did not change anything. In fact it was quite stable in the past 14 days. Never had issue before.

Is there free space?

Code:

root@OpenWrt:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                     320       224        96  70% /
/dev/root                 2816      2816         0 100% /rom
tmpfs                    30916        88     30828   0% /tmp
tmpfs                      512         0       512   0% /dev
/dev/mtdblock3             320       224        96  70% /overlay
overlayfs:/overlay         320       224        96  70% /

[goxed]

Points more towards a flash memory corruption issue

https://forum.openwrt.org/viewtopic.php?id=11224
https://dev.openwrt.org/ticket/2131
http://larsmichelsen.com/wl-500gp/asus-wl-500g-premium-openwrt-not-booting-failsave-possible/

[foo]

Did issue begin when the difficulty recently readjusted, perhaps?

Bingo! Seems to me that OP's problems started exactly then. If that is the case then jgarzik's Avalon should also have b0rked, unless the new firmware fixed something.

I did not adjust anything recently.  For btcguild it is 32. For ozco it is -1 (means dynamic).

Network difficulty, not share size. The difficulty changed from 3,651,011 to 4,367,876 at 2013-03-01 17:39:09 UTC. Was that when your Avalons stopped?

[rudrigorc2]

anyone knows if its possible to run both conected to only one 703n? its usb and they have usb hub. did u try that?

[libertybuck]

To all gentlemen,

Issue fixed immediately after I upload latest firmware to avalon.   

Thanks avalon team for their prompt supporting.

[Korbman]

To all gentlemen,

Issue fixed immediately after I upload latest firmware to avalon.   

Thanks avalon team for their prompt supporting.

Fantastic!

Thanks for the update, and happy mining