mersenneforum.org Server outrages
 Register FAQ Search Today's Posts Mark Forums Read

 2016-04-04, 05:02 #463 gd_barnes     May 2007 Kansas; USA 101000011110102 Posts OK I had in mind that I would boot from an old Ubuntu disk that I have laying around. If it boots to a desktop then I know it's the hard drive. I'll edit this post as soon as I do that to let you know. I agree that the O.S. needs updating. If the hard drive is bad, I'll buy a new one sometime tomorrow and install the new O.S. (Mint) that Max sent me a few weeks ago. For future record, here are some of the messages I am getting: Code: kinit: No resume image, doing normal boot... mount: mounting /dev/disk/by-uuid/6d54e625-ec49-4b06-8c5b-609f615887f3 on /root failed: Invalid argument mount: mounting /dev on /root/dev failed: No such file or directory mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init. No init found. Try passing init= bootarg. BusyBox v1.10.2 (Ubuntu 1:1.10.2-2ubuntu7) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Last fiddled with by gd_barnes on 2016-04-04 at 05:03
 2016-04-04, 05:21 #464 gd_barnes     May 2007 Kansas; USA 2·3·11·157 Posts I was able to boot it from a very old Ubuntu disk (version 8.04). I then was able to access the hard drive and see all of the files; PRPnet servers, the web pages, etc. So...it appears nothing is lost. My suspicion at this point is that there are a few bad sectors in the boot up part of the hard drive. I'll see what I can do with a newer version of Ubuntu. Edit: And it works...lol. I pulled out the old C.D, and tried another reboot and it came right up normally with no C.D. and no new install. I had tried about 20 different reboots earlier this evening trying various things and it kept coming back to the same error messages. So...everything will be back online shortly. We will see how long it lasts. Last fiddled with by gd_barnes on 2016-04-04 at 05:26
 2016-04-04, 05:57 #465 gd_barnes     May 2007 Kansas; USA 287A16 Posts Everything is back up. There was no loss of data.
 2016-04-04, 07:04 #467 gd_barnes     May 2007 Kansas; USA 287A16 Posts lol on that final idea. I'm a little too old school for that. I'm not quite willing to buy a new computer yet but I agree that we need to upgrade the O.S. I'm not going to give any timeline but it is something I'll keep in the back of my mind. What you said about a power blip makes sense. I noticed a "dulling" of my lights on-and-off for a minute or more right about the time that it happened. No complete outage so my clocks weren't flashing or anything. Perhaps it was some sort of minor electrical log jam somewhere up the line. Usually the lights go completely out for a few secs and then come back on with all of the clocks flashing so this was a more unique occurrence. Anyway, when that has happened in the past, usually some or all my computers go down. If the blip is fast enough, most of them will not be affected. But with the sustained dulling of the lights, I suspected that they all had been affected, which they had. Oddly some had just rebooted while others completely shut down so the apparent "reduction" in electricity for a minute or so affected some more than others. Jeepford had just rebooted to the error messages that I posted. Based on your explanation, I think it is very possible that the sustained reduction in electricity flow (or whatever it was) maybe messed with the booting sectors because it was likely trying to reboot itself while the dulling was going on since it lasted for a minute or more. Perhaps putting the old O.S. boot disk in there for a while allowed it to fix itself...very cool if that is what happened. Last fiddled with by gd_barnes on 2016-04-04 at 07:06
 2016-04-04, 10:42 #469 gd_barnes     May 2007 Kansas; USA 101000011110102 Posts I'm not sure that what you stated is completely true but I think it is mostly true. When I tried rebooting it many times, a couple of the times I waited 20-30 minutes in between just to maybe give it a chance to figure itself out. Nothing worked. Later in the night, I tried rebooting it a couple of more times. No luck. Right after that I used the boot CD and it only took a couple of minutes for it to boot from that. I then looked around for maybe 3 more minutes with the boot CD in to make sure all of the files were on the hard drive, which they were. So at that point, it had only been about 5 minutes since the last reboot. I then took the CD out and it rebooted fine directly from the hard drive. Regardless something clicked in those last 5 minutes that didn't previously click in two 20-30 minute attempts...maybe because it wasn't specifically accessing the bad sectors.
 2016-04-05, 10:21 #470 AMDave     Jan 2006 deep in a while-loop 10100100102 Posts Ahh. Interesting. That's a feature I should have known about, but didn't. Thanks Max. I learned something today which makes it a good day :) I'm glad it worked out and the HDD is responding again. Although, I thought you (Gary) would be using the same term as me, given our comparable age group. We have always called it a "Brown out". So called because, although the power does not completely fail, the voltage drops dramatically causing the old tungsten light filaments to die down to a yellow glow then brown as they cool. However, there is a nasty consequence to this for modern equipment. As the voltage drops the Amps increase and that's generally when my el-cheep-o power supply components overload and die, if they are not on the UPS (which handily cleans up the sine waves and regulates the current). The more robust (and pricey) PSUs can last longer under these conditions, but will also eventually succumb if it happens repeatedly. I have had it happen so many times that it calculated out as being better at the cheaper end of the scale. As Max says, we're good to go on a new OS on either a new or existing machine whenever you are ready and at your own pace. The software rebuild is a known factor and the DR server demonstrates that the daemons, databases and web sites all work on current OS and software versions, along with the built in "stim pack" of bug fixes and speed and security improvements. We can make an email trail out of that, offline, when you are ready.
 2016-04-05, 11:19 #471 gd_barnes     May 2007 Kansas; USA 287A16 Posts Interesting. I had heard the term brown out but I never knew what it meant. I've lived at my current residence for about 10 years and this is likely only the 2nd or 3rd time that I can recall a brown out. Usually it's a full blip where the lights go out for a few secs or mins and the digital clocks flash after power comes back on. So now I know what a brown out is and it is an unusual occurrence here. Last fiddled with by gd_barnes on 2016-04-05 at 11:20
 2016-04-19, 02:23 #472 mdettweiler A Sunny Moo     Aug 2007 USA (GMT-5) 141518 Posts Brief server downtime around 2016-04-18, 20:00 CDT (server time) - RESOLVED The noprimeleftbehind.net server apparently rebooted itself around 20:00 server time today. Nothing seems to be "broken" - it had just rebooted (possibly a power blip), which shut down all the PRPnet servers. I logged in around 21:00 and restarted the servers - everything is back up and running now. Total downtime is just about an hour. Nothing to see here, move along people.
 2016-04-19, 08:49 #473 AMDave     Jan 2006 deep in a while-loop 29216 Posts Excellent catch. I didn't even get around to noticing it! I have been too busy watching that and other Frank Drebin quotes on You-Tube :P It was worth the sojourn.

 Similar Threads Thread Thread Starter Forum Replies Last Post paul0 NFS@Home 2 2015-03-12 23:00 Christenson Information & Answers 5 2011-07-12 21:44 Grant Information & Answers 13 2008-11-24 19:37 andi314 Factoring 3 2003-08-31 11:22 Angular PrimeNet 32 2002-12-09 01:12

All times are UTC. The time now is 00:35.

Sun May 9 00:35:29 UTC 2021 up 30 days, 19:16, 0 users, load averages: 2.09, 2.08, 2.12