# Revision history [back]

So the reason those directories exist is that your Logical Volume Manager created a volume group called "fedora_BadHostname" when you selected the default disk layout in anaconda while first installing the system. If you use the command sudo vgs, you'll see that you have a volume group named "fedora_BadHostname". The reason GRUB references the location is that it's the location of your root and swap volumes, necessary for booting your system, and you would have rendered your system unbootable if you had stripped those references from GRUB.

What you need to do is rename the volume group using the vgrename command. Unfortunately, in this case, it's your root volume group. In order to rename it, it can't be mounted, so you're going to have to:

1. Make sure everything you care about is backed up to a separate system (as it should be; regularly, of course)
2. Boot from a Fedora (preferably) rescue disk to access your system while its root volume group isn't mounted.
3. Use vgrename to reconfigure fedora_BadHostname into fedora_GoodHostname.
4. Make the appropriate directories and mount the pertinent volumes of your old OS to /mnt/oldOS/rootvolume , /mnt/oldOS/anyothervolumes
5. chroot /mnt/oldOS /bin/bash
6. Modify the /etc/default/grub file, replacing all references to fedora_BadHostname to fedora_GoodHostname, and grub-mkconfig yourself a new grub.conf file.
7. Reboot your system and allow GRUB to boot into your old host.
8. Confirm that the volume group name has been changed, and the /dev/fedora_BadHostname directory is renamed along with it.

I don't know if you'll conclude this to be too much trouble to simply rename your volume group; unless you had a really bad breakup with BadHostname, I wouldn't consider it necessarily pressing enough to change. If you aren't willing and able to recover from backup in the event of some sort of disaster, I wouldn't advise doing it. It's not a difficult procedure, but mistakes can be costly enough to prevent your system from booting, so you need to be very careful in attempting it.

Don't take that list above as the final, authoritative guide on this. If you need help constructing more specific steps from that general outline, I'll be glad to assist, but unless you're interested in it purely as a technical exercise (which is laudable), it's probably not worth your while.

So the reason those directories exist is that your Logical Volume Manager created a volume group called "fedora_BadHostname" when you selected the default disk layout in anaconda while first installing the system. If you use the command sudo vgs, you'll see that you have a volume group named "fedora_BadHostname". The reason GRUB references the location volume group is that it's the location of your root and swap volumes, necessary for booting your system, and you would have rendered your system unbootable if you had stripped those references from GRUB.

What you need to do is rename the volume group using the vgrename command. Unfortunately, in this case, it's your root volume group. In order to rename it, it can't be mounted, so you're going to have to:

1. Make sure everything you care about is backed up to a separate system (as it should be; regularly, of course)
2. Boot from a Fedora (preferably) rescue disk to access your system while its root volume group isn't mounted.
3. Use vgrename to reconfigure fedora_BadHostname into fedora_GoodHostname.
4. Make the appropriate directories and mount the pertinent volumes of your old OS to /mnt/oldOS/rootvolume , /mnt/oldOS/anyothervolumes
5. chroot /mnt/oldOS /bin/bash
6. Modify the /etc/default/grub file, replacing all references to fedora_BadHostname to fedora_GoodHostname, and grub-mkconfig yourself a new grub.conf file.
7. Reboot your system and allow GRUB to boot into your old host.
8. Confirm that the volume group name has been changed, and the /dev/fedora_BadHostname directory is renamed along with it.

I don't know if you'll conclude this to be too much trouble to simply rename your volume group; unless you had a really bad breakup with BadHostname, I wouldn't consider it necessarily pressing enough to change. If you aren't willing and able to recover from backup in the event of some sort of disaster, I wouldn't advise doing it. It's not a difficult procedure, but mistakes can be costly enough to prevent your system from booting, so you need to be very careful in attempting it.

Don't take that list above as the final, authoritative guide on this. If you need help constructing more specific steps from that general outline, I'll be glad to assist, but unless you're interested in it purely as a technical exercise (which is laudable), it's probably not worth your while.

So the reason those directories exist is that your Logical Volume Manager created a volume group called "fedora_BadHostname" when you selected the default disk layout in anaconda while first installing the system. If you use the command sudo vgs, you'll see that you have a volume group named "fedora_BadHostname". The reason GRUB references the volume group is that it's the location of your root and swap volumes, necessary for booting your system, and you would have rendered your system unbootable if you had stripped those references from GRUB.

What you need to do is rename the volume group using the vgrename command. Unfortunately, in this case, it's your root volume group. In order to rename it, it can't be mounted, so you're going to have to:

