Hard drive bigger than 2TB, expand LVM

the only thing I’d say is that 1 issue -> 1 topic

@alefattorini, could you please split this topic?

TIA

python-pycurl-7.19.0-8.el6.x86_64
python-iniparse-0.3.1-2.1.el6.noarch
python-libs-2.6.6-52.el6.x86_64
python-urlgrabber-3.9.1-9.el6.noarch
newt-python-0.52.11-3.el6.x86_64
python-simplejson-2.5.2-1.centos6.x86_64
python-dateutil-1.4.1-6.el6.noarch
python-2.6.6-52.el6.x86_64
rpm-python-4.8.0-38.el6_6.x86_64

nothing

I’m not sure if the issues are not related to each other. That’s because I didn’t split the Topic.
The only thing I’d like to archive is to get a neth distro running with more than 2TB and with the work arounds I tried the yum issue came up. When using mbr disks and the neth installer I have no yum issues.

I archieved the target to have a VM running with neth and storage of more than 2TB by doing following:

  1. creating VM with small HD (~16GB)
  2. installing neth with interactive install
  3. adding anover virtual disk with ~3TB
  4. expanding LVM to new disk

everything works now. No issues during installation out of software center.

To expand LVM I followed this guide (german):
https://www.thomas-krenn.com/de/wiki/LVM_vergrößern

So:

  1. I created a LVM partition with gparted, not cfdisk as in the guide
  2. extended the volume groupe: vgextend VolGroup /dev/sdb1
  3. extended logical volume: lvextend -l +100%FREE /dev/mapper/VolGroup-lv_root
  4. extended partition: resize2fs -p /dev/mapper/VolGroup-lv_root

it is not a good practice at all, it is better to investigate about GRUB , why does he refuse to install.

You solved your problem, without giving us the possibility to understand it an solve it for everybody

please have a look to my last post. I solved it with LVM. As Nas writes it is not a good practice but I haven’t found another solution.

I have to thank’s @Nas for his support.

1 Like

I read it…

you solved your problem with a workaround that couldn’t be an option for other users… that’s why we had to investigate it… that’s all

OK. I deleted the solved tag.