[opensuse] Big problem with mdadm and grub after update from 11.4 to 12.2
Hello all, After a DVD update from OpenSuSE 11.4 to 12.2, the system won't boot anymore. I can see now uses /dev/md125 /dev/md126 /dev/md127 (previously are /dev/md0 md1 etc.). I tryied what described here: http://lists.opensuse.org/opensuse-updates/2012-09/msg00019.html Without any success. Now i am trying to fix it, but with strange results. My actual situation is the following: mdadm --examine --scan ARRAY /dev/md127 UUID=41b65403:6ae2a15a:e25497b3:838ac1a8 ARRAY /dev/md125 UUID=8faffc2b:c1cbcd9f:40cf110f:2c33bb8a ARRAY /dev/md127 UUID=c649ac3a:7e130d44:da2c2182:96c632e9 notice the two md127 with different UUID. cat /proc/mdstat Personalities : [raid1] [raid0] [raid10] [raid6] [raid5] [raid4] md127 : active (auto-read-only) raid1 sda1[0] sdb1[1] 1052160 blocks [2/2] [UU] md125 : active raid1 sda2[0] sdb2[1] 3148672 blocks [2/2] [UU] unused devices: <none> mount devtmpfs on /dev type devtmpfs (rw,relatime,size=503192k,nr_inodes=125798,mode=755) tmpfs on /dev/shm type tmpfs (rw,relatime) tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) /dev/md125 on / type reiserfs (rw,relatime,user_xattr,acl) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=25,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) securityfs on /sys/kernel/security type securityfs (rw,relatime) tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) /dev/md125 on /var type reiserfs (rw,relatime,user_xattr,acl) tmpfs on /var/run type tmpfs (rw,nosuid,nodev,relatime,mode=755) tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,relatime,mode=755) md125 is mounted two times, in / and in /var.... cat /etc/fstab /dev/md126 / reiserfs acl,user_xattr 1 1 /dev/md125 /var reiserfs acl,user_xattr 1 2 /dev/md127 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 I am now a little confused, what i am missing? Help is needed.... Claudio. notice the two /dev/md126, with different UUID... Here is my mdadm --examine --scan output: -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Claudio ML wrote:
Hello all,
After a DVD update from OpenSuSE 11.4 to 12.2, the system won't boot anymore. ... I am now a little confused, what i am missing? Help is needed....
12.2 is considerably different from 11.4. You say you did an update. Did you update through 12.0 and 12.1 before going to 12.2? I wasn't aware that upgrading more than 1 version was supported, let alone 3. Can you boot from a rescue image and mount your root in /mnt of the rescue?... Depending on the state of things -- it used to be the case that you could chroot to /mnt and then do a mount -a, but depending on your partitions, that is much less likely to work in 12.2. You might try mounting root and var into /mnt .. i.e.: mount /dev/md126 / -o acl,user_xattr mount /dev/md125 /var -o acl,user_xattr mount proc /mnt/proc -t proc mount sysfs /mnt/sysfs -t sysfs mount devtmpfs /mnt/dev -t devtmpfs mount devpts /mnt/dev/pts -t devpts then chroot /mnt, and see if you can bring it up by hand. I think that will still work in 12.2, but unfortunately, it might not with systemd... but if it does, I'd try all the boot scripts at once -- but if it is really broken, you might want to run each by hand in order. But for a sequential, automated version: chroot /mnt cd /etc/rc.d/boot.d #(or "cd /etc/init.d/boot.d" # if you don't have an rc.d=>init.d symlink) for i in *;do $i start done --- At this point you might try "init 3" and see the rest of your services come up to the command line -- but I'm not sure that's supported on 12.2 -- it seems to default to a graphical boot, with 'systemd' having direct dependencies on X11 and full graphics mode (another design flaw, as X11 is yet another shaky layer to depend on if your intent is just to get the system up so you can login and see what's wrong). If none of that works, you might try "upgrading"/downgrading to 12.1. I think it supported most of the scripts (though I am not 100% sure about that given my own experience). Supposedly, if you use initd, all this should just work -- but if it doesn't, prospects for corrective action are shrinking. Note: I don't use /dev/md (my root is a RAID, but controlled via the driver (LSI)), so it looks like 1 device to linux, so if it is a problem in the /dev/md driver, or some interaction w/it. Given you only have 2 partitions setup in a RAID1, I have no clue why it would list 3 -- that just looks 'wrong'... (i.e. "bad"...but I don't know enough about the md driver to even begin to make suggestions there...)... Good luck.. BTW -- bringing up the system like above isn't meant as a "solution" -- just 1 step toward getting a working system that can allow you to fix it further!.... ;^) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 27 Nov 2012 22:24:00 -0800, Linda Walsh
Claudio ML wrote:
Hello all,
After a DVD update from OpenSuSE 11.4 to 12.2, the system won't boot anymore. ... I am now a little confused, what i am missing? Help is needed....
12.2 is considerably different from 11.4. You say you did an update. Did you update through 12.0 and 12.1 before going to 12.2?
I wasn't aware that upgrading more than 1 version was supported, let alone 3.
Can you boot from a rescue image and mount your root in /mnt of the rescue?...
Depending on the state of things -- it used to be the case that you could chroot to /mnt and then do a mount -a, but depending on your partitions, that is much less likely to work in 12.2.
You might try mounting root and var into /mnt .. i.e.:
mount /dev/md126 / -o acl,user_xattr mount /dev/md125 /var -o acl,user_xattr mount proc /mnt/proc -t proc mount sysfs /mnt/sysfs -t sysfs mount devtmpfs /mnt/dev -t devtmpfs mount devpts /mnt/dev/pts -t devpts
then chroot /mnt, and see if you can bring it up by hand.
I think that will still work in 12.2, but unfortunately, it might not with systemd...
but if it does, I'd try all the boot scripts at once -- but if it is really broken, you might want to run each by hand in order.
But for a sequential, automated version:
chroot /mnt cd /etc/rc.d/boot.d #(or "cd /etc/init.d/boot.d" # if you don't have an rc.d=>init.d symlink) for i in *;do $i start done --- At this point you might try "init 3" and see the rest of your services come up to the command line -- but I'm not sure that's supported on 12.2 -- it seems to default to a graphical boot, with 'systemd' having direct dependencies on X11 and full graphics mode (another design flaw, as X11 is yet another shaky layer to depend on if your intent is just to get the system up so you can login and see what's wrong).
If none of that works, you might try "upgrading"/downgrading to 12.1.
I think it supported most of the scripts (though I am not 100% sure about that given my own experience).
Supposedly, if you use initd, all this should just work -- but if it doesn't, prospects for corrective action are shrinking.
Note: I don't use /dev/md (my root is a RAID, but controlled via the driver (LSI)), so it looks like 1 device to linux, so if it is a problem in the /dev/md driver, or some interaction w/it.
Given you only have 2 partitions setup in a RAID1, I have no clue why it would list 3 -- that just looks 'wrong'... (i.e. "bad"...but I don't know enough about the md driver to even begin to make suggestions there...)...
Good luck..
BTW -- bringing up the system like above isn't meant as a "solution" -- just 1 step toward getting a working system that can allow you to fix it further!.... ;^)
Hello, You could also do a fresh 12.2 install and use the old boot partition, # fdisk -l tells you that info see[1] for example. --Glenn [1] # fdisk -l Disk /dev/sda: 64.0 GB, 64023257088 bytes 255 heads, 63 sectors/track, 7783 cylinders, total 125045424 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xcc791374 Device Boot Start End Blocks Id System /dev/sda1 63 41046074 20523006 7 HPFS/NTFS/exFAT /dev/sda2 * 41048064 61528063 10240000 83 Linux /dev/sda3 61528950 120937319 29704185 83 Linux /dev/sda4 120937320 125033894 2048287+ 82 Linux swap / Solaris -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Linda Walsh wrote:
Claudio ML wrote:
Hello all,
After a DVD update from OpenSuSE 11.4 to 12.2, the system won't boot anymore. ... I am now a little confused, what i am missing? Help is needed....
12.2 is considerably different from 11.4. You say you did an update. Did you update through 12.0 and 12.1 before going to 12.2?
I wasn't aware that upgrading more than 1 version was supported, let alone 3.
"Not supported" != "doesn't work" :-) I'm pretty certain I've done upgrades from 11.4 to 12.2 with no or only minimum problems.
Can you boot from a rescue image and mount your root in /mnt of the rescue?...
Depending on the state of things -- it used to be the case that you could chroot to /mnt and then do a mount -a, but depending on your partitions, that is much less likely to work in 12.2.
It works fine actually, but don't forget to bind in /proc and /dev before chroot'ing. Still, the OP's problem is really about the RAID config, afaict. I know have also seen the mysterious md12[567] et al but in my case it was caused by left-over superblocks that I no longer needed. It's been a week since the original posting, so perhaps the problem has been solved? Otherwise I would be tempted to delete the md12[567], and then re-assemble the arrays in the way you know they're supposed to work. With all the usual caveats, don't forget to backup, wear belts and suspenders, hard hat etc. -- Per Jessen, Zürich (5.9°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-11-28 09:43, Per Jessen wrote:
Still, the OP's problem is really about the RAID config, afaict. I know have also seen the mysterious md12[567] et al but in my case it was caused by left-over superblocks that I no longer needed.
I have seen several similar reports. I understand there is a bugzilla about it. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlC11tIACgkQIvFNjefEBxpc/gCgsWpXjMcAXZmlo9NAFA3+taE6 OTwAn1aUWmIW0XZrhmzE7+3i7FNa7gWR =KBEC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 28/11/2012 09:43, Per Jessen ha scritto:
Linda Walsh wrote:
Claudio ML wrote:
Hello all,
After a DVD update from OpenSuSE 11.4 to 12.2, the system won't boot anymore. ... I am now a little confused, what i am missing? Help is needed....
12.2 is considerably different from 11.4. You say you did an update. Did you update through 12.0 and 12.1 before going to 12.2?
I wasn't aware that upgrading more than 1 version was supported, let alone 3. "Not supported" != "doesn't work" :-) I'm pretty certain I've done upgrades from 11.4 to 12.2 with no or only minimum problems.
Can you boot from a rescue image and mount your root in /mnt of the rescue?...
Depending on the state of things -- it used to be the case that you could chroot to /mnt and then do a mount -a, but depending on your partitions, that is much less likely to work in 12.2. It works fine actually, but don't forget to bind in /proc and /dev before chroot'ing.
Still, the OP's problem is really about the RAID config, afaict. I know have also seen the mysterious md12[567] et al but in my case it was caused by left-over superblocks that I no longer needed.
It's been a week since the original posting, so perhaps the problem has been solved? Otherwise I would be tempted to delete the md12[567], and then re-assemble the arrays in the way you know they're supposed to work. With all the usual caveats, don't forget to backup, wear belts and suspenders, hard hat etc.
I have solved the problem re-installing everything, but i have also made some experiments with a virtual machine. My setup is the following: - Install virtual machine with 11.4, md0 = root (/), md1 = swap, md2 = /home. - Upgrade the system with OpenSuSE 12.2 from DVD: same result, md renamed as md125 etc, system won't boot - Upgrade the system with OpenSuSE 12.2 from internet (zypper dup): system boot up normally after update, no md rename, and no problems at all. - Upgrade the system with OpenSuSE 12.1 from DVD: same result, md renamed as md125 etc, system won't boot I hope this tests can be useful for someone, now my guess is the DVD upgrade system with md devices is broken.a Cordially, Claudio Prono. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-11-28 13:12, Claudio ML wrote:
I hope this tests can be useful for someone, now my guess is the DVD upgrade system with md devices is broken.a
True. As I said, I think there is a bugzilla, but I'm not sure which. You should add a note to it. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlC2AhMACgkQIvFNjefEBxo9QQCfT+j5eQJbTAj9WnhqIO3F1465 3xwAoJdCDbqVMpR+IiwdEhlQeUwFh2YI =ZcLD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-11-28 07:24, Linda Walsh wrote:
Claudio ML wrote:
12.2 is considerably different from 11.4. You say you did an update. Did you update through 12.0 and 12.1 before going to 12.2?
there is no 12.0
I wasn't aware that upgrading more than 1 version was supported, let alone 3.
Via DVD upgrade, yes. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlC11nkACgkQIvFNjefEBxqU4gCdHHzGQ/i04BiJ7DZGgqvAguBP CHMAn1JcHfdQahv5GuxtMe9QX5zphSoI =W3il -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R. -
Claudio ML -
doiggl＠velocitynet.com.au -
Linda Walsh -
Per Jessen