Bitcoin Forum
July 16, 2024, 03:59:20 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Volt modded Blades suddenly died?  (Read 561 times)
dyland (OP)
Full Member
***
Offline Offline

Activity: 238
Merit: 100

We must become the pitiless censors of ourselves.


View Profile
June 14, 2014, 03:46:26 AM
 #1

I hope they haven't...maybe someone with some expertise can help me out.

*edit--lights are flashing on the units, but hashra blade controla does not seem to recognize any units. I get "NaN" for the hashrates, and "loading" for the rejects.

Hi All:

I have a weird problem; been running beautifully and effortlessly for two weeks until tonight with three volt-mod blades on hashra blade controla.

Only thing that I changed tonight was I went from 988 down to 963, and now the blades aren't even getting recognized or anything on controla. I have previously switched around speeds without issue.

This sucks-- I always seem to have some sort of problem crop up when the profitability is high (currently 162% LTC on clever).

Help appreciated.

Here's my history:

Code:
Jun 14 03:17:04 kernel: [    5.313714] usb 1-1.2.4.1: Product: STM32 Virtual COM Port

Jun 14 03:17:04 kernel: [    5.331168] usb 1-1.2.4.1: Manufacturer: STMicroelectronics

Jun 14 03:17:04 kernel: [    5.338497] usb 1-1.2.4.1: SerialNumber: 48D772613137

Jun 14 03:17:04 kernel: [    5.362010] cdc_acm 1-1.2.4.1:1.0: This device cannot do calls on its own. It is not a modem.

Jun 14 03:17:04 kernel: [    5.393721] cdc_acm 1-1.2.4.1:1.0: ttyACM0: USB ACM device

Jun 14 03:17:04 kernel: [    5.497235] cdc_acm 1-1.2.1:1.0: ttyACM1: USB ACM device

Jun 14 03:17:04 kernel: [    5.509254] usb 1-1.2.4.2: new full-speed USB device number 10 using dwc_otg

Jun 14 03:17:04 kernel: [    5.630263] cdc_acm 1-1.2.2:1.0: This device cannot do calls on its own. It is not a modem.

Jun 14 03:17:04 kernel: [    5.643858] usb 1-1.2.4.2: New USB device found, idVendor=0483, idProduct=5740

Jun 14 03:17:04 kernel: [    5.653094] usb 1-1.2.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

Jun 14 03:17:04 kernel: [    5.676079] usb 1-1.2.4.2: Product: STM32 Virtual COM Port

Jun 14 03:17:04 kernel: [    5.689102] usb 1-1.2.4.2: Manufacturer: STMicroelectronics

Jun 14 03:17:04 kernel: [    5.696498] usb 1-1.2.4.2: SerialNumber: 48DD7F6E3135

Jun 14 03:17:04 kernel: [    5.720098] cdc_acm 1-1.2.4.2:1.0: This device cannot do calls on its own. It is not a modem.

Jun 14 03:17:04 kernel: [    5.751768] cdc_acm 1-1.2.4.2:1.0: ttyACM2: USB ACM device

Jun 14 03:17:04 kernel: [    5.869344] usb 1-1.2.4.3: new full-speed USB device number 11 using dwc_otg

Jun 14 03:17:04 kernel: [    5.886114] cdc_acm 1-1.2.2:1.0: ttyACM3: USB ACM device

Jun 14 03:17:04 kernel: [    5.973082] cdc_acm 1-1.2.3:1.0: This device cannot do calls on its own. It is not a modem.

Jun 14 03:17:04 kernel: [    6.002133] usb 1-1.2.4.3: New USB device found, idVendor=0483, idProduct=5740

Jun 14 03:17:04 kernel: [    6.020301] usb 1-1.2.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

Jun 14 03:17:04 kernel: [    6.045302] usb 1-1.2.4.3: Product: STM32 Virtual COM Port

Jun 14 03:17:04 kernel: [    6.061240] usb 1-1.2.4.3: Manufacturer: STMicroelectronics

Jun 14 03:17:04 kernel: [    6.068595] usb 1-1.2.4.3: SerialNumber: 48D4836A3135

Jun 14 03:17:04 kernel: [    6.092820] cdc_acm 1-1.2.4.3:1.0: This device cannot do calls on its own. It is not a modem.

Jun 14 03:17:04 kernel: [    6.127223] cdc_acm 1-1.2.4.3:1.0: ttyACM5: USB ACM device

Jun 14 03:17:04 kernel: [    6.201521] cdc_acm 1-1.2.3:1.0: ttyACM4: USB ACM device

Jun 14 03:17:04 kernel: [    6.380513] usbcore: registered new interface driver cdc_acm

Jun 14 03:17:04 kernel: [    6.530690] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

Jun 14 03:17:04 kernel: [    6.630457] bcm2708-i2s bcm2708-i2s.0: Failed to create debugfs directory

Jun 14 03:17:04 kernel: [   10.744210] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

Jun 14 03:17:04 kernel: [   11.214581] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

Jun 14 03:17:04 kernel: [   16.662520] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Jun 14 03:17:04 kernel: [   19.371551] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup

Jun 14 03:17:04 kernel: [   20.885632] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1

Jun 14 03:17:07 /usr/sbin/cron[2038]: (CRON) INFO (pidfile fd = 3)

Jun 14 03:17:07 /usr/sbin/cron[2039]: (CRON) STARTUP (fork ok)

Jun 14 03:17:07 /usr/sbin/cron[2039]: (CRON) INFO (Running @reboot jobs)

Jun 14 03:17:08 kernel: [   27.286417] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SSFS

Jun 14 03:24:21 ntpdate[1912]: step time server 206.108.0.131 offset 426.715767 sec

Jun 14 03:24:21 ifplugd(eth0)[1588]: Program executed successfully.

Jun 14 03:24:30 ntpd[2241]: ntpd 4.2.6p5@1.2349-o Fri May 18 20:30:57 UTC 2012 (1)

Jun 14 03:24:30 ntpd[2242]: proto: precision = 1.000 usec

Jun 14 03:24:30 ntpd[2242]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123

Jun 14 03:24:30 ntpd[2242]: Listen normally on 1 lo 127.0.0.1 UDP 123

Jun 14 03:24:30 ntpd[2242]: Listen normally on 2 eth0 192.168.1.71 UDP 123

Jun 14 03:24:30 ntpd[2242]: peers refreshed

Jun 14 03:24:30 ntpd[2242]: Listening on routing socket on fd #19 for interface updates

Jun 14 03:24:30 ntpd[2242]: restrict: error in address '::' on line 38. Ignoring...

Jun 14 03:24:30 ntpd[2242]: restrict: error in address '::1' on line 42. Ignoring...

Jun 14 03:24:30 ntpd[2242]: format error frequency file /var/lib/ntp/ntp.drift


Blackcoin ~ 10 second transactions (fastest coin) ~ 100% proof of stake (the first) ~ No wasteful mining (most efficient)
Brassguy
Full Member
***
Offline Offline

Activity: 139
Merit: 100


View Profile
June 14, 2014, 05:01:17 AM
 #2

My completely uneducated guess is to reformat and reinstall the hashra controla software... Just based on you changing a setting (causing a write to disk most likely) and a failure immediately after. Sounds like a failed/corrupted write to me.

15xNxXy2PfFv3rz8rnfkV6L7WQiwuYax2K
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!