People,
For the last few versions of Fedora (x86_64) I have been going through this process:
- install a new SATA drive as /dev/sda
- boot to the previous Fedora now on /dev/sdb
- create a new virtual system using the latest Fedora on the new physical drive on /dev/sda
- get the new virtual Fedora on /dev/sda as ready as possible
- then re-boot to the new live system on /dev/sda
This process has been working fine for the last few versions but now for going from F19 to F20 and booting on the new F20 the process stops at:
[OK] Reached target Paths [OK] Reached target Basic System
I can still do a live boot on /dev/sdb and run the new F20 as a virt machine using physical drive /dev/sda OK but it was a nice process to reduce down time to be able to get the new Fedora as ready as possible as a virtual machine and then reboot it as the live machine. Has something changed that stops me doing this now?
Thanks,
Phil.
On Sat, 2014-05-31 at 11:40 +1000, Philip Rhoades wrote:
but now for going from F19 to F20 and booting on the new F20 the process stops at:
[OK] Reached target Paths [OK] Reached target Basic System
I encountered the same stalling point, but with an ordinary install.
Out of the two or three recent bouts of install grief, this one was due to the device numbering. During install, thanks to booting from a DVD, the install thought that the system root was /dev/sde instead of /dev/sda, and configured things like that. Check your kernel line in the boot menu for the wrong device name, and either correct it, or use the UUID of the drive partition, instead.
Oddly enough the next entry in my grub.cfg file was for a recovery boot mode, and that one had used the UUID, instead of the wrong device name.
I'm not impressed with the current install routine, and that was just one of the things about it that annoyed me.
-
Philip Rhoades -
Tim