Hi Erich,
Well, there isn't much I can tell you. The box in question resides 8 hours away. It worked for approximately 6 months, then I got the call from that office to tell me it wouldn't boot. They sent the CF back to me and I poked around it a little. Not much to see, it simply wouldn't boot. So I assumed a bad CF, rebuilt their system on a new card and sent it back to them. They plugged the new card into the box and it has worked properly since mid-May, failing just before Christmas. Same symptoms. This time I had them send the whole box back to me. I don't see anything wrong with the box. However, as this happens so rarely, it could really be anything. Flakey power supply, two bad CF's in a row (possible if not very likely), maybe even an unwelcome visitor... who knows. When it takes 6 or 7 months to repeat the failure, it's difficult to efficiently trouble shoot this problem. ;-)
Unfortunately, the symptoms aren't much to go on! It worked one day, but not the next! I'm going to use a twin machine to replace this one, with a new (same model PC-Engines adapter board - type 1C) CF adapter and CF card. If this one fails later this year I'll be back where I started... pretty much nowhere.
I just don't understand what could wipe the boot area twice in a row, but leave the rest of the card untouched... power spikes, flakey IDE cable, nothing really adds up to this result. My only idea revolves around the possibility that the BIOS is not auto-detecting the card properly. I've talked to Lexar, but so far they have not produced any CHS information for their cards. And I can't find anything useful on the 'net. I'm thinking I should manually configure the CHS settings, just in case it is being auto-detected incorrectly.
Brock
Erich Titl wrote:
Brock
Brock Nanson wrote:
I've got several boxes running several versions of Bering and Bering uClibc, all on Compact Flash cards. They've all been reliable, except for one box. Twice in the last six months, the box has failed to boot. The CF is recognized in the BIOS, but no boot information seems to be found. The first time it happened, I swapped the CF card for another and built the system from scratch. This time I'm wondering if the computer could be part of the problem. I don't like the double coincidences of it a) failing in the first place and b) failing *twice* in the same box on different CF's. Especially when all the others have run for years.
Has anyone had a problem like this? I'd like to know if the box could be the problem before I take the time to replace this CF yet again. The unit is in a remote location and is fairly mission-critical. I can't have this happen so regularly.
Yes, I have seen this before, mostly caused by bad CF's, sometimes by bad saves of the entire system.Would you mind to give us details about the failure
Erich
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
