Ask Your Question
1

Upgrading 16 to 17 with RAID boot

asked 2013-12-08 12:00:17 -0500

Baz Barbatus gravatar image

My Fedora server has languished in v15 since I bought it, and I recently managed to upgrade it to v16. It seems that I am now stuck not being able to go to v17 because preupgrade won't work with a mirrored disk boot (how do I confirm that boot is on the raid device?).

Sorry for very elementary knowledge but I am trying to be careful not to destroy my only file server while doing this!

I have seen some of the workarounds and they are beyond my level of understanding of Linux, involving burning something along the way. Apparently having a DVD drive will be useful and I have that. Internet connection is also OK. My yum is up to date. What route do you recommend from there?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2013-12-11 09:01:07 -0500

Nils Philippsen gravatar image

updated 2013-12-11 09:10:04 -0500

The only idea I have (preupgrade really can't cope with /boot on RAID) is to do a YUM upgrade[1] from 16 to 17[2] and from there on use fedup -- which should know about /boot on RAID1[3] -- to upgrade to a currently maintained version: Fedora 20 should be out in not quite a week[4], version 18 will be retired about a month after that.

  1. http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
  2. http://fedoraproject.org/wiki/Upgrading_from_EOL_Fedora_using_yum
  3. http://ohjeezlinux.wordpress.com/2012/11/13/fedup-a-little-background/
  4. http://fedoraproject.org/wiki/Releases/20/Schedule
edit flag offensive delete link more

Comments

Thank you very much, Nils. Having seen some comments elsewhere on difficulties with yum in some situations I was thinking that preupgrade was the only way in this case. But your answer gives me confidence to proceed with yum - it's obviously not the demon that it is painted. The long march to Fedora 20 begins!

Baz Barbatus gravatar imageBaz Barbatus ( 2013-12-13 05:17:15 -0500 )edit

I am following reference 2. above and got to the bit about grub: "Change the following kernel commandline parameter directly in the bootloader menu, which is shown during bootup, or edit the line in /etc/grub*.cfg to remove ro and rhgb and append rw rd.info rd.convertfs enforcing=0". I don't see a grub*.cfg but there is a grub.conf with three 'kernel' lines in. So I carried out the prescribed edit on all three, using vi, not knowing which is which. (I don't get it "shown during bootup" - so I don't know how to edit it that way). Reboot just shows blank screen with a cursor. What next?

Baz Barbatus gravatar imageBaz Barbatus ( 2013-12-18 09:13:52 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2013-12-08 12:00:17 -0500

Seen: 88 times

Last updated: Dec 11 '13