Solution to RAID /boot issue in fc17?

[Reindl Harald]

Am 30.05.2012 15:43, schrieb Alan Cox:
>> Now, if your partition table starts at sector 63, you're still boned. But  
> 
> Nope. You can do it by hand.

confirmed

i moved /boot to 4096 to have peace the next years
on > 20 F15 installs before upgrade to F16

> Basically the Fedora installer is a mess. It's been going downhill for
> years and it just gets worse each release. Unfortunately with FC17 you
> can't really avoid using it due to the giant re-arrangement of /bin
> and /usr/bin

not really

http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_16_-.3E_Fedora_17

this works, expect that after the upgrade "revott" leads into
a kernel panic and you should do "sync; sync; sync" before
which will be funny on some remote amchines needing a person
to restart the machine hard

this is the same mess as the upgrade to F15 killed "reboot"
as long as you do not know about "kill 1" is working

after reboot my first test VM was upgraded from F16->F17 with YUM

never touch anaconda if there is any other way because it is the
most broken part of fedora including the preupgrade-incarnation
_____________________________

this machine was originally F14->F15->F16 and after
recognize that you have to add all mdraid-UUIDs to
kernel-bootline /boot on RAID1 is sync and stable

[root at raid ~]# uname -a
Linux raid.vmware.local 3.3.7-1.fc17.x86_64 #1 SMP Mon May 21 22:32:19 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

[root at raid ~]# cat /proc/mdstat
Personalities : [raid1] [raid10]
md1 : active raid10 sda2[4] sdc2[2] sdb2[1] sdd2[3]
      30428160 blocks super 1.1 512K chunks 2 near-copies [4/4] [UUUU]
      bitmap: 0/1 pages [0KB], 65536KB chunk

md0 : active raid1 sda1[6] sdd1[5] sdb1[4] sdc1[2]
      511988 blocks super 1.0 [4/4] [UUUU]

unused devices: <none>
[root at raid ~]# /bin/df -hT | grep ext4
/dev/md1       ext4       29G    1,8G   28G    7% /
/dev/md0       ext4      497M     56M  442M   12% /boot
_____________________________

May 19 18:47:26 Erased: less-444-2.fc16.x86_64
May 19 18:47:26 Erased: libpipeline-1.2.0-1.fc16.x86_64
May 19 18:47:26 Erased: procmail-3.22-29.fc16.x86_64
May 19 18:47:26 Erased: pciutils-3.1.7-6.fc16.x86_64
May 19 18:47:26 Erased: groff-1.21-3.fc16.x86_64
May 30 16:31:28 Updated: rpm-libs-4.9.1.3-7.fc17.x86_64
May 30 16:31:28 Updated: rpm-4.9.1.3-7.fc17.x86_64
May 30 16:31:28 Updated: rpm-build-libs-4.9.1.3-7.fc17.x86_64
May 30 16:31:28 Updated: rpm-python-4.9.1.3-7.fc17.x86_64
May 30 16:33:22 Updated: libgcc-4.7.0-5.fc17.x86_64
May 30 16:33:23 Updated: setup-2.8.48-1.fc17.noarch
May 30 16:33:24 Updated: filesystem-3-2.fc17.x86_64
May 30 16:33:24 Updated: ca-certificates-2012.81-1.fc17.noarch
May 30 16:33:24 Updated: color-filesystem-1-9.noarch
May 30 16:33:24 Updated: shared-color-profiles-0.1.5-2.fc17.noarch
May 30 16:33:24 Updated: kde-filesystem-4-39.fc17.x86_64





-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20120531/2c1e5aed/attachment.sig>