Hi there,
Please forgive me for asking what is likely a recurring question. I have a CentOS 5.8 Guest OS on top of a Windows 7 host. I successfully increased the size of the drive from 15GB to 60GB but, now I am unsure how to exactly proceed to enable the Linux OS see this additional space? I am pretty new to Linux disk management, and although I have spent time looking online, and in this forum, I have not seen a disk partition setup the same as mine? I would really appreciate some guidelines please?
I downloaded the current version of gparted live, and added a CD Drive to the VM Host. I then rebooted and went through all the screens to get to the main gparted application menu. I have my current configuration of my drive as follows:
/dev/sda (60.00 GiB)
Partition File System Mount Point Label Size Used Unused Flags
/dev/sda1 ext3 /boot 101.94 Mib 36.25 Mib 65.70 MiB boot
/dev/sda2 (yellow padlock) lvm2 pv VolGroup00 15.24 GiB 15.24 GiB 0.00 B lvm
unallocated unallocated 44.66 GiB --- ---
I am unsure why I am getting the yellow padlock? I am booted up off the Live gparted so there must be something wrong here?
Any help would be very much appreciated!
Thank you,
Mark
CentOS 5.8 - How to get Guest OS to recognize new disk space
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: CentOS 5.8 - How to get Guest OS to recognize new disk s
Download GParted Live CD ISO, boot the VM from it, use it to resize guest partitions to fill the new unpartitioned space.
Re: CentOS 5.8 - How to get Guest OS to recognize new disk s
Thank you for the response.
That worked great! I was expecting this to be more complex, but it went smoothly!
That worked great! I was expecting this to be more complex, but it went smoothly!
Re: CentOS 5.8 - How to get Guest OS to recognize new disk s
I guess I spoke too soon! I just ran out of disk space.
This is what I have now:
Partition File System Mount Point Label Size Used Unused Flags
/dev/sda1 ext3 /boot 101.94 Mib 36.25 Mib 65.70 MiB boot
/dev/sda2 (yellow padlock) lvm2 pv VolGroup00 15.24 GiB 15.24 GiB 0.00 B lvm
/dev/sda3 ext4 44.66 GiB 897.47 MiB 43.78 GiB
I need to install a large app from my home directory, but just run out of space? How do I use this new storage? Even though I should be booted from the Live gparted iso, it looks like the /dev/sda2 partition is still locked? Does this mean that it is still mounted?
Thanks,
Mark
This is what I have now:
Partition File System Mount Point Label Size Used Unused Flags
/dev/sda1 ext3 /boot 101.94 Mib 36.25 Mib 65.70 MiB boot
/dev/sda2 (yellow padlock) lvm2 pv VolGroup00 15.24 GiB 15.24 GiB 0.00 B lvm
/dev/sda3 ext4 44.66 GiB 897.47 MiB 43.78 GiB
I need to install a large app from my home directory, but just run out of space? How do I use this new storage? Even though I should be booted from the Live gparted iso, it looks like the /dev/sda2 partition is still locked? Does this mean that it is still mounted?
Thanks,
Mark
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: CentOS 5.8 - How to get Guest OS to recognize new disk s
If the VM drive is virtual (not accessing a real host partition) then it can't be locked if the VM is booted from a live CD.
Best guest is that you aren't writing to the correct partition (your additional space seems to have been allocated as a new partition, not an enlarged existing partition).
Also I see now that your partition list mentions LVM, which is never a good sign. A simple legacy MBR partitioning system is better if you need to tweak things after the fact like this. Unfortunately I can't tell you how to solve this as I've never used LVM: perhaps someone else can suggest something.
Best guest is that you aren't writing to the correct partition (your additional space seems to have been allocated as a new partition, not an enlarged existing partition).
Also I see now that your partition list mentions LVM, which is never a good sign. A simple legacy MBR partitioning system is better if you need to tweak things after the fact like this. Unfortunately I can't tell you how to solve this as I've never used LVM: perhaps someone else can suggest something.