Solved CentOS 7 VM will not boot
-
Ok, This VM was running along just fine this morning.
I logged into SSH and told it to shut down with power off
I made a change to the network card not part of the hyper-v switch, ran windows updates, and rebooted the windows server (Datacenter 2012R2, Core + GUI + Hyper-V)
All of the windows server VM's booted up just fine. My CentOS 7 VM did not.
-
Hope you made a backup!
-
@thecreativeone91
not yet I hadn't. was not too much on there, but enough that I am highly annoyed -
Looks like a corrupted or missing boot filesystem. Boot from a CentOS 7 Live CD to fix from there.
-
the biggest thing on there was my daerma.com wordpress site.
I do have a backup of that from the day I moved it to this VM. I will lose a few posts but nothing important.
-
@scottalanmiller said:
Looks like a corrupted or missing boot filesystem. Boot from a CentOS 7 Live CD to fix from there.
I'll have to google that process, but can do.
-
Getting the disc in is easy. Recovering May or may not be.
-
cannot change the boot device. No idea WTF happened here.
-
What hypervisor is that?
If the firmware failed, maybe that is the issue.
-
@scottalanmiller said:
What hypervisor is that?
If the firmware failed, maybe that is the issue.Hyper-V Role inside Server 2012 R2.
I did a quick Google and did not get any results. But I had to leave for a dinner with the family and friends. Will look again tonight.
-
The Panic Code refers to a IPMI (BIOS) Issue. I wonder if you could just make a new VM and attach the disk to it and boot it?
-
@thecreativeone91 said:
The Panic Code refers to a IPMI (BIOS) Issue. I wonder if you could just make a new VM and attach the disk to it and boot it?
Was thinking to try that if my google fu fails later. Maybe I should just try it first.
-
Not familiar with what might make HyperV do that
-
@scottalanmiller said:
Not familiar with what might make HyperV do that
Tried to make a new VM and just attach the VHDX with no luck.
Created a complete VM installed CentOS and then shut down and added the old drive as a second HDD. it shows up when I check fdisk. So now to figure out how to copy the everything.
-
looks like sdb3 is not readable? sdb1 and sdb2 mounted and were readable.
Here is a screenshot. typo's included
-
learning more linux.. there is the data. so how to recover.
-
If you can see it like that, what is stopping you from just copying it?
-
@scottalanmiller said:
If you can see it like that, what is stopping you from just copying it?
i copied that. now looking for the mariadb files
-
found the db files. now to figure out how to connect them
-
Oh database files, that sucks. What DB engine is it? MyISAM? InnoDB? Something else?