On Fri, 20 Aug 2004, Greg Wallace wrote:
On Friday, August 20, 2004 6:56 AM, Greg Wallace wrote
On Friday, August 20, 2004 4:51 AM, Greg Wallace wrote
On Friday, August 20, 2004 4:51 AM, Greg Wallace wrote
On Thursday 19 August 2004 @ 6:15 PM, C. Richard Matson wrote:
On Thursday 19 August 2004 6:39 pm, Greg Wallace wrote:
> What an idiot I am! I moved my backup to this EFG80 device via ftp. All >I > have to do is connect to it and ftp my backup back down to my Linux > machine! Actually, I'd have already done it already, but I can't get back > on my network. I'm REALLY back to square one! I went into YAST and > started inetd, but that wasn't enough. I still can't get back on my > network. I did a plain vanilla install, so do I need to get some > additional packages installed before I can get this up and going? I >tried > simply doing -- > > Ping 192.168.1.77 (the ip address of my Linksys EFG80 where my backup is) > > It came back with "Network is unreachable". What do I need to do to get > basic networking going again. My machines all connect via a Linksys 4 port > Router.
Check the settings of your network card. Rich
Thanks, Greg Wallace
-- C. Richard Matson
I go through a router. I can't even get to the router! And I mean I can't even "Ping" it! I have taken the following steps in YAST.
- Made sure intetd was up and running
- Gone to Network Advanced and a) Gone under Host name and DNS and *) Entered my machine name and the Domain Name I'm using in my router. *) Checked "Update name servers and search list via DHCP" b) Gone to Routing and checked "Enable IP forwarding"
No luck. I still can't ping my router. I never had this problem before, and I installed from the exact same disk. I did simply take all of the default packages, but I know you don't have to install a special package just to have internet support! This is so aggravating because as soon as I can get on the network and can grab my backup and get my system back. Grrrr! Something sort of amusing about this though -- The default "wallpaper" for Root shows a round back bomb with a burning fuse and a big triangle with an exclamation mark in it. The desktop itself is bright red!! I think Linux is playing games with me!!
Greg Wallace
This issue is resolved. The problem with my network connection was in my Router. I had gone to fixed IP addresses on all of my machines, meaning I had certain required things set up that would not be on a "fresh out of the box" installation. To get around that, I had to re-enable DHCP on the router and that took care of the problem. I was able to diagnose it because I finally saw an item in the "Administration Guide" (page 349) that said "See if your card has been integrated properly by entering the command ifstatus eth0". I did that end received an error message mentioning eth0 as the culprit. So, my ehternet connection wasn't functioning properly. Luckily, it wasn't hardware related (that's all I would have needed to completely go over the edge!). Anyway, once I got that up and going, I was able to suck my 6 GIG backup across my network. The recovery is running now. It's already through the packages and is now restoring my data, which includes literally 10's of thousands of Oracle files. It will run for hours, but I sort of like just sitting there watching it (gives me a good feeling). Of course, the proof of the pudding is in the eating, as the old saying goes, so until I can get in and actually startup Oracle, I'll still be on pins and needles a bit.
Yours truly, Greg Wallace
And I'm staying as far away from system administration as I can get for at least the next six months!!
Greg W
Well, I did the restore and all is not well. At the end of the restore, I got a message about SuSE not being able to write the boot record. I try to re-boot and it just hangs with the word GRUB sitting there. When I re-boot from the Installation CD, I get the following --
Activating SWAP failed
Bread: Cannot read a block #2.
Warning... fsck.reiserfs for device /dev/hda3 exited with Signal 6. Fsck.reiserfs /dev/hda3 failed (status 0x0) Run manually! Failed . . . Fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read/write do: bash# mount -n -o remount,rw/
I'm sure this is due to the fact that the original setup had a Windows partition sitting above Linux. When I installed, I went into Partitioning, removed that Windows partition, and moved everything to the top. Hopefully, there's a way to get Linux to recognize this. I would think if I could get a clean boot out off of the installation CD, I'd be able to then re-write the MBR via "grub" and I'd be home free. I did go ahead and do --
Cd / Dir
It appears that all of my high level directories are there, including both of my Oracle directories. Can someone tell me what to do next here?
Thanks and yours truly, Greg Wallace
Well, I tried doing what Marcos Lazarini said. I entered --
Grub Grub> find /boot/grub/stage1
It came back (hd0,1), so I entered --
Root (hd0,1) Setup (hd0)
It said it had written the MBR, so I re-booted. Now, I get this --
GRUB version 0.92 (640K lower / 2095556K upper memory)
Below that is a box listing -- Linux Windows Floppy Failsafe
When I hit enter on Linux, I get this --
Booting 'linux' Kernel (hd0/2)/boot/vmlinuz root=/dev/hda3 hdc=ide=scsi vga=788 Error 22: No such partition Press any key to continue
Why is he saying he's trying to boot hd0/2? When I did "find /boot/grub/stage1", I got back (hd0,1). I then said root (hd0,1) and setup (hd0) and got a message back saying everything was successful when I did that. Looks like it's trying to boot some non-existant hd0/2. There is nothing after my (hd0,1) linux partition on the disk, so there really is no hd0/2!
Yours truly, Greg Wallace
Greg, the point is you still have to change your /boot/grub/menu.lst file to point to the correct place. Grub works in a 2 stage process: What you've done: you have installed grub in you MBR, and configured it to look for this file (/boot/grub/menu.lst) in (hd0,1), which is the same as /dev/hda2. It found the menu.lst file, but this file points to the wrong place! Boot again with the rescue CD, and edit the menu.lst file (using pico, emacs, vi, etc), changing the (hd0,2) to (hd0,1), as you expected. You are almost there! :-) Grub usually permits the user to replace the boot parameters to the kernel on the fly, but SuSE disable it for some reason (may be they are tring to hide the details of the dark side of the force :-))... Regards, Marcos Lazarini