Create virt F20 on new physical /dev/sda -> OK; boot live > F20 on /dev/sda now fails

Philip Rhoades phil at pricom.com.au
Sat May 31 23:44:46 UTC 2014


Tim,


> Date: Sat, 31 May 2014 13:35:38 +0930
> From: Tim <ignored_mailbox at yahoo.com.au>
> To: users at lists.fedoraproject.org
> Subject: Re: Create virt F20 on new physical /dev/sda -> OK; boot live
> 	F20	on /dev/sda now fails
> Message-ID: <1401509138.1661.5.camel at fluffy.lan.cameratim.com>
> Content-Type: text/plain; charset="UTF-8"
> 
> 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.


Ah . . well spotted - I should have seen that - thanks!


> George Orwell's '1984' was supposed to be a warning against tyranny, 
> not
> a set of instructions for supposedly democratic governments.


A great (but sad) sig!

Regards,

Phil.
-- 
Philip Rhoades

GPO Box 3411
Sydney NSW	2001
Australia
E-mail:  phil at pricom.com.au


More information about the users mailing list