KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2437 blocks

[clgrissom3]

Block by Buransla!    That would be his 8th Kano block and our 2nd of the day.

[CryptoBuddha]

At last one more green. Has been solved while I was typing smth like "omg now I hate everything red"))

[edonkey]

Still can't get the frakking SD card to load/work...oh, well. Gonna continue putzing with it today. Could be it's a bad card (old) or a crappy reader (also old). Could be, too, that I don't know what the frak I'm doing. 

At this point all you're trying to do is copy from a disk image to an SD card, then boot that in an RPi, right? What OS are you using to do the copy?

I'm on a Mac and use the "dd" command line tool. Works great.

Someone else posted a link to using dd for Linux. Here's one for Mac OS X that works well (there are many like this online):

https://www.raspberrypi.org/documentation/installation/installing-images/mac.md

The section called "COMMAND LINE" is the one to use, if you're not afraid of the terminal app.

[firetreeactual]

Still can't get the frakking SD card to load/work...oh, well. Gonna continue putzing with it today. Could be it's a bad card (old) or a crappy reader (also old). Could be, too, that I don't know what the frak I'm doing. 

At this point all you're trying to do is copy from a disk image to an SD card, then boot that in an RPi, right? What OS are you using to do the copy?

I'm on a Mac and use the "dd" command line tool. Works great.

Someone else posted a link to using dd for Linux. Here's one for Mac OS X that works well (there are many like this online):

https://www.raspberrypi.org/documentation/installation/installing-images/mac.md

The section called "COMMAND LINE" is the one to use, if you're not afraid of the terminal app.

Thanks a bunch...I've got all the resources OK. The issue is permissions and the chip being repeatedly reset to read-only on its own (and no, it's not the slide tab). I've done a chown and other tweaks, to no avail, and so the dd fails.  I'm also not sure the file I've got is actually correct, as I kept getting 404 errors on the Canaan site trying to download (they seem to be doing a lot of updating...some things aren't working quite OK yet), and ended up getting it via Github. If y'all have a direct link to the appropriate .img file for the A6, I'd try it. I use Ubuntu 16.04LTS, but also have a Win10 machine available (that I avoid like the plague). I may just give up and try doing it via Windows just to get the chip done...and dd is not just a copy, I believe. The img file has to be processed/written to the chip, and that's where the problem comes in. Onward. I'll shut up until I find out something.

[edonkey]

Still can't get the frakking SD card to load/work...oh, well. Gonna continue putzing with it today. Could be it's a bad card (old) or a crappy reader (also old). Could be, too, that I don't know what the frak I'm doing. 

At this point all you're trying to do is copy from a disk image to an SD card, then boot that in an RPi, right? What OS are you using to do the copy?

I'm on a Mac and use the "dd" command line tool. Works great.

Someone else posted a link to using dd for Linux. Here's one for Mac OS X that works well (there are many like this online):

https://www.raspberrypi.org/documentation/installation/installing-images/mac.md

The section called "COMMAND LINE" is the one to use, if you're not afraid of the terminal app.

Thanks a bunch...I've got all the resources OK. The issue is permissions and the chip being repeatedly reset to read-only on its own (and no, it's not the slide tab). I've done a chown and other tweaks, to no avail, and so the dd fails.  I'm also not sure the file I've got is actually correct, as I kept getting 404 errors on the Canaan site trying to download (they seem to be doing a lot of updating...some things aren't working quite OK yet), and ended up getting it via Github. If y'all have a direct link to the appropriate .img file for the A6, I'd try it. I use Ubuntu 16.04LTS, but also have a Win10 machine available (that I avoid like the plague). I may just give up and try doing it via Windows just to get the chip done...and dd is not just a copy, I believe. The img file has to be processed/written to the chip, and that's where the problem comes in. Onward. I'll shut up until I find out something.

Quick question. You're calling dd as root, or using the sudo command right? You have to be root to write to the SD drive device.

If you want to talk further, please send me a PM. We're OT enough already here...

[sorry2xs]

Still can't get the frakking SD card to load/work...oh, well. Gonna continue putzing with it today. Could be it's a bad card (old) or a crappy reader (also old). Could be, too, that I don't know what the frak I'm doing. 

At this point all you're trying to do is copy from a disk image to an SD card, then boot that in an RPi, right? What OS are you using to do the copy?

I'm on a Mac and use the "dd" command line tool. Works great.

Someone else posted a link to using dd for Linux. Here's one for Mac OS X that works well (there are many like this online):

https://www.raspberrypi.org/documentation/installation/installing-images/mac.md

The section called "COMMAND LINE" is the one to use, if you're not afraid of the terminal app.

Thanks a bunch...I've got all the resources OK. The issue is permissions and the chip being repeatedly reset to read-only on its own (and no, it's not the slide tab). I've done a chown and other tweaks, to no avail, and so the dd fails.  I'm also not sure the file I've got is actually correct, as I kept getting 404 errors on the Canaan site trying to download (they seem to be doing a lot of updating...some things aren't working quite OK yet), and ended up getting it via Github. If y'all have a direct link to the appropriate .img file for the A6, I'd try it. I use Ubuntu 16.04LTS, but also have a Win10 machine available (that I avoid like the plague). I may just give up and try doing it via Windows just to get the chip done...and dd is not just a copy, I believe. The img file has to be processed/written to the chip, and that's where the problem comes in. Onward. I'll shut up until I find out something.

just fyi I had to do multiple down loads and kill all browser accelerators before I got a clean uncorrupted img. from cannan

[beltsniffer]

Still can't get the frakking SD card to load/work...oh, well. Gonna continue putzing with it today. Could be it's a bad card (old) or a crappy reader (also old). Could be, too, that I don't know what the frak I'm doing. 

