Help! Stuck on GNU GRUB 2.02 after restart












2















I just restarted Linux, and a purple GNU GRUB 2.02 screen came up. When I press “c” to enter the command line and enter “ls,” it says “error: no such partition.”



I am completely new to Linux, and there is some very important data on this machine. Any help appreciated and I’ll respond quickly to comments. Thanks!










share|improve this question























  • Welcome to Ask Ubuntu. My guess is you have just deleted a partition that was used in booting your system, so your MBR points to a now-deleted spot which needed to be fixed prior to reboot. I don't know what else is on your system, or anything else about it - so I don't see what else we help, but you need to fix using another OS on your system (usually done when you delete the partition) More details may help, but we support Ubuntu and official-flavors, not other Linux.

    – guiverc
    Jan 11 at 3:42











  • Thank you for the response. I should clarify - it’s not my machine. The owner is away on vacation. I just pressed restart, and this happened. How can I change the partition the MBR points to? If it helps, I noticed that “OS” was in the “media” directory, which I thought was strange.

    – Jordan
    Jan 11 at 3:50


















2















I just restarted Linux, and a purple GNU GRUB 2.02 screen came up. When I press “c” to enter the command line and enter “ls,” it says “error: no such partition.”



I am completely new to Linux, and there is some very important data on this machine. Any help appreciated and I’ll respond quickly to comments. Thanks!










share|improve this question























  • Welcome to Ask Ubuntu. My guess is you have just deleted a partition that was used in booting your system, so your MBR points to a now-deleted spot which needed to be fixed prior to reboot. I don't know what else is on your system, or anything else about it - so I don't see what else we help, but you need to fix using another OS on your system (usually done when you delete the partition) More details may help, but we support Ubuntu and official-flavors, not other Linux.

    – guiverc
    Jan 11 at 3:42











  • Thank you for the response. I should clarify - it’s not my machine. The owner is away on vacation. I just pressed restart, and this happened. How can I change the partition the MBR points to? If it helps, I noticed that “OS” was in the “media” directory, which I thought was strange.

    – Jordan
    Jan 11 at 3:50
















2












2








2


1






I just restarted Linux, and a purple GNU GRUB 2.02 screen came up. When I press “c” to enter the command line and enter “ls,” it says “error: no such partition.”



I am completely new to Linux, and there is some very important data on this machine. Any help appreciated and I’ll respond quickly to comments. Thanks!










share|improve this question














I just restarted Linux, and a purple GNU GRUB 2.02 screen came up. When I press “c” to enter the command line and enter “ls,” it says “error: no such partition.”



I am completely new to Linux, and there is some very important data on this machine. Any help appreciated and I’ll respond quickly to comments. Thanks!







boot grub2 partitioning error-handling gnu






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 11 at 3:32









JordanJordan

212




212













  • Welcome to Ask Ubuntu. My guess is you have just deleted a partition that was used in booting your system, so your MBR points to a now-deleted spot which needed to be fixed prior to reboot. I don't know what else is on your system, or anything else about it - so I don't see what else we help, but you need to fix using another OS on your system (usually done when you delete the partition) More details may help, but we support Ubuntu and official-flavors, not other Linux.

    – guiverc
    Jan 11 at 3:42











  • Thank you for the response. I should clarify - it’s not my machine. The owner is away on vacation. I just pressed restart, and this happened. How can I change the partition the MBR points to? If it helps, I noticed that “OS” was in the “media” directory, which I thought was strange.

    – Jordan
    Jan 11 at 3:50





















  • Welcome to Ask Ubuntu. My guess is you have just deleted a partition that was used in booting your system, so your MBR points to a now-deleted spot which needed to be fixed prior to reboot. I don't know what else is on your system, or anything else about it - so I don't see what else we help, but you need to fix using another OS on your system (usually done when you delete the partition) More details may help, but we support Ubuntu and official-flavors, not other Linux.

    – guiverc
    Jan 11 at 3:42











  • Thank you for the response. I should clarify - it’s not my machine. The owner is away on vacation. I just pressed restart, and this happened. How can I change the partition the MBR points to? If it helps, I noticed that “OS” was in the “media” directory, which I thought was strange.

    – Jordan
    Jan 11 at 3:50



















Welcome to Ask Ubuntu. My guess is you have just deleted a partition that was used in booting your system, so your MBR points to a now-deleted spot which needed to be fixed prior to reboot. I don't know what else is on your system, or anything else about it - so I don't see what else we help, but you need to fix using another OS on your system (usually done when you delete the partition) More details may help, but we support Ubuntu and official-flavors, not other Linux.

– guiverc
Jan 11 at 3:42





