How to solve “Kernel panic - not syncing - Attempted to kill init” [closed]
How to solve “Kernel panic - not syncing - Attempted to kill init”
Kindly share your findings. How to solve it??
init
asked Jan 16 at 6:18
Harshad HarshuHarshad Harshu
1
closed as too broad by G-Man, Romeo Ninov, Jeff Schaller, Mr Shunz, Toby Speight Jan 16 at 15:26
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
How to solve “Kernel panic - not syncing - Attempted to kill init”
Kindly share your findings. How to solve it??
init
asked Jan 16 at 6:18
Harshad HarshuHarshad Harshu
1
closed as too broad by G-Man, Romeo Ninov, Jeff Schaller, Mr Shunz, Toby Speight Jan 16 at 15:26
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
I already did long since at unix.stackexchange.com/questions/195889 and unix.stackexchange.com/questions/197437 .
– JdeBP
Jan 16 at 6:55
If this happens at boot time, this is usually a sign of a failure to mount the root filesystem. Perhaps your kernel configuration or initramfs is missing the driver for your disk controller or the filesystem type that is used by your root filesystem? Or perhaps there was an error in creating the initramfs file at the latest kernel update, maybe because the filesystem became full of temporary files? If possible, try booting the system with an older kernel, or with an installation media in rescue mode, or with a Linux Live CD/DVD/USB, and then investigate further.
– telcoM
Jan 16 at 7:03
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
Jan 16 at 7:04
add a comment |
How to solve “Kernel panic - not syncing - Attempted to kill init”
Kindly share your findings. How to solve it??
init
asked Jan 16 at 6:18
Harshad HarshuHarshad Harshu
1
How to solve “Kernel panic - not syncing - Attempted to kill init”
Kindly share your findings. How to solve it??
init
init
asked Jan 16 at 6:18
Harshad HarshuHarshad Harshu
1
asked Jan 16 at 6:18
Harshad HarshuHarshad Harshu
1
asked Jan 16 at 6:18
Harshad HarshuHarshad Harshu
1
asked Jan 16 at 6:18
Harshad HarshuHarshad Harshu
1
asked Jan 16 at 6:18
Harshad HarshuHarshad Harshu
1
1
closed as too broad by G-Man, Romeo Ninov, Jeff Schaller, Mr Shunz, Toby Speight Jan 16 at 15:26
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by G-Man, Romeo Ninov, Jeff Schaller, Mr Shunz, Toby Speight Jan 16 at 15:26
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
I already did long since at unix.stackexchange.com/questions/195889 and unix.stackexchange.com/questions/197437 .
– JdeBP
Jan 16 at 6:55
If this happens at boot time, this is usually a sign of a failure to mount the root filesystem. Perhaps your kernel configuration or initramfs is missing the driver for your disk controller or the filesystem type that is used by your root filesystem? Or perhaps there was an error in creating the initramfs file at the latest kernel update, maybe because the filesystem became full of temporary files? If possible, try booting the system with an older kernel, or with an installation media in rescue mode, or with a Linux Live CD/DVD/USB, and then investigate further.
– telcoM
Jan 16 at 7:03
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
Jan 16 at 7:04
add a comment |
I already did long since at unix.stackexchange.com/questions/195889 and unix.stackexchange.com/questions/197437 .
– JdeBP
Jan 16 at 6:55
If this happens at boot time, this is usually a sign of a failure to mount the root filesystem. Perhaps your kernel configuration or initramfs is missing the driver for your disk controller or the filesystem type that is used by your root filesystem? Or perhaps there was an error in creating the initramfs file at the latest kernel update, maybe because the filesystem became full of temporary files? If possible, try booting the system with an older kernel, or with an installation media in rescue mode, or with a Linux Live CD/DVD/USB, and then investigate further.
– telcoM
Jan 16 at 7:03
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
Jan 16 at 7:04
I already did long since at unix.stackexchange.com/questions/195889 and unix.stackexchange.com/questions/197437 .
– JdeBP
Jan 16 at 6:55
I already did long since at unix.stackexchange.com/questions/195889 and unix.stackexchange.com/questions/197437 .
– JdeBP
Jan 16 at 6:55
If this happens at boot time, this is usually a sign of a failure to mount the root filesystem. Perhaps your kernel configuration or initramfs is missing the driver for your disk controller or the filesystem type that is used by your root filesystem? Or perhaps there was an error in creating the initramfs file at the latest kernel update, maybe because the filesystem became full of temporary files? If possible, try booting the system with an older kernel, or with an installation media in rescue mode, or with a Linux Live CD/DVD/USB, and then investigate further.
– telcoM
Jan 16 at 7:03
If this happens at boot time, this is usually a sign of a failure to mount the root filesystem. Perhaps your kernel configuration or initramfs is missing the driver for your disk controller or the filesystem type that is used by your root filesystem? Or perhaps there was an error in creating the initramfs file at the latest kernel update, maybe because the filesystem became full of temporary files? If possible, try booting the system with an older kernel, or with an installation media in rescue mode, or with a Linux Live CD/DVD/USB, and then investigate further.
– telcoM
Jan 16 at 7:03
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
Jan 16 at 7:04
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
Jan 16 at 7:04
add a comment |
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
I already did long since at unix.stackexchange.com/questions/195889 and unix.stackexchange.com/questions/197437 .
– JdeBP
Jan 16 at 6:55
If this happens at boot time, this is usually a sign of a failure to mount the root filesystem. Perhaps your kernel configuration or initramfs is missing the driver for your disk controller or the filesystem type that is used by your root filesystem? Or perhaps there was an error in creating the initramfs file at the latest kernel update, maybe because the filesystem became full of temporary files? If possible, try booting the system with an older kernel, or with an installation media in rescue mode, or with a Linux Live CD/DVD/USB, and then investigate further.
– telcoM
Jan 16 at 7:03
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
Jan 16 at 7:04