GRUB installing CentOS 7 on CentOS 6 machine with kickstartMultiple RAID controllers plus SAN volumes during CentOS 5 kickstart installCentOS Install - Starting a Kickstartcentos 6.2 grub fails with a black screen with a blinking cursor, but works when manually entering boot command linegrub always will boot to grub command lineWhich vmlinuz and initrd.img should I use for 'headless' CentOS installation?Stuck at grub prompt after a default CentOS 6 installationCloudlinux, GRUB 0.97, software RAID, won't automatically bootNetwork Kickstart RHEL 5 vs Kickstart RHEL 6, vmlinuz doesn't support nameservers?CentOS 7 kickstart hangsinstall centos from USB

How can one's career as a reviewer be ended?

Do you really need a KDF when you have a PRF?

Analogy between an unknown in an argument, and a contradiction in the principle of explosion

How (un)safe is it to ride barefoot?

Tikz-cd diagram arrow passing under a node - not crossing it

Should I refuse to be named as co-author of a low quality paper?

How to avoid typing 'git' at the begining of every Git command

Oil draining out shortly after turbo hose detached/broke

What should I discuss with my DM prior to my first game?

Should I put programming books I wrote a few years ago on my resume?

NUL delimited variable

Grep Match and extract

Wizard clothing for warm weather

So a part of my house disappeared... But not because of a chunk resetting

Why do radiation hardened IC packages often have long leads?

Razzle Dazzle simulator

What STL algorithm can determine if exactly one item in a container satisfies a predicate?

How was the airlock installed on the Space Shuttle mid deck?

What do you call the action of "describing events as they happen" like sports anchors do?

How to befriend someone who doesn't like to talk?

Do you have to have figures when playing D&D?

That's not my X, its Y is too Z

Does the Nuka-Cola bottler actually generate nuka cola?

How to write a convincing religious myth?



GRUB installing CentOS 7 on CentOS 6 machine with kickstart


Multiple RAID controllers plus SAN volumes during CentOS 5 kickstart installCentOS Install - Starting a Kickstartcentos 6.2 grub fails with a black screen with a blinking cursor, but works when manually entering boot command linegrub always will boot to grub command lineWhich vmlinuz and initrd.img should I use for 'headless' CentOS installation?Stuck at grub prompt after a default CentOS 6 installationCloudlinux, GRUB 0.97, software RAID, won't automatically bootNetwork Kickstart RHEL 5 vs Kickstart RHEL 6, vmlinuz doesn't support nameservers?CentOS 7 kickstart hangsinstall centos from USB






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















I am wondering if someone can provide some help. I am trying to do an automated install (with kickstart file) with CentOS 7 on a CentOS 6 server.
However I have failed multiple times so far. I did Google on it, but no such luck...



The latest source, which explains exactly what I am trying to do is located here.



So what did I do? I first downloaded the CentOS 7 vmlinuz and initrd.img files to /boot/



curl -o /boot/vmlinuz http://mirror.zetup.net/CentOS/7/os/x86_64/isolinux/vmlinuz
curl -o /boot/initrd.img http://mirror.zetup.net/CentOS/7/os/x86_64/isolinux/initrd.img


After that I edited the grub.conf with "vi /boot/grub/grub.conf" and added:



title Install CentOS 7
kernel /vmlinuz ks=http://my-server-ip/installation.ks
initrd /initrd.img


Sidenote: yes, I tested the IP from the server with the current CentOS 6 version and I could download/open it.



So in the end my grub.conf looked like this:



default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Install CentOS 7
kernel /vmlinuz http://my-server-ip/installation.ks
initrd /initrd.img
[older entries below]


and I also tried:



default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Install CentOS 7
kernel /boot/vmlinuz http://my-server-ip/installation.ks
initrd /boot/initrd.img
[older entries below]


Both ways fail for some reason. I had to physically check the server and I saw either of the following errors:



Error 1:



Error 15: File not found
Press any key to continue...


Error 2:



