buildworld actually crashed
During buildworld, I wandered off. When I returned, my machine was, alarmingly, in single user mode, demanding that I run fsck manually. I'm running fsck right now, and it's finding all sorts of block size errors, to which I'm simply hitting 'y' and agreeing that things should be salvaged and corrected. Before running fsck, I had a look at the buildworld.out script that was being written to during the buildworld process. I can't tell you exactly what it says, but it definitely came to a stop in the middle of a 'sentence' of output. I.e. it looks like my new machine (yeah, the soon-to-be-fanless EPIA again) must have crashed during buildworld. What could cause buildworld to crash like that? I'm now worried that my PSU board *was* damaged the other day. Is a damaged PSU the most likely cause of this incident? All advice very welcome. -- Bob London, UK echo Mail fefsensmrrjyaheeoceoq\! | tr jefroq\! @obe.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld actually crashed
Robert Downes wrote: During buildworld, I wandered off. When I returned, my machine was, alarmingly, in single user mode, demanding that I run fsck manually. I'm running fsck right now, and it's finding all sorts of block size errors, to which I'm simply hitting 'y' and agreeing that things should be salvaged and corrected. Before running fsck, I had a look at the buildworld.out script that was being written to during the buildworld process. I can't tell you exactly what it says, but it definitely came to a stop in the middle of a 'sentence' of output. I.e. it looks like my new machine (yeah, the soon-to-be-fanless EPIA again) must have crashed during buildworld. What could cause buildworld to crash like that? I'm now worried that my PSU board *was* damaged the other day. Is a damaged PSU the most likely cause of this incident? All advice very welcome. Not enough information here to be sure, but it sure sounds like a hardware problem. You might do well to try memtest86 and cpuburn on that machine for a while, to see if you can track down a hardware problem. Monitor the temperature of the machine while doing so, could be that the cooling is inadequate. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld actually crashed
On Friday 28 May 2004 10:00 am, Robert Downes wrote: During buildworld, I wandered off. When I returned, my machine was, alarmingly, in single user mode, demanding that I run fsck manually. I'm running fsck right now, and it's finding all sorts of block size errors, to which I'm simply hitting 'y' and agreeing that things should be salvaged and corrected. Before running fsck, I had a look at the buildworld.out script that was being written to during the buildworld process. I can't tell you exactly what it says, but it definitely came to a stop in the middle of a 'sentence' of output. I.e. it looks like my new machine (yeah, the soon-to-be-fanless EPIA again) must have crashed during buildworld. What could cause buildworld to crash like that? I'm now worried that my PSU board *was* damaged the other day. Is a damaged PSU the most likely cause of this incident? Just one of the possibilities. There are connectors that will test ATX psu's. My experience with psu failures is the system dies and you don't have something like HDs. I had what I think is a cpu failure that caused a voltage regulator IC to explode on the mobo. I was looking at the mobo from about 2 feet when it did this. That was about the most exciting thing that happended that day :). I was telling a friend about it and he made the comment that they don't throw shrapnel but disappear into dust. I never saw or felt anything and assume that he was right. Insufficient size will cause intermitant errors depending on the cpu. I usually go at least the next 50 watts up from what is recommended for a cpu. I also have a tendancy to like 350+'s with dual fans. All advice very welcome. In the FAQs trouble shooting link is a section on signal 11's. I would look at the options. Very little will cause a buildwold to die but hardware errors. You have to use wavy hands at this point because -stable and -current occasionaly have errors but none of the software errors are likely to cause the system to reset it self during a build. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
