Re: Restore from Backup
Posted: Fri Apr 06, 2018 2:46 pm
So it looks /dev/sda2 is your disk that you want to boot from. If all of this seems a little too much for you, the second option might work better. That scenario goes like this.
1) you use /dev/sda1 (50GB root disk) as your boot disk and centos operating system
2) you install zimbra software only to this 50GB envrionment
3) you blow away the /opt/zimbra that you just installed on/dev/sda1 since we are after the other stuff zimbra installs in /etc and libs, etc
4) you mount /dev/sda2 as you are doing now but symlink /home/opt/zimbra to /opt/zimbra on 50GB root disk.
4b) you try and start zimbra (might work)
4c) you rerun zimbra install in update mode and let it fix everything should permissions be out, etc.
5) Over time begin removing all that extra stuff that you don't use on /dev/sda2 and free up more disk space for zimbra to grow into. That you chose LVM will help you grow this for the future anyway by adding more disk and resizing the filesystem.
This is the second strategy should you fail to get /dev/sda2 bootable but given you want to boot /dev/sda2,
add this to the list of things to do... modify /etc/fstab on /dev/sad2 so that the entries match... ie. run blkid /dev/sda2 and replace UUID's with those values if that is being used. You also need to navigate having LVM as your boot disk so I am unsure if you need a parameter with install-grub /dev/sda2 or if that is enough. It been a long time since I have done this (over 15 years). Running through a gentoo installation by hand on a VM will teach you a lot about the bootstrapping of linux as everything is done by hand. You might try that to get a feel for grub, LVM, chroot, etc.
As these are zimbra boards, you probably would get better advice on a centos board but I'll try because who doesn't like a good challenge and learn something.
1) you use /dev/sda1 (50GB root disk) as your boot disk and centos operating system
2) you install zimbra software only to this 50GB envrionment
3) you blow away the /opt/zimbra that you just installed on/dev/sda1 since we are after the other stuff zimbra installs in /etc and libs, etc
4) you mount /dev/sda2 as you are doing now but symlink /home/opt/zimbra to /opt/zimbra on 50GB root disk.
4b) you try and start zimbra (might work)
4c) you rerun zimbra install in update mode and let it fix everything should permissions be out, etc.
5) Over time begin removing all that extra stuff that you don't use on /dev/sda2 and free up more disk space for zimbra to grow into. That you chose LVM will help you grow this for the future anyway by adding more disk and resizing the filesystem.
This is the second strategy should you fail to get /dev/sda2 bootable but given you want to boot /dev/sda2,
add this to the list of things to do... modify /etc/fstab on /dev/sad2 so that the entries match... ie. run blkid /dev/sda2 and replace UUID's with those values if that is being used. You also need to navigate having LVM as your boot disk so I am unsure if you need a parameter with install-grub /dev/sda2 or if that is enough. It been a long time since I have done this (over 15 years). Running through a gentoo installation by hand on a VM will teach you a lot about the bootstrapping of linux as everything is done by hand. You might try that to get a feel for grub, LVM, chroot, etc.
As these are zimbra boards, you probably would get better advice on a centos board but I'll try because who doesn't like a good challenge and learn something.