Currently I run F30 and have been using md to mirror two identical disks as a personal raid solution and a form of crude backup. However, I want to change my setup where I mount my /dev/md0 directly to \home. Currently my setup looks like this (I have left out non essential info like tmp directories):
Now my worry is, that if I do an upgrade, I will still have my md0 as an independent directory under /home/data, while I want the /dev/md0 to be mounted on the /home in stead of /dev/mapper/fedora-home.
If I do a fresh install, I will lose my configuration of /dev/md0 and not sure how to reconfigure md0 without losing my data (which is currently mirrored).
Can anyone point me in the right direction to get my /dev/md0 mounted on /home without losing my data and my configuration?
Or, alternatively, even have /dev/md0 mounted on home in my current setup, i.e. before I do the upgrade?
Then it should be straightforward, you’ll need to edit the filesystem table to point to the new one. If you post the output of cat /etc/fstab, I can walk you through it.
Thank you. That was the push I needed. I suspect I can also mount /dev/md0 to /home while, remounting the /dev/mapper/fedora-home to some other partition in order to see if I missed something essential. Also, I could clean the fedora-home partition or maybe even remove it?
The one point I worry about is, if I delete a line from fstab, will the system shutdown properly? The same for /dev/md0. Should I log on as root on a console, umount /home and remount it from /dev/md0? Or would that complicate matters even more?
You can do it at runtime; that’s just a list of things to mount at startup. Actually mounted things are stored in the kernel, and can be viewed in /proc/mounts or using mount -l. Remounting it is probably more complication than it’s worth rather than just rebooting.
Since you seem to be using LVM, once everything is working, you should be able to delete the partition after, and extend the volume for the new one to contain the old space.
When executing this procedure it worked as described. However, be altert that some programs register the absolute path to their files. In my case the ~/.thunderbird/profile.ini was pointing to the old directory /home/data/gbonnema which no longer exists. So when I started the thunderbird program it could no longer find its profile and quit with an error message. Editing the profile.ini file solved the issue and I could normally start thunderbird.
I mention this for anyone wanting to do this procedure. Other programs may register the absolute path as well.