1. Make sure everything you care about is backed up to a separate system (as it should be; regularly, of course)
2. Boot from a Fedora (preferably) rescue disk to access your system while its root volume group isn't mounted.
3. Use vgrename to reconfigure fedora_BadHostname into fedora_GoodHostname.
4. Make the appropriate directories and I'll need to see your logical volume layout before providing specific advice on this step, but if you have the standard logical volume layout, I'd mkdir /mnt/GoodHostname and mount /dev/mapper/fedora_GoodHostname-root /mnt/GoodHostname
5. Here, depending on your use of BIOS or UEFI, we'll need to mount the pertinent volumes of your old OS to /mnt/oldOS/rootvolume , /mnt/oldOS/anyothervolumes your boot(/efi) partition(s) into /mnt/GoodHostname/boot(/efi) so that grub2-mkconfig below will be able to place the new GRUB configuration file in the proper location.
6. chroot /mnt/oldOS /bin/bash
7. Modify the /etc/default/grub file, replacing all references to fedora_BadHostname to fedora_GoodHostname, and grub-mkconfig grub-mkconfig yourself a new grub.conf file.
8. Reboot your system and allow GRUB to boot into your old host.
9. Confirm that the volume group name has been changed, and the /dev/fedora_BadHostname directory is renamed along with it.

I don't know if you'll conclude this to be too much trouble to simply rename your volume group; unless you had a really bad breakup with BadHostname, I wouldn't consider it necessarily pressing enough to change. If you aren't willing and able to recover from backup in the event of some sort of disaster, I wouldn't advise doing it. It's not a difficult procedure, but mistakes can be costly enough to prevent your system from booting, so you need to be very careful in attempting it.

Don't take that list above as the final, authoritative guide on this. If you need help constructing more specific steps from that general outline, I'll be glad to assist, but unless you're interested in it purely as a technical exercise (which is laudable), it's probably not worth your while.

So the reason those directories exist is that your Logical Volume Manager created a volume group called "fedora_BadHostname" when you selected the default disk layout in anaconda while first installing the system. If you use the command sudo vgs, you'll see that you have a volume group named "fedora_BadHostname". The reason GRUB references the volume group is that it's the location of your root and swap volumes, necessary for booting your system, and you would have rendered your system unbootable if you had stripped those references from GRUB.

What you need to do is rename the volume group using the vgrename command. Unfortunately, in this case, it's your root volume group. In order to rename it, it can't be mounted, so you're going to have to:

1. Make sure everything you care about is backed up to a separate system (as it should be; regularly, of course)
2. Boot from a Fedora (preferably) rescue disk to access your system while its root volume group isn't mounted.
3. Use vgrename to reconfigure fedora_BadHostname into fedora_GoodHostname.
4. I'll need to see your logical volume layout before providing specific advice on this step, but if you have the standard logical volume layout, I'd mkdir /mnt/GoodHostname and mount -t xfs /dev/mapper/fedora_GoodHostname-root /mnt/GoodHostname
5. Here, depending on your use of BIOS or UEFI, we'll need to mount your boot(/efi) partition(s) into /mnt/GoodHostname/boot(/efi) so that grub2-mkconfig below will be able to place the new GRUB configuration file in the proper location.
6. chroot /mnt/oldOS /bin/bash
7. Modify the /etc/default/grub file, replacing all references to fedora_BadHostname to fedora_GoodHostname, and grub-mkconfig yourself a new grub.conf file.
8. Reboot your system and allow GRUB to boot into your old host.
9. Confirm that the volume group name has been changed, and the /dev/fedora_BadHostname directory is renamed along with it.

I don't know if you'll conclude this to be too much trouble to simply rename your volume group; unless you had a really bad breakup with BadHostname, I wouldn't consider it necessarily pressing enough to change. If you aren't willing and able to recover from backup in the event of some sort of disaster, I wouldn't advise doing it. It's not a difficult procedure, but mistakes can be costly enough to prevent your system from booting, so you need to be very careful in attempting it.

Don't take that list above as the final, authoritative guide on this. If you need help constructing more specific steps from that general outline, I'll be glad to assist, but unless you're interested in it purely as a technical exercise (which is laudable), it's probably not worth your while.

So the reason those directories exist is that your Logical Volume Manager created a volume group called "fedora_BadHostname" when you selected the default disk layout in anaconda while first installing the system. If you use the command sudo vgs, you'll see that you have a volume group named "fedora_BadHostname". The reason GRUB references the volume group is that it's the location of your root and swap volumes, necessary for booting your system, and you would have rendered your system unbootable if you had stripped those references from GRUB.

