Bitcoin Forum
May 02, 2024, 03:51:19 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 [178] 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 ... 230 »
  Print  
Author Topic: Official BITMINE CoinCraft series 28nm ASIC miners thread  (Read 565006 times)
stevebrowne
Full Member
***
Offline Offline

Activity: 128
Merit: 100


View Profile
June 02, 2014, 06:35:37 PM
 #3541

I'm hoping it's just another address in the same wallet, and that this is the change balance from the 4 smaller payments. Is there a way to check that?
1714621879
Hero Member
*
Offline Offline

Posts: 1714621879

View Profile Personal Message (Offline)

Ignore
1714621879
Reply with quote  #2

1714621879
Report to moderator
TalkImg was created especially for hosting images on bitcointalk.org: try it next time you want to post an image
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
AC~DC
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
June 02, 2014, 07:37:57 PM
 #3542

Those of you that have been around long enough, can see the writing on the wall!
I'm not a troll never have been, never will. I will always be polite, and use comon sense. I'm too old to be childish in the point to get stated..

Right now, Bitmine is showing the moves of getting as much out as possible, (even if it's not all they are supposed to) before they get hit with a legal hammer. May be close to shutting down and getting a long, long vacation. Guess: are they ahead on $ matters? Oh yes...Moving btc around? uhhhh? Baby I have seen that before...

They are not scamers but a business gone wrong. And trying to salvage for what's up ahead. Their own farm? Better customers? Get out before the fire reaches your knees?  Who knows...
Right now I feel lucky to be able too deal with their technical blunders and find a work around for what I need to do to keep theem going (WARRANTY NON EXISTING) . Not everyone that has the means to do so, I feel for you. Honestly.

Learning costs $, call all this a learning experience and don't preorder !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you all do the same it will let all this wiseasses to develope before you order. Let them sweat it out first like we are doing now.

IF SOMEONE TOLD YOU WILL GET RICH WITH BTC THEN THEY ARE AS CLUELESS AS YOU ARE BUDDY! This is a hobby. Been arround Bitcoin since week 2.

I just hate to be taken for and idiot and rely on this people: Oh yes, we are Swiss and we are better than BFL and everyone else!

@Bitmine.ch

I don't want a refund. I want (modules) you owe me. Stinky 50btc #587. ( no trust anymore) just like you.
AC~DC
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
June 02, 2014, 08:32:35 PM
Last edit: June 29, 2014, 02:49:51 PM by AC~DC
 #3543

ARGHHHHH!

It's shameful but I have to do it for my on sanity. Hopefuly this shows dept of my honesty and character.
There are 2 people in this forum a while back I classified ( as trolls?) and I was wrong to do so.
Someone may learn from this, Including Bitmine.ch. I'm a very sure man and willing to recognize when I make a mistake. It will not deminish me but make me a better person.

I have come to understand that we are are not all the same and express our fellings in different ways. To be direct it was the clown and the guy with half a brain.
Please accept my appologies.

I was too quick to judge and was overtaken by too many negative statements while looking for an answer to my questions at hand. My mentioning you has made it a personal burden I can not carry further so I extend my apologies in public. It does not mean you were right or wrong but means I was wrong to judge you.

All of you I wish you the best and cheer you!
I will sign out as one of them named me...

"The Power Plant"
segaklon
Sr. Member
****
Offline Offline

Activity: 246
Merit: 250


View Profile
June 02, 2014, 09:00:08 PM
Last edit: June 02, 2014, 09:28:48 PM by segaklon
 #3544

Good night fellow,

I have a big problem, my Desk 1 Thash not light, the source seems it has been marred by several aftershocks has given first could not stay in nominal mode, but if a lower power as was undermining has played like a capacitor it had exploded and no longer lit, the machine turns on but does not boot seems to have no power, someone has failed him its mining and you have known the same repair or have to call bitmine and they send you another power supply.


I worth this power supply?

http://www.alternate.es/Chieftec/Navitas-1250W-ATX23/html/product/1111174?tk=7&lk=6782


I appreciate your help

thanks
kapanec
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
June 03, 2014, 08:44:38 AM
 #3545

My story:
I have two orders : 1. 1Th CCD January batch, 2. 600Gh March week 3 batch. Both BTC payments. My first miner was sent in late April and arrived in Sofia, Bulgaria on 30 April. I authorized FedEx to carry out customs formalities for me. It took 16 /! / days. Customs required all my documents for payments that I printed from my Bitmine account and validated them by my signature. Then customs requested invoice from Bitmine because they refused to accept delivery note as valid payment document on which to charge me tax. My request to Bitmine for invoice has no answer yet. The customs agents drew attention to wrongly charged transport costs: real transportation costs were $ 79 but Bitmine had charged  $ 79 for each of my 4 upgrade modules. So I overpaid $ 316. On 13 May I managed to convince customs that I can't oblige a company in another country to give me an invoice, so they adopted a declaration from me that I paid $ 5838. On this amount I paid 20% VAT or $ 7000 total. Finally I got my precious on May 16 and...how frustrating - power cord and PSU did not match: power cord into shipment was C17 standard, PSU was C19 standard. I lost another day to find C19 power cord. Then my miner worked fine almost two weeks before module № 3 to fail. I contacted Bitmine support for RMA but they want to send them all the machine for repair not only the damaged module. This is not acceptable to me because: first, again I will have to arrange customs clearance, and second, repair will take a week and more. I wasted enough time, and now one of the modules. I hope you understand why I'm so upset. But I have an additional reason to be upset: I recommended Bitmine to my friends and they have lost a lot of money there. They asked refund but I doubt they will get their money.


Very sorry to hear about all the problems you had to go through. All the stories we have been hearing paint a not so pretty picture of being an amateur miner, and also of the customer support of Bitmine. Swiss business efficiency is clearly something they boast about but not live up to.

their hardware works like 99%. blaming the company because you made bad business is just stupid. and when everyone could do good business for what would be there people working hard for success? just anyone could do anything. yeah, that would be great.

I would like to say that I was one of the few clients who believed in Bitmine and I was punished for my stupidity. This is my view of the situation and if it sounds like a blame I blame myself.
Collider
Hero Member
*****
Offline Offline

Activity: 714
Merit: 500



View Profile
June 03, 2014, 08:51:13 AM
 #3546

You can get the same for 1700 inkl Vat and shipping from

asic-hardware.com

Hello all

I sell my bitmine DESK 1.1 TH  received 1 week ago (Belgium)
All VAT et taxes already paid...

I sell it for 3000 euro + free shipping
or 6.5 BTC ...


Have a nice day

asic-hardware.com is a big scam Wink
you can buy it from there, no problem Smiley
The only one who is a big scam is you, wanting 3000€ for a 1700€ device.

I can vouch for www.asic-hardware.com
It is the website of cryptx, who run a 1200TH community owned mine.
They are a registered company, operating out of Belgium, Brussels

Public stats are available here: http://peta-mine.co/stats/

This proves that they have the hardware and they have been paying dividends from it since day one.

petamine itself sell their customers hardware instead of mining with it. now the shareholders have to pay a ton of money for the loan taken to buy the new one.

supporting a scam company? no. not even bitmine is making such a bad performance.


They are selling this hardware as they have sourced over 1 Petahash of Bitfury hardware which is 20% more efficient.

Do you really think you are getting a good protection against failure of the unit from bitmine?

All the sold units are in working condition an priced very competitively. Miners nearly never fail if they were once fully functional, unless you decide to put them in a bathtub.
mrpark
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250


View Profile
June 03, 2014, 07:41:24 PM
 #3547

Just so you all are aware, they have listed AMT Miners as their "Authorized distributer" in the USA. After AMT not answering emails for months not telling customers going on, they finally shipped "Something". They distributed something to me alright, a broken miner with different runs of cards in them. The heat sinks were too small and overheated, bad components and even resisters soldered in where compasitors were supposed to be. Some of the heat sinks in a few cards were aluminum, some in other cards were copper (in the same miner). AMT customers have lost thousands, and there is a class action lawsuit already in place. AMT miners (authorized reseller of Bitmine) told me to RMA my broken miner, yet there were no employees at the location for 7 business days and the 1.2T miner came back to me. The hardware was so bad, that the few people that did get them to mine at all (Sometimes 1 or 2 cards), the cards would just die for no reason. Oh, but don't worry, there is a LIFETIME WARRANTY, however, AMT does not answer the door and they move around so how can you RMA them? Even if you did RMA they do not bother to pick up their mail. AMT told their clients they were going to give them options, as in brand new miners, but never made good on that promise either. Not sure how you can trust bitmine when they list AMT as an authorized distributer when they have no distributed anything except boxes of non-working parts.

BTC: 1JDjCGtxtxoZ46XgTqUoXBDxNFKwcsEmik
segaklon
Sr. Member
****
Offline Offline

Activity: 246
Merit: 250


View Profile
June 03, 2014, 08:17:30 PM
 #3548

BITMINE, I HAVE BEEN SPOILED MY MINE, I HAVE SENT AN EMAIL TO YOUR SUPPORT AND DOES NOT RESPOND, WHERE IS YOUR SERIOUS.

RETURN MONEY TO CLIENTS who bet on IT, AND GIVE THE DEAL THAT ARE NOT DESERVE NOTHING WITHOUT U.S..

Respect and dignity is what I ask.
Black_ice666
Newbie
*
Offline Offline

Activity: 54
Merit: 0


View Profile WWW
June 04, 2014, 09:59:38 AM
 #3549

Half a year.... no miners...

Refund: 8 weeks wait or so, and counting....

This is so much butterfly labs or BLF all over again, and i said so already on first delay, in December 2013 !!!

http://i59.tinypic.com/311tk51.png
Black_ice666
Newbie
*
Offline Offline

Activity: 54
Merit: 0


View Profile WWW
June 04, 2014, 10:05:40 AM
 #3550


I guess that every body else then the Petamine deal is in the 5 % ...... face palm to us ;S

this is so LOL

(In a bad way, my tears has dried out, so nothing else to do here then laugh and try to report them for fraud ;S )
Kalfer
Member
**
Offline Offline

Activity: 75
Merit: 10


View Profile
June 04, 2014, 10:35:06 AM
 #3551

I sent the refund form on April 29, and I have not received my money.
Is effective also send a certified letter?
Thanks
enemiesaround
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
June 04, 2014, 10:58:37 AM
 #3552

Kalfer I sent the refund form a month earlier than you. Still waiting. Getting really nervous, especially after MtGox bankruptcy. I feel like i lost enough already.
Kalfer
Member
**
Offline Offline

Activity: 75
Merit: 10


View Profile
June 04, 2014, 11:58:46 AM
 #3553

Kalfer I sent the refund form a month earlier than you. Still waiting. Getting really nervous, especially after MtGox bankruptcy. I feel like i lost enough already.
OMG! Now I'm going to get nervous too.  Angry
trombel
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
June 04, 2014, 02:48:45 PM
 #3554

I am very interest, why bitmine don't sending refund to customer.

I sent refund request 44days ago and still nothing. Support only replied me, what they are limited by number of transaction daily(daily limit? wtf?) and they confirmed me, what I am on refund list.

I am starting be very nervous. Can somebody explain us, why it take too long time?
stevebrowne
Full Member
***
Offline Offline

Activity: 128
Merit: 100


View Profile
June 04, 2014, 03:23:38 PM
 #3555

Because they are acting in an ongoing criminal way.  All of this will be taken into account once the legal hammer hits them.  They are deliberately withholding funds.

I will certainly be doing everything I can to ensure that Giorgio will not have any luck with future businesses. He has been flagged.  Whether he is allowed to leave Switzerland on his up coming vacation to Thailand is yet to be seen. It would be such a shame for him and his wife and 2 kids to be refused onto the plane. In fact no it wouldn't.  He's a criminal, acting in a criminal way. The authorities should treat him like any other fraudster.

Airwhale
Full Member
***
Offline Offline

Activity: 221
Merit: 100


View Profile
June 04, 2014, 06:10:33 PM
 #3556

Spoke to bitmine this morning (their morning,  which was 2am here in west coast USA)  They confirmed that I was still in the refund cue (now about 13 days overdue) but would not tell me my position or give me a time estimate.  I offered to take hardware at market rates instead of my refund... they offered me twice my original order (which is about $3 per ghash,  market rates are *at the most* $2 per ghash at the moment) so I declined.  Maybe I should have just taken my 2/3rds of my investment in hardware and walked away?  But who knows when they would be able to get me the miners if I had agreed.

I see liquidity problems with bitmine,  and I don't see any money coming in their operation.  *I hope* they take the cheap chips coming in and start mining themselves to pay off refunds,  it's the only way I can see them making money. But I doubt they have the technical know-how to do it,  based on the problems they have had with their rig.  I guess my only real recourse is to join one of the lawsuits coming up.  =(  A shame.
kapanec
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
June 05, 2014, 08:24:19 AM
 #3557

Perhaps the delais of USD and EUR payments  due to any bank limits, but is there any reason to postpone rufunds in BTC? "Bank limits" was the mantra of MtGOX before their bankruptcy.
Puppet
Legendary
*
Offline Offline

Activity: 980
Merit: 1040


View Profile
June 05, 2014, 08:33:53 AM
 #3558

"Bank limits" was the mantra of MtGOX

It may well be the same kind of "bank limits": insufficient funds.
Collider
Hero Member
*****
Offline Offline

Activity: 714
Merit: 500



View Profile
June 05, 2014, 09:25:47 AM
 #3559

"Bank limits" was the mantra of MtGOX

It may well be the same kind of "bank limits": insufficient funds.
Cashflow problems don´t mean a company is defaulting.

The problem is that manufacturers have equipment and components and chips that they need to assemble and ship to customers.
They have to use atleast parts of their money to buy all this.

I would give them some time to ship to existing customers, eventually everyone should receive their gear and if they want to their refund.
Wolke
Legendary
*
Offline Offline

Activity: 966
Merit: 1000


View Profile
June 05, 2014, 01:07:27 PM
 #3560

what the hell is this Huh?? i get this on some miner:

Apr 29 06:44:31 raspberrypi user.warn kernel: [1035414.735754] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 06:54:12 raspberrypi user.warn kernel: [1035996.155693] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 06:56:10 raspberrypi user.warn kernel: [1036113.395691] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 06:56:23 raspberrypi user.warn kernel: [1036126.775702] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 06:56:36 raspberrypi user.warn kernel: [1036140.145756] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 06:56:50 raspberrypi user.warn kernel: [1036153.605766] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 06:59:15 raspberrypi user.warn kernel: [1036299.345731] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 06:59:29 raspberrypi user.warn kernel: [1036312.715757] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 06:59:42 raspberrypi user.warn kernel: [1036326.105714] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:06:56 raspberrypi user.warn kernel: [1036759.945756] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:07:09 raspberrypi user.warn kernel: [1036773.335753] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:07:23 raspberrypi user.warn kernel: [1036786.736397] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:07:36 raspberrypi user.warn kernel: [1036800.127491] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:14:10 raspberrypi user.warn kernel: [1037194.215717] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:20:24 raspberrypi user.warn kernel: [1037568.225715] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:22:20 raspberrypi user.warn kernel: [1037683.827071] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:22:33 raspberrypi user.warn kernel: [1037697.195694] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:22:47 raspberrypi user.warn kernel: [1037710.565732] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:23:00 raspberrypi user.warn kernel: [1037723.935684] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:23:13 raspberrypi user.warn kernel: [1037737.355718] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:23:27 raspberrypi user.warn kernel: [1037750.755713] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:30:06 raspberrypi user.warn kernel: [1038150.155722] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:52:28 raspberrypi user.warn kernel: [1039491.865693] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:57:14 raspberrypi user.warn kernel: [1039777.436092] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:57:27 raspberrypi user.warn kernel: [1039790.825726] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:57:40 raspberrypi user.warn kernel: [1039804.275725] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:57:54 raspberrypi user.warn kernel: [1039817.685716] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:58:07 raspberrypi user.warn kernel: [1039831.075758] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:58:21 raspberrypi user.warn kernel: [1039844.445816] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:58:34 raspberrypi user.warn kernel: [1039857.830635] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 07:58:47 raspberrypi user.warn kernel: [1039871.275688] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:03:07 raspberrypi user.warn kernel: [1040131.075791] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:03:21 raspberrypi user.warn kernel: [1040144.505879] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:03:34 raspberrypi user.warn kernel: [1040157.885710] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:05:30 raspberrypi user.warn kernel: [1040274.285692] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:05:44 raspberrypi user.warn kernel: [1040287.685735] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:05:57 raspberrypi user.warn kernel: [1040301.055714] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:09:42 raspberrypi user.warn kernel: [1040525.385738] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:09:55 raspberrypi user.warn kernel: [1040538.755790] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:10:08 raspberrypi user.warn kernel: [1040552.215697] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:10:22 raspberrypi user.warn kernel: [1040565.605781] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:10:35 raspberrypi user.warn kernel: [1040578.988326] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:10:48 raspberrypi user.warn kernel: [1040592.355799] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:11:02 raspberrypi user.warn kernel: [1040605.815902] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:15:04 raspberrypi user.warn kernel: [1040847.485802] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:17:05 raspberrypi user.warn kernel: [1040968.725829] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:17:18 raspberrypi user.warn kernel: [1040982.126684] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:17:32 raspberrypi user.warn kernel: [1040995.565707] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:17:45 raspberrypi user.warn kernel: [1041008.945750] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:21:36 raspberrypi user.warn kernel: [1041240.135718] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:21:49 raspberrypi user.warn kernel: [1041252.725708] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:22:02 raspberrypi user.warn kernel: [1041266.135675] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:33:57 raspberrypi user.warn kernel: [1041980.525741] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:34:10 raspberrypi user.warn kernel: [1041993.923296] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:34:23 raspberrypi user.warn kernel: [1042007.355703] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:34:37 raspberrypi user.warn kernel: [1042020.715765] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:34:50 raspberrypi user.warn kernel: [1042034.095794] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:37:43 raspberrypi user.warn kernel: [1042207.185779] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:37:57 raspberrypi user.warn kernel: [1042220.605810] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:38:10 raspberrypi user.warn kernel: [1042233.985756] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:41:43 raspberrypi user.warn kernel: [1042446.545772] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:43:57 raspberrypi user.warn kernel: [1042580.995695] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:44:11 raspberrypi user.warn kernel: [1042594.425766] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:44:24 raspberrypi user.warn kernel: [1042607.795727] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:44:37 raspberrypi user.warn kernel: [1042621.175756] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:44:51 raspberrypi user.warn kernel: [1042634.625803] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:46:46 raspberrypi user.warn kernel: [1042750.135755] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:47:00 raspberrypi user.warn kernel: [1042763.515721] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:47:13 raspberrypi user.warn kernel: [1042776.955750] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 08:47:26 raspberrypi user.warn kernel: [1042790.335748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:03:04 raspberrypi user.warn kernel: [1043727.635852] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:06:37 raspberrypi user.warn kernel: [1043940.615724] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:11:04 raspberrypi user.warn kernel: [1044208.035736] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:11:18 raspberrypi user.warn kernel: [1044221.415775] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:11:31 raspberrypi user.warn kernel: [1044234.835736] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:11:44 raspberrypi user.warn kernel: [1044248.215691] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:11:58 raspberrypi user.warn kernel: [1044261.575712] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:17:19 raspberrypi user.warn kernel: [1044582.405782] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:17:32 raspberrypi user.warn kernel: [1044595.845680] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:21:43 raspberrypi user.warn kernel: [1044847.095716] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:21:57 raspberrypi user.warn kernel: [1044860.515709] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:22:10 raspberrypi user.warn kernel: [1044873.885741] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:22:23 raspberrypi user.warn kernel: [1044887.275725] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:22:37 raspberrypi user.warn kernel: [1044900.655766] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:22:50 raspberrypi user.warn kernel: [1044914.115746] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:23:04 raspberrypi user.warn kernel: [1044927.495802] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:23:17 raspberrypi user.warn kernel: [1044940.865735] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:28:25 raspberrypi user.warn kernel: [1045248.735791] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:28:38 raspberrypi user.warn kernel: [1045262.145718] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:33:47 raspberrypi user.warn kernel: [1045570.776158] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:35:47 raspberrypi user.warn kernel: [1045691.125729] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:36:31 raspberrypi user.warn kernel: [1045734.535729] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:36:44 raspberrypi user.warn kernel: [1045747.925788] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:36:57 raspberrypi user.warn kernel: [1045761.325734] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:56:01 raspberrypi user.warn kernel: [1046904.505747] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:56:14 raspberrypi user.warn kernel: [1046917.945709] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:56:27 raspberrypi user.warn kernel: [1046931.325730] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 09:56:41 raspberrypi user.warn kernel: [1046944.715757] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:00:06 raspberrypi user.warn kernel: [1047149.385767] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:00:19 raspberrypi user.warn kernel: [1047162.755747] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:00:32 raspberrypi user.warn kernel: [1047176.165772] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:00:46 raspberrypi user.warn kernel: [1047189.555741] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:00:59 raspberrypi user.warn kernel: [1047202.945740] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:01:12 raspberrypi user.warn kernel: [1047216.315761] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:01:26 raspberrypi user.warn kernel: [1047229.735727] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:01:39 raspberrypi user.warn kernel: [1047243.125705] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:01:53 raspberrypi user.warn kernel: [1047256.495701] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:02:06 raspberrypi user.warn kernel: [1047269.885789] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:02:20 raspberrypi user.warn kernel: [1047283.365693] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:06:59 raspberrypi user.warn kernel: [1047562.885798] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:07:12 raspberrypi user.warn kernel: [1047576.255757] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:13:41 raspberrypi user.warn kernel: [1047964.545692] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:28:10 raspberrypi user.warn kernel: [1048834.065753] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:33:23 raspberrypi user.warn kernel: [1049147.095681] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:33:37 raspberrypi user.warn kernel: [1049160.455748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:33:50 raspberrypi user.warn kernel: [1049173.908314] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:34:03 raspberrypi user.warn kernel: [1049187.295796] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:36:36 raspberrypi user.warn kernel: [1049339.505697] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:36:49 raspberrypi user.warn kernel: [1049352.885751] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:37:02 raspberrypi user.warn kernel: [1049366.265724] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:37:16 raspberrypi user.warn kernel: [1049379.645788] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:37:29 raspberrypi user.warn kernel: [1049393.065694] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:37:43 raspberrypi user.warn kernel: [1049406.445722] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:37:56 raspberrypi user.warn kernel: [1049419.825753] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:38:09 raspberrypi user.warn kernel: [1049433.205710] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:38:23 raspberrypi user.warn kernel: [1049446.615690] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:38:36 raspberrypi user.warn kernel: [1049459.995754] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:38:49 raspberrypi user.warn kernel: [1049472.585772] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:39:02 raspberrypi user.warn kernel: [1049485.955748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:49:40 raspberrypi user.warn kernel: [1050123.425756] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 10:49:53 raspberrypi user.warn kernel: [1050136.795775] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:01:05 raspberrypi user.warn kernel: [1050809.035723] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:01:19 raspberrypi user.warn kernel: [1050822.415754] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:01:32 raspberrypi user.warn kernel: [1050835.785748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:15:42 raspberrypi user.warn kernel: [1051685.365753] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:17:43 raspberrypi user.warn kernel: [1051807.095746] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:17:57 raspberrypi user.warn kernel: [1051820.545689] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:18:10 raspberrypi user.warn kernel: [1051833.925724] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:18:23 raspberrypi user.warn kernel: [1051847.305748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:18:37 raspberrypi user.warn kernel: [1051860.685803] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:23:49 raspberrypi user.warn kernel: [1052172.785718] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:24:02 raspberrypi user.warn kernel: [1052186.226314] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:24:16 raspberrypi user.warn kernel: [1052199.605674] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:24:29 raspberrypi user.warn kernel: [1052212.985707] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:24:43 raspberrypi user.warn kernel: [1052226.365800] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:24:55 raspberrypi user.warn kernel: [1052238.965742] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:25:08 raspberrypi user.warn kernel: [1052252.345768] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:25:22 raspberrypi user.warn kernel: [1052265.795855] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:25:35 raspberrypi user.warn kernel: [1052279.166306] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:25:49 raspberrypi user.warn kernel: [1052292.545712] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:26:02 raspberrypi user.warn kernel: [1052305.935717] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:34:14 raspberrypi user.warn kernel: [1052798.275758] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:43:06 raspberrypi user.warn kernel: [1053329.415684] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:43:19 raspberrypi user.warn kernel: [1053342.785757] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:43:32 raspberrypi user.warn kernel: [1053356.195689] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:43:46 raspberrypi user.warn kernel: [1053369.575732] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:43:59 raspberrypi user.warn kernel: [1053382.955749] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:44:12 raspberrypi user.warn kernel: [1053396.345714] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:44:26 raspberrypi user.warn kernel: [1053409.785732] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:44:39 raspberrypi user.warn kernel: [1053423.185808] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:53:51 raspberrypi user.warn kernel: [1053974.485749] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 11:59:41 raspberrypi user.warn kernel: [1054325.145764] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:04:38 raspberrypi user.warn kernel: [1054621.545752] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:04:51 raspberrypi user.warn kernel: [1054634.935797] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:05:04 raspberrypi user.warn kernel: [1054648.352519] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:05:18 raspberrypi user.warn kernel: [1054661.775706] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:05:31 raspberrypi user.warn kernel: [1054675.155748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:05:45 raspberrypi user.warn kernel: [1054688.535737] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:05:58 raspberrypi user.warn kernel: [1054701.915765] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:06:11 raspberrypi user.warn kernel: [1054714.565753] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:06:24 raspberrypi user.warn kernel: [1054727.995739] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:06:37 raspberrypi user.warn kernel: [1054740.585719] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:06:49 raspberrypi user.warn kernel: [1054753.202295] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:07:03 raspberrypi user.warn kernel: [1054766.665690] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:07:16 raspberrypi user.warn kernel: [1054780.045724] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:09:07 raspberrypi user.warn kernel: [1054890.400582] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:09:20 raspberrypi user.warn kernel: [1054903.885678] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:09:33 raspberrypi user.warn kernel: [1054917.275729] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:09:47 raspberrypi user.warn kernel: [1054930.655785] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:10:00 raspberrypi user.warn kernel: [1054944.035775] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:10:14 raspberrypi user.warn kernel: [1054957.465762] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:10:27 raspberrypi user.warn kernel: [1054970.846262] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:21:19 raspberrypi user.warn kernel: [1055622.645803] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:21:32 raspberrypi user.warn kernel: [1055636.015769] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:21:46 raspberrypi user.warn kernel: [1055649.465770] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:21:59 raspberrypi user.warn kernel: [1055662.846285] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:22:12 raspberrypi user.warn kernel: [1055676.215715] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:22:26 raspberrypi user.warn kernel: [1055689.595757] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:25:42 raspberrypi user.warn kernel: [1055885.575788] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:25:55 raspberrypi user.warn kernel: [1055899.045751] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:26:09 raspberrypi user.warn kernel: [1055912.505746] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:26:22 raspberrypi user.warn kernel: [1055925.885737] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:26:35 raspberrypi user.warn kernel: [1055939.275741] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:26:49 raspberrypi user.warn kernel: [1055952.665714] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:27:02 raspberrypi user.warn kernel: [1055966.158564] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:27:16 raspberrypi user.warn kernel: [1055979.525745] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:27:29 raspberrypi user.warn kernel: [1055992.895875] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:27:42 raspberrypi user.warn kernel: [1056006.315740] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:33:56 raspberrypi user.warn kernel: [1056379.795734] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:34:09 raspberrypi user.warn kernel: [1056393.195746] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:38:11 raspberrypi user.warn kernel: [1056635.225698] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:38:25 raspberrypi user.warn kernel: [1056648.595693] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:38:38 raspberrypi user.warn kernel: [1056661.985749] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:38:52 raspberrypi user.warn kernel: [1056675.415681] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:39:05 raspberrypi user.warn kernel: [1056688.795787] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:39:18 raspberrypi user.warn kernel: [1056702.175743] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:39:32 raspberrypi user.warn kernel: [1056715.575756] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:43:01 raspberrypi user.warn kernel: [1056924.675739] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:43:14 raspberrypi user.warn kernel: [1056938.055740] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:43:28 raspberrypi user.warn kernel: [1056951.415816] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:43:41 raspberrypi user.warn kernel: [1056964.815756] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:45:42 raspberrypi user.warn kernel: [1057086.146329] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:45:56 raspberrypi user.warn kernel: [1057099.515785] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:46:09 raspberrypi user.warn kernel: [1057112.935758] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:46:22 raspberrypi user.warn kernel: [1057125.509669] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:48:25 raspberrypi user.warn kernel: [1057248.445745] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:48:38 raspberrypi user.warn kernel: [1057261.825714] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:48:51 raspberrypi user.warn kernel: [1057275.185741] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:49:05 raspberrypi user.warn kernel: [1057288.625711] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:51:07 raspberrypi user.warn kernel: [1057410.745681] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:54:03 raspberrypi user.warn kernel: [1057586.385682] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:54:16 raspberrypi user.warn kernel: [1057599.775759] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:54:29 raspberrypi user.warn kernel: [1057613.225741] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:54:43 raspberrypi user.warn kernel: [1057626.595738] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:54:56 raspberrypi user.warn kernel: [1057639.975713] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:55:09 raspberrypi user.warn kernel: [1057653.338876] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:55:23 raspberrypi user.warn kernel: [1057666.796364] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:55:36 raspberrypi user.warn kernel: [1057680.185713] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 12:55:50 raspberrypi user.warn kernel: [1057693.575682] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:06:01 raspberrypi user.warn kernel: [1058304.975727] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:08:14 raspberrypi user.warn kernel: [1058437.595746] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:08:27 raspberrypi user.warn kernel: [1058450.975724] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:15:26 raspberrypi user.warn kernel: [1058869.475753] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:15:39 raspberrypi user.warn kernel: [1058882.855702] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:17:56 raspberrypi user.warn kernel: [1059020.035680] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:33:31 raspberrypi user.warn kernel: [1059954.435661] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:33:44 raspberrypi user.warn kernel: [1059967.825700] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:33:57 raspberrypi user.warn kernel: [1059981.195774] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:34:11 raspberrypi user.warn kernel: [1059994.645738] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:37:34 raspberrypi user.warn kernel: [1060197.685763] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:37:47 raspberrypi user.warn kernel: [1060211.045675] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:40:02 raspberrypi user.warn kernel: [1060345.445754] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:40:15 raspberrypi user.warn kernel: [1060358.905712] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:40:28 raspberrypi user.warn kernel: [1060372.315730] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:45:37 raspberrypi user.warn kernel: [1060681.115777] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:45:51 raspberrypi user.warn kernel: [1060694.495667] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:46:04 raspberrypi user.warn kernel: [1060707.895800] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:46:17 raspberrypi user.warn kernel: [1060721.317290] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:46:31 raspberrypi user.warn kernel: [1060734.685691] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:46:44 raspberrypi user.warn kernel: [1060748.055684] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:46:58 raspberrypi user.warn kernel: [1060761.465741] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:47:11 raspberrypi user.warn kernel: [1060774.905736] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:47:24 raspberrypi user.warn kernel: [1060788.285721] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:47:38 raspberrypi user.warn kernel: [1060801.685700] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:47:51 raspberrypi user.warn kernel: [1060815.085742] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 13:55:24 raspberrypi user.warn kernel: [1061267.955741] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:07:41 raspberrypi user.warn kernel: [1062004.895817] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:07:54 raspberrypi user.warn kernel: [1062018.295756] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:08:08 raspberrypi user.warn kernel: [1062031.685747] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:11:43 raspberrypi user.warn kernel: [1062246.415724] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:11:56 raspberrypi user.warn kernel: [1062259.795716] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:12:09 raspberrypi user.warn kernel: [1062273.165700] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:12:23 raspberrypi user.warn kernel: [1062286.585724] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:15:07 raspberrypi user.warn kernel: [1062451.105742] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:15:21 raspberrypi user.warn kernel: [1062464.475704] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:15:34 raspberrypi user.warn kernel: [1062477.855788] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:15:47 raspberrypi user.warn kernel: [1062490.445698] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:16:00 raspberrypi user.warn kernel: [1062503.825741] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:16:13 raspberrypi user.warn kernel: [1062517.265718] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:16:27 raspberrypi user.warn kernel: [1062530.625675] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:16:40 raspberrypi user.warn kernel: [1062544.005770] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:16:54 raspberrypi user.warn kernel: [1062557.385728] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:17:07 raspberrypi user.warn kernel: [1062570.815721] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:19:27 raspberrypi user.warn kernel: [1062711.195751] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:19:41 raspberrypi user.warn kernel: [1062724.575792] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:19:54 raspberrypi user.warn kernel: [1062738.015708] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:27:42 raspberrypi user.warn kernel: [1063206.305726] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:34:29 raspberrypi user.warn kernel: [1063612.755683] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:34:42 raspberrypi user.warn kernel: [1063626.155794] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:34:56 raspberrypi user.warn kernel: [1063639.545708] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:35:09 raspberrypi user.warn kernel: [1063652.975771] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:39:53 raspberrypi user.warn kernel: [1063936.515773] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:40:06 raspberrypi user.warn kernel: [1063949.975726] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:40:19 raspberrypi user.warn kernel: [1063963.345750] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:40:33 raspberrypi user.warn kernel: [1063976.725687] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:40:46 raspberrypi user.warn kernel: [1063990.105743] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:41:00 raspberrypi user.warn kernel: [1064003.535689] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:43:13 raspberrypi user.warn kernel: [1064137.015750] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:43:27 raspberrypi user.warn kernel: [1064150.375727] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:43:40 raspberrypi user.warn kernel: [1064163.765763] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:43:53 raspberrypi user.warn kernel: [1064177.155712] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:44:06 raspberrypi user.warn kernel: [1064189.815758] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:44:19 raspberrypi user.warn kernel: [1064203.295738] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:57:17 raspberrypi user.warn kernel: [1064981.027026] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:57:31 raspberrypi user.warn kernel: [1064994.405736] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:57:44 raspberrypi user.warn kernel: [1065007.785735] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 14:59:39 raspberrypi user.warn kernel: [1065123.305733] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:00:15 raspberrypi user.warn kernel: [1065158.825738] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:00:28 raspberrypi user.warn kernel: [1065171.395732] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:00:41 raspberrypi user.warn kernel: [1065184.805764] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:00:54 raspberrypi user.warn kernel: [1065198.185840] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:01:08 raspberrypi user.warn kernel: [1065211.656403] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:01:21 raspberrypi user.warn kernel: [1065225.025698] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:01:35 raspberrypi user.warn kernel: [1065238.385685] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:01:48 raspberrypi user.warn kernel: [1065251.785766] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:02:01 raspberrypi user.warn kernel: [1065265.205704] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:02:15 raspberrypi user.warn kernel: [1065278.585718] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:02:28 raspberrypi user.warn kernel: [1065291.955766] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:03:28 raspberrypi user.warn kernel: [1065352.345754] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:03:42 raspberrypi user.warn kernel: [1065365.735723] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:03:55 raspberrypi user.warn kernel: [1065379.135743] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:04:57 raspberrypi user.warn kernel: [1065440.575741] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:05:10 raspberrypi user.warn kernel: [1065453.975768] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:05:24 raspberrypi user.warn kernel: [1065467.375689] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:11:45 raspberrypi user.warn kernel: [1065849.235735] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:11:59 raspberrypi user.warn kernel: [1065862.626261] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:12:12 raspberrypi user.warn kernel: [1065876.005734] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:12:24 raspberrypi user.warn kernel: [1065887.825695] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:12:37 raspberrypi user.warn kernel: [1065901.285718] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:12:51 raspberrypi user.warn kernel: [1065914.665747] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:13:04 raspberrypi user.warn kernel: [1065928.055682] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:13:18 raspberrypi user.warn kernel: [1065941.425747] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:13:31 raspberrypi user.warn kernel: [1065954.875753] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:13:44 raspberrypi user.warn kernel: [1065968.245709] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:13:58 raspberrypi user.warn kernel: [1065981.615732] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:16:58 raspberrypi user.warn kernel: [1066161.475713] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:17:10 raspberrypi user.warn kernel: [1066174.075747] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:17:24 raspberrypi user.warn kernel: [1066187.455755] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:17:37 raspberrypi user.warn kernel: [1066200.875737] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:17:50 raspberrypi user.warn kernel: [1066213.455696] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:18:03 raspberrypi user.warn kernel: [1066226.845776] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:18:16 raspberrypi user.warn kernel: [1066240.235789] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:18:30 raspberrypi user.warn kernel: [1066253.625747] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:18:42 raspberrypi user.warn kernel: [1066266.225713] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:22:10 raspberrypi user.warn kernel: [1066473.675698] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:22:23 raspberrypi user.warn kernel: [1066487.045777] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:22:37 raspberrypi user.warn kernel: [1066500.425808] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:22:50 raspberrypi user.warn kernel: [1066513.805689] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:23:03 raspberrypi user.warn kernel: [1066527.265725] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:23:17 raspberrypi user.warn kernel: [1066540.655781] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:23:30 raspberrypi user.warn kernel: [1066554.035736] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:28:15 raspberrypi user.warn kernel: [1066838.725693] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:28:28 raspberrypi user.warn kernel: [1066852.155715] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:28:41 raspberrypi user.warn kernel: [1066864.759646] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:28:54 raspberrypi user.warn kernel: [1066878.139830] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:29:08 raspberrypi user.warn kernel: [1066891.535793] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:29:21 raspberrypi user.warn kernel: [1066904.931732] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:29:35 raspberrypi user.warn kernel: [1066918.375759] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:29:48 raspberrypi user.warn kernel: [1066931.745715] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:30:01 raspberrypi user.warn kernel: [1066945.115756] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:30:15 raspberrypi user.warn kernel: [1066958.505762] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:30:28 raspberrypi user.warn kernel: [1066971.955805] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:30:42 raspberrypi user.warn kernel: [1066985.375723] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:30:55 raspberrypi user.warn kernel: [1066998.745712] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:31:08 raspberrypi user.warn kernel: [1067012.145685] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:38:23 raspberrypi user.warn kernel: [1067446.995782] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:43:10 raspberrypi user.warn kernel: [1067733.905733] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:43:23 raspberrypi user.warn kernel: [1067747.275758] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:43:37 raspberrypi user.warn kernel: [1067760.755720] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:47:38 raspberrypi user.warn kernel: [1068002.215769] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:47:52 raspberrypi user.warn kernel: [1068015.605754] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:51:41 raspberrypi user.warn kernel: [1068244.415766] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:51:54 raspberrypi user.warn kernel: [1068257.785734] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:52:07 raspberrypi user.warn kernel: [1068271.155769] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:52:21 raspberrypi user.warn kernel: [1068284.595718] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 15:59:51 raspberrypi user.warn kernel: [1068734.865723] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:05:25 raspberrypi user.warn kernel: [1069068.765766] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:05:38 raspberrypi user.warn kernel: [1069082.155749] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:05:52 raspberrypi user.warn kernel: [1069095.535771] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:09:05 raspberrypi user.warn kernel: [1069288.965761] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:09:19 raspberrypi user.warn kernel: [1069302.395721] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:09:32 raspberrypi user.warn kernel: [1069315.875697] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:09:45 raspberrypi user.warn kernel: [1069329.255837] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:09:59 raspberrypi user.warn kernel: [1069342.655720] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:28:28 raspberrypi user.warn kernel: [1070452.195801] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:28:42 raspberrypi user.warn kernel: [1070465.605778] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:28:55 raspberrypi user.warn kernel: [1070478.995705] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:29:09 raspberrypi user.warn kernel: [1070492.385750] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:29:22 raspberrypi user.warn kernel: [1070505.825727] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:29:35 raspberrypi user.warn kernel: [1070519.195748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:29:49 raspberrypi user.warn kernel: [1070532.605763] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:33:22 raspberrypi user.warn kernel: [1070745.935686] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:33:35 raspberrypi user.warn kernel: [1070759.305742] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:33:49 raspberrypi user.warn kernel: [1070772.685745] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:34:02 raspberrypi user.warn kernel: [1070786.045768] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:34:16 raspberrypi user.warn kernel: [1070799.457360] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:34:29 raspberrypi user.warn kernel: [1070812.825694] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:34:42 raspberrypi user.warn kernel: [1070826.208781] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:34:56 raspberrypi user.warn kernel: [1070839.585710] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:35:09 raspberrypi user.warn kernel: [1070853.035680] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:35:23 raspberrypi user.warn kernel: [1070866.405656] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:35:36 raspberrypi user.warn kernel: [1070879.765742] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:35:49 raspberrypi user.warn kernel: [1070893.125787] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:36:03 raspberrypi user.warn kernel: [1070906.547196] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:48:41 raspberrypi user.warn kernel: [1071665.205784] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:48:55 raspberrypi user.warn kernel: [1071678.615727] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:49:08 raspberrypi user.warn kernel: [1071691.985744] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:49:22 raspberrypi user.warn kernel: [1071705.375682] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:51:21 raspberrypi user.warn kernel: [1071825.135715] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:55:24 raspberrypi user.warn kernel: [1072068.265697] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:55:38 raspberrypi user.warn kernel: [1072081.655721] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 16:55:51 raspberrypi user.warn kernel: [1072095.055828] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:01:41 raspberrypi user.warn kernel: [1072444.905761] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:01:54 raspberrypi user.warn kernel: [1072458.285711] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:02:08 raspberrypi user.warn kernel: [1072471.715748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:02:21 raspberrypi user.warn kernel: [1072485.145678] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:02:35 raspberrypi user.warn kernel: [1072498.525734] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:02:48 raspberrypi user.warn kernel: [1072511.905757] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:03:01 raspberrypi user.warn kernel: [1072525.336547] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:03:15 raspberrypi user.warn kernel: [1072538.765753] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:03:28 raspberrypi user.warn kernel: [1072552.145689] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:03:42 raspberrypi user.warn kernel: [1072565.515782] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:03:55 raspberrypi user.warn kernel: [1072578.915745] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:08:35 raspberrypi user.warn kernel: [1072858.415755] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:19:02 raspberrypi user.warn kernel: [1073485.405742] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:19:15 raspberrypi user.warn kernel: [1073498.785768] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:19:28 raspberrypi user.warn kernel: [1073512.175748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:19:42 raspberrypi user.warn kernel: [1073525.665704] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:22:06 raspberrypi user.warn kernel: [1073670.215732] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:22:20 raspberrypi user.warn kernel: [1073683.595713] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:22:33 raspberrypi user.warn kernel: [1073696.975748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:22:47 raspberrypi user.warn kernel: [1073710.415685] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:23:00 raspberrypi user.warn kernel: [1073723.835738] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:23:13 raspberrypi user.warn kernel: [1073736.425695] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:29:59 raspberrypi user.warn kernel: [1074143.025778] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:30:13 raspberrypi user.warn kernel: [1074156.405814] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:30:26 raspberrypi user.warn kernel: [1074169.795766] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:30:39 raspberrypi user.warn kernel: [1074183.176902] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:39:07 raspberrypi user.warn kernel: [1074691.175691] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:44:32 raspberrypi user.warn kernel: [1075015.875800] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:44:45 raspberrypi user.warn kernel: [1075029.265762] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:44:59 raspberrypi user.warn kernel: [1075042.645730] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:45:12 raspberrypi user.warn kernel: [1075056.025712] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:45:26 raspberrypi user.warn kernel: [1075069.395759] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:45:39 raspberrypi user.warn kernel: [1075082.805784] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:47:35 raspberrypi user.warn kernel: [1075198.385747] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:47:48 raspberrypi user.warn kernel: [1075211.765701] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:48:01 raspberrypi user.warn kernel: [1075225.135748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:48:15 raspberrypi user.warn kernel: [1075238.556907] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:48:28 raspberrypi user.warn kernel: [1075251.955767] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:48:41 raspberrypi user.warn kernel: [1075265.345775] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:48:55 raspberrypi user.warn kernel: [1075278.725687] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:49:08 raspberrypi user.warn kernel: [1075292.095685] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:49:22 raspberrypi user.warn kernel: [1075305.505689] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:49:35 raspberrypi user.warn kernel: [1075318.888400] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:49:48 raspberrypi user.warn kernel: [1075332.266330] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:50:22 raspberrypi user.warn kernel: [1075365.685771] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 17:50:35 raspberrypi user.warn kernel: [1075379.075682] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:01:10 raspberrypi user.warn kernel: [1076013.606667] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:01:23 raspberrypi user.warn kernel: [1076026.985732] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:01:36 raspberrypi user.warn kernel: [1076040.355818] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:01:50 raspberrypi user.warn kernel: [1076053.785706] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:02:03 raspberrypi user.warn kernel: [1076067.155733] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:02:17 raspberrypi user.warn kernel: [1076080.525742] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:02:30 raspberrypi user.warn kernel: [1076093.885736] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:02:43 raspberrypi user.warn kernel: [1076107.305742] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:10:54 raspberrypi user.warn kernel: [1076597.565760] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:13:09 raspberrypi user.warn kernel: [1076732.485760] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:13:22 raspberrypi user.warn kernel: [1076745.926754] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:13:35 raspberrypi user.warn kernel: [1076759.305717] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:15:43 raspberrypi user.warn kernel: [1076886.925723] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:15:56 raspberrypi user.warn kernel: [1076900.305699] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:16:10 raspberrypi user.warn kernel: [1076913.715724] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:18:00 raspberrypi user.warn kernel: [1077024.075747] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:18:14 raspberrypi user.warn kernel: [1077037.475736] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:18:27 raspberrypi user.warn kernel: [1077050.845735] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:18:40 raspberrypi user.warn kernel: [1077064.225773] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:18:54 raspberrypi user.warn kernel: [1077077.645673] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:19:07 raspberrypi user.warn kernel: [1077091.035701] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:19:21 raspberrypi user.warn kernel: [1077104.408432] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:19:34 raspberrypi user.warn kernel: [1077117.785748] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:19:47 raspberrypi user.warn kernel: [1077131.185752] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:21:53 raspberrypi user.warn kernel: [1077256.835750] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:22:06 raspberrypi user.warn kernel: [1077270.245762] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:24:05 raspberrypi user.warn kernel: [1077388.375790] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:28:48 raspberrypi user.warn kernel: [1077672.145775] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:29:02 raspberrypi user.warn kernel: [1077685.525716] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:29:15 raspberrypi user.warn kernel: [1077698.905789] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:29:28 raspberrypi user.warn kernel: [1077712.318571] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:29:42 raspberrypi user.warn kernel: [1077725.735686] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:29:55 raspberrypi user.warn kernel: [1077739.135701] w1_slave_driver 28-000005cc638d: Read failed CRC check
Apr 29 18:35:24 raspberrypi user.warn kernel: [1078067.485718] w1_slave_driver 28-000005cc638d: Read failed CRC check


Pages: « 1 ... 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 [178] 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 ... 230 »
  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!