10

What is the mean time before failure (MTBF) for a Raspberry Pi Model B? I can't seem to find this information anywhere.

I have an idea for a kind of art project that would require one to run as long as possible, and I want to have some idea of how long that would be. I'm only concerned with hardware failures on the Pi board itself that would render it unbootable, software instability is fine as long as the watchdog timer can manage an automatic reboot.

6
  • The SD card is the first point of failure. If it used constantly like full read and write the entire card about 2 years.But its a bit longer because of distribution for least wear. Second point of failure will be power supply(if its cheap 2USD one dont expect more than 1~2 constant use-go for switched PSU) But as the Pi in general it depends on the conditions. If in a dry and constant environment you could find it runs several years. In extreme conditions it might not last a year. We need more information.
    – Piotr Kula
    Commented Jul 24, 2013 at 19:29
  • why are you concerned about MTBF? at the current prices, i'd buy several and replace as needed.
    – lenik
    Commented Jul 24, 2013 at 19:36
  • 1
    I care about MTBF because part of the point is that the project will be totally unmaintained. The MTBF number that I want is for the Pi itself, ignoring things like SD cards and power supplies (those numbers are more available).
    – Kaypro II
    Commented Jul 24, 2013 at 19:48
  • 2
    I don't think you will be able to find any useful numbers for MTBF. The RPi was not designed for critical uses where this would be a concern.
    – Craig
    Commented Jul 24, 2013 at 20:06
  • 2
    Perhaps this is a question for the Raspberry Pi team. I would shoot them off an email, since they stress test the devices. For what it counts, I've had mine since they first started selling them and it's still going strong.
    – syb0rg
    Commented Jul 24, 2013 at 20:33

3 Answers 3

2

I think the only way to get a realistic answer is to look up the data sheets on the important ICs, which should have a published MTBF rating.

1
  • 4
    Unfortunately the datasheet for the SoC BCM2835, the main IC on the Pi, is not available for general use.
    – Marco Poli
    Commented Aug 29, 2013 at 22:34
3

I'd backup the suggestions so far. The most likely point of failure would be the SD card. My own experience is that the SD card is fairly fragile. I had a power outage for just a second (New Zealand's electricity network is not that great even in the main cities!) and though the Pi would be able to restart after a power outage, in my case the SD cards failed dramatically. I had two Pis crash and get corrupted SD cards - I had to re-install the OS. My 3rd was able to pick itself up and reboot OK. Of the two that failed one had such a badly corrupted card that I was not able to put a operating system on it, it ended in the bin.

For a permanent fixture, you should consider that the power is likely to go off and come on without warning. Make sure your app will start automatically on boot. Also look at avoiding writing to the SD card - which will wear the card out (albeit very slowly). I'd imagine that an art installation wouldn't need to write to files or anything, but if it did then look at having your files in /tmp, which should be in RAM not on the SD card. You might consider ways of including a backup power supply. Perhaps solar cells or LiPo batteries.

Another approach would be to think about redundancy. Would your project be able to use two Pis, one that would cut in if the other failed? It could greatly complicate your project but for mission critical applications, that's a standard approach.

Sorry I've not included any actual figures as you have looked for, but maybe there's some information here that could help you think round the problem.

1
  • 2
    This is not an answer to my question. My question, restated simply, is how long, on average, can the Raspberry Pi board itself operate before it fails. While SD card reliability is important to the integrated system, it's a totally different thing.
    – Kaypro II
    Commented Aug 10, 2013 at 2:49
-2

Mean Time Before Failure for my rPi 3 was eleven (11) months.

4
  • 3
    That isn't a "mean" (i.e, average) time. It's just a single value.
    – user28237
    Commented Jul 7, 2018 at 5:37
  • That and the fact that the question is about the Raspberry Pi Model B not the 3B.
    – Ghanima
    Commented Jul 7, 2018 at 8:01
  • Thank you so much for clarifying that for me .... I mistakenly thought that since the question was: "What is the mean time before failure (MTBF) for a Raspberry Pi Model B"
    – Michael
    Commented Jul 7, 2018 at 17:25
  • Fun Fact: the first signs of trouble on my Raspberry Pi Model B V1.2 (yes, it's a 3B) was in a network analyzer .. it began showing up with two (2) addresses; the first had the MAC address listed, the other showed 'n/a'. VNC was still possible, but very, very slow to connect. If your Model B (3 or not) starts showing up with a generic address, you might want to consider it failing. #justsayin
    – Michael
    Commented Jul 11, 2018 at 13:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.