What you need to do is rename the volume group using the vgrename command. Unfortunately, in this case, it's your root volume group. In order to rename it, it can't be mounted, so you're going to have to:

1. Make sure everything you care about is backed up to a separate system (as it should be; regularly, of course)
2. Boot from a Fedora (preferably) rescue disk to access your system while its root volume group isn't mounted.
3. Use vgrename to reconfigure fedora_BadHostname into fedora_GoodHostname.
4. I'll need to see your logical volume layout before providing specific advice on this step, but if you have chose the standard logical volume layout, installation options, I'd mkdir /mnt/GoodHostname and mount -t xfs /dev/mapper/fedora_GoodHostname-root /mnt/GoodHostname
5. Here, depending on your use of BIOS or UEFI, we'll need to mount your boot(/efi) partition(s) into /mnt/GoodHostname/boot(/efi) so that grub2-mkconfig below will be able to place the new GRUB configuration file in the proper location.
6. chroot /mnt/oldOS /bin/bash
7. Modify the /etc/default/grub file, replacing all references to fedora_BadHostname to fedora_GoodHostname, and grub-mkconfig yourself a new grub.conf file.
8. Reboot your system and allow GRUB to boot into your old host.
9. Confirm that the volume group name has been changed, and the /dev/fedora_BadHostname directory is renamed along with it.

I don't know if you'll conclude this to be too much trouble to simply rename your volume group; unless you had a really bad breakup with BadHostname, I wouldn't consider it necessarily pressing enough to change. If you aren't willing and able to recover from backup in the event of some sort of disaster, I wouldn't advise doing it. It's not a difficult procedure, but mistakes can be costly enough to prevent your system from booting, so you need to be very careful in attempting it.

Don't take that list above as the final, authoritative guide on this. If you need help constructing more specific steps from that general outline, I'll be glad to assist, but unless you're interested in it purely as a technical exercise (which is laudable), it's probably not worth your while.

So the reason those directories exist that directory exists is that your Logical Volume Manager created a volume group called "fedora_BadHostname" when you selected the default disk layout in anaconda while first installing the system. If you use the command sudo vgs, you'll see that you have a volume group named "fedora_BadHostname". The reason GRUB references the volume group is that it's the location of your root and swap volumes, necessary for booting your system, and you would have rendered your system unbootable if you had stripped those references from GRUB.

What you need to do is rename the volume group using the vgrename command. Unfortunately, in this case, it's your root volume group. In order to rename it, it can't be mounted, so you're going to have to:

1. Make sure everything you care about is backed up to a separate system (as it should be; regularly, of course)
2. Boot from a Fedora (preferably) rescue disk to access your system while its root volume group isn't mounted.
3. Use vgrename to reconfigure fedora_BadHostname into fedora_GoodHostname.
4. I'll need to see your logical volume layout before providing specific advice on this step, but if you chose the standard installation options, I'd mkdir /mnt/GoodHostname and mount -t xfs /dev/mapper/fedora_GoodHostname-root /mnt/GoodHostname
5. Here, depending on your use of BIOS or UEFI, we'll need to mount your boot(/efi) partition(s) into /mnt/GoodHostname/boot(/efi) so that grub2-mkconfig below will be able to place the new GRUB configuration file in the proper location.
6. chroot /mnt/oldOS /bin/bash
7. Modify the /etc/default/grub file, replacing all references to fedora_BadHostname to fedora_GoodHostname, and grub-mkconfig yourself a new grub.conf file.
8. Reboot your system and allow GRUB to boot into your old host.
9. Confirm that the volume group name has been changed, and the /dev/fedora_BadHostname directory is renamed along with it.

I don't know if you'll conclude this to be too much trouble to simply rename your volume group; unless you had a really bad breakup with BadHostname, I wouldn't consider it necessarily pressing enough to change. If you aren't willing and able to recover from backup in the event of some sort of disaster, I wouldn't advise doing it. It's not a difficult procedure, but mistakes can be costly enough to prevent your system from booting, so you need to be very careful in attempting it.

Don't take that list above as the final, authoritative guide on this. If you need help constructing more specific steps from that general outline, I'll be glad to assist, but unless you're interested in it purely as a technical exercise (which is laudable), it's probably not worth your while.

So the reason that directory exists is that your Logical Volume Manager created a volume group called "fedora_BadHostname" when you selected the default disk layout in anaconda while first installing the system. If you use the command sudo vgs, you'll see that you have a volume group named "fedora_BadHostname". The reason GRUB references the volume group is that it's the location of your root and swap volumes, necessary for booting your system, and you would have rendered your system unbootable if you had stripped those references from GRUB.

