f18 update woes

[William Murray]

   Dear Fedora-enthusiasts,
     I have just run fedup on a couple of F17 systems with sad 
consequences, and I am looking for help.

1) The first was an F17 along machine. I did a network 'fedup' which ran 
with no errors and left it for the
night. In the morning it was stick in a boot sequence. I can still boot 
the FC17 kernels (fortunately)
but the F18 always hangs almost immediately with an error about being 
unable to mount the filesystem.
No errors in the 3 log files. I tried reinstalling grub2 and 
removing/reading the F18 kernel but no joy

Generally install went OK, but with 2 monitors I still fall-back to 
gnome 3 mode. KDE did not upgrade; I think
it may be because later version numbers are already in FC17 then FC18.

2) The worse one in my dual-booting laptop. Win7+Fedora, using grub2 to 
chainload windows if desired.
  It is a somewhat convoluted system with Fedora 17 unencrypted plus a 
big encrypted partition.
I ran 'fedup' (to an iso DVD file) and got no errors. Then I hit reboot 
- and stuck at:
    File system boot sector (C) is reserved
    There is no OS to bot on this disk.
Using a rescue disk and reinstalling GRUB2 fixed the boot startup, but 
loading the fedup dracut then
times out waiting for device-mapper-luks and cannot boot. So I comment 
out the entry in /etc/fstab
But still the boot fails in the disk setup phase.  Any ideas?

   Thanks!
     Bill

-- 
Bill Murray                     ----                       ATLAS
STFC RAL at: Bat 40 4-C28, CERN,1211 Meyrin, Geneve 23, Switzerland
   Tel:- CERN +41 22 7678432    or  RAL +44 (0)1235 446256