Hi, You are right, with the online solution (zypper dup), it worked like a sharm.... I have earned something new... Btw, for the OpenSuSE developers, i think that is a thing must be warned during the installation process from dvd, because it make the system un-bootable after update... I think this is a bad thing for a distro like OpenSuSE.... Cheers, Claudio. Il 23/11/2012 11:08, Vojtěch Zeisek ha scritto:
Hi, I was upgrading similar configuration to 12.1 and tomorrow I'm going to upgrade it to 12.2. I used upgrade using zypper dup from running system and it was working fine. Did You try this way? Once, when the system was broken, I booted from DVD and I was not able to see correct RAIDs nor LVM. Good luck! Vojtěch
Dne Pá 23. listopadu 2012 11:02:34, Claudio ML napsal(a):
Hello all,
I am testing on a virtual machine a problem it going me crazy. The problem is a rename of the md devices after the upgrade.
My system before the update have this configuration:
Personalities : [raid1] [raid0] [raid10] [raid6] [raid5] [raid4] md0 : active (auto-read-only) raid1 sda1[0] sdb1[1] 1051636 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk
md1: active raid1 sdb2[1] sda2[0] 3148788 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk
md2 : active raid1 sda3[0] sdb3[1] 16769976 blocks super 1.0 [2/2] [UU] bitmap: 1/1 pages [4KB], 65536KB chunk
md0 is swap, md1 is the root and md2 is the var partition.
The first problem i notice is on the upgrade process from the dvd. The system don't see automatically the root partition of the previous system, i have to select "show all partitions" and then select manually the root partition.
Then, after the update the system don't boot. I have to go to grub command line, set the kernel and initrd manually, and then the system boot. Then, i make a system update, and the mdadmd is patched.
After a reboot the situation is the following:
Personalities : [raid1] [raid0] [raid10] [raid6] [raid5] [raid4] md0 : active (auto-read-only) raid1 sda1[0] sdb1[1] 1051636 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk
md2 : active raid1 sda3[0] sdb3[1] 16769976 blocks super 1.0 [2/2] [UU] bitmap: 1/1 pages [4KB], 65536KB chunk
md127 : active raid1 sdb2[1] sda2[0] 3148788 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk
md1 is renamed as md127. Now, my questions are basically two:
- How i can rename md127 back to md1 ? i cant stop mdadm on this partition, is the root partition, so is mounted. - How i can do a clean update without all this issues? In this case the issue is small, but i have some cases where the md devices are renamed all, as md125,md126,md127 and the system won't boot anymore...
I have a backup of the system before the upgrade, so i can make any test if necessary to resolve that issue.
Help is needed, i am really disappointed about the update process for the OpenSuSE 12.1 and 12.2 with mdadm drives....
Claudio.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org