kernel panic on /usr/bin/switch_root -d

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite
1












I use arch linux and after an update about a month ago I can't boot the system anymore.



The logs show a kernel panic caused by calling /usr/bin/switch_root with arg -d.



I've tried a live cd boot and chroot into the system, followed by another update, but no luck. Also tried renaming the initramfs-fallback.img (name probably not correct, I don't recall it perfectly) to initramfs.img. I read somewhere that this could be caused by the ram disk. Google wasn't very helpful on this specific problem, also.



whatever is calling switch_root seems to run after arch prints out the lines

:: Mounting '/dev/sdc4' on real root
:: Running cleanup hook [udev]



What do you guys think?



Kernel panic picture:
enter image description here










share|improve this question























  • The release notes for util-linux show no changes to switch_root for the last two releases, and there have been no Arch patches. Paste the full journal from a failed boot.
    – jasonwryan
    Nov 25 at 2:20










  • @jasonwryan I think it's this man: git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/…
    – Thomazella
    Nov 26 at 1:37










  • That would seem unlikely: this would be an issue affecting a lot more people. Please paste the actual journal.
    – jasonwryan
    Nov 26 at 1:47










  • @jasonwryan could you advise on pasting the journal, please? I booted to the live system, did a chroot into the old one, and read the output of journalctl, the last entries. It didn't look abnormal. Is that output what you want me to paste? I took a picture of the kernel panic at least.
    – Thomazella
    Nov 26 at 2:52






  • 1




    Paste the text, not a screenshot wiki.archlinux.org/index.php/…
    – jasonwryan
    Nov 26 at 3:02














up vote
0
down vote

favorite
1












I use arch linux and after an update about a month ago I can't boot the system anymore.



The logs show a kernel panic caused by calling /usr/bin/switch_root with arg -d.



I've tried a live cd boot and chroot into the system, followed by another update, but no luck. Also tried renaming the initramfs-fallback.img (name probably not correct, I don't recall it perfectly) to initramfs.img. I read somewhere that this could be caused by the ram disk. Google wasn't very helpful on this specific problem, also.



whatever is calling switch_root seems to run after arch prints out the lines

:: Mounting '/dev/sdc4' on real root
:: Running cleanup hook [udev]



What do you guys think?



Kernel panic picture:
enter image description here










share|improve this question























  • The release notes for util-linux show no changes to switch_root for the last two releases, and there have been no Arch patches. Paste the full journal from a failed boot.
    – jasonwryan
    Nov 25 at 2:20










  • @jasonwryan I think it's this man: git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/…
    – Thomazella
    Nov 26 at 1:37










  • That would seem unlikely: this would be an issue affecting a lot more people. Please paste the actual journal.
    – jasonwryan
    Nov 26 at 1:47










  • @jasonwryan could you advise on pasting the journal, please? I booted to the live system, did a chroot into the old one, and read the output of journalctl, the last entries. It didn't look abnormal. Is that output what you want me to paste? I took a picture of the kernel panic at least.
    – Thomazella
    Nov 26 at 2:52






  • 1




    Paste the text, not a screenshot wiki.archlinux.org/index.php/…
    – jasonwryan
    Nov 26 at 3:02












up vote
0
down vote

favorite
1









up vote
0
down vote

favorite
1






1





I use arch linux and after an update about a month ago I can't boot the system anymore.



The logs show a kernel panic caused by calling /usr/bin/switch_root with arg -d.



I've tried a live cd boot and chroot into the system, followed by another update, but no luck. Also tried renaming the initramfs-fallback.img (name probably not correct, I don't recall it perfectly) to initramfs.img. I read somewhere that this could be caused by the ram disk. Google wasn't very helpful on this specific problem, also.



whatever is calling switch_root seems to run after arch prints out the lines

:: Mounting '/dev/sdc4' on real root
:: Running cleanup hook [udev]



What do you guys think?



Kernel panic picture:
enter image description here










share|improve this question















I use arch linux and after an update about a month ago I can't boot the system anymore.



The logs show a kernel panic caused by calling /usr/bin/switch_root with arg -d.



I've tried a live cd boot and chroot into the system, followed by another update, but no luck. Also tried renaming the initramfs-fallback.img (name probably not correct, I don't recall it perfectly) to initramfs.img. I read somewhere that this could be caused by the ram disk. Google wasn't very helpful on this specific problem, also.



whatever is calling switch_root seems to run after arch prints out the lines

:: Mounting '/dev/sdc4' on real root
:: Running cleanup hook [udev]



What do you guys think?



Kernel panic picture:
enter image description here







linux arch-linux boot kernel-panic






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 6 hours ago

























asked Nov 24 at 16:26









Thomazella

34




