kernel panic error
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
my linux server can't boot because of some error and i don't access to console either.
There are the errors :
mounting /dev/vg1/root on /sysroot failed : No such device
mounting /dev on /sysroot/dev failed : No such file or directory
switch_root: bad newroot /sysroot
Kernel panic - not syncing: Attempting to kill init
do you know what should i do when i can't even access to console?
linux command-line mount console kernel-panic
asked Feb 19 at 7:48
user276724
1
add a comment |Â
up vote
0
down vote
favorite
my linux server can't boot because of some error and i don't access to console either.
There are the errors :
mounting /dev/vg1/root on /sysroot failed : No such device
mounting /dev on /sysroot/dev failed : No such file or directory
switch_root: bad newroot /sysroot
Kernel panic - not syncing: Attempting to kill init
do you know what should i do when i can't even access to console?
linux command-line mount console kernel-panic
asked Feb 19 at 7:48
user276724
1
1
Did you do anything in particular to put your system in that state? What Linux distribution are you using?
– Kusalananda
Feb 19 at 7:53
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
my linux server can't boot because of some error and i don't access to console either.
There are the errors :
mounting /dev/vg1/root on /sysroot failed : No such device
mounting /dev on /sysroot/dev failed : No such file or directory
switch_root: bad newroot /sysroot
Kernel panic - not syncing: Attempting to kill init
do you know what should i do when i can't even access to console?
linux command-line mount console kernel-panic
asked Feb 19 at 7:48
user276724
1
my linux server can't boot because of some error and i don't access to console either.
There are the errors :
mounting /dev/vg1/root on /sysroot failed : No such device
mounting /dev on /sysroot/dev failed : No such file or directory
switch_root: bad newroot /sysroot
Kernel panic - not syncing: Attempting to kill init
do you know what should i do when i can't even access to console?
linux command-line mount console kernel-panic
asked Feb 19 at 7:48
user276724
1
asked Feb 19 at 7:48
user276724
1
asked Feb 19 at 7:48
user276724
1
asked Feb 19 at 7:48
user276724
1
1
1
Did you do anything in particular to put your system in that state? What Linux distribution are you using?
– Kusalananda
Feb 19 at 7:53
add a comment |Â
1
Did you do anything in particular to put your system in that state? What Linux distribution are you using?
– Kusalananda
Feb 19 at 7:53
1
1
Did you do anything in particular to put your system in that state? What Linux distribution are you using?
– Kusalananda
Feb 19 at 7:53
Did you do anything in particular to put your system in that state? What Linux distribution are you using?
– Kusalananda
Feb 19 at 7:53
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
The actual problem is, your server fails to mount its root filesystem. The kernel panic error message is just a consequence of that.
You said you don't have console access - then how are you getting these error messages? ("No console access" with servers typically means something like "the server is locked away in a server room somewhere and I can not get at it physically or by any sort of remote console access system." If you mean "the console is non-responsive", well, that can be expected after a kernel panic.)
If you have access to the bootloader, in some distributions (RHEL 7 and newer, most modern Debian-related systems) there is a boot option that will give you access to an "emergency shell". If that is not possible for your distribution of choice, then you'll need to boot from the installation media and select "rescue mode" or similar in the bootloader.
answered Feb 19 at 8:00
telcoM
10.7k11132
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The actual problem is, your server fails to mount its root filesystem. The kernel panic error message is just a consequence of that.
You said you don't have console access - then how are you getting these error messages? ("No console access" with servers typically means something like "the server is locked away in a server room somewhere and I can not get at it physically or by any sort of remote console access system." If you mean "the console is non-responsive", well, that can be expected after a kernel panic.)
If you have access to the bootloader, in some distributions (RHEL 7 and newer, most modern Debian-related systems) there is a boot option that will give you access to an "emergency shell". If that is not possible for your distribution of choice, then you'll need to boot from the installation media and select "rescue mode" or similar in the bootloader.
answered Feb 19 at 8:00
telcoM
10.7k11132
add a comment |Â
up vote
0
down vote
The actual problem is, your server fails to mount its root filesystem. The kernel panic error message is just a consequence of that.
You said you don't have console access - then how are you getting these error messages? ("No console access" with servers typically means something like "the server is locked away in a server room somewhere and I can not get at it physically or by any sort of remote console access system." If you mean "the console is non-responsive", well, that can be expected after a kernel panic.)
If you have access to the bootloader, in some distributions (RHEL 7 and newer, most modern Debian-related systems) there is a boot option that will give you access to an "emergency shell". If that is not possible for your distribution of choice, then you'll need to boot from the installation media and select "rescue mode" or similar in the bootloader.
answered Feb 19 at 8:00
telcoM
10.7k11132
add a comment |Â
up vote
0
down vote
up vote
0
down vote
The actual problem is, your server fails to mount its root filesystem. The kernel panic error message is just a consequence of that.
You said you don't have console access - then how are you getting these error messages? ("No console access" with servers typically means something like "the server is locked away in a server room somewhere and I can not get at it physically or by any sort of remote console access system." If you mean "the console is non-responsive", well, that can be expected after a kernel panic.)
If you have access to the bootloader, in some distributions (RHEL 7 and newer, most modern Debian-related systems) there is a boot option that will give you access to an "emergency shell". If that is not possible for your distribution of choice, then you'll need to boot from the installation media and select "rescue mode" or similar in the bootloader.
answered Feb 19 at 8:00
telcoM
10.7k11132
The actual problem is, your server fails to mount its root filesystem. The kernel panic error message is just a consequence of that.
You said you don't have console access - then how are you getting these error messages? ("No console access" with servers typically means something like "the server is locked away in a server room somewhere and I can not get at it physically or by any sort of remote console access system." If you mean "the console is non-responsive", well, that can be expected after a kernel panic.)
If you have access to the bootloader, in some distributions (RHEL 7 and newer, most modern Debian-related systems) there is a boot option that will give you access to an "emergency shell". If that is not possible for your distribution of choice, then you'll need to boot from the installation media and select "rescue mode" or similar in the bootloader.
answered Feb 19 at 8:00
telcoM
10.7k11132
answered Feb 19 at 8:00
telcoM
10.7k11132
answered Feb 19 at 8:00
telcoM
10.7k11132
answered Feb 19 at 8:00
telcoM
10.7k11132
10.7k11132
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f425105%2fkernel-panic-error%23new-answer', 'question_page');
);
Post as a guest
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
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
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
1
Did you do anything in particular to put your system in that state? What Linux distribution are you using?
– Kusalananda
Feb 19 at 7:53