Kernel Panic after FreePBX 14 Upgrade

I attempted to upgrade from FreePBX 13 to 14 on my Sangoma Appliance PBX using the 13 to 14 upgrader Module. It stated that since this was an official distro I had to update using the CLI and gave Upgrading from FreePBX 10.13.66 to SNG7 from the wiki for the instructions. I ran the RPM command: yum -y install (Ommitted URL As I’m Not allowed)

Initially I ran ‘distro-upgrade’ and it said that some of the dependencies needed to be upgraded, so I ran the yum update with completed with no issues. So I ran ‘distro-upgrade’ again. This time it reported that some of the packages installed were 32-bit and needed to be uninstalled and reinstalled as 64-bit. That completed with no issue.

Next I ran ‘distro-upgrade’ again and it completed, prompting me to "reboot the appliance at my convenience. "
I issued the reboot command and when it booted back up, I was expecting the green grub menu screen with the system upgrade option, but instead got a blue screen with two options:

SHMZ (2.6.32-642.6.2.el6.x86_64)
SHMZ 6 (2.6.32-504.8.1.el6.x86_64)

The 4 second timer ran out and the first option ran and resulted in this:

sd 1:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 1:0:0:0: [sda] Attached SCSI disk
usb 1-2: new high speed USB device number 2 using xhci_hcd
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: 
dracut: Mounted root filesystem /dev/sda2
usb 1-2: New USB device found, idVendor=05e3, idProduct=0608
usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 1-2: Product: USB2.0 Hub
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
dracut: chroot: failed to run command `/sbin/load_policy': Input/output error
dracut: Switching root
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: switch_root Not tainted 2.6.32-642.6.2.el6.x86_64 #1
Call Trace:
 [<ffffffff815482b1>] ? panic+0xa7/0x179
 [<ffffffff8112aea0>] ? perf_event_exit_task+0xc0/0x340
 [<ffffffff81081f97>] ? do_exit+0x867/0x870
 [<ffffffff81081ff8>] ? do_group_exit+0x58/0xd0
 [<ffffffff81082087>] ? sys_exit_group+0x17/0x20
 [<ffffffff8100b0d2>] ? system_call_fastpath+0x16/0x1b

Next I rebooted and selected the second option and got this:

sd 1:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 1:0:0:0: [sda] Attached SCSI disk
usb 1-2: new high speed USB device number 2 using xhci_hcd
EXT4-fs (sda2): 
usb 1-2: New USB device found, idVendor=05e3, idProduct=0608
usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 1-2: Product: USB2.0 Hub
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
mounted filesystem with ordered data mode. Opts: 
dracut: Mounted root filesystem /dev/sda2
dracut: chroot: failed to run command `/sbin/load_policy': Input/output error
dracut: Switching root
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: switch_root Not tainted 2.6.32-504.8.1.el6.x86_64 #1
Call Trace:
  [<ffffffff815292d6>] ? panic+0xa7/0x16f
  [<ffffffff8107a5f2>] ? do_exit+0x862/0x870
  [<ffffffff8107a658>] ? do_group_exit+0x58/0xd0
  [<ffffffff8107a6e7>] ? sys_exit_group+0x17/0x20
  [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
drm_kms_helper: panic occurred, switching back to text console

As of right now I have a non-functioning system. I do have a backup, but don’t really want to reinstall if there is another fix. Also, based on my own Googling, I think I might have a bad SSD. I plugged it into my laptop (OS X) and it wanted to initialize the drive. I’m trying to image the disk to try some recovery methods on the drive. If anyone can confirm a bad SSD based on the info given that would be helpful.

Any help would be greatly appreciated!! Thanks

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.