Rich Freeman on 8 Dec 2011 04:28:12 -0800

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] Lost gigabytes?

On Thu, Dec 8, 2011 at 6:39 AM, LeRoy <> wrote:
> On 12/07/2011 02:38 PM, Adam Zion wrote:
>> Linux boot partition, 524 MB, ext4
>> 145 GB physical volume shared w/145 GB extended volume, linux LVM/Extended
>> a check of the size of / reveals only 45 GB drive space- I've lost 100 GB.
>> Methinks it has something to do w/the odd 145GB/145GB partition that's
>> listed last.

I don't see anything odd about it.  MBR-style hard drives only have
four primary partitions, so gparted set up an extended partition in
the 4th physical partition to allow for more flexibility if you
repartition in the future.  This is a pretty typical setup, and both
windows and linux support it fine (going WAY back in time).

Can you post the output of a few commands?:

fdisk -l /dev/sda (or whatever device your hard drive is on)
cat /proc/mounts
cat /etc/fstab
df -h

> Ext4 cannot be used on the /boot partition because of GRUB, meaning a
> separate /boot partition with a different filesystem must be made.

Does Fedora use Grub2?  If so there should be no problem.

In any case, if grub can't access /boot then the system won't boot.
Grub doesn't even look at the root partition - it just passes whatever
is in your boot line to the kernel and the kernel and initramfs mount
root.  Grub shouldn't write to any filesystem (I think), so if it
boots it should boot up just fine.  It shouldn't boot up but then have
odd issues with the root filesystem.

I think the output of the commands I listed will help narrow things
down.  One consideration is that it is possible to create a filesystem
that doesn't fill the partition that it lies within (usually that
happens if you resize things after creation).  If that is the case a
resize2fs from a rescue disk will fix things.

Philadelphia Linux Users Group         --
Announcements -
General Discussion  --