CentOS Kernel panic - not syncing: Attempted to kill int during bootup
by JealousDonut from LinuxQuestions.org on (#6GWB2)
Building has a annual power shutdown for maintenance for 2 days.
As such, prior to it, I have shut down the CentOS 6 server.
After the power is back on (2 days later), when I boot back up, I encountered the following image :
[![Kernel panic - not syncing: Attempted to kill int][1]][1]
[1]: https://i.stack.imgur.com/x7EPk.jpg
I've Googled search around, and the most common answer is to disable SELinux during the boot.
I have tried that - and it didnt helped (which made sense since I didn't touched SELinux).
Also, at the GRUB page, I tried booting into other kernel, 2.6.32-358.el6.x86_64 kernel - however, it encountered the same kernel panic.
I'm unsure if its due to hardware issues like disk failing, RAMs etc, or other issues
What I've also done :
- I removed rghb and quiet parameters when booting the kernel, and there are more logs, specifically saying that lv_root and lv_swap could not be found.
- Tried using rescue USB thumbdrive. However after selecting Rescued installed system", it has problem locating the system partition. Even explicitly stating the disk that contains the system, it has error.
- Tried using live DVD as thumbdrive instead. In the live environment, mounting /dev/sda gives me error stating wrong file system : isw_raid_member. I believe it's because my OS disk is configured as raid1(mirror) using mdadm. Googling around and I discovered dmraid -ay", which seems to sync /dev/sda and /dev/sdb as a volume. However, when I tried to mount the volume, it keeps saying that it is already mounted or the mount folder is busy.
At this point, I'm not sure what to do. My main priority is to retrieve the files inside. Of course, if the system can be booted back up, that'll the most ideal
As such, prior to it, I have shut down the CentOS 6 server.
After the power is back on (2 days later), when I boot back up, I encountered the following image :
[![Kernel panic - not syncing: Attempted to kill int][1]][1]
[1]: https://i.stack.imgur.com/x7EPk.jpg
I've Googled search around, and the most common answer is to disable SELinux during the boot.
I have tried that - and it didnt helped (which made sense since I didn't touched SELinux).
Also, at the GRUB page, I tried booting into other kernel, 2.6.32-358.el6.x86_64 kernel - however, it encountered the same kernel panic.
I'm unsure if its due to hardware issues like disk failing, RAMs etc, or other issues
What I've also done :
- I removed rghb and quiet parameters when booting the kernel, and there are more logs, specifically saying that lv_root and lv_swap could not be found.
- Tried using rescue USB thumbdrive. However after selecting Rescued installed system", it has problem locating the system partition. Even explicitly stating the disk that contains the system, it has error.
- Tried using live DVD as thumbdrive instead. In the live environment, mounting /dev/sda gives me error stating wrong file system : isw_raid_member. I believe it's because my OS disk is configured as raid1(mirror) using mdadm. Googling around and I discovered dmraid -ay", which seems to sync /dev/sda and /dev/sdb as a volume. However, when I tried to mount the volume, it keeps saying that it is already mounted or the mount folder is busy.
At this point, I'm not sure what to do. My main priority is to retrieve the files inside. Of course, if the system can be booted back up, that'll the most ideal