How to fix “Failed to mount root filesystem - failed to open /dev/console” in RedHat after Cloning Disk
Clash Royale CLAN TAG#URR8PPP
After cloning my HDD by Norton Ghost to a new one, I moved the new disk to new PC (with different hardware).
In the new PC , I see this message at boot, as you see in this screenshot:
What exactly is this message supposed to tell me, and how can i fix that?
I also tested some grub solutions like this page :
https://kb.acronis.com/content/1686
Thanks
linux rhel grub boot-loader clonezilla
edited Mar 8 '16 at 19:00
Jenny D
10.6k22746
asked Mar 8 '16 at 18:25
user880414user880414
62
add a comment |
After cloning my HDD by Norton Ghost to a new one, I moved the new disk to new PC (with different hardware).
In the new PC , I see this message at boot, as you see in this screenshot:
What exactly is this message supposed to tell me, and how can i fix that?
I also tested some grub solutions like this page :
https://kb.acronis.com/content/1686
Thanks
linux rhel grub boot-loader clonezilla
edited Mar 8 '16 at 19:00
Jenny D
10.6k22746
asked Mar 8 '16 at 18:25
user880414user880414
62
After you cloned the drive, did you do a grub-install on the boot partition? This is necessary sometimes when disk geometries are different. I think if this were the problem, you wouldn't have gotten as far as you did. But I have trouble reconciling Murphy's answer with something as vanilla as the console ... unless the initrd image isn't properly mapped (logical blocks to physical ones)
– Otheus
Mar 9 '16 at 12:20
add a comment |
After cloning my HDD by Norton Ghost to a new one, I moved the new disk to new PC (with different hardware).
In the new PC , I see this message at boot, as you see in this screenshot:
What exactly is this message supposed to tell me, and how can i fix that?
I also tested some grub solutions like this page :
https://kb.acronis.com/content/1686
Thanks
linux rhel grub boot-loader clonezilla
edited Mar 8 '16 at 19:00
Jenny D
10.6k22746
asked Mar 8 '16 at 18:25
user880414user880414
62
After cloning my HDD by Norton Ghost to a new one, I moved the new disk to new PC (with different hardware).
In the new PC , I see this message at boot, as you see in this screenshot:
What exactly is this message supposed to tell me, and how can i fix that?
I also tested some grub solutions like this page :
https://kb.acronis.com/content/1686
Thanks
linux rhel grub boot-loader clonezilla
linux rhel grub boot-loader clonezilla
edited Mar 8 '16 at 19:00
Jenny D
10.6k22746
asked Mar 8 '16 at 18:25
user880414user880414
62
edited Mar 8 '16 at 19:00
Jenny D
10.6k22746
asked Mar 8 '16 at 18:25
user880414user880414
62
edited Mar 8 '16 at 19:00
Jenny D
10.6k22746
edited Mar 8 '16 at 19:00
Jenny D
10.6k22746
edited Mar 8 '16 at 19:00
Jenny D
10.6k22746
10.6k22746
asked Mar 8 '16 at 18:25
user880414user880414
62
asked Mar 8 '16 at 18:25
user880414user880414
62
asked Mar 8 '16 at 18:25
user880414user880414
62
62
After you cloned the drive, did you do a grub-install on the boot partition? This is necessary sometimes when disk geometries are different. I think if this were the problem, you wouldn't have gotten as far as you did. But I have trouble reconciling Murphy's answer with something as vanilla as the console ... unless the initrd image isn't properly mapped (logical blocks to physical ones)
– Otheus
Mar 9 '16 at 12:20
add a comment |
After you cloned the drive, did you do a grub-install on the boot partition? This is necessary sometimes when disk geometries are different. I think if this were the problem, you wouldn't have gotten as far as you did. But I have trouble reconciling Murphy's answer with something as vanilla as the console ... unless the initrd image isn't properly mapped (logical blocks to physical ones)
– Otheus
Mar 9 '16 at 12:20
After you cloned the drive, did you do a grub-install on the boot partition? This is necessary sometimes when disk geometries are different. I think if this were the problem, you wouldn't have gotten as far as you did. But I have trouble reconciling Murphy's answer with something as vanilla as the console ... unless the initrd image isn't properly mapped (logical blocks to physical ones)
– Otheus
Mar 9 '16 at 12:20
After you cloned the drive, did you do a grub-install on the boot partition? This is necessary sometimes when disk geometries are different. I think if this were the problem, you wouldn't have gotten as far as you did. But I have trouble reconciling Murphy's answer with something as vanilla as the console ... unless the initrd image isn't properly mapped (logical blocks to physical ones)
– Otheus
Mar 9 '16 at 12:20
add a comment |
1 Answer
1
active
oldest
votes
Most probably the device nodes of the new drive on the new system don't match the old ones you cloned with the partition(s). Start a rescue system (Knoppix or any other live system), determine which node in /dev is used for which partition, mount the root partition and adjust <mountpoint>/etc/fstab and your bootloader configuration (probably in <mountpoint>/boot, or on the boot partition if you have one).
If the device nodes/partition scheme seems to be identical, perhaps you are missing some basic nodes in <mountpoint>/dev that are needed before devtmpfs is mounted to /dev; create them from the rescue system, e. g.
mknod <mountpoint>/dev/console c 5 1
You should be able to determine the node type/IDs and their permissions from /dev of the rescue system. I'm not totally sure, but I think /dev/null and one or two others are necessary, too, but that may vary with each distribution.
answered Mar 8 '16 at 20:50
MurphyMurphy
1,7861617
I changed Motherboard and afetr that kernel started but holds on this error i.stack.imgur.com/Yax9G.jpg
– user880414
Mar 12 '16 at 18:50
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f268463%2fhow-to-fix-failed-to-mount-root-filesystem-failed-to-open-dev-console-in-re%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
Most probably the device nodes of the new drive on the new system don't match the old ones you cloned with the partition(s). Start a rescue system (Knoppix or any other live system), determine which node in /dev is used for which partition, mount the root partition and adjust <mountpoint>/etc/fstab and your bootloader configuration (probably in <mountpoint>/boot, or on the boot partition if you have one).
If the device nodes/partition scheme seems to be identical, perhaps you are missing some basic nodes in <mountpoint>/dev that are needed before devtmpfs is mounted to /dev; create them from the rescue system, e. g.
mknod <mountpoint>/dev/console c 5 1
You should be able to determine the node type/IDs and their permissions from /dev of the rescue system. I'm not totally sure, but I think /dev/null and one or two others are necessary, too, but that may vary with each distribution.
answered Mar 8 '16 at 20:50
MurphyMurphy
1,7861617
I changed Motherboard and afetr that kernel started but holds on this error i.stack.imgur.com/Yax9G.jpg
– user880414
Mar 12 '16 at 18:50
add a comment |
Most probably the device nodes of the new drive on the new system don't match the old ones you cloned with the partition(s). Start a rescue system (Knoppix or any other live system), determine which node in /dev is used for which partition, mount the root partition and adjust <mountpoint>/etc/fstab and your bootloader configuration (probably in <mountpoint>/boot, or on the boot partition if you have one).
If the device nodes/partition scheme seems to be identical, perhaps you are missing some basic nodes in <mountpoint>/dev that are needed before devtmpfs is mounted to /dev; create them from the rescue system, e. g.
mknod <mountpoint>/dev/console c 5 1
You should be able to determine the node type/IDs and their permissions from /dev of the rescue system. I'm not totally sure, but I think /dev/null and one or two others are necessary, too, but that may vary with each distribution.
answered Mar 8 '16 at 20:50
MurphyMurphy
1,7861617
I changed Motherboard and afetr that kernel started but holds on this error i.stack.imgur.com/Yax9G.jpg
– user880414
Mar 12 '16 at 18:50
add a comment |
Most probably the device nodes of the new drive on the new system don't match the old ones you cloned with the partition(s). Start a rescue system (Knoppix or any other live system), determine which node in /dev is used for which partition, mount the root partition and adjust <mountpoint>/etc/fstab and your bootloader configuration (probably in <mountpoint>/boot, or on the boot partition if you have one).
If the device nodes/partition scheme seems to be identical, perhaps you are missing some basic nodes in <mountpoint>/dev that are needed before devtmpfs is mounted to /dev; create them from the rescue system, e. g.
mknod <mountpoint>/dev/console c 5 1
You should be able to determine the node type/IDs and their permissions from /dev of the rescue system. I'm not totally sure, but I think /dev/null and one or two others are necessary, too, but that may vary with each distribution.
answered Mar 8 '16 at 20:50
MurphyMurphy
1,7861617
Most probably the device nodes of the new drive on the new system don't match the old ones you cloned with the partition(s). Start a rescue system (Knoppix or any other live system), determine which node in /dev is used for which partition, mount the root partition and adjust <mountpoint>/etc/fstab and your bootloader configuration (probably in <mountpoint>/boot, or on the boot partition if you have one).
If the device nodes/partition scheme seems to be identical, perhaps you are missing some basic nodes in <mountpoint>/dev that are needed before devtmpfs is mounted to /dev; create them from the rescue system, e. g.
mknod <mountpoint>/dev/console c 5 1
You should be able to determine the node type/IDs and their permissions from /dev of the rescue system. I'm not totally sure, but I think /dev/null and one or two others are necessary, too, but that may vary with each distribution.
answered Mar 8 '16 at 20:50
MurphyMurphy
1,7861617
edited Mar 9 '16 at 9:59
answered Mar 8 '16 at 20:50
MurphyMurphy
1,7861617
answered Mar 8 '16 at 20:50
MurphyMurphy
1,7861617
answered Mar 8 '16 at 20:50
MurphyMurphy
1,7861617
1,7861617
I changed Motherboard and afetr that kernel started but holds on this error i.stack.imgur.com/Yax9G.jpg
– user880414
Mar 12 '16 at 18:50
add a comment |
I changed Motherboard and afetr that kernel started but holds on this error i.stack.imgur.com/Yax9G.jpg
– user880414
Mar 12 '16 at 18:50
I changed Motherboard and afetr that kernel started but holds on this error i.stack.imgur.com/Yax9G.jpg
– user880414
Mar 12 '16 at 18:50
I changed Motherboard and afetr that kernel started but holds on this error i.stack.imgur.com/Yax9G.jpg
– user880414
Mar 12 '16 at 18:50
add a comment |
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f268463%2fhow-to-fix-failed-to-mount-root-filesystem-failed-to-open-dev-console-in-re%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
After you cloned the drive, did you do a grub-install on the boot partition? This is necessary sometimes when disk geometries are different. I think if this were the problem, you wouldn't have gotten as far as you did. But I have trouble reconciling Murphy's answer with something as vanilla as the console ... unless the initrd image isn't properly mapped (logical blocks to physical ones)
– Otheus
Mar 9 '16 at 12:20