From brkittycat at verizon.net Mon Mar 2 16:31:08 2009 From: brkittycat at verizon.net (Brenda Radford) Date: Mon, 02 Mar 2009 11:31:08 -0500 Subject: New Monitor In-Reply-To: <9A0EB8A8C4C2411BB375B3301F6D03DA@brendace5b4803> References: <653C4A3EC6544A43B705682F2E24A528@brendace5b4803> <20090223211751.GA998@bobcat.bobcatos.com> <997E2B2321D34D188ED198A9F0A7DECF@brendace5b4803> <49A350A8.6080407@nerd.com> <485361BF45ED468380C70AB22F0507A9@brendace5b4803> <20090224030309.GA15972@bobcat.bobcatos.com> <49A42E9B.8060000@nerd.com> <7793AF05BB7A481A9B1AAFB99EFDDA51@brendace5b4803> <20090225022919.GA10463@bobcat.bobcatos.com> <52F000DF225B4652BD1A586BD3011042@brendace5b4803> <5ce05200902251058v671a54a7id69dc72cf487aa01@mail.gmail.com> <3E435D6E9EE648D797A84AEC039A3E8D@brendace5b4803> <49A5B24E.1040209@nerd.com> <3286F6B025FC484BB69F0396F1A668C3@brendace5b4803> <49A5B977.4080904@nerd.com> <9A0EB8A8C4C2411BB375B3301F6D03DA@brendace5b4803> Message-ID: <63A26A56FEF743B190ED4D18823F9A6C@brendace5b4803> -----Original Message----- From: redhat-install-list-bounces at redhat.com [mailto:redhat-install-list-bounces at redhat.com] On Behalf Of Brenda Radford Sent: Wednesday, February 25, 2009 4:40 PM To: 'Getting started with Red Hat Linux' Subject: RE: New Monitor -----Original Message----- From: redhat-install-list-bounces at redhat.com [mailto:redhat-install-list-bounces at redhat.com] On Behalf Of Rick Stevens Sent: Wednesday, February 25, 2009 4:35 PM To: Getting started with Red Hat Linux Subject: Re: New Monitor Brenda Radford wrote: > > -----Original Message----- > From: redhat-install-list-bounces at redhat.com > [mailto:redhat-install-list-bounces at redhat.com] On Behalf Of Rick Stevens > Sent: Wednesday, February 25, 2009 4:04 PM > To: Getting started with Red Hat Linux > Subject: Re: New Monitor > > (bunch of stuff snipped) > (Brenda said:) > >> fdisk -l >> >> Device boot start end ID system >> >> /dev/hde1 * 1 13 83 Linux >> /dev/hde2 14 9729 8e Linux LVM >> >> lvscan >> >> inactive /dev/VolGroup00/LogVol00 [72.62GB] inherit >> inactive /dev/VolGroup00/LogVol01 [1.75GB] inherit >> >> >> e2fsck /dev// >> /dev/VolGroup00/LogVol00 >> /dev/VolGroup00/LogVol01 >> I got this error message for both: >> >> No such file or directory while trying to open >> The superblock could not be read or does not describe a correct ext2 >> filesystem. If the device is valid and it really contains an ext2 file >> system (and not swap or ufs or something else), then the superblock is >> corrupt and you might try running e2fsck with an alternate superblock: >> E2fsck -b 8193 >> >> Linux rescue gave me this: >> You don't have any Linux partitions. >> >> The chroot /mnt/sysimage >> And cat /etc/fstab also failed. No such file or directory >> >> Nothing wonderful happened when it rebooted. >> >> Now what do I do? Do I have to start over with a fresh install? >> This reminds me of a blue screen in Windows. I had one of those last >> January. >> >> Thanks, >> Brenda >> >> >> >> Bob or Rick may have a different take. I say if you have nothing to lose >> then why not do a fresh install. Still in reviewing this post it seems > some >> part of the file systems is hosed. If a recovery option exists, as a >> tech-guy >> I would pursue it just for the learning experience. From a sys admin point >> of >> view with the goal of having a running box do a fresh install. Assuming no >> data or apps are needed from the existing install. > >> I'd tend to agree. There's something very odd here. The fdisk -l shows >> Linux partitions on /dev/hde? You'd have to have at least five IDE >> drives to get out there, and Linux now treats all drives as SCSI so they >> should show up as /dev/sde (not /dev/hde) with any fairly recent kernel. >> >> You could, theoretically, do an "fsck /dev/hde1" as it's a regular >> partition with a filesystem on it. Do NOT fsck /dev/hde2 as that's an >> LVM volume. >> >> The rescue disk should have found that stuff and activated your volume >> groups. You can try it again by going into rescue mode and entering >> "vgchange -ay" to activate the volume groups. >> >> Going back to the initial problem, a message such as "FS: can't find >> ext 3 filesystem on dev dm-0" smells more like we have a software RAID >> here and it somehow is degraded or the RAID modules aren't loaded in the >> initrd image. A device such as dm-0 is a software RAID volume. >> >> Brenda, was this configured on a software RAID? > > > No RAID configuration. This box has four hard drives in it, but they are not > cabled. How do you mean? No data cables or no power cables? If they still have data cables but no power cables, that's bad and they can hang the bus. Tell you what, can you give us a full rundown on the system? Things like CPU type (32- or 64-bit), amount of RAM, video card type, numbers and types of drives, how they're connected and what you think you have on them now, any external devices (USB, etc.) and which operating systems you're trying to work with. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks at nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Is that a buffer overflow or are you just happy to see me? - No data cables AND no power cables. They are just in the case. They were not connected when I did the install, I do not think. I have good news to report. Linux rescue did not work again, so I decided to try the Live CD (Knoppix) to see if I could activate the Logical Volumes. It worked. I then ran e2fsck on the LV's and told it to fix everything it found wrong, and it worked. I am able to boot and have now updated the box to RHEL AS 4 Update 7. As for the hde thing, I seem to remember that I installed on a master while I had a slave drive that had Red Hat on it. The slave drive was not mounted automatically; I had to mount it to access the data on it. I must have unplugged it at some point after the fire (I cannot remember because that motherboard was installed into a new case), but none of the filesystem from the last install was on that drive. I might have unplugged it when I put the DVD burner in there on an IDE controller card last summer or fall, but I cannot be sure. I do not think that had anything to do with the box not booting last week, but I could be wrong, Rick. I do not know how the filesystem became corrupted. I do not know whether to trust that hard drive or not. Thanks again to all who replied to my posts, especially when you were sure I did not know what I was doing. The new monitor is working fine on a DVI cable. Now if I could just get the HP printer to work . . . Something about HPLIP not being compatible with HPOJ, and errors related to qt while trying to install PyQt 4.x (python configure.py fails). I am in over my head on this one. Thanks, Brenda From mnedai at yahoo.com Sun Mar 15 20:51:45 2009 From: mnedai at yahoo.com (Ml Cole) Date: Sun, 15 Mar 2009 13:51:45 -0700 (PDT) Subject: problem to start x server after installation can't open display vidio card RIVA128 Message-ID: <983097.84486.qm@web52009.mail.re2.yahoo.com> I'm running rh 4.2 on Micron PC. Installation was success. But got an error when starting X server (display was ?not properly configured...) running system-config-display for card RIVA128 did not help! ? Any suggestion? ? TIA -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob at bobcatos.com Sun Mar 15 22:31:09 2009 From: bob at bobcatos.com (Bob McClure Jr) Date: Sun, 15 Mar 2009 17:31:09 -0500 Subject: problem to start x server after installation can't open display vidio card RIVA128 In-Reply-To: <983097.84486.qm@web52009.mail.re2.yahoo.com> References: <983097.84486.qm@web52009.mail.re2.yahoo.com> Message-ID: <20090315223109.GA12578@bobcat.bobcatos.com> On Sun, Mar 15, 2009 at 01:51:45PM -0700, Ml Cole wrote: > I'm running rh 4.2 on Micron PC. > Installation was success. > But got an error when starting X server (display was > ?not properly configured...) > running system-config-display for card RIVA128 did not help! > ? > Any suggestion? > ? > TIA Did it correctly recognize your video card or did you have to tell it what it was? Is that a pretty recent video card? (Sorry, I'm not much of a hardware maven.) Did it correctly recognize your monitor or did you have to tell it what it was? Actually RHEL 4.2 is a bit long in the tooth and may not adequately support your card. And unless you purchase(d) support for it, you won't be able to get updates, which are a must. I'd recommend you download and install CentOS 5(.2), http://www.centos.org/ which is a free repackaging of RHEL 5(.2), for which you can get free updates and a number of extras. My first installation of Red Hat was v4.2 (the old series that went from 1 to 9, before Fedora), back when the whole thing was on one CD. I had migrated from Slackware. I think I still have the box and CD. Suppose that will be a collector's item someday? Before I die? Cheers, -- Bob McClure, Jr. Bobcat Open Systems, Inc. bob at bobcatos.com http://www.bobcatos.com My heart says of you, "Seek his face!" Your face, LORD, I will seek. Psalm 27:8 (NIV) From ivanhec at gmail.com Wed Mar 25 11:56:13 2009 From: ivanhec at gmail.com (Ivan .) Date: Wed, 25 Mar 2009 22:56:13 +1100 Subject: RedHat EL 5package requirements Message-ID: <6450e99d0903250456l597c5391m899fab070b654e50@mail.gmail.com> Hi All, What is the minimum, practical install list of packages you can build a Squid 3.1 box with only it, sshd, syslog, snmp, iptables via kickstart? Is the file system performance argument relevant? ext3? Thanks Ivan -------------- next part -------------- An HTML attachment was scrubbed... URL: