Resized Filesystems & LV's via RescueCD Can't Boot OS

SaveVM · 04-20-2012, 11:16 PM

So, it all started when I had my root fs at 50GB and my /home fs at 15GB.
I needed more room on /home so I asked management to do it for me.
They made root 15GB and home 50GB.
My mistake was I didn't pay attention to when they were doing it and had 16GB of files on the root partion.
My CentOS server crashed and would not boot past the loading screen.

So now it's the weekend and won't hear a response for another few days.
I tried using system rescue cd combined with these two tutorials to try and fix things.
http://paulpodolny.blogspot.com/2011...artitions.html
http://www.howtoforge.com/logical-vo...a-volume-group

I made root 20GB and /home 40GB.

It all looked well from there, but when I try and restart my VM I get the same thing.
CentOS wont load past a full white bar loading screen.
No SSH, just vSphere and me.

Please help.

djsoundfx · 05-15-2012, 11:37 AM

Quote:

Originally Posted by SaveVM

So, it all started when I had my root fs at 50GB and my /home fs at 15GB.
I needed more room on /home so I asked management to do it for me.
They made root 15GB and home 50GB.
My mistake was I didn't pay attention to when they were doing it and had 16GB of files on the root partion.
My CentOS server crashed and would not boot past the loading screen.

So now it's the weekend and won't hear a response for another few days.
I tried using system rescue cd combined with these two tutorials to try and fix things.
http://paulpodolny.blogspot.com/2011...artitions.html
http://www.howtoforge.com/logical-vo...a-volume-group

I made root 20GB and /home 40GB.

It all looked well from there, but when I try and restart my VM I get the same thing.
CentOS wont load past a full white bar loading screen.
No SSH, just vSphere and me.

Please help.

My worry is that you lost some data when you resized... you did perform a backup before you started right?
But don't cry yet it is likely fixable with enough time and effort. We need logs can you post the contents of /var/log/boot.log and /var/log/dmesg. If you're having trouble accessing these either use a live cd or modify your grub loader by doing the following:

Code:

Boot to run level 3: interrupt GRUB by typing a character such as space (if necessary) Then appending to the kernel line by typing "a" and appending "3"(without "") press <enter>. If it worked this should give you a text login prompt. You can also backspace through "rhgb quiet" on the kernel line to get more verbose boot output as suggested above in conjunction with any of those (basically it shows you screen output of what would be in the boot.log)

If that doesn't, boot to single user mode by interrupting GRUB by typing a character such as "space" then appending to the kernel line by typing "a" and appending "1"(again without the "") press <enter>. Which will give you a root shell.