Solaris 11 - (unix: Could not start init) Program terminated)
Clash Royale CLAN TAG#URR8PPP
During a restart of a server with Solaris 11, the system halted with the following alert:
WARNING: exec(/usr/sbin/init) failed with errno 8. (unix: Could not start init) Program terminated.
The operating system keeps on reboot and never comes online. Since init
is one of the first processes to come up we are assuming that we will never be able to log onto the server.
Is there a way that we can log into the system and check what the issue is, and possible resolve it?
solaris init
add a comment |
During a restart of a server with Solaris 11, the system halted with the following alert:
WARNING: exec(/usr/sbin/init) failed with errno 8. (unix: Could not start init) Program terminated.
The operating system keeps on reboot and never comes online. Since init
is one of the first processes to come up we are assuming that we will never be able to log onto the server.
Is there a way that we can log into the system and check what the issue is, and possible resolve it?
solaris init
As far as I know, errno 8 is "exec format error", which tells me init might somehow be corrupted. Maybe this helps.
– schaiba
Oct 29 '13 at 18:40
Yes @schaiba, you're right. errno 8 is in fact an exec format error. However going into the system to check and possible fix that is a bit of a problem.
– oneway
Oct 30 '13 at 7:24
1
Can you try booting from a different media (CD, DVD, bootserver), and check the boot disk? Could be a disk problem. Otherwise, if you manage to get the exact version of Solaris, you could make some diff.
– ludiegu
Oct 30 '13 at 8:13
add a comment |
During a restart of a server with Solaris 11, the system halted with the following alert:
WARNING: exec(/usr/sbin/init) failed with errno 8. (unix: Could not start init) Program terminated.
The operating system keeps on reboot and never comes online. Since init
is one of the first processes to come up we are assuming that we will never be able to log onto the server.
Is there a way that we can log into the system and check what the issue is, and possible resolve it?
solaris init
During a restart of a server with Solaris 11, the system halted with the following alert:
WARNING: exec(/usr/sbin/init) failed with errno 8. (unix: Could not start init) Program terminated.
The operating system keeps on reboot and never comes online. Since init
is one of the first processes to come up we are assuming that we will never be able to log onto the server.
Is there a way that we can log into the system and check what the issue is, and possible resolve it?
solaris init
solaris init
edited Oct 29 '13 at 16:16
Anthon
61k17104166
61k17104166
asked Oct 29 '13 at 16:01
onewayoneway
264
264
As far as I know, errno 8 is "exec format error", which tells me init might somehow be corrupted. Maybe this helps.
– schaiba
Oct 29 '13 at 18:40
Yes @schaiba, you're right. errno 8 is in fact an exec format error. However going into the system to check and possible fix that is a bit of a problem.
– oneway
Oct 30 '13 at 7:24
1
Can you try booting from a different media (CD, DVD, bootserver), and check the boot disk? Could be a disk problem. Otherwise, if you manage to get the exact version of Solaris, you could make some diff.
– ludiegu
Oct 30 '13 at 8:13
add a comment |
As far as I know, errno 8 is "exec format error", which tells me init might somehow be corrupted. Maybe this helps.
– schaiba
Oct 29 '13 at 18:40
Yes @schaiba, you're right. errno 8 is in fact an exec format error. However going into the system to check and possible fix that is a bit of a problem.
– oneway
Oct 30 '13 at 7:24
1
Can you try booting from a different media (CD, DVD, bootserver), and check the boot disk? Could be a disk problem. Otherwise, if you manage to get the exact version of Solaris, you could make some diff.
– ludiegu
Oct 30 '13 at 8:13
As far as I know, errno 8 is "exec format error", which tells me init might somehow be corrupted. Maybe this helps.
– schaiba
Oct 29 '13 at 18:40
As far as I know, errno 8 is "exec format error", which tells me init might somehow be corrupted. Maybe this helps.
– schaiba
Oct 29 '13 at 18:40
Yes @schaiba, you're right. errno 8 is in fact an exec format error. However going into the system to check and possible fix that is a bit of a problem.
– oneway
Oct 30 '13 at 7:24
Yes @schaiba, you're right. errno 8 is in fact an exec format error. However going into the system to check and possible fix that is a bit of a problem.
– oneway
Oct 30 '13 at 7:24
1
1
Can you try booting from a different media (CD, DVD, bootserver), and check the boot disk? Could be a disk problem. Otherwise, if you manage to get the exact version of Solaris, you could make some diff.
– ludiegu
Oct 30 '13 at 8:13
Can you try booting from a different media (CD, DVD, bootserver), and check the boot disk? Could be a disk problem. Otherwise, if you manage to get the exact version of Solaris, you could make some diff.
– ludiegu
Oct 30 '13 at 8:13
add a comment |
1 Answer
1
active
oldest
votes
There are various ways, but you left off which architecture (SPARC or x86), as well as your boot device configuration (SAN, NAS, disk, mirrored disks, ...).
Agree with ludiegu that you could boot off media to check the state of the rpool. However, under Solaris 11, with ZFS and BEs, the easiest thing to do would also be to boot from a different BE.
- On SPARC, you could use a combination of booting at the OBB off the dev with -L to determine the BEs, and -Z for the BE/dataset.
- On x86 pick a different BE from GRUB.
From either media or a different BE, issue a scrub on rpool which may require being imported.
And if the drives are mirrored try booting off the alternate boot drive.
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%2f98081%2fsolaris-11-unix-could-not-start-init-program-terminated%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
There are various ways, but you left off which architecture (SPARC or x86), as well as your boot device configuration (SAN, NAS, disk, mirrored disks, ...).
Agree with ludiegu that you could boot off media to check the state of the rpool. However, under Solaris 11, with ZFS and BEs, the easiest thing to do would also be to boot from a different BE.
- On SPARC, you could use a combination of booting at the OBB off the dev with -L to determine the BEs, and -Z for the BE/dataset.
- On x86 pick a different BE from GRUB.
From either media or a different BE, issue a scrub on rpool which may require being imported.
And if the drives are mirrored try booting off the alternate boot drive.
add a comment |
There are various ways, but you left off which architecture (SPARC or x86), as well as your boot device configuration (SAN, NAS, disk, mirrored disks, ...).
Agree with ludiegu that you could boot off media to check the state of the rpool. However, under Solaris 11, with ZFS and BEs, the easiest thing to do would also be to boot from a different BE.
- On SPARC, you could use a combination of booting at the OBB off the dev with -L to determine the BEs, and -Z for the BE/dataset.
- On x86 pick a different BE from GRUB.
From either media or a different BE, issue a scrub on rpool which may require being imported.
And if the drives are mirrored try booting off the alternate boot drive.
add a comment |
There are various ways, but you left off which architecture (SPARC or x86), as well as your boot device configuration (SAN, NAS, disk, mirrored disks, ...).
Agree with ludiegu that you could boot off media to check the state of the rpool. However, under Solaris 11, with ZFS and BEs, the easiest thing to do would also be to boot from a different BE.
- On SPARC, you could use a combination of booting at the OBB off the dev with -L to determine the BEs, and -Z for the BE/dataset.
- On x86 pick a different BE from GRUB.
From either media or a different BE, issue a scrub on rpool which may require being imported.
And if the drives are mirrored try booting off the alternate boot drive.
There are various ways, but you left off which architecture (SPARC or x86), as well as your boot device configuration (SAN, NAS, disk, mirrored disks, ...).
Agree with ludiegu that you could boot off media to check the state of the rpool. However, under Solaris 11, with ZFS and BEs, the easiest thing to do would also be to boot from a different BE.
- On SPARC, you could use a combination of booting at the OBB off the dev with -L to determine the BEs, and -Z for the BE/dataset.
- On x86 pick a different BE from GRUB.
From either media or a different BE, issue a scrub on rpool which may require being imported.
And if the drives are mirrored try booting off the alternate boot drive.
answered Jan 19 '17 at 19:10
sleepyweaselsleepyweasel
88329
88329
add a comment |
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%2f98081%2fsolaris-11-unix-could-not-start-init-program-terminated%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
As far as I know, errno 8 is "exec format error", which tells me init might somehow be corrupted. Maybe this helps.
– schaiba
Oct 29 '13 at 18:40
Yes @schaiba, you're right. errno 8 is in fact an exec format error. However going into the system to check and possible fix that is a bit of a problem.
– oneway
Oct 30 '13 at 7:24
1
Can you try booting from a different media (CD, DVD, bootserver), and check the boot disk? Could be a disk problem. Otherwise, if you manage to get the exact version of Solaris, you could make some diff.
– ludiegu
Oct 30 '13 at 8:13