Error 1: Filename must be either an absolute pathname or blocklist
Press any key to continue...


Sorry, but I don't recall which error I received on which approach anymore.



There is one small / minor change to everything above. Instead of using CentOS 7 vmlinuz and initrd.img files, I used the ones from the OpenVZ 7 iso.
Both files were located under the folder: /images/pxeboot/



The reason for this is that I want to install OpenVZ 7 on the server (so removing the current CentOS 6 version and replacing it with a clean, but kickstarted OpenVZ 7 version). I doubt the vmlinuz and initrd.img files are that different, so that it results in the above errors, right?



The kickstart file I created works. This was tested with PXE boot (on several different servers), however I want to be able to also install CentOS 7 or OpenVZ 7 (preferred) through the GRUB loader. This should be possible right?



Maybe I missed something, somewhere? Maybe someone has an idea what I am doing wrong or what I can try?



In the meantime I will retry again, but use the files from CentOS 7. I doubt that's the issue, but worth a shot anywas....



My test server specifications (dunno if it's important):




  • LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 (RAID controller)

  • 2x HDD's in RAID 1

  • Running currently on CentOS 6.10 (Final)



The below might be related (sorry for the complete mess in this post, I am trying to be as detailed as possible).
While I was typing the above server specifications I noticed a "similar" issue with a PXE boot machine with the same RAID controller card. Maybe that's the issue? Since I was fed up with failing the installation of OpenVZ 7, I decided to an automated kickstart with PXE (which worked on other serves). Mind you, this is another / different server, which has the same RAID card, however it was flashed to IT-mode and only has one (older) 400GB SAS SSD from Toshiba installed.



Anyways, running the automated installation (through the kickstart file) I noticed the server was hanging after I connected a monitor to it with the following (last) errors:



dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
x many more and followed by:
dracut-initqueue[723]: Warning: Could not boot
dracut-initqueue[723]: Warning: /dev/root does not exist


At this point I was like okay. You know what? I will do a manual installation of OpenVZ 7 through the PXE boot (I have an option for that).



So rebooted the server again, waited till it presented me the GRUB 2 menu (through the PXE server) and selected the manual install.
I reached the menu and wanted to select the disk to install OpenVZ 7 on it. Now to my "surprise" it didn't find any drives!? So it could not continue the installation obviously. No matter how often I clicked "Rescan", no drives... At all...!



I have no clue what the issue is. But maybe it's the RAID controller being unsupported in CentOS 7 / OpenVZ 7? This one was flashed (orignally a PERC H200 Dell RAID controller, which equals a LSI-9211-8i) to IT-mode with a single Toshiba 400 GB SAS SSD connected to it (which is been seen by the controller during posting). So maybe this is the whole issue? Maybe someone knows?



I didn't notice the same controller until I typed server specifications above. Though one is IT-mode and the other one is in regular RAID 1 mode. So I tempted to think it's the controller, but then again the LSI-9211-8i is widely supported by all OS and versions, as far as I can tell. Even the current CentOS 6.x installation on it has no issues with it apparently?



Thanks in advance. And sorry for the big / detailed post.



Regards










share|improve this question




























    0















    I am wondering if someone can provide some help. I am trying to do an automated install (with kickstart file) with CentOS 7 on a CentOS 6 server.
    However I have failed multiple times so far. I did Google on it, but no such luck...



    The latest source, which explains exactly what I am trying to do is located here.



    So what did I do? I first downloaded the CentOS 7 vmlinuz and initrd.img files to /boot/



    curl -o /boot/vmlinuz http://mirror.zetup.net/CentOS/7/os/x86_64/isolinux/vmlinuz
    curl -o /boot/initrd.img http://mirror.zetup.net/CentOS/7/os/x86_64/isolinux/initrd.img


    After that I edited the grub.conf with "vi /boot/grub/grub.conf" and added:



    title Install CentOS 7
    kernel /vmlinuz ks=http://my-server-ip/installation.ks
    initrd /initrd.img


    Sidenote: yes, I tested the IP from the server with the current CentOS 6 version and I could download/open it.



    So in the end my grub.conf looked like this:



    default=0
    timeout=5
    splashimage=(hd0,0)/boot/grub/splash.xpm.gz
    hiddenmenu
    title Install CentOS 7
    kernel /vmlinuz http://my-server-ip/installation.ks
    initrd /initrd.img
    [older entries below]


    and I also tried:



    default=0
    timeout=5
    splashimage=(hd0,0)/boot/grub/splash.xpm.gz
    hiddenmenu
    title Install CentOS 7
    kernel /boot/vmlinuz http://my-server-ip/installation.ks
    initrd /boot/initrd.img
    [older entries below]


    Both ways fail for some reason. I had to physically check the server and I saw either of the following errors:



    Error 1:



    Error 15: File not found
    Press any key to continue...


    Error 2:



    Error 1: Filename must be either an absolute pathname or blocklist
    Press any key to continue...


    Sorry, but I don't recall which error I received on which approach anymore.



    There is one small / minor change to everything above. Instead of using CentOS 7 vmlinuz and initrd.img files, I used the ones from the OpenVZ 7 iso.
    Both files were located under the folder: /images/pxeboot/



    The reason for this is that I want to install OpenVZ 7 on the server (so removing the current CentOS 6 version and replacing it with a clean, but kickstarted OpenVZ 7 version). I doubt the vmlinuz and initrd.img files are that different, so that it results in the above errors, right?



    The kickstart file I created works. This was tested with PXE boot (on several different servers), however I want to be able to also install CentOS 7 or OpenVZ 7 (preferred) through the GRUB loader. This should be possible right?



    Maybe I missed something, somewhere? Maybe someone has an idea what I am doing wrong or what I can try?



    In the meantime I will retry again, but use the files from CentOS 7. I doubt that's the issue, but worth a shot anywas....



    My test server specifications (dunno if it's important):




    • LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 (RAID controller)

    • 2x HDD's in RAID 1

    • Running currently on CentOS 6.10 (Final)



    The below might be related (sorry for the complete mess in this post, I am trying to be as detailed as possible).
    While I was typing the above server specifications I noticed a "similar" issue with a PXE boot machine with the same RAID controller card. Maybe that's the issue? Since I was fed up with failing the installation of OpenVZ 7, I decided to an automated kickstart with PXE (which worked on other serves). Mind you, this is another / different server, which has the same RAID card, however it was flashed to IT-mode and only has one (older) 400GB SAS SSD from Toshiba installed.



    Anyways, running the automated installation (through the kickstart file) I noticed the server was hanging after I connected a monitor to it with the following (last) errors:



    dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
    dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
    dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
    x many more and followed by:
    dracut-initqueue[723]: Warning: Could not boot
    dracut-initqueue[723]: Warning: /dev/root does not exist


    At this point I was like okay. You know what? I will do a manual installation of OpenVZ 7 through the PXE boot (I have an option for that).



    So rebooted the server again, waited till it presented me the GRUB 2 menu (through the PXE server) and selected the manual install.
    I reached the menu and wanted to select the disk to install OpenVZ 7 on it. Now to my "surprise" it didn't find any drives!? So it could not continue the installation obviously. No matter how often I clicked "Rescan", no drives... At all...!



    I have no clue what the issue is. But maybe it's the RAID controller being unsupported in CentOS 7 / OpenVZ 7? This one was flashed (orignally a PERC H200 Dell RAID controller, which equals a LSI-9211-8i) to IT-mode with a single Toshiba 400 GB SAS SSD connected to it (which is been seen by the controller during posting). So maybe this is the whole issue? Maybe someone knows?



    I didn't notice the same controller until I typed server specifications above. Though one is IT-mode and the other one is in regular RAID 1 mode. So I tempted to think it's the controller, but then again the LSI-9211-8i is widely supported by all OS and versions, as far as I can tell. Even the current CentOS 6.x installation on it has no issues with it apparently?



    Thanks in advance. And sorry for the big / detailed post.



    Regards










    share|improve this question
























      0












      0








      0


      1






      I am wondering if someone can provide some help. I am trying to do an automated install (with kickstart file) with CentOS 7 on a CentOS 6 server.
      However I have failed multiple times so far. I did Google on it, but no such luck...



      The latest source, which explains exactly what I am trying to do is located here.



      So what did I do? I first downloaded the CentOS 7 vmlinuz and initrd.img files to /boot/



      curl -o /boot/vmlinuz http://mirror.zetup.net/CentOS/7/os/x86_64/isolinux/vmlinuz
      curl -o /boot/initrd.img http://mirror.zetup.net/CentOS/7/os/x86_64/isolinux/initrd.img


      After that I edited the grub.conf with "vi /boot/grub/grub.conf" and added:



      title Install CentOS 7
      kernel /vmlinuz ks=http://my-server-ip/installation.ks
      initrd /initrd.img


      Sidenote: yes, I tested the IP from the server with the current CentOS 6 version and I could download/open it.



      So in the end my grub.conf looked like this:



      default=0
      timeout=5
      splashimage=(hd0,0)/boot/grub/splash.xpm.gz
      hiddenmenu
      title Install CentOS 7
      kernel /vmlinuz http://my-server-ip/installation.ks
      initrd /initrd.img
      [older entries below]


      and I also tried:



      default=0
      timeout=5
      splashimage=(hd0,0)/boot/grub/splash.xpm.gz
      hiddenmenu
      title Install CentOS 7
      kernel /boot/vmlinuz http://my-server-ip/installation.ks
      initrd /boot/initrd.img
      [older entries below]


      Both ways fail for some reason. I had to physically check the server and I saw either of the following errors:



      Error 1:



      Error 15: File not found
      Press any key to continue...


      Error 2:



      Error 1: Filename must be either an absolute pathname or blocklist
      Press any key to continue...


      Sorry, but I don't recall which error I received on which approach anymore.



      There is one small / minor change to everything above. Instead of using CentOS 7 vmlinuz and initrd.img files, I used the ones from the OpenVZ 7 iso.
      Both files were located under the folder: /images/pxeboot/



      The reason for this is that I want to install OpenVZ 7 on the server (so removing the current CentOS 6 version and replacing it with a clean, but kickstarted OpenVZ 7 version). I doubt the vmlinuz and initrd.img files are that different, so that it results in the above errors, right?



      The kickstart file I created works. This was tested with PXE boot (on several different servers), however I want to be able to also install CentOS 7 or OpenVZ 7 (preferred) through the GRUB loader. This should be possible right?



      Maybe I missed something, somewhere? Maybe someone has an idea what I am doing wrong or what I can try?



      In the meantime I will retry again, but use the files from CentOS 7. I doubt that's the issue, but worth a shot anywas....



      My test server specifications (dunno if it's important):




      • LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 (RAID controller)

      • 2x HDD's in RAID 1

      • Running currently on CentOS 6.10 (Final)



      The below might be related (sorry for the complete mess in this post, I am trying to be as detailed as possible).
      While I was typing the above server specifications I noticed a "similar" issue with a PXE boot machine with the same RAID controller card. Maybe that's the issue? Since I was fed up with failing the installation of OpenVZ 7, I decided to an automated kickstart with PXE (which worked on other serves). Mind you, this is another / different server, which has the same RAID card, however it was flashed to IT-mode and only has one (older) 400GB SAS SSD from Toshiba installed.



      Anyways, running the automated installation (through the kickstart file) I noticed the server was hanging after I connected a monitor to it with the following (last) errors:



      dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
      dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
      dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
      x many more and followed by:
      dracut-initqueue[723]: Warning: Could not boot
      dracut-initqueue[723]: Warning: /dev/root does not exist


      At this point I was like okay. You know what? I will do a manual installation of OpenVZ 7 through the PXE boot (I have an option for that).



      So rebooted the server again, waited till it presented me the GRUB 2 menu (through the PXE server) and selected the manual install.
      I reached the menu and wanted to select the disk to install OpenVZ 7 on it. Now to my "surprise" it didn't find any drives!? So it could not continue the installation obviously. No matter how often I clicked "Rescan", no drives... At all...!



      I have no clue what the issue is. But maybe it's the RAID controller being unsupported in CentOS 7 / OpenVZ 7? This one was flashed (orignally a PERC H200 Dell RAID controller, which equals a LSI-9211-8i) to IT-mode with a single Toshiba 400 GB SAS SSD connected to it (which is been seen by the controller during posting). So maybe this is the whole issue? Maybe someone knows?



      I didn't notice the same controller until I typed server specifications above. Though one is IT-mode and the other one is in regular RAID 1 mode. So I tempted to think it's the controller, but then again the LSI-9211-8i is widely supported by all OS and versions, as far as I can tell. Even the current CentOS 6.x installation on it has no issues with it apparently?



      Thanks in advance. And sorry for the big / detailed post.



      Regards










      share|improve this question














      I am wondering if someone can provide some help. I am trying to do an automated install (with kickstart file) with CentOS 7 on a CentOS 6 server.
      However I have failed multiple times so far. I did Google on it, but no such luck...



      The latest source, which explains exactly what I am trying to do is located here.



      So what did I do? I first downloaded the CentOS 7 vmlinuz and initrd.img files to /boot/



      curl -o /boot/vmlinuz http://mirror.zetup.net/CentOS/7/os/x86_64/isolinux/vmlinuz
      curl -o /boot/initrd.img http://mirror.zetup.net/CentOS/7/os/x86_64/isolinux/initrd.img


      After that I edited the grub.conf with "vi /boot/grub/grub.conf" and added:



      title Install CentOS 7
      kernel /vmlinuz ks=http://my-server-ip/installation.ks
      initrd /initrd.img


      Sidenote: yes, I tested the IP from the server with the current CentOS 6 version and I could download/open it.



      So in the end my grub.conf looked like this:



      default=0
      timeout=5
      splashimage=(hd0,0)/boot/grub/splash.xpm.gz
      hiddenmenu
      title Install CentOS 7
      kernel /vmlinuz http://my-server-ip/installation.ks
      initrd /initrd.img
      [older entries below]


      and I also tried:



      default=0
      timeout=5
      splashimage=(hd0,0)/boot/grub/splash.xpm.gz
      hiddenmenu
      title Install CentOS 7
      kernel /boot/vmlinuz http://my-server-ip/installation.ks
      initrd /boot/initrd.img
      [older entries below]


      Both ways fail for some reason. I had to physically check the server and I saw either of the following errors:



      Error 1:



      Error 15: File not found
      Press any key to continue...


      Error 2:



      Error 1: Filename must be either an absolute pathname or blocklist
      Press any key to continue...


      Sorry, but I don't recall which error I received on which approach anymore.



      There is one small / minor change to everything above. Instead of using CentOS 7 vmlinuz and initrd.img files, I used the ones from the OpenVZ 7 iso.
      Both files were located under the folder: /images/pxeboot/



      The reason for this is that I want to install OpenVZ 7 on the server (so removing the current CentOS 6 version and replacing it with a clean, but kickstarted OpenVZ 7 version). I doubt the vmlinuz and initrd.img files are that different, so that it results in the above errors, right?



      The kickstart file I created works. This was tested with PXE boot (on several different servers), however I want to be able to also install CentOS 7 or OpenVZ 7 (preferred) through the GRUB loader. This should be possible right?



      Maybe I missed something, somewhere? Maybe someone has an idea what I am doing wrong or what I can try?



      In the meantime I will retry again, but use the files from CentOS 7. I doubt that's the issue, but worth a shot anywas....



      My test server specifications (dunno if it's important):




      • LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 (RAID controller)

      • 2x HDD's in RAID 1

      • Running currently on CentOS 6.10 (Final)



      The below might be related (sorry for the complete mess in this post, I am trying to be as detailed as possible).
      While I was typing the above server specifications I noticed a "similar" issue with a PXE boot machine with the same RAID controller card. Maybe that's the issue? Since I was fed up with failing the installation of OpenVZ 7, I decided to an automated kickstart with PXE (which worked on other serves). Mind you, this is another / different server, which has the same RAID card, however it was flashed to IT-mode and only has one (older) 400GB SAS SSD from Toshiba installed.



      Anyways, running the automated installation (through the kickstart file) I noticed the server was hanging after I connected a monitor to it with the following (last) errors:



      dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
      dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
      dracut-initqueue[723]: Warning: dracut-initqueue timeout - starting timeout scripts
      x many more and followed by:
      dracut-initqueue[723]: Warning: Could not boot
      dracut-initqueue[723]: Warning: /dev/root does not exist


      At this point I was like okay. You know what? I will do a manual installation of OpenVZ 7 through the PXE boot (I have an option for that).



      So rebooted the server again, waited till it presented me the GRUB 2 menu (through the PXE server) and selected the manual install.
      I reached the menu and wanted to select the disk to install OpenVZ 7 on it. Now to my "surprise" it didn't find any drives!? So it could not continue the installation obviously. No matter how often I clicked "Rescan", no drives... At all...!



      I have no clue what the issue is. But maybe it's the RAID controller being unsupported in CentOS 7 / OpenVZ 7? This one was flashed (orignally a PERC H200 Dell RAID controller, which equals a LSI-9211-8i) to IT-mode with a single Toshiba 400 GB SAS SSD connected to it (which is been seen by the controller during posting). So maybe this is the whole issue? Maybe someone knows?



      I didn't notice the same controller until I typed server specifications above. Though one is IT-mode and the other one is in regular RAID 1 mode. So I tempted to think it's the controller, but then again the LSI-9211-8i is widely supported by all OS and versions, as far as I can tell. Even the current CentOS 6.x installation on it has no issues with it apparently?



      Thanks in advance. And sorry for the big / detailed post.



      Regards







      centos grub kickstart






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 27 at 6:45









      HudsonHawkHudsonHawk

      64




      64




















          1 Answer
          1






          active

          oldest

          votes


















          0














          Your grub.conf doesn't specify a root so it has no idea from which drive or partition to load the files vmlinuz and initrd.img.



          You are also missing inst.ks= in front of the URL.



          Instead of trying to do a hard drive boot, boot from CentOS 7 installation media and specify inst.ks=<URL> on the boot command line.






          share|improve this answer























          • Thank you for taking tht time to answer. But if I want to install remotely (without physical access to the server) can I still install CentOS 7 on this server? For example load the CentOS 7.x installation remotely? That's what I am trying to achieve. In the provided link it shows it's possible? But I am failing, no matter what I try?

            – HudsonHawk
            May 27 at 7:23











          • " install remotely (without physical access to the server)" - that's why most enterprise server systems come equipped with a built in an out-of-band management console, relying on the currently installed OS to install a replacement can be tricky, as you already experience

            – HBruijn
            May 27 at 7:32











          • Yeah, but that does actually require a connection to the management port, which I don't have unfortunately. Anyways, I looked again at Michael's answer and I edited the grub.conf to this: title Install CentOS 7 root (hd0,0) kernel /boot/vmlinuz inst.ks=server-ip/openvz7/example.ks initrd /boot/initrd.img

            – HudsonHawk
            May 27 at 7:43












          • A proper out of band management system would allow you to use installation media such as ISO images which are on your own computer. Inserting physical media into the server is not necessary.

            – Michael Hampton
            May 27 at 16:46











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "2"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f968932%2fgrub-installing-centos-7-on-centos-6-machine-with-kickstart%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          Your grub.conf doesn't specify a root so it has no idea from which drive or partition to load the files vmlinuz and initrd.img.



          You are also missing inst.ks= in front of the URL.



          Instead of trying to do a hard drive boot, boot from CentOS 7 installation media and specify inst.ks=<URL> on the boot command line.






          share|improve this answer























          • Thank you for taking tht time to answer. But if I want to install remotely (without physical access to the server) can I still install CentOS 7 on this server? For example load the CentOS 7.x installation remotely? That's what I am trying to achieve. In the provided link it shows it's possible? But I am failing, no matter what I try?

            – HudsonHawk
            May 27 at 7:23











          • " install remotely (without physical access to the server)" - that's why most enterprise server systems come equipped with a built in an out-of-band management console, relying on the currently installed OS to install a replacement can be tricky, as you already experience

            – HBruijn
            May 27 at 7:32











          • Yeah, but that does actually require a connection to the management port, which I don't have unfortunately. Anyways, I looked again at Michael's answer and I edited the grub.conf to this: title Install CentOS 7 root (hd0,0) kernel /boot/vmlinuz inst.ks=server-ip/openvz7/example.ks initrd /boot/initrd.img

            – HudsonHawk
            May 27 at 7:43












          • A proper out of band management system would allow you to use installation media such as ISO images which are on your own computer. Inserting physical media into the server is not necessary.

            – Michael Hampton
            May 27 at 16:46















          0














          Your grub.conf doesn't specify a root so it has no idea from which drive or partition to load the files vmlinuz and initrd.img.



          You are also missing inst.ks= in front of the URL.



          Instead of trying to do a hard drive boot, boot from CentOS 7 installation media and specify inst.ks=<URL> on the boot command line.






          share|improve this answer























          • Thank you for taking tht time to answer. But if I want to install remotely (without physical access to the server) can I still install CentOS 7 on this server? For example load the CentOS 7.x installation remotely? That's what I am trying to achieve. In the provided link it shows it's possible? But I am failing, no matter what I try?

            – HudsonHawk
            May 27 at 7:23











          • " install remotely (without physical access to the server)" - that's why most enterprise server systems come equipped with a built in an out-of-band management console, relying on the currently installed OS to install a replacement can be tricky, as you already experience

            – HBruijn
            May 27 at 7:32











          • Yeah, but that does actually require a connection to the management port, which I don't have unfortunately. Anyways, I looked again at Michael's answer and I edited the grub.conf to this: title Install CentOS 7 root (hd0,0) kernel /boot/vmlinuz inst.ks=server-ip/openvz7/example.ks initrd /boot/initrd.img

            – HudsonHawk
            May 27 at 7:43












          • A proper out of band management system would allow you to use installation media such as ISO images which are on your own computer. Inserting physical media into the server is not necessary.

            – Michael Hampton
            May 27 at 16:46













          0












          0








          0







          Your grub.conf doesn't specify a root so it has no idea from which drive or partition to load the files vmlinuz and initrd.img.



          You are also missing inst.ks= in front of the URL.



          Instead of trying to do a hard drive boot, boot from CentOS 7 installation media and specify inst.ks=<URL> on the boot command line.






          share|improve this answer













          Your grub.conf doesn't specify a root so it has no idea from which drive or partition to load the files vmlinuz and initrd.img.



          You are also missing inst.ks= in front of the URL.



          Instead of trying to do a hard drive boot, boot from CentOS 7 installation media and specify inst.ks=<URL> on the boot command line.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered May 27 at 7:11









          Michael HamptonMichael Hampton

          179k27329661




          179k27329661












          • Thank you for taking tht time to answer. But if I want to install remotely (without physical access to the server) can I still install CentOS 7 on this server? For example load the CentOS 7.x installation remotely? That's what I am trying to achieve. In the provided link it shows it's possible? But I am failing, no matter what I try?

            – HudsonHawk
            May 27 at 7:23











          • " install remotely (without physical access to the server)" - that's why most enterprise server systems come equipped with a built in an out-of-band management console, relying on the currently installed OS to install a replacement can be tricky, as you already experience

            – HBruijn
            May 27 at 7:32











          • Yeah, but that does actually require a connection to the management port, which I don't have unfortunately. Anyways, I looked again at Michael's answer and I edited the grub.conf to this: title Install CentOS 7 root (hd0,0) kernel /boot/vmlinuz inst.ks=server-ip/openvz7/example.ks initrd /boot/initrd.img

            – HudsonHawk
            May 27 at 7:43












          • A proper out of band management system would allow you to use installation media such as ISO images which are on your own computer. Inserting physical media into the server is not necessary.

            – Michael Hampton
            May 27 at 16:46

















          • Thank you for taking tht time to answer. But if I want to install remotely (without physical access to the server) can I still install CentOS 7 on this server? For example load the CentOS 7.x installation remotely? That's what I am trying to achieve. In the provided link it shows it's possible? But I am failing, no matter what I try?

            – HudsonHawk
            May 27 at 7:23











          • " install remotely (without physical access to the server)" - that's why most enterprise server systems come equipped with a built in an out-of-band management console, relying on the currently installed OS to install a replacement can be tricky, as you already experience

            – HBruijn
            May 27 at 7:32











          • Yeah, but that does actually require a connection to the management port, which I don't have unfortunately. Anyways, I looked again at Michael's answer and I edited the grub.conf to this: title Install CentOS 7 root (hd0,0) kernel /boot/vmlinuz inst.ks=server-ip/openvz7/example.ks initrd /boot/initrd.img

            – HudsonHawk
            May 27 at 7:43












          • A proper out of band management system would allow you to use installation media such as ISO images which are on your own computer. Inserting physical media into the server is not necessary.

            – Michael Hampton
            May 27 at 16:46
















          Thank you for taking tht time to answer. But if I want to install remotely (without physical access to the server) can I still install CentOS 7 on this server? For example load the CentOS 7.x installation remotely? That's what I am trying to achieve. In the provided link it shows it's possible? But I am failing, no matter what I try?

          – HudsonHawk
          May 27 at 7:23





          Thank you for taking tht time to answer. But if I want to install remotely (without physical access to the server) can I still install CentOS 7 on this server? For example load the CentOS 7.x installation remotely? That's what I am trying to achieve. In the provided link it shows it's possible? But I am failing, no matter what I try?

          – HudsonHawk
          May 27 at 7:23













          " install remotely (without physical access to the server)" - that's why most enterprise server systems come equipped with a built in an out-of-band management console, relying on the currently installed OS to install a replacement can be tricky, as you already experience

          – HBruijn
          May 27 at 7:32





          " install remotely (without physical access to the server)" - that's why most enterprise server systems come equipped with a built in an out-of-band management console, relying on the currently installed OS to install a replacement can be tricky, as you already experience

          – HBruijn
          May 27 at 7:32













          Yeah, but that does actually require a connection to the management port, which I don't have unfortunately. Anyways, I looked again at Michael's answer and I edited the grub.conf to this: title Install CentOS 7 root (hd0,0) kernel /boot/vmlinuz inst.ks=server-ip/openvz7/example.ks initrd /boot/initrd.img

          – HudsonHawk
          May 27 at 7:43






          Yeah, but that does actually require a connection to the management port, which I don't have unfortunately. Anyways, I looked again at Michael's answer and I edited the grub.conf to this: title Install CentOS 7 root (hd0,0) kernel /boot/vmlinuz inst.ks=server-ip/openvz7/example.ks initrd /boot/initrd.img

          – HudsonHawk
          May 27 at 7:43














          A proper out of band management system would allow you to use installation media such as ISO images which are on your own computer. Inserting physical media into the server is not necessary.

          – Michael Hampton
          May 27 at 16:46





          A proper out of band management system would allow you to use installation media such as ISO images which are on your own computer. Inserting physical media into the server is not necessary.

          – Michael Hampton
          May 27 at 16:46

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Server Fault!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f968932%2fgrub-installing-centos-7-on-centos-6-machine-with-kickstart%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

          Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

          What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company