34











  • The release notes for util-linux show no changes to switch_root for the last two releases, and there have been no Arch patches. Paste the full journal from a failed boot.
    – jasonwryan
    Nov 25 at 2:20










  • @jasonwryan I think it's this man: git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/…
    – Thomazella
    Nov 26 at 1:37










  • That would seem unlikely: this would be an issue affecting a lot more people. Please paste the actual journal.
    – jasonwryan
    Nov 26 at 1:47










  • @jasonwryan could you advise on pasting the journal, please? I booted to the live system, did a chroot into the old one, and read the output of journalctl, the last entries. It didn't look abnormal. Is that output what you want me to paste? I took a picture of the kernel panic at least.
    – Thomazella
    Nov 26 at 2:52






  • 1




    Paste the text, not a screenshot wiki.archlinux.org/index.php/…
    – jasonwryan
    Nov 26 at 3:02
















  • The release notes for util-linux show no changes to switch_root for the last two releases, and there have been no Arch patches. Paste the full journal from a failed boot.
    – jasonwryan
    Nov 25 at 2:20










  • @jasonwryan I think it's this man: git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/…
    – Thomazella
    Nov 26 at 1:37










  • That would seem unlikely: this would be an issue affecting a lot more people. Please paste the actual journal.
    – jasonwryan
    Nov 26 at 1:47










  • @jasonwryan could you advise on pasting the journal, please? I booted to the live system, did a chroot into the old one, and read the output of journalctl, the last entries. It didn't look abnormal. Is that output what you want me to paste? I took a picture of the kernel panic at least.
    – Thomazella
    Nov 26 at 2:52






  • 1




    Paste the text, not a screenshot wiki.archlinux.org/index.php/…
    – jasonwryan
    Nov 26 at 3:02















The release notes for util-linux show no changes to switch_root for the last two releases, and there have been no Arch patches. Paste the full journal from a failed boot.
– jasonwryan
Nov 25 at 2:20




The release notes for util-linux show no changes to switch_root for the last two releases, and there have been no Arch patches. Paste the full journal from a failed boot.
– jasonwryan
Nov 25 at 2:20












@jasonwryan I think it's this man: git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/…
– Thomazella
Nov 26 at 1:37




@jasonwryan I think it's this man: git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/…
– Thomazella
Nov 26 at 1:37












That would seem unlikely: this would be an issue affecting a lot more people. Please paste the actual journal.
– jasonwryan
Nov 26 at 1:47




That would seem unlikely: this would be an issue affecting a lot more people. Please paste the actual journal.
– jasonwryan
Nov 26 at 1:47












@jasonwryan could you advise on pasting the journal, please? I booted to the live system, did a chroot into the old one, and read the output of journalctl, the last entries. It didn't look abnormal. Is that output what you want me to paste? I took a picture of the kernel panic at least.
– Thomazella
Nov 26 at 2:52




@jasonwryan could you advise on pasting the journal, please? I booted to the live system, did a chroot into the old one, and read the output of journalctl, the last entries. It didn't look abnormal. Is that output what you want me to paste? I took a picture of the kernel panic at least.
– Thomazella
Nov 26 at 2:52




1




1




Paste the text, not a screenshot wiki.archlinux.org/index.php/…
– jasonwryan
Nov 26 at 3:02




Paste the text, not a screenshot wiki.archlinux.org/index.php/…
– jasonwryan
Nov 26 at 3:02










1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










I solved it by chrooting into the unbootable system and running pacman -Suy with /boot mounted correctly. Linux was updated and mkinitcpio was run automatically. My /boot is in another partition and the first time I did pacman -Suy, I didn't mount it (newbie mistake lol!).



Thanks to the commenters that tried to help! Much appreciated guys, thanks.






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',
    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%2f483890%2fkernel-panic-on-usr-bin-switch-root-d%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








    up vote
    0
    down vote



    accepted










    I solved it by chrooting into the unbootable system and running pacman -Suy with /boot mounted correctly. Linux was updated and mkinitcpio was run automatically. My /boot is in another partition and the first time I did pacman -Suy, I didn't mount it (newbie mistake lol!).



    Thanks to the commenters that tried to help! Much appreciated guys, thanks.






    share|improve this answer
























      up vote
      0
      down vote



      accepted










      I solved it by chrooting into the unbootable system and running pacman -Suy with /boot mounted correctly. Linux was updated and mkinitcpio was run automatically. My /boot is in another partition and the first time I did pacman -Suy, I didn't mount it (newbie mistake lol!).



      Thanks to the commenters that tried to help! Much appreciated guys, thanks.






      share|improve this answer






















        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        I solved it by chrooting into the unbootable system and running pacman -Suy with /boot mounted correctly. Linux was updated and mkinitcpio was run automatically. My /boot is in another partition and the first time I did pacman -Suy, I didn't mount it (newbie mistake lol!).



        Thanks to the commenters that tried to help! Much appreciated guys, thanks.






        share|improve this answer












        I solved it by chrooting into the unbootable system and running pacman -Suy with /boot mounted correctly. Linux was updated and mkinitcpio was run automatically. My /boot is in another partition and the first time I did pacman -Suy, I didn't mount it (newbie mistake lol!).



        Thanks to the commenters that tried to help! Much appreciated guys, thanks.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 6 hours ago









        Thomazella

        34




        34



























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f483890%2fkernel-panic-on-usr-bin-switch-root-d%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

            Peggy Mitchell

            Palaiologos

            The Forum (Inglewood, California)