How to solve “Kernel panic - not syncing - Attempted to kill init” [on hold]
How to solve “Kernel panic - not syncing - Attempted to kill init”
Kindly share your findings. How to solve it??
init
asked yesterday
Harshad HarshuHarshad Harshu
1
New contributor
Harshad Harshu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as too broad by G-Man, Romeo Ninov, Jeff Schaller, Mr Shunz, Toby Speight 20 hours ago
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 yesterday
Harshad HarshuHarshad Harshu
1
New contributor
Harshad Harshu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as too broad by G-Man, Romeo Ninov, Jeff Schaller, Mr Shunz, Toby Speight 20 hours ago
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
yesterday
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
yesterday
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
yesterday
add a comment |
How to solve “Kernel panic - not syncing - Attempted to kill init”
Kindly share your findings. How to solve it??
init
asked yesterday
Harshad HarshuHarshad Harshu
1
New contributor
Harshad Harshu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
How to solve “Kernel panic - not syncing - Attempted to kill init”
Kindly share your findings. How to solve it??
init
init
asked yesterday
Harshad HarshuHarshad Harshu
1
New contributor
Harshad Harshu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
Harshad HarshuHarshad Harshu
1
New contributor
Harshad Harshu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
Harshad HarshuHarshad Harshu
1
New contributor
Harshad Harshu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
Harshad HarshuHarshad Harshu
1
asked yesterday
Harshad HarshuHarshad Harshu
1
1
New contributor
Harshad Harshu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Harshad Harshu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Harshad Harshu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as too broad by G-Man, Romeo Ninov, Jeff Schaller, Mr Shunz, Toby Speight 20 hours ago
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.
put on hold as too broad by G-Man, Romeo Ninov, Jeff Schaller, Mr Shunz, Toby Speight 20 hours ago
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
yesterday
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
yesterday
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
yesterday
add a comment |
I already did long since at unix.stackexchange.com/questions/195889 and unix.stackexchange.com/questions/197437 .
– JdeBP
yesterday
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
yesterday
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
yesterday
I already did long since at unix.stackexchange.com/questions/195889 and unix.stackexchange.com/questions/197437 .
– JdeBP
yesterday
I already did long since at unix.stackexchange.com/questions/195889 and unix.stackexchange.com/questions/197437 .
– JdeBP
yesterday
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
yesterday
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
yesterday
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
yesterday
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
yesterday
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
yesterday
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
yesterday
You can't sovle it. You didn't provide or probably don't know any information.
– 炸鱼薯条德里克
yesterday