Welcome to Ask Ubuntu. My guess is you have just deleted a partition that was used in booting your system, so your MBR points to a now-deleted spot which needed to be fixed prior to reboot. I don't know what else is on your system, or anything else about it - so I don't see what else we help, but you need to fix using another OS on your system (usually done when you delete the partition) More details may help, but we support Ubuntu and official-flavors, not other Linux.

– guiverc
Jan 11 at 3:42













Thank you for the response. I should clarify - it’s not my machine. The owner is away on vacation. I just pressed restart, and this happened. How can I change the partition the MBR points to? If it helps, I noticed that “OS” was in the “media” directory, which I thought was strange.

– Jordan
Jan 11 at 3:50







Thank you for the response. I should clarify - it’s not my machine. The owner is away on vacation. I just pressed restart, and this happened. How can I change the partition the MBR points to? If it helps, I noticed that “OS” was in the “media” directory, which I thought was strange.

– Jordan
Jan 11 at 3:50












1 Answer
1






active

oldest

votes


















1














So, dumbest solution possible: I fixed it by turning the computer off and on again.



Man is that a relief. Now that my heart rate is slowing down, I think I’m going to crawl back to being coddled by my Mac.






share|improve this answer
























  • It sounds like you had added a device (eg. usb thumb-drive) which caused the BIOS to re-order devices (ideally devices should be coded to UUID's or unique-IDs, but new people often use device names which are short alas can change if devices are added/removed or changes made in bios; though could also be on purpose so if devices change it will fail to boot). Either way thankfully it's solved.

    – guiverc
    Jan 11 at 4:42













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1108746%2fhelp-stuck-on-gnu-grub-2-02-after-restart%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









1














So, dumbest solution possible: I fixed it by turning the computer off and on again.



Man is that a relief. Now that my heart rate is slowing down, I think I’m going to crawl back to being coddled by my Mac.






share|improve this answer
























  • It sounds like you had added a device (eg. usb thumb-drive) which caused the BIOS to re-order devices (ideally devices should be coded to UUID's or unique-IDs, but new people often use device names which are short alas can change if devices are added/removed or changes made in bios; though could also be on purpose so if devices change it will fail to boot). Either way thankfully it's solved.

    – guiverc
    Jan 11 at 4:42


















1














So, dumbest solution possible: I fixed it by turning the computer off and on again.



Man is that a relief. Now that my heart rate is slowing down, I think I’m going to crawl back to being coddled by my Mac.






share|improve this answer
























  • It sounds like you had added a device (eg. usb thumb-drive) which caused the BIOS to re-order devices (ideally devices should be coded to UUID's or unique-IDs, but new people often use device names which are short alas can change if devices are added/removed or changes made in bios; though could also be on purpose so if devices change it will fail to boot). Either way thankfully it's solved.

    – guiverc
    Jan 11 at 4:42
















1












1








1







So, dumbest solution possible: I fixed it by turning the computer off and on again.



Man is that a relief. Now that my heart rate is slowing down, I think I’m going to crawl back to being coddled by my Mac.






share|improve this answer













So, dumbest solution possible: I fixed it by turning the computer off and on again.



Man is that a relief. Now that my heart rate is slowing down, I think I’m going to crawl back to being coddled by my Mac.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 11 at 4:11









JordanJordan

212




212













  • It sounds like you had added a device (eg. usb thumb-drive) which caused the BIOS to re-order devices (ideally devices should be coded to UUID's or unique-IDs, but new people often use device names which are short alas can change if devices are added/removed or changes made in bios; though could also be on purpose so if devices change it will fail to boot). Either way thankfully it's solved.

    – guiverc
    Jan 11 at 4:42





















  • It sounds like you had added a device (eg. usb thumb-drive) which caused the BIOS to re-order devices (ideally devices should be coded to UUID's or unique-IDs, but new people often use device names which are short alas can change if devices are added/removed or changes made in bios; though could also be on purpose so if devices change it will fail to boot). Either way thankfully it's solved.

    – guiverc
    Jan 11 at 4:42



















It sounds like you had added a device (eg. usb thumb-drive) which caused the BIOS to re-order devices (ideally devices should be coded to UUID's or unique-IDs, but new people often use device names which are short alas can change if devices are added/removed or changes made in bios; though could also be on purpose so if devices change it will fail to boot). Either way thankfully it's solved.

– guiverc
Jan 11 at 4:42







It sounds like you had added a device (eg. usb thumb-drive) which caused the BIOS to re-order devices (ideally devices should be coded to UUID's or unique-IDs, but new people often use device names which are short alas can change if devices are added/removed or changes made in bios; though could also be on purpose so if devices change it will fail to boot). Either way thankfully it's solved.

– guiverc
Jan 11 at 4:42




















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • 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%2faskubuntu.com%2fquestions%2f1108746%2fhelp-stuck-on-gnu-grub-2-02-after-restart%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

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