Kernel panic on fedup option using rEFInd

[Alexander H. Viborg]

Hello,

I'm running a dual boot system with Win8.1 and Fedora20 on a Samsung Ativ Book 9+.

I'm trying to upgrade from Fedora20 to Fedora21 on an up-to-date system. The initial upgrade process is running fine using FedUp, however when I reboot my system to proceed and I pick the linuzfedup using rEFInd I get the following error:

Kernel panic - Not syncing: VFC: Unable to mount root fs on unknown-block(0,0).
(This is how the entire screen output looks like: www.ahv.dk/kp.jpg)

Can anyone kindly advise me how I can try to solve this problem?
Also I'm now running kernel.3.7.17 (still I have the 3.17.4 in my system) but my attempts to get fedup to update to the newest kernel have also failed.

I'd appreciate any advise, thank you.

[Roderick W. Smith]

Fedup requires special kernel parameters on reboot. Unfortunately, I don't recall what they are, but you should be able to figure it out by examining the grub.cfg file that Fedup will have modified. You can then replicate those options by hitting F2 or Insert twice, rather than Enter, to launch the Fedup kernel. This will open a simple line editor in which you can edit the default options.

[Alexander H. Viborg]

Thanks for clarifying this.

Unfortunately I'm missing the grub.cfg file for whatever reason, so I can't access it to get the details that you advise.

Can I get these details somewhere else?

[Roderick W. Smith]

You could try Googling, or peruse the fedup source code. Unfortunately, I don't happen to know the options that fedup wants passed to the kernel.

[Alexander H. Viborg]

After consulting one of the main contributors of FedUp it became clear that FedUp after version 0.8 doesn't require any special boot parameters.

I ran a fedup --clean, then updated my system and ran FedUp again, everything went smooth from there - I'm not sure what caused the first kernel panic on reboot.

[Roderick W. Smith]

That's odd. I'd like to know what caused the problem initially, but at least you got past the problem. (My initial guess is that you had some random disk corruption on the first pass -- but I'm far from certain of that.)