Re: Is that all?

Well, for awhile now the box had been throwing really funky errors:

FAT bread failed.

And would just spam the screen. I couldn't find anything on what would cause that, and it didn't seem to cause any problems. So, I just continued to let it spam the screen.

Then, about 3-4 weeks ago, the box went down. I got to the console to find:

hda1: read/write failed (status: busy)

Or some such. Box frozen, this message spamming the screen every 1-3 seconds.

I reboot. Upon reboot, lo and behold, someone/something had flubbed glibc 2.2 and SSHD wouldn't start, and a few other really icky things. That's when I posted to the Linux boards here for possible solutions. No luck.

So, we flew blind for a couple of weeks until the same issue came up. At this point, I knew this was going to be a consistent problem.

We were already 2 weeks out, probably, from switching to the new server. Everything at the host is going to rack mountable boxes; the old box was a ATX minitower case, this new box is a 2U rack mount (Intel ISP somethingsomething). So, given the downtime, and the need, I went ahead and "pulled the trigger".

The new box is a dual P4-750MHz, 1 GB of RAM, 2-10GB SCSI HDs. SuSE 7.3 Professional.

The old box was a Athlon 1.4GHz, 384 MBs of RAM, 1-15 GB IDE HD (WD, btw, Tabby). Mandrake 7.2.

This new box screams comparatively.

So, installed the new box, brought it up on the network. Moved DNS (that's when everyone saw the default Apache site). Then took the old box to my house and threw it on my network at home.

Now, how to get access to the box so that Scott can work his magic with Zope/zIWT, and manage to transfer stuff off, otherwise? I'm far from being a Linux guru. I know much more then I used to, but I'm still far from guru status. I'd say I'm at "alright" status. ;)

With that in mind, I wasn't able to fix the SSHD issue or open telnet. I was floundering. So, I just decided to install VNC. Installed VNC, poked a hole in my home firewall.

All was well. 2 days later, everything was back online.

So, no great stories of flaming piles of smoking hardware. But, regardless, it was still quite a task. I'm lucky my wife was out of town for 2 weeks, as there were a few really late nights. :) And, she just *loves* that! :P

Anyways, thanks for everyone's patience. I apologize for the downtime. Hopefully this will be the last time we have to deal with that.

-Jason

Post #50,581 by jlalexander 9/5/02 7:59:40 AM Reply	Re: Is that all? Well, for awhile now the box had been throwing really funky errors: FAT bread failed. And would just spam the screen. I couldn't find anything on what would cause that, and it didn't seem to cause any problems. So, I just continued to let it spam the screen. Then, about 3-4 weeks ago, the box went down. I got to the console to find: hda1: read/write failed (status: busy) Or some such. Box frozen, this message spamming the screen every 1-3 seconds. I reboot. Upon reboot, lo and behold, someone/something had flubbed glibc 2.2 and SSHD wouldn't start, and a few other really icky things. That's when I posted to the Linux boards here for possible solutions. No luck. So, we flew blind for a couple of weeks until the same issue came up. At this point, I knew this was going to be a consistent problem. We were already 2 weeks out, probably, from switching to the new server. Everything at the host is going to rack mountable boxes; the old box was a ATX minitower case, this new box is a 2U rack mount (Intel ISP somethingsomething). So, given the downtime, and the need, I went ahead and "pulled the trigger". The new box is a dual P4-750MHz, 1 GB of RAM, 2-10GB SCSI HDs. SuSE 7.3 Professional. The old box was a Athlon 1.4GHz, 384 MBs of RAM, 1-15 GB IDE HD (WD, btw, Tabby). Mandrake 7.2. This new box screams comparatively. So, installed the new box, brought it up on the network. Moved DNS (that's when everyone saw the default Apache site). Then took the old box to my house and threw it on my network at home. Now, how to get access to the box so that Scott can work his magic with Zope/zIWT, and manage to transfer stuff off, otherwise? I'm far from being a Linux guru. I know much more then I used to, but I'm still far from guru status. I'd say I'm at "alright" status. ;) With that in mind, I wasn't able to fix the SSHD issue or open telnet. I was floundering. So, I just decided to install VNC. Installed VNC, poked a hole in my home firewall. All was well. 2 days later, everything was back online. So, no great stories of flaming piles of smoking hardware. But, regardless, it was still quite a task. I'm lucky my wife was out of town for 2 weeks, as there were a few really late nights. :) And, she just loves that! :P Anyways, thanks for everyone's patience. I apologize for the downtime. Hopefully this will be the last time we have to deal with that. -Jason ---- My pid is Inigo Montoya. You "killed -9" my parent process. Prepare to vi.
Post #50,684 by ben_tilly 9/5/02 7:11:32 PM Reply	FAT bread failed Based on [link\|http://www.redhat-linux.com.my/faq/boot10.html\|this] it is possible that Linux thought there was a FAT partition, tried to do a binary read, and that failed. No idea why that would be the case for you, but at least you know that you are not alone in seeing that error message. Cheers, Ben Computer Science is no more about computers than astronomy is about telescopes. -- Edsger Wybe Dijkstra (1930-2002)
Post #50,707 by a6l6e6x 9/5/02 8:52:54 PM Reply	Interesting. Pierre is in the Charlotte (NC) LUG. Alex "Resort is had to ridicule when reason is against us." -- Thomas Jefferson

Welcome to IWETHEY!