Fedora 16 fails to boot after Win7 installed a GPT Drive












1















So, I have Windows 7 and Fedora 16 installed on my old HDD. Everything worked well and fine before I've had my new 3TB drive built in, which I initialized as GPT in Windows. Actually I initialized 1,5TB - the rest remains untouched.



After that Fedora won't boot up anymore. Instead it prompts me to maintenance mode, showing something like:



[...]/sbin/blkid -o udev -p /dev/sda[number] [...] terminated by signal 15 (Terminated)


Whenever I press Ctrl+D it shows one or multiple messages similar to that. Using



parted /dev/sdb print


shows that the drive as such is recognized as GPT. It also shows up in /etc/fstab. Using older kernels results in the same problem.



What should I do ?



Edit: I initialized the remaining ~1,5TB in Windows - nothing changed.










share|improve this question

























  • Now's a great time to upgrade to Fedora 17.

    – Michael Hampton
    Sep 1 '12 at 6:17
















1















So, I have Windows 7 and Fedora 16 installed on my old HDD. Everything worked well and fine before I've had my new 3TB drive built in, which I initialized as GPT in Windows. Actually I initialized 1,5TB - the rest remains untouched.



After that Fedora won't boot up anymore. Instead it prompts me to maintenance mode, showing something like:



[...]/sbin/blkid -o udev -p /dev/sda[number] [...] terminated by signal 15 (Terminated)


Whenever I press Ctrl+D it shows one or multiple messages similar to that. Using



parted /dev/sdb print


shows that the drive as such is recognized as GPT. It also shows up in /etc/fstab. Using older kernels results in the same problem.



What should I do ?



Edit: I initialized the remaining ~1,5TB in Windows - nothing changed.










share|improve this question

























  • Now's a great time to upgrade to Fedora 17.

    – Michael Hampton
    Sep 1 '12 at 6:17














1












1








1








So, I have Windows 7 and Fedora 16 installed on my old HDD. Everything worked well and fine before I've had my new 3TB drive built in, which I initialized as GPT in Windows. Actually I initialized 1,5TB - the rest remains untouched.



After that Fedora won't boot up anymore. Instead it prompts me to maintenance mode, showing something like:



[...]/sbin/blkid -o udev -p /dev/sda[number] [...] terminated by signal 15 (Terminated)


Whenever I press Ctrl+D it shows one or multiple messages similar to that. Using



parted /dev/sdb print


shows that the drive as such is recognized as GPT. It also shows up in /etc/fstab. Using older kernels results in the same problem.



What should I do ?



Edit: I initialized the remaining ~1,5TB in Windows - nothing changed.










share|improve this question
















So, I have Windows 7 and Fedora 16 installed on my old HDD. Everything worked well and fine before I've had my new 3TB drive built in, which I initialized as GPT in Windows. Actually I initialized 1,5TB - the rest remains untouched.



After that Fedora won't boot up anymore. Instead it prompts me to maintenance mode, showing something like:



[...]/sbin/blkid -o udev -p /dev/sda[number] [...] terminated by signal 15 (Terminated)


Whenever I press Ctrl+D it shows one or multiple messages similar to that. Using



parted /dev/sdb print


shows that the drive as such is recognized as GPT. It also shows up in /etc/fstab. Using older kernels results in the same problem.



What should I do ?



Edit: I initialized the remaining ~1,5TB in Windows - nothing changed.







linux fedora boot windows gpt






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 1 '12 at 5:18







tesseract

















asked Aug 31 '12 at 21:34









tesseracttesseract

18438




18438













  • Now's a great time to upgrade to Fedora 17.

    – Michael Hampton
    Sep 1 '12 at 6:17



















  • Now's a great time to upgrade to Fedora 17.

    – Michael Hampton
    Sep 1 '12 at 6:17

















Now's a great time to upgrade to Fedora 17.

– Michael Hampton
Sep 1 '12 at 6:17





Now's a great time to upgrade to Fedora 17.

– Michael Hampton
Sep 1 '12 at 6:17










2 Answers
2






active

oldest

votes


















1














I'd try rebuilding the initial ramdisk:



/sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --update `uname -r`


Failing that, I'd probably give up and update to F17, which should sort out the problem as well.






share|improve this answer
























  • Thank you for your input, I guess it really is a good idea to upgrade now.

    – tesseract
    Sep 2 '12 at 12:59



















0














Try reinstall, but reverse the order. Install Win7 first, then Fedora. This method has worked for me. Including Win7 and Win10.
Good Luck!
30years






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f46847%2ffedora-16-fails-to-boot-after-win7-installed-a-gpt-drive%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    I'd try rebuilding the initial ramdisk:



    /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --update `uname -r`


    Failing that, I'd probably give up and update to F17, which should sort out the problem as well.






    share|improve this answer
























    • Thank you for your input, I guess it really is a good idea to upgrade now.

      – tesseract
      Sep 2 '12 at 12:59
















    1














    I'd try rebuilding the initial ramdisk:



    /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --update `uname -r`


    Failing that, I'd probably give up and update to F17, which should sort out the problem as well.






    share|improve this answer
























    • Thank you for your input, I guess it really is a good idea to upgrade now.

      – tesseract
      Sep 2 '12 at 12:59














    1












    1








    1







    I'd try rebuilding the initial ramdisk:



    /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --update `uname -r`


    Failing that, I'd probably give up and update to F17, which should sort out the problem as well.






    share|improve this answer













    I'd try rebuilding the initial ramdisk:



    /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --update `uname -r`


    Failing that, I'd probably give up and update to F17, which should sort out the problem as well.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Sep 1 '12 at 6:19









    Michael HamptonMichael Hampton

    5,87412044




    5,87412044













    • Thank you for your input, I guess it really is a good idea to upgrade now.

      – tesseract
      Sep 2 '12 at 12:59



















    • Thank you for your input, I guess it really is a good idea to upgrade now.

      – tesseract
      Sep 2 '12 at 12:59

















    Thank you for your input, I guess it really is a good idea to upgrade now.

    – tesseract
    Sep 2 '12 at 12:59





    Thank you for your input, I guess it really is a good idea to upgrade now.

    – tesseract
    Sep 2 '12 at 12:59













    0














    Try reinstall, but reverse the order. Install Win7 first, then Fedora. This method has worked for me. Including Win7 and Win10.
    Good Luck!
    30years






    share|improve this answer




























      0














      Try reinstall, but reverse the order. Install Win7 first, then Fedora. This method has worked for me. Including Win7 and Win10.
      Good Luck!
      30years






      share|improve this answer


























        0












        0








        0







        Try reinstall, but reverse the order. Install Win7 first, then Fedora. This method has worked for me. Including Win7 and Win10.
        Good Luck!
        30years






        share|improve this answer













        Try reinstall, but reverse the order. Install Win7 first, then Fedora. This method has worked for me. Including Win7 and Win10.
        Good Luck!
        30years







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 19 at 18:22









        Mike30-yearsMike30-years

        11




        11






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f46847%2ffedora-16-fails-to-boot-after-win7-installed-a-gpt-drive%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

            How to make a Squid Proxy server?

            Is this a new Fibonacci Identity?

            19世紀