At this point all you're trying to do is copy from a disk image to an SD card, then boot that in an RPi, right? What OS are you using to do the copy?

I'm on a Mac and use the "dd" command line tool. Works great.

Someone else posted a link to using dd for Linux. Here's one for Mac OS X that works well (there are many like this online):

https://www.raspberrypi.org/documentation/installation/installing-images/mac.md

The section called "COMMAND LINE" is the one to use, if you're not afraid of the terminal app.

Thanks a bunch...I've got all the resources OK. The issue is permissions and the chip being repeatedly reset to read-only on its own (and no, it's not the slide tab). I've done a chown and other tweaks, to no avail, and so the dd fails.  I'm also not sure the file I've got is actually correct, as I kept getting 404 errors on the Canaan site trying to download (they seem to be doing a lot of updating...some things aren't working quite OK yet), and ended up getting it via Github. If y'all have a direct link to the appropriate .img file for the A6, I'd try it. I use Ubuntu 16.04LTS, but also have a Win10 machine available (that I avoid like the plague). I may just give up and try doing it via Windows just to get the chip done...and dd is not just a copy, I believe. The img file has to be processed/written to the chip, and that's where the problem comes in. Onward. I'll shut up until I find out something.

It could just be a corrupt SD. Have you tried moving a different largish file to the SD to test it?

[wolfen]

Have two unspent outputs from june that are not showing up in the keepkey balance.
About 1.3 BTC total. Opened ticket with keepkey support.
4th and 5th transaction ever in the keepkey on june 6 are not showing up in keepkey total balance.
I sent them the debug log and they are looking at it. BTC not gone, just inaccessible for now.

[firetreeactual]

Timeout, guyz. This has to be a bad card. No matter what utility I use in whatever OS, this card always shows write protected. Could be the reader, though. Gonna go into town tomorrow and get a new, fresh (empty) chip and an external reader.

[kano]

... and make sure it's a Class 10 (or better) SD card

[VRobb]

Nice one, kano-san, both helpful and in haiku!

and make sure it's a
Class 10 (or better) SD
card (emoticon)

 

[firetreeactual]

OK, youz guyz...

It won't be tomorrow...got yet another housing inspection tomorrow, so I get to sit here and wait for inspectors that most often never show up. Clean, new card and known good reader, using BlockC image, = (probably) good image and load. Looks like Saturday instead. You guyz are sweet. 

[kano]

Gonna do one of those, lately, rare events ...

CKDB restart in about 40 mins i.e. around 08:20 UTC
No miners will be affected of course.

Web site and API will show lotsa '?' for about 10mins (or less hopefully)
This is mainly a performance update and a few minor changes here and there behind the scenes.
The performance change wont make anything look faster, but simply increase the limits of CKDB, which are currently about 5 times what it is running at the moment, and with the change should be around 20 times.
It should make the CKDB restart faster also, but I'll see when I do it

CKDB restart complete.
Was from 08:22:21 to 08:32:30 - just over 10mins - so all good.

[fuzion1]

Block!!!!!! Yessss

[wolfen]

Looks like the latest firmware for s9 is July 13, is that correct?
I have two other dates for s9 firmware installed
July 5
June 24
Has anyone tried the July 13 version? I hate to change things that are working.

[AriesIV10]

block by kremit!  The start of a Block Friday!

[kano]

Gonna do one of those, lately, rare events ...

CKDB restart in about 40 mins i.e. around 08:20 UTC
No miners will be affected of course.

Web site and API will show lotsa '?' for about 10mins (or less hopefully)
This is mainly a performance update and a few minor changes here and there behind the scenes.
The performance change wont make anything look faster, but simply increase the limits of CKDB, which are currently about 5 times what it is running at the moment, and with the change should be around 20 times.
It should make the CKDB restart faster also, but I'll see when I do it

CKDB restart complete.
Was from 08:22:21 to 08:32:30 - just over 10mins - so all good.

Gonna do another CKDB restart, my lock detection code found a mistake in the new code
(searching for a user record without holding the lock)
and although it wont cause any problems under anything but extremely unlikely circumstances, I'd prefer to restart with the fix.

This will be in roughly 30 minutes at about 13:45 UTC

Of course this has nothing to do with the fact we found 2 blocks not long after the last restart

Web site and API will show lotsa '?' for about 10mins
No miners will be affected.

[kano]

CKDB restart completed ... eventually
Was from 13:45 but had problems there for 45 minutes until 14:30

No miners were affected.

'That' common large failover happened during the restart, which wasn't expected since they know when I do restarts ...
CKDB consumed all the resources it could, but wasn't able to complete the reload due to not getting enough.
Stopping the web server gave it the necessary resources and now it's finally back and all OK again.

Looks like that's decided what I have to do next.
The main one will mean a memory reduction - that obviously would have helped this time.
That's what I'll be working on next.

[clgrissom3]

CKDB restart completed ... eventually
Was from 13:45 but had problems there for 45 minutes until 14:30

No miners were affected.

'That' common large failover happened during the restart, which wasn't expected since they know when I do restarts ...
CKDB consumed all the resources it could, but wasn't able to complete the reload due to not getting enough.
Stopping the web server gave it the necessary resources and now it's finally back and all OK again.

Looks like that's decided what I have to do next.
The main one will mean a memory reduction - that obviously would have helped this time.
That's what I'll be working on next.

Thanks for keep us up to date on things...it's quite refreshing to not be kept in the dark! 

[VRobb]

All right, Blocks, quit screwing around...   

You know you want to be claimed by the best pool out there, so don't be coy, c'mon down!

Time to start the Block Party Weekend already!!!