Re: [CentOS] 75% - 80% Rebuild Complete
On 8.6.2012 08:38, Bob Hoffman wrote: out of curiosity, how do you prevent centos from ejecting the dvd when it is done installing? There is a boot option (from RHEL5 Installation Guide) noeject do not eject optical discs after installation. This option is useful in remote installations where it is difficult to close the tray afterwards. I did not find it mentioned in the RHEL6 Installation Guide, so I am not sure if it has gone. I did not test it. -- Kind Regards, Markus Falb signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
On 6/8/2012 1:13 AM, Nataraj wrote: On 06/07/2012 03:48 PM, Les Mikesell wrote: And if the server is colocated, but you have remote console access, you can leave a recovery CD in the drive, but set the boot order to boot the hard drive and then remotely change the boot order if you have problems. Nataraj out of curiosity, how do you prevent centos from ejecting the dvd when it is done installing? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
On 06/07/2012 11:38 PM, Bob Hoffman wrote: On 6/8/2012 1:13 AM, Nataraj wrote: On 06/07/2012 03:48 PM, Les Mikesell wrote: And if the server is colocated, but you have remote console access, you can leave a recovery CD in the drive, but set the boot order to boot the hard drive and then remotely change the boot order if you have problems. Nataraj out of curiosity, how do you prevent centos from ejecting the dvd when it is done installing? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos That I don't know, but once CentOS is installed, if my memory serves me correctly, I think you can leave a CD/DVD in the drive over reboots as long as you don't eject it. Alternatively, I think it would work to use a USB stick to boot a recovery system remotely. Dell actually provides the ability to boot a remote CD over the DRAC interface but it's extremely slow unless you have a very high bandwidth connection, and at least a few years ago when I last looked, most people did not recommend using that functionality. Actually now that I think about it, I believe that if you have a CD/DVD drive with a self loading tray, it will suck the tray back in when the BIOS resets. This will not work with the slim drives with manual trays that they put in most servers, so you would have to have rack space that allows you to leave an external drive plugged in. The USB stick or other flash drive is probably a better solution. The main thing is having remote access to the BIOS. Nataraj ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
Bob Hoffman wrote: On 6/8/2012 1:13 AM, Nataraj wrote: On 06/07/2012 03:48 PM, Les Mikesell wrote: And if the server is colocated, but you have remote console access, you can leave a recovery CD in the drive, but set the boot order to boot the hard drive and then remotely change the boot order if you have problems. Nataraj out of curiosity, how do you prevent centos from ejecting the dvd when it is done installing? some drives support eject -t to close the tray ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
On 6/5/2012 7:21 PM, Eugene Poole wrote: OK, I'm about 90% sure that I've corrected the boot loader situation with RAID-1 and the second hard drive. I haven't tested the correction, but here's what I did: Examined the grub.conf file and noticed that hd0 uses (hd0,1), so what followed was grub grub device (hd1) /dev/sdc grub root (hd1,1) grub setup (hd1) after receiving the successful message grub quit I didn't rebuild the boot loader on /dev/sda because it is working (if it ain't broke don't fix it). My situation is that I'm using 4 - 1 TB hard drives and I used the following pattern: /dev/sda | /dev/sdc = First Raid -1 volume /dev/sdb | /dev/sdd = Second Raid-1 volume There is no complete solution to this problem. The question is this: When one of the drives dies, how will the system see the remaining drive? Will it still see it as sdb, or will it now see that drive as sda? These situations need different grub configs. I generally configure both drives as if they were hd0/sda. That way, if sda crashes, I can remove the disk and boot the second drive normally. -- Bowie ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
on 6/7/2012 9:40 AM Bowie Bailey spake the following: On 6/5/2012 7:21 PM, Eugene Poole wrote: OK, I'm about 90% sure that I've corrected the boot loader situation with RAID-1 and the second hard drive. I haven't tested the correction, but here's what I did: Examined the grub.conf file and noticed that hd0 uses (hd0,1), so what followed was grub grub device (hd1) /dev/sdc grub root (hd1,1) grub setup (hd1) after receiving the successful message grub quit I didn't rebuild the boot loader on /dev/sda because it is working (if it ain't broke don't fix it). My situation is that I'm using 4 - 1 TB hard drives and I used the following pattern: /dev/sda | /dev/sdc = First Raid -1 volume /dev/sdb | /dev/sdd = Second Raid-1 volume There is no complete solution to this problem. The question is this: When one of the drives dies, how will the system see the remaining drive? Will it still see it as sdb, or will it now see that drive as sda? These situations need different grub configs. I generally configure both drives as if they were hd0/sda. That way, if sda crashes, I can remove the disk and boot the second drive normally. In older versions sdb would become sda, but I don't have enough time on the 6 series to know for sure... Maybe I will fire up a virtual machine with a couple emulated sata drives and see ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
On Thu, Jun 7, 2012 at 4:48 PM, Scott Silva ssi...@sgvwater.com wrote: In older versions sdb would become sda, but I don't have enough time on the 6 series to know for sure... Maybe I will fire up a virtual machine with a couple emulated sata drives and see Sda/sdb are the kernel's conventions. What matters is what bios sees. And that may be different depending not only on the hardware but also the failure mode - sometimes a drive will fail but not really disappear from detection and it is hard to emulate that. Also, back in ATA days it was pretty common for a failed drive to lock both channels on the controller. As long as you have physical access to the box you can fix it fairly quickly by booting a rescue iso and re-installing grub, even if you have to try a couple of times to get it right. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
On 06/07/2012 03:48 PM, Les Mikesell wrote: On Thu, Jun 7, 2012 at 4:48 PM, Scott Silva ssi...@sgvwater.com wrote: In older versions sdb would become sda, but I don't have enough time on the 6 series to know for sure... Maybe I will fire up a virtual machine with a couple emulated sata drives and see Sda/sdb are the kernel's conventions. What matters is what bios sees. And that may be different depending not only on the hardware but also the failure mode - sometimes a drive will fail but not really disappear from detection and it is hard to emulate that. Also, back in ATA days it was pretty common for a failed drive to lock both channels on the controller. As long as you have physical access to the box you can fix it fairly quickly by booting a rescue iso and re-installing grub, even if you have to try a couple of times to get it right. And if the server is colocated, but you have remote console access, you can leave a recovery CD in the drive, but set the boot order to boot the hard drive and then remotely change the boot order if you have problems. Nataraj ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] 75% - 80% Rebuild Complete
First I want to thank all of you who responded to me both on this list and in the CentOS wiki. Your responses helped greatly! I want to say that if you are running CentOS 5 and you do not have a overriding reason to go to CentOS 6, stay where you are. It was so much easier installing CentOS 6 on a new machine, migrating is next to impossible. Here's where I am today: 1. The base DVD install would not allow me to run the gnome desktop at 1920x1080 resolution with the default nVidia driver, the highest resolution I could obtain was 1024x768. However the text screen worked just fine after I introduced the video=1920x1080 in the grub.conf file. 2. When I installed the nVidia closed source drivers, the gnome desktop ran perfectly in the high resolution mode. The text mode then dropped to 1024x768 even though it retained the video=1920x1080 parameter (could it be those blacklist parameters introduced to disable the noveau drivers?). 3. During the installation I instituted software raid-1 along with LVM. It all worked perfectly until I got to the Boot Loader screen and instead of using the default (/dev/sda) I used what I thought would work in a raid-1 environment IF one of the hard drives went bad. I chose to install the boot loader in /dev/md0. Of course it would not boot. I recovered from this by going through the install and choosing to upgrade a existing installation and it allowed me to place the boot loader in /dev/sda. What that leaves me with is a raid-1 environment that works great as long as /dev/sda remains. How do I fix that??? 4. I still need to add all of those extra repositories (adobe; webmin; rpmfusion; etc). 5. I'm still trying to decide if I want a high resolution text screen (that I would use almost everyday) or a high resolution GUI screen (that I'll only use for certain application installs)??? At my 'real' job, we use RHEL and we've done some things using RHEL 6.2 for POC (Proof Of Concept) projects. With a POC, we install using a standard installation DVD (as opposed to using our RH Satellite Server). All of this to say that there are application installation options that really fit the needs of a server installation, you can choose 'Server' and 'Server GUI', which installs the gnome GUI without selecting a desktop environment.. Some things we run require a GUI to install (Oracle DB; IBM DB2 UDB; IBM WebSphere; etc.). How do I select this type of environment using CentOS 6.2? In other words, I'm running CentOS 6.2 x86_64 Desktop TIA, Gene Poole + It's impossible for everything to be true. + ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
On Tue, Jun 5, 2012 at 9:47 AM, Gene Poole gene.po...@macys.com wrote: 3. During the installation I instituted software raid-1 along with LVM. It all worked perfectly until I got to the Boot Loader screen and instead of using the default (/dev/sda) I used what I thought would work in a raid-1 environment IF one of the hard drives went bad. I chose to install the boot loader in /dev/md0. Of course it would not boot. I recovered from this by going through the install and choosing to upgrade a existing installation and it allowed me to place the boot loader in /dev/sda. What that leaves me with is a raid-1 environment that works great as long as /dev/sda remains. How do I fix that??? The MBR isn't mirrored, so you just have to install grub on the other drive, usually by executing grub, then: grub root (hd1,0) grub setup (hd1) but the numbers depend on how bios sees the alternate drive when the primary dies. It is always a good idea to practice re-installing grub from an install disk booted in rescue mode so you know how to fix things even if you have to move your mirror disk into the primary position to make it boot. 5. I'm still trying to decide if I want a high resolution text screen (that I would use almost everyday) or a high resolution GUI screen (that I'll only use for certain application installs)??? If you sit at the machine, you probably want a high res gui and to do text work in terminal windows. If you don't sit at the machine you probably don't even want X installed for the console. Run freenx for occasional (or even regular) remote GUI access, or use ssh with X forwarding for single GUI applications at a time. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
OK, I'm about 90% sure that I've corrected the boot loader situation with RAID-1 and the second hard drive. I haven't tested the correction, but here's what I did: Examined the grub.conf file and noticed that hd0 uses (hd0,1), so what followed was grub grub device (hd1) /dev/sdc grub root (hd1,1) grub setup (hd1) after receiving the successful message grub quit I didn't rebuild the boot loader on /dev/sda because it is working (if it ain't broke don't fix it). My situation is that I'm using 4 - 1 TB hard drives and I used the following pattern: /dev/sda | /dev/sdc = First Raid -1 volume /dev/sdb | /dev/sdd = Second Raid-1 volume Thanks all for the suggestions and thoughts! Gene ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 75% - 80% Rebuild Complete
On 5.6.2012 17:15, Les Mikesell wrote: On Tue, Jun 5, 2012 at 9:47 AM, Gene Poole gene.poole-swiuadtplfgavxtiumw...@public.gmane.org wrote: 3. During the installation I instituted software raid-1 along with LVM. It all worked perfectly until I got to the Boot Loader screen and instead of using the default (/dev/sda) I used what I thought would work in a raid-1 environment IF one of the hard drives went bad. I chose to install the boot loader in /dev/md0. Of course it would not boot. I recovered from this by going through the install and choosing to upgrade a existing installation and it allowed me to place the boot loader in /dev/sda. What that leaves me with is a raid-1 environment that works great as long as /dev/sda remains. How do I fix that??? The MBR isn't mirrored, so you just have to install grub on the other drive, usually by executing grub There is an open bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=799501 I am irritated regularly about this. Because It WORKSFORME. Of course the mbr isn't mirrored but at installation time it is written to both disks. I wipe the mbr of sdb, reinstall and after that $ dd if=/dev/sdb count=1 bs=512|strings shows something like GRUB, on *both disks* in /root/anaconda-ks.cfg I find bootloader --location=mbr --driveorder=sda,sdb ... in the original kickstart there is bootloader --location=mbr ... I did it per kickstart, is this a problem with manual installs only? Or only with upgrade mode (Gene said he used upgrade mode)? But then again there is this bugzilla... -- Kind Regards, Markus Falb signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