What you need to do is rename the volume group using the vgrename command. Unfortunately, in this case, it's your root volume group. In order to rename it, it can't be mounted, so you're going to have to:

1. Make sure everything you care about is backed up to a separate system (as it should be; regularly, of course)
2. Boot from a Fedora (preferably) rescue disk to access your system while its root volume group isn't mounted.
3. Use vgrename to reconfigure fedora_BadHostname into fedora_GoodHostname.
4. I'll need to see your logical volume layout before providing specific advice on this step, but if you chose the standard installation options, I'd mkdir /mnt/GoodHostname and mount -t xfs /dev/mapper/fedora_GoodHostname-root /mnt/GoodHostname
5. Here, depending on your use of BIOS or UEFI, we'll need to mount your boot(/efi) partition(s) into /mnt/GoodHostname/boot(/efi) so that grub2-mkconfig below will be able to place the new GRUB configuration file in the proper location.
6. chroot /mnt/oldOS /mnt/GoodHostname /bin/bash
7. Modify the /etc/default/grub file, replacing all references to fedora_BadHostname to fedora_GoodHostname, and grub-mkconfig yourself a new grub.conf file.
8. Reboot your system and allow GRUB to boot into your old host.
9. Confirm that the volume group name has been changed, and the /dev/fedora_BadHostname directory is renamed along with it.

I don't know if you'll conclude this to be too much trouble to simply rename your volume group; unless you had a really bad breakup with BadHostname, I wouldn't consider it necessarily pressing enough to change. If you aren't willing and able to recover from backup in the event of some sort of disaster, I wouldn't advise doing it. It's not a difficult procedure, but mistakes can be costly enough to prevent your system from booting, so you need to be very careful in attempting it.

Don't take that list above as the final, authoritative guide on this. If you need help constructing more specific steps from that general outline, I'll be glad to assist, but unless you're interested in it purely as a technical exercise (which is laudable), it's probably not worth your while.

So the reason that directory exists is that your Logical Volume Manager created a volume group called "fedora_BadHostname" when you selected the default disk layout in anaconda while first installing the system. If you use the command sudo vgs, you'll see that you have a volume group named "fedora_BadHostname". The reason GRUB references the volume group is that it's the location of your root and swap volumes, necessary for booting your system, and you would have rendered your system unbootable if you had stripped those references from GRUB.

What you need to do is rename the volume group using the vgrename command. Unfortunately, in this case, it's your root volume group. In order to rename it, it can't be mounted, so you're going to have to:

1. Make sure everything you care about is backed up to a separate system (as it should be; regularly, of course)
2. Boot from a Fedora (preferably) rescue disk to access your system while its root volume group isn't mounted.
3. Use vgrename to reconfigure fedora_BadHostname into fedora_GoodHostname.
4. I'll need to see your logical volume layout before providing specific advice on this step, but if you chose the standard installation options, I'd mkdir /mnt/GoodHostname and mount -t xfs /dev/mapper/fedora_GoodHostname-root /mnt/GoodHostname
5. Here, depending on your use of BIOS or UEFI, we'll need to mount your boot(/efi) partition(s) into /mnt/GoodHostname/boot(/efi) so that grub2-mkconfig below will be able to place the new GRUB configuration file in the proper location.
6. chroot /mnt/GoodHostname /bin/bash
7. Modify the /etc/fstab file, replacing all references to fedora_BadHostname to fedora_GoodHostname
8. Modify the /etc/default/grub file, replacing all references to fedora_BadHostname to fedora_GoodHostname, and grub-mkconfig yourself a new grub.conf file.
9. Reboot your system and allow GRUB to boot into your old host.
10. Confirm that the volume group name has been changed, and the /dev/fedora_BadHostname directory is renamed along with it.

I don't know if you'll conclude this to be too much trouble to simply rename your volume group; unless you had a really bad breakup with BadHostname, I wouldn't consider it necessarily pressing enough to change. If you aren't willing and able to recover from backup in the event of some sort of disaster, I wouldn't advise doing it. It's not a difficult procedure, but mistakes can be costly enough to prevent your system from booting, so you need to be very careful in attempting it.

Don't take that list above as the final, authoritative guide on this. If you need help constructing more specific steps from that general outline, I'll be glad to assist, but unless you're interested in it purely as a technical exercise (which is laudable), it's probably not worth your while.