Home > Cannot Boot > Cannot Boot After Vgrename

Cannot Boot After Vgrename

Learn More Red Hat Product Security Center Engage with our Red Hat Product Security team, access security updates, and ensure your environments are not exposed to any known security vulnerabilities. FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc. Comments from Brian suggest that there is no need to recreate the initramfs and that it can be done without booting into rescue mode. I've just tested Brian suggestions and he's right. lmo View Public Profile Find all posts by lmo Tags boot, lvm, problem, rename « Previous Thread | Next Thread » Thread Tools Show Printable Version Display Modes Linear Mode Switch this contact form

The live CD's won't even mount the partition! share|improve this answer answered Jan 29 '12 at 22:11 Nils 6,28911556 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign Spread the word:Click to share on Twitter (Opens in new window)Click to share on LinkedIn (Opens in new window)Click to email (Opens in new window)Click to print (Opens in new window)Like Code blocks~~~ Code surrounded in tildes is easier to read ~~~ Links/URLs[Red Hat Customer Portal](https://access.redhat.com) Learn more Close First time here? http://forums.fedoraforum.org/showthread.php?t=101931

Exit out of the chroot environment: exit Finally, unmount the filesystems and reboot (run the commands as root): umount -a reboot After that, the system should load normally. vgrename vg_old vg_new edit /etc/fstab and change the old vg references to the new vg name edit /boot/grub/grub.conf and change the old vg references to the new vg name reboot enjoy asked 4 years ago viewed 486 times active 4 years ago Visit Chat Related 1Cannot mount cdrom in Linux due to “I/O error”2Shouldn't all Linux based servers have / and /boot?2Linux In my case, there's a symlink named initrd that points to the appropriate file, but if there's none, use the name of the image file (it should look something like this:

I pressed 'e' and replaced all the old naming to the new one but no change. Setup Networking - Select "No" Rescue - Select "Continue" Rescue (message about your system being mounted under /mnt/sysimage and use of chroot) - OK. First Aid Kit quickstart menu - Select "shell  Start shell", then OK. yes, exactly here starts the problem.

Privacy policy About NST Wiki Disclaimers menuentry " ---------------------NST 20 (64 Bit) Boot Choices---------------------" { true } menuentry 'Console, Kernel: 3.12.5-302.fc20.x86_64' --class nst --class gnu-linux --class gnu --class os { savedefault load_video set gfxpayload=keep insmod gzio insmod Am I interrupting my husband's parenting? more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed

Volume group "nst_localhost" successfully renamed to "nst20" Wiping cache of LVM-capable devices Wiping internal VG cache Step 2: Update The File System Configuration File: "/etc/fstab" Use an editor (e.g., vi) to OS X: Some Icons Suddenly Disappeared in Finder OS X: Aquamacs and GNU Emacs -- Keyboard Problems on the Mac WebSphere Application Server: Jython Throws an IOException While Accessing Environment Variables If you do screw it up, it can be saved from a rescue image. Here are more steps and a reboot of the system necessary.

This said, here is a recipe: Boot your machine with a rescue or live Linux system which supports LVM as well as the file systems used on your system. (A good http://serverfault.com/questions/342258/linux-boot-issue-volgroup-issue What is the definition of "rare language"? I shall not be liable for any errors or for incidental or consequential damages. Probability of All Combinations of Given Events Storage of a material that passes through non-living matter n-dimensional circles!

I searched, found a few articles that seemed to have logic in their approach and figured I had nothing to lose. weblink You will change an essential part of your system so be prepared if something goes accidentally wrong or this instruction does not fit your Linux system. Here's the details: 1) Boot Into Rescue Mode For me booting from CD/iso was the easiest way to get into "rescue mode". End of update [5th August 2014] Fairly recently I walked into the same situation again, only this time I decided that I wasn't going to take "more complicated" for an answer🙂.

[email protected]# sudo [email protected]# apt-get install [email protected]# lvm vgscan Reading all physical volumes. Reply Josiah says: September 8, 2014 at 4:25 pm Actually, here's a bit of the script I use for setting up new VMs from a template: echo "changing LVM names" vgrename Current Customers and Partners Log in for full access Log In New to Red Hat? navigate here So system was rebooting again and again.

simonz View Public Profile Find all posts by simonz #2 30th March 2006, 08:10 PM SlowJet Offline Registered User Join Date: Jan 2005 Posts: 5,059 /boot/grub/menu.lst I think If there is no reference to volume groups or logical volumes, or activating them in the initrd then that may be a problem. Rescue Method - Select "Local CD/DVD", then OK.

edit flag offensive delete link more CommentsHi, it has brought me one step closer but it doesn't mount the boot file system.It says found the device.

This page has been accessed 39,844 times. Connect with top rated Experts 13 Experts available now in Live! asked 8 months ago viewed 100 times active 8 months ago Visit Chat Related 3Is it wise to still use Fedora 8 on a server?0Is there a Fedora boot CD image All relevant entries need to be changed.): . . .

Join & Ask a Question Need Help in Real-Time? How is it packed? Writing out updated volume group Renaming "/dev/nst_localhost" to "/dev/nst20" Loading nst_localhost-root table (253:0) Suppressed nst_localhost-root (253:0) identical table reload. his comment is here Then try and boot from the older kernel and if it works then you are away to the races.

You clone it and you realize that your preferred Linux distribution used the hostname of the original image for a volume group's name. It also says VolGroup01 found. Then it drops to initramfs, which lets me read some stuff but not write.