f18 update woes - success
Bill Murray
bill.murray at cern.ch
Thu Jan 17 12:43:55 UTC 2013
Hi all,
I finally made fedup work. Whoopee, now I have a nice new system.
Procedure:
* comment out two funny mounts I have in /etc/fstab
(mount an internal iso and mount a big encrypted disk with soft-links
into it)
* run fedup & boot
* reinstate the mounts
And finally all is well. As a side-bonus I have 60GB free that used to
have an unused windows partition :)
Bill
On 17/01/13 10:17, William Murray wrote:
> Dear all,
> I am still unable to install F18 on my laptop. After giving up on
> F17->F18 fedup upgrading
> I decided to delete my window partition and install F18 there. The
> installer started fine, but
> neither automatically not manually would it let me assign the disks.
> There is "only" 70GB free, but this should not be too little. But
> that is what both disk
> setup options report. Possibly this us due to the odd disk layout I
> have now:
>
> /dev/sda1 0.1GB DellUtility
> /dev/sda2 20GB Windows recovery
> Blank 68GB unused
> /dev/sda4 extended
> /dev/sda5 0.5GB /boot
> /dev/sda6 7.8GB luks (swap)
> /dev/sda7 400GB luks All-my-files
> /dev/sda8 99GB ext4 / F17 system
>
> Somehow F18 install is unable to squeeze in, whether I tell it to use the
> old swap space or not...
> Ideas?
> Bill
>
>
>
>
> On 16/01/13 16:14, William Murray wrote:
>> 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-C26, CERN,1211 Meyrin, Geneve 23, Switzerland
Tel:- CERN +41 22 7678432 or RAL +44 (0)1235 446256
More information about the users
mailing list