[Bug 779087] New: after 12.1->12.2 upgrade, system with ROOT on LVM-on-RAID fails to boot; loops VG not found/partial mode
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c0 Summary: after 12.1->12.2 upgrade, system with ROOT on LVM-on-RAID fails to boot; loops VG not found/partial mode Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ar16@imapmail.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 My a number opensuse 12.1 boxes that have: /boot on RAID-1 /root on LVM on RAID-10 They've been configured and running that way, without issue, for a long time. I'm working on 12.1->12.2 upgrades. The upgrades were performed by (1) adding the full isntall DVD as a priority 98 (1 above default 99) source (2) zypper dup (3) remove/disable the DVD source (4) zypper dup All boxes that have NO raid involvement have upgraded without incident; boot is fine. On all boxes that have a RAID array +LVMs, post 12.1->12.2 upgrade fail to find their respective VolumeGroups. They boot, 'thru' grub, but only get so far as the boot console endlessly looping the following message: "Volume Group "VG_XX" not found. Partial Mode. Incomplete logical volumes will not be processed" I've verified that it's not a problem with the array -- it assembles fine if I boot from a non-systemd-init rescue disk, e.g. SystemRescueCD. I've been asked (by AJaeger @ #opensuse-factory) to file this bug, and attache a photo of the boot screen and to "use the rescue system to show the setup". I've attached the photo here, but boot from the Opensuse 122 full-install diskis'sresuce system fails. It just hangs at the 'green screen + chameleon'. Attempting to booting from a sysvinit fallback init via the grub prompt to switch the init system , specifying "init=/sbin/init.sysv.fallback" on kernel grub line, unfortunately does NOT fix the problem; same error -- not finding the VG. Again, boot from 'systemrescueCD' does find the array. This is true on 3 different upgraded machines I've just checked. Chatting in #lvm, the following was offered: <kabi_> Aresby: I guess you will need to ask package maintainer for your distro for help [07:19] <Aresby> kabi_: So nothing @lvm that's fundamentally at-odds with systemd? [07:20] <kabi_> Aresby: since systemd is quite invasive in the system boot process and it's highly quite a bit distro specific [07:21] <kabi_> Aresby: Well there are some on going steps being made in Fedora Rawhide towards better intergration of systemd and lvm and in general Fedora should mostly always work [07:21] <kabi_> Aresby: but I've no idea how the Opensuse is resolving related problems (and there are some...) [07:22] <wN> Aresby: i was giogn to say that if it was a non-root volume you could try adding _netdev to the mount options to delay the startup [07:23] <Aresby> wN to grub kernel line? [07:23] <wN> to fstab [07:23] <Aresby> ah, hence the non-root reqt. [07:23] <wN> partially activation usually only happens when some PVs are missing, but others are not. [07:24] <wN> (in the vg) [07:24] <wN> it looks like you're already going into partial mode, which means that parts of the LV could be missing [07:25] <Aresby> wN Not clear how that might be the case. It's one PV & one VG across a 4-disk RAID-10 array. [07:25] <wN> that is odd. [07:25] <kabi_> do problem is that you need to ensure all volumes are ready and available [07:25] <wN> perhaps there is another scenario that invokes partial activation. [07:26] <kabi_> and in Fedora for a long time there was udevadm settle used for this [07:26] <Aresby> wN: & if it were 'missing' for some persistent/physical reason, I'd expect it to be also the case when booted from other media [07:26] <Aresby> kabi_: specifically for the systemd case? [07:27] <kabi_> Aresby: yes - which slows down to booting process - since udev cannot wait only for particalar discs [07:28] <kabi_> Aresby: now ongoing modificaition are trying to bring-in auto-activation in the right time - but that's still under developement and just somehow explored/tested in Rawhide Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c1 --- Comment #1 from A R <ar16@imapmail.org> 2012-09-06 15:24:13 UTC --- Created an attachment (id=504718) --> (http://bugzilla.novell.com/attachment.cgi?id=504718) Requested photo of failed boot process -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c2 --- Comment #2 from A R <ar16@imapmail.org> 2012-09-06 16:17:39 UTC --- boot unbootable-box from systemresucecd mount partitions & chroot in systemctl enable udev-settle.service exit reboot unfortunately makes no difference -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c3 --- Comment #3 from A R <ar16@imapmail.org> 2012-09-06 16:40:14 UTC --- also, boot unbootable-box from systemresucecd mount partitions & chroot in uninstall systemd-sysvinit install sysvinit-init reboot i.e., effectively removing systemd from the equation STILL makes no difference -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com, | |fcrozat@suse.com, | |fehr@suse.com AssignedTo|bnc-team-screening@forge.pr |xwhu@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c4 --- Comment #4 from A R <ar16@imapmail.org> 2012-09-06 20:30:18 UTC --- Created an attachment (id=504768) --> (http://bugzilla.novell.com/attachment.cgi?id=504768) verbose lvm2.log capture @ boot process / fail here's an lvn log of the event edit /etc/lvm.conf ... log { ... verbose = 3 file=/var/log/lvm2.log overwrite=1 level=7 ... reboot from opensuse 12.2 root fail @ VG/LVM mount reboot from systemrescueCD capture /var/log/lvm2.log egrep -i "lv_|vg|desk|/dev/md" lvm2.log > lvm2.filter.log <==== attachment It's confusing in that it appears the VG & LVs are being recognized. Doesn't explain to me why it'd be failing to complete the boot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c5 --- Comment #5 from A R <ar16@imapmail.org> 2012-09-06 20:38:32 UTC --- This only seems to a problem if ROOT lvms are on RAID. Upgrade of 12.1 -> 12.2 where /boot is on partition, and 'rest', including ROOT "/" is on LVMs, has no issues. It's only a problem if RAID is in the mix as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c6 --- Comment #6 from A R <ar16@imapmail.org> 2012-09-06 21:48:48 UTC --- Chatting in #systemd, <MK_FG> Not sure if suse has these, but do you see green "[ OK ]"'s on the left, as in http://freedesktop.org/wiki/Software/systemd?action=AttachFile&do=get&target=screenshot.png ? ;) <MK_FG> If not, might be a good indication that it's not systemd yet, and you might need to rebuild or reconfigure that initrd, which is probably suse-specific and should have docs somewhere... <MK_FG> I think grub can handle mdraid and lvm these days, so running grub isn't really an indication that kernel or initrd gets them right <Aresby> MK_FG: In normal/functional boots, yes. E.g., booting to a box that has "/" on LVM, that's NOT on RAID works fine, and I get the usual "green [OK]" bits n pieces. With this misbehaving system, I'm seeing endless looping of this: http://bugzillafiles.novell.org/attachment.cgi?id=504718 ... <MK_FG> Maybe replace /sbin/init (systemd) on lvm-root with /bin/bash? I replaced the Opensuse 122's /sbin/init -> ../lib/systemd/systemd link with /sbin/int -> /bin/bash and rebooted. No change in bahvior, I'm stuck again in that green-screen VG "not found" loop. Further comment in channel, <MK_FG> I think it's safe to say that initrd just can't find/mount / <MK_FG> So not much point debugging systemd, if it doesn't even try to run it -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c7 --- Comment #7 from A R <ar16@imapmail.org> 2012-09-06 22:31:03 UTC --- If in fact the comments @ #irc are correct, and the problem is in/at the initrd, looking for the source of the failure's "Partial" mode VG scan message, I might arise from: /lib/mkinitrd/scripts/boot-devfunctions.sh 85 usleep 25000 86 ((timeout % 40 == 1)) && echo -n "." 87 let timeout-- 88 # Recheck for LVM volumes 89 if [ -n "$vg_root" -a -n "$vg_roots" ] ; then 90 vgscan 91 for vgr in $vg_root $vg_roots; do 92 vgchange -a y --partial --sysinit $vgr 93 done 94 wait_for_events 95 fi 96 done 97 fi 98 if [ -x /sbin/multipath ] && [ -n "$vg_root" -a -n "$vg_roots" ] ; then 99 echo "Resetting LVM for multipath" 100 vgchange --sysinit -a n 101 multipath -v 0 102 wait_for_events 103 vgscan 104 for vgr in $vg_root $vg_roots; do 105 vgchange -a y --partial --sysinit $vgr 106 done 107 wait_for_events Which, at 1st glance, looks like a timeout issue. Trying to get a better sense for what's going in that code. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c8 --- Comment #8 from A R <ar16@imapmail.org> 2012-09-07 00:10:53 UTC --- There's some trouble in mkinitrd, as exec'd while in the chroot'd Opensuse env: mkinitrd -v ---------------------------------- Kernel image: /boot/vmlinuz-3.4.6-2.10-desktop Initrd image: /boot/initrd-3.4.6-2.10-desktop Root device: /dev/VG_DESK/LV_ROOT (mounted on / as ext4) /lib/mkinitrd/setup/41-md.sh: line 83: md_conf_ardesk:ardesk1=ARRAY /dev/md/ardesk:ardesk1 metadata=1.2 name=ardesk:ardesk1 UUID=d47afb79:e5fa9b28:ff35c586:f2602920: No such file or directory [BLOCK] /dev/sda -> ahci [BLOCK] /dev/sdb -> ahci [BLOCK] /dev/sdc -> ahci [BLOCK] /dev/sdd -> ahci [MODULES] 01-acpi.sh: thermal processor fan [MODULES] 02-start.sh: jbd2 jbd raid0 raid1 raid10 raid456 ahci dm-mod dm-crypt dm-snapshot ext4 btrfs xfs vfat aes sha1 sha256 sha512 dummy processor thermal pata_amd sata_nv ata_generic fan edd forcedeth nvidia [MODULES] 02-start.sh: [MODULES] 03-dm.sh: [MODULES] 03-dm.sh: dm-mod [MODULES] 03-dm.sh: dm-snapshot [MODULES] 03-rtc.sh: rtc_cmos [MODULES] 03-scsi_dh.sh: scsi_dh_emc scsi_dh_alua scsi_dh_rdac scsi_dh_hp_sw [MODULES] 03-storage.sh: [MODULES] 11-block.sh: ahci [MODULES] 11-usb.sh: usbcore [MODULES] 11-usb.sh: ohci_hcd [MODULES] 11-usb.sh: uhci-hcd [MODULES] 11-usb.sh: ehci_hcd [MODULES] 11-usb.sh: xhci-hcd [MODULES] 11-usb.sh: usbhid [MODULES] 11-usb.sh: hid-logitech-dj [MODULES] 11-usb.sh: hid-generic [MODULES] 21-nfs.sh: nfs [MODULES] 51-md.sh: raid0 [MODULES] 51-md.sh: raid1 [MODULES] 51-md.sh: raid10 [MODULES] 51-md.sh: raid456 [MODULES] 61-lvm2.sh: linear [MODULES] 'modinfo -k "3.4.6-2.10-desktop" -F supported' returned with an error. modprobe: Module hid_generic not found. WARNING: no dependencies for kernel module 'hid-generic' found. Kernel Modules: thermal_sys thermal processor fan raid0 raid1 raid10 async_tx async_memcpy xor async_xor raid6_pq async_pq async_raid6_recov raid456 dm-mod dm-crypt dm-snapshot libcrc32c zlib_deflate btrfs xfs fat vfat aes-x86_64 cryptd aesni-intel padlock-aes sha1_generic sha1-ssse3 sha256_generic sha512_generic dummy pata_amd sata_nv ata_generic edd forcedeth nvidia scsi_dh scsi_dh_emc scsi_dh_alua scsi_dh_rdac scsi_dh_hp_sw xhci-hcd hid-logitech-dj sunrpc nfs_acl auth_rpcgss fscache lockd nfs linear crc32c [MOUNT] Root: /dev/VG_DESK/LV_ROOT Features: acpi dm EC2 block usb nfs md lvm2 Bootsplash: openSUSE (1280x1024), openSUSE (1920x1080) Shared libs: lib64/ld-2.15.so lib64/libacl.so.1.1.0 lib64/libattr.so.1.1.0 lib64/libcap.so.2.22 usr/lib64/libcom_err.so.2.1 lib64/libcrypto.so.1.0.0 lib64/libc-2.15.so lib64/libdbus-1.so.3.7.0 lib64/libdevmapper-event.so.1.02 lib64/libdevmapper.so.1.02 lib64/libdl-2.15.so usr/lib64/libe2p.so.2.3 usr/lib64/libext2fs.so.2.4 lib64/libgssglue.so.1.0.0 lib64/libkeyutils.so.1.4 usr/lib64/libkmod.so.2.1.0 lib64/libm-2.15.so lib64/libpci.so.3.1.9 lib64/libpthread-2.15.so lib64/libreadline.so.6.2 lib64/libresolv-2.15.so lib64/librt-2.15.so lib64/libselinux.so.1 lib64/libsepol.so.1 lib64/libssl.so.1.0.0 lib64/libtinfo.so.5.9 lib64/libtirpc.so.1.0.10 lib64/libudev.so.0.13.1 lib64/libutil-2.15.so lib64/libz.so.1.2.7 usr/lib64/libatasmart.so.4.0.4 usr/lib64/libblkid.so.1.1.0 usr/lib64/libcups.so.2 usr/lib64/libdal-0.3.so.0.0.0 usr/lib64/libffi.so.4.0.1 usr/lib64/libgdk_pixbuf-2.0.so.0.2600.1 usr/lib64/libgio-2.0.so.0.3200.3 usr/lib64/libglib-2.0.so.0.3200.3 usr/lib64/libgmodule-2.0.so.0.3200.3 usr/lib64/libgobject-2.0.so. 0.3200.3 usr/lib64/libgpod.so.4.3.2 usr/lib64/libgssapi_krb5.so.2.2 usr/lib64/libimobiledevice.so.3.0.1 usr/lib64/libk5crypto.so.3.1 usr/lib64/libkrb5.so.3.3 usr/lib64/libkrb5support.so.0.1 usr/lib64/liblzma.so.5.0.3 usr/lib64/libmount.so.1.1.0 usr/lib64/libmtp.so.9.0.3 usr/lib64/libparted.so.0.0.2 usr/lib64/libpcre.so.1.0.0 usr/lib64/libplist.so.1.1.8 usr/lib64/libreiserfs-0.3.so.0.0.0 usr/lib64/libsgutils2.so.2.0.0 usr/lib64/libsqlite3.so.0.8.6 usr/lib64/libsystemd-daemon.so.0.0.1 usr/lib64/libsystemd-id128.so.0.0.3 usr/lib64/libsystemd-journal.so.0.0.3 usr/lib64/libusb-0.1.so.4.4.4 usr/lib64/libusb-1.0.so.0.1.0 usr/lib64/libusbmuxd.so.1.0.8 usr/lib64/libuuid.so.1.3.0 usr/lib64/libxml2.so.2.7.8 lib64/libnss_dns-2.15.so lib64/libnss_dns.so.2 lib64/libnss_files-2.15.so lib64/libnss_files.so.2 lib64/libgcc_s.so.1 ---------------------------------- There are consistent/carried over from prior to the upgrade: mdadm -D -s ARRAY /dev/md/ardesk:ardesk1 metadata=1.2 name=ardesk:ardesk1 UUID=d47afb79:e5fa9b28:ff35c586:f2602920 ARRAY /dev/md/126_0 metadata=0.90 UUID=52f5b43c:e83f7e2a:be6ad32e:0536ab0e cat /etc/mdadm.conf ARRAY /dev/md/0_0 level=raid1 num-devices=4 metadata=0.90 UUID=52f5b43c:e83f7e2a:be6ad32e:0536ab0e ARRAY /dev/md/ardesk:ardesk1 level=raid10 num-devices=4 metadata=1.2 UUID=d47afb79:e5fa9b28:ff35c586:f2602920 name=name=ardesk:ardesk1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@suse.com, | |xwhu@suse.com AssignedTo|xwhu@suse.com |mmarek@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c9 Michal Marek <mmarek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ar16@imapmail.org --- Comment #9 from Michal Marek <mmarek@suse.com> 2012-09-07 13:49:52 UTC --- Please attach http://en.opensuse.org/openSUSE:Bugreport_mkinitrd#Logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c10 A R <ar16@imapmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ar16@imapmail.org | --- Comment #10 from A R <ar16@imapmail.org> 2012-09-07 14:07:39 UTC --- Created an attachment (id=504866) --> (http://bugzilla.novell.com/attachment.cgi?id=504866) requested mkinitrd log
Please attach http://en.opensuse.org/openSUSE:Bugreport_mkinitrd#Logs
attached -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c11 A R <ar16@imapmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #504866|0 |1 is obsolete| | --- Comment #11 from A R <ar16@imapmail.org> 2012-09-07 14:21:07 UTC --- Created an attachment (id=504867) --> (http://bugzilla.novell.com/attachment.cgi?id=504867) requested mkinitrd log Created an attachment (id=504866) --> (http://bugzilla.novell.com/attachment.cgi?id=504866) [details] requested mkinitrd log
Please attach http://en.opensuse.org/openSUSE:Bugreport_mkinitrd#Logs
attached -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c12 --- Comment #12 from A R <ar16@imapmail.org> 2012-09-08 16:01:48 UTC --- Had to get these 'down' operating/in-production boxes back up. Downgrade 12.2 back to 12.1 (using zypper dup + 12.1 iso) cures the problem. 1st reboot after downgrade recognizes ROOT on LVM-on-RAID. Boot to desktop is complete - no issues. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c13 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ar16@imapmail.org --- Comment #13 from Neil Brown <nfbrown@suse.com> 2012-09-12 02:15:47 UTC --- If/when you would like to try again, I think I can make it work for you. I'll attach an updated mkinitrd-setup file for md. To try it out, you would need to "zypper dup" back up to 12.2, then copy this file to /lib/mkinitrd/scripts/setup-md.sh and then run "mkinitrd". This should then create a correct initrd and the system should boot. Please report if when works when convenient. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c14 --- Comment #14 from Neil Brown <nfbrown@suse.com> 2012-09-12 02:17:09 UTC --- Created an attachment (id=505339) --> (http://bugzilla.novell.com/attachment.cgi?id=505339) New /lib/mkinitrd/scripts/setup-md.sh file -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c15 A R <ar16@imapmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|ar16@imapmail.org |nfbrown@suse.com --- Comment #15 from A R <ar16@imapmail.org> 2012-09-12 02:39:26 UTC --- Thanks for the script. Question: The boxes I'd reported having trouble with all had root "/" on LV-on-RAID-10. To test this on those production boxes again will take a little time. I *do* have a less-critical, more readily available, box that is similarly configured, but rather than RAID-10, metadata_v1.2, it's "/" on LV-on-RAID-1, with metadata_v1.0 Looking at the script, IIUC, neither the RAID class nor metadata type should matter. Is that correct? Will a test on the -RAID-1, metadata_v1.0 box be sufficient? or at least informative? Its config is: mdadm -D -s ARRAY /dev/md0 metadata=0.90 UUID=ec1... <-- /boot ARRAY /dev/md126 metadata=1.0 name=Rescue:1 UUID=a1b... <-- / cat /proc/mdstat md0 : active raid1 sda1[0] sdb1[1] 200704 blocks [2/2] [UU] bitmap: 0/25 pages [0KB], 4KB chunk md126 : active raid1 sda2[0] sdb2[2] 243987048 blocks super 1.0 [2/2] [UU] unused devices: <none> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c16 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|nfbrown@suse.com |ar16@imapmail.org --- Comment #16 from Neil Brown <nfbrown@suse.com> 2012-09-12 02:56:07 UTC --- Yes, it is worth checking on that machine. The key problem is that the name of the md array, as found in "ls /dev/md" has a ':' in it. So the style of array and even the presence of LVM isn't relevant. It is just the name that causes problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c17 --- Comment #17 from A R <ar16@imapmail.org> 2012-09-12 20:27:58 UTC --- On the RAID-1 box -- mkinitrd Scanning scripts ... Resolve dependencies ... Install symlinks in /lib/mkinitrd/setup ... Install symlinks in /lib/mkinitrd/boot ... Kernel image: /boot/vmlinuz-3.4.6-2.10-default Initrd image: /boot/initrd-3.4.6-2.10-default Root device: /dev/VG_S03/LV_ROOT (mounted on / as ext4) modprobe: Module hid_generic not found. WARNING: no dependencies for kernel module 'hid-generic' found. Kernel Modules: thermal_sys thermal processor fan raid0 raid1 raid10 async_tx async_memcpy xor async_xor raid6_pq async_pq async_raid6_recov raid456 dm-mod dm-crypt dm-snapshot libcrc32c zlib_deflate btrfs xfs aes-x86_64 cryptd aesni-intel padlock-aes sha1_generic sha1-ssse3 sha256_generic sha512_generic dummy edd cpuid sata_sil24 scsi_dh scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac scsi_dh_alua crc-itu-t firewire-core firewire-ohci usb-common usbcore pcmcia_core pcmcia mmc_core ssb ohci-hcd uhci-hcd ehci-hcd xhci-hcd usbhid hid-logitech-dj scsi_transport_iscsi libiscsi libiscsi_tcp iscsi_tcp crc32c sunrpc nfs_acl auth_rpcgss fscache lockd nfs linear Features: acpi dm plymouth block firewire usb iscsi dmraid nfs kpartx md lvm2 resume.userspace resume.kernel Kernel image: /boot/vmlinuz-3.4.6-2.10-xen Initrd image: /boot/initrd-3.4.6-2.10-xen Root device: /dev/VG_S03/LV_ROOT (mounted on / as ext4) modprobe: Module hid_generic not found. WARNING: no dependencies for kernel module 'hid-generic' found. Kernel Modules: hwmon thermal_sys thermal processor fan raid0 raid1 raid10 async_tx async_memcpy xor async_xor raid6_pq async_pq async_raid6_recov raid456 dm-mod dm-crypt dm-snapshot libcrc32c zlib_deflate btrfs xfs aes-x86_64 cryptd aesni-intel padlock-aes sha1_generic sha1-ssse3 sha256_generic sha512_generic dummy edd cpuid serial_core 8250 sata_sil24 xennet cdrom xenblk scsi_dh scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac scsi_dh_alua crc-itu-t firewire-core firewire-ohci usb-common usbcore pcmcia_core pcmcia mmc_core ssb ohci-hcd uhci-hcd ehci-hcd xhci-hcd hid usbhid hid-logitech-dj scsi_transport_iscsi libiscsi libiscsi_tcp iscsi_tcp crc32c sunrpc nfs_acl auth_rpcgss fscache lockd nfs linear Features: acpi dm plymouth block firewire usb iscsi dmraid nfs kpartx md lvm2 resume.userspace resume.kernel unclear what that "modprobe: Module hid_generic not found." is about. anyway, for now, reboot to default, NON-Xen kernel ... boots completely. after boot, lsb_release -a LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch Distributor ID: SUSE LINUX Description: openSUSE 12.2 (x86_64) Release: 12.2 Codename: Mantis uname -a Linux server 3.4.6-2.10-default #1 SMP Thu Jul 26 09:36:26 UTC 2012 (641c197) x86_64 x86_64 x86_64 GNU/Linux but, cat /proc/mdstat Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [linear] md0 : active raid1 sda1[0] sdb1[1] 200704 blocks [2/2] [UU] bitmap: 0/25 pages [0KB], 4KB chunk md126 : active raid1 sdb2[2] sda2[0] 243987048 blocks super 1.0 [2/2] [UU] [>....................] resync = 4.0% (9968128/243987048) finish=48.8min speed=79788K/sec unused devices: <none> where 'md126' is the ROOT vol. I don't know if that's problematic, or even related. In any case, I'm going to allow that rebuild to complete before I do anything further, and/or try the -Xen kernel's boot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c18 A R <ar16@imapmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ar16@imapmail.org | --- Comment #18 from A R <ar16@imapmail.org> 2012-09-12 20:30:37 UTC --- . -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c19 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|mmarek@suse.com |nfbrown@suse.com --- Comment #19 from Neil Brown <nfbrown@suse.com> 2012-09-12 23:59:27 UTC --- That's looking good. The "hid-generic" this is messy but unrelated. I get it too. It seems that hid-generic was added in 3.5 so the initrd code needs to look for it, but will fail for 3.4 kernels. Strangely 3.5.0-35-desktop has hid-generic, but 3.5.0-36-desktop doesn't.... looks like it was changed from being a module to being built in to the kernel. It might be a message we just have to live with. The resync is not expected. The mostly likely explantion is that the shutdown wasn't a clean shutdown. Is that possible? If it recurs on subsequent reboots I try to work out why, otherwise it probably isn't fruitful to explore it further. I've got another mdadm issue that I'm awaiting confirmation of the fix for. Once that is confirmed I'll see about scheduling an update to fix this bug and that one. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c20 --- Comment #20 from A R <ar16@imapmail.org> 2012-09-13 02:58:23 UTC --- After allowing that resync to finish, I was able to boot successfully three times in sequence, without triggering another resync. Next, I tried to boot to the Xen kernel (this box's "natural state" is, in fact, as a Xen server) -- hung on boot. Rebooted immediately to the NON-Xen, default kernel, and again: Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [linear] md2 : active raid10 sdc1[0] sdf1[3] sde1[2] sdd1[1] 1953519616 blocks super 1.2 512K chunks 2 far-copies [4/4] [UUUU] bitmap: 1/466 pages [4KB], 2048KB chunk md0 : active raid1 sda1[0] sdb1[1] 200704 blocks [2/2] [UU] bitmap: 0/25 pages [0KB], 4KB chunk !!! md126 : active raid1 sda2[0] sdb2[2] <------------ ROOT VOL 243987048 blocks super 1.0 [2/2] [UU] [==>..................] resync = 10.4% (25572480/243987048) finish=42.9min speed=84758K/sec unused devices: <none> Where I've also got an external, RAID-10 storage array attached. A quick check of boot.omsg, from the failed boot-to-xen attempt: egrep -i "md|xen" boot.omsg <6>[ 0.000000] RAMDISK: 36d62000 - 37ff0000 <4>[ 0.000000] ACPI: SSDT 00000000cff87950 0088C (v01 A M I POWERNOW 00000001 AMD 00000001) <7>[ 0.000000] [ffffea0000000000-ffffea00077fffff] PMD -> [ffff880217a00000-ffff88021e7fffff] on node 0 <6>[ 0.048227] CPU0: AMD Phenom(tm) II X4 920 Processor stepping 02 <6>[ 0.154156] Performance Events: AMD PMU driver. <6>[ 0.986012] perf: AMD IBS detected (0x0000001f) <6>[ 1.238079] Fixed MDIO Bus: probed <6>[ 2.639177] md: raid0 personality registered for level 0 <6>[ 2.665771] md: raid1 personality registered for level 1 <6>[ 2.691754] md: raid10 personality registered for level 10 <6>[ 3.501502] md: raid6 personality registered for level 6 <6>[ 3.525819] md: raid5 personality registered for level 5 <6>[ 3.549644] md: raid4 personality registered for level 4 <4>[ 14.249595] mdadm: sending ioctl 800c0910 to a partition! <4>[ 14.249597] mdadm: sending ioctl 800c0910 to a partition! <4>[ 14.249651] mdadm: sending ioctl 1261 to a partition! <4>[ 14.249652] mdadm: sending ioctl 1261 to a partition! <4>[ 14.255122] mdadm: sending ioctl 1261 to a partition! <4>[ 14.255124] mdadm: sending ioctl 1261 to a partition! <4>[ 14.255309] mdadm: sending ioctl 1261 to a partition! <4>[ 14.255311] mdadm: sending ioctl 1261 to a partition! <4>[ 14.255450] mdadm: sending ioctl 1261 to a partition! <4>[ 14.255451] mdadm: sending ioctl 1261 to a partition! <6>[ 14.343631] md: bind<sdb2> <6>[ 14.407758] md: bind<sda2> <6>[ 14.591243] md/raid1:md126: active with 2 out of 2 mirrors <6>[ 14.591260] md126: detected capacity change from 0 to 249842737152 <6>[ 14.591329] ehci_hcd 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround <7>[ 14.591354] QUIRK: Enable AMD PLL fix <6>[ 14.591356] ehci_hcd 0000:00:12.2: applying AMD SB600/SB700 USB freeze workaround <6>[ 14.592381] md126: unknown partition table <6>[ 14.990688] ehci_hcd 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround <6>[ 14.990699] ehci_hcd 0000:00:13.2: applying AMD SB600/SB700 USB freeze workaround <6>[ 16.866637] md: linear personality registered for level -1 <4>[ 21.774172] mdadm: sending ioctl 1261 to a partition! <4>[ 21.774174] mdadm: sending ioctl 1261 to a partition! <6>[ 23.529416] ata11: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xff00 irq 14 <6>[ 23.529418] ata12: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xff08 irq 15 <6>[ 24.172157] powernow-k8: Found 1 AMD Phenom(tm) II X4 920 Processor (4 cpu cores) (version 2.20.00) <6>[ 24.208952] AMD64 EDAC driver v3.4.0 <6>[ 24.384052] EDAC amd64: DRAM ECC disabled. <5>[ 24.416467] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. <4>[ 24.947993] mdadm: sending ioctl 800c0910 to a partition! <4>[ 24.950245] mdadm: sending ioctl 800c0910 to a partition! <4>[ 24.950247] mdadm: sending ioctl 800c0910 to a partition! <4>[ 24.950251] mdadm: sending ioctl 1261 to a partition! <4>[ 24.950252] mdadm: sending ioctl 1261 to a partition! <4>[ 24.950423] mdadm: sending ioctl 1261 to a partition! <4>[ 24.950424] mdadm: sending ioctl 1261 to a partition! <4>[ 24.950564] mdadm: sending ioctl 1261 to a partition! <4>[ 27.543656] mdadm: sending ioctl 800c0910 to a partition! <4>[ 27.543662] mdadm: sending ioctl 800c0910 to a partition! <4>[ 27.543690] mdadm: sending ioctl 1261 to a partition! <4>[ 27.543691] mdadm: sending ioctl 1261 to a partition! <4>[ 27.552043] mdadm: sending ioctl 800c0910 to a partition! <4>[ 27.552045] mdadm: sending ioctl 800c0910 to a partition! <4>[ 27.552048] mdadm: sending ioctl 1261 to a partition! <4>[ 27.552049] mdadm: sending ioctl 1261 to a partition! <4>[ 27.558591] mdadm: sending ioctl 800c0910 to a partition! <4>[ 27.558593] mdadm: sending ioctl 800c0910 to a partition! <6>[ 27.642922] md: md0 stopped. <6>[ 27.674772] md: bind<sdb1> <6>[ 27.677548] md: bind<sda1> <6>[ 27.680865] md/raid1:md0: active with 2 out of 2 mirrors <6>[ 27.681061] created bitmap (25 pages) for device md0 <6>[ 27.681843] md0: bitmap initialized from disk: read 2/2 pages, set 0 of 50176 bits <6>[ 27.699744] md0: detected capacity change from 0 to 205520896 <6>[ 28.019634] md0: unknown partition table <6>[ 28.069113] md: md2 stopped. <6>[ 28.073767] md: bind<sdd1> <6>[ 28.073979] md: bind<sde1> <6>[ 28.074180] md: bind<sdf1> <6>[ 28.074342] md: bind<sdc1> <6>[ 28.076472] md/raid10:md2: active with 4 out of 4 devices <6>[ 28.076609] created bitmap (466 pages) for device md2 <6>[ 28.089020] md2: bitmap initialized from disk: read 30/30 pages, set 798 of 953867 bits <6>[ 28.123303] md2: detected capacity change from 0 to 2000404086784 <6>[ 28.309250] md2: unknown partition table <4>[ 63.587281] mdadm: sending ioctl 1261 to a partition! <4>[ 63.610886] mdadm: sending ioctl 1261 to a partition! <6>[ 64.951102] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: acl,user_xattr,journal_checksum,barrier=1 init /sbin/init is not systemd, terminate plymouth Loading drivers, configuring devices: udevd[501]: RUN+="socket:..." support will be removed from a future udev release. Please remove it from: /etc/udev/rules.d/40-xend.rules:1 and use libudev to subscribe to events. udevd[501]: RUN+="socket:..." support will be removed from a future udev release. Please remove it from: /etc/udev/rules.d/40-xend.rules:2 and use libudev to subscribe to events. udevd[501]: RUN+="socket:..." support will be removed from a future udev release. Please remove it from: /etc/udev/rules.d/40-xend.rules:3 and use libudev to subscribe to events. udevd[501]: RUN+="socket:..." support will be removed from a future udev release. Please remove it from: /etc/udev/rules.d/xend.rules:1 and use libudev to subscribe to events. udevd[501]: RUN+="socket:..." support will be removed from a future udev release. Please remove it from: /etc/udev/rules.d/xend.rules:2 and use libudev to subscribe to events. udevd[501]: RUN+="socket:..." support will be removed from a future udev release. Please remove it from: /etc/udev/rules.d/xend.rules:3 and use libudev to subscribe to events. <notice -- Sep 12 14:58:07.464558000> service boot.clock done<notice -- Sep 12 14:58:07.464727000> service boot.device-mapper start<notice -- Sep 12 14:58:07.465162000> service boot.localnet start<notice -- Sep 12 14:58:07.465589000> service boot.md start Starting MD RAID mdadm: /dev/md0 has been started with 2 drives. mdadm: /dev/md2 has been started with 4 drives. <notice -- Sep 12 14:58:08.375196000> service boot.md done<notice -- Sep 12 14:58:08.375287000> service boot.lvm start /dev/mapper/VG_S03-LV_DOMU_XENSTOR: /dev/md0: clean, 373/50200 files, 112924/200704 blocks DOMU_XENSTOR: clean, 76/1966080 files, 1979881/7864320 blocks /home/xen_store : successfully mounted <notice -- Sep 12 14:58:54.125829000> service xencommons start <notice -- Sep 12 14:58:54.126302000> service xend start <notice -- Sep 12 14:58:54.143633000> service bluez-coldplug done<notice -- Sep 12 14:58:54.152380000> service xend done<notice -- Sep 12 14:58:54.152546000> service xen-setup start<notice -- Sep 12 14:58:54.152741000> service xendomains start xend unused <notice -- Sep 12 14:58:54.202851000> service xencommons done <notice -- Sep 12 14:58:54.208436000> service xen-setup done xendomains unused <notice -- Sep 12 14:58:54.353895000> service xendomains done<notice -- Sep 12 14:58:54.354811000> service irq_balancer done <notice -- Sep 12 14:58:59.222964000> service postfix done<notice -- Sep 12 14:58:59.223406000> service cron start<notice -- Sep 12 14:58:59.223872000> service mdadmd start<notice -- Sep 12 14:58:59.224316000> service smartd start <notice -- Sep 12 14:58:59.258988000> startproc: execve (/sbin/mdadm) [ /sbin/mdadm -F /dev/md0 /dev/md2 /dev/md126 -d 60 -m ar@ardev.loc -s -t -c /etc/mdadm.conf ], [ DO_FASTBOOT=no CONSOLE=/dev/console _=/sbin/startproc DAEMON=/sbin/mdadm service mdadmd done Starting mdadmd done <notice -- Sep 12 14:59:07.820092000> startproc: execve (/usr/sbin/ntpd) [ /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf ], [ TERM=linux LC_ALL=POSIX COLUMNS=160 PATH=/sbin:/usr/sbin:/usr/local/sbin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin PWD=/ LANG=POSIX LINES=64 SHLVL=1 SYSTEMD_NO_WRAP= _=/sbin/startproc PREVLEVEL=N RUNLEVEL=3 DAEMON=/usr/sbin/ntpd ] Skipped services in runlevel 3: xend xendomains <notice -- Sep 12 17:37:18.956166000> service mdadmd stop <notice -- Sep 12 17:37:18.957332000> service xen-setup stop <notice -- Sep 12 17:37:18.957721000> service xencommons stop <notice -- Sep 12 17:37:18.958132000> service xendomains stop service xencommons done <notice -- Sep 12 17:37:18.981200000> service xen-setup done xendomains done <notice -- Sep 12 17:37:19.68721000> service xendomains done<notice -- Sep 12 17:37:19.68874000> service xend stop<notice -- Sep 12 17:37:19.79155000> killproc: kill(2639,15) Shutting down mdadmd done <notice -- Sep 12 17:37:19.92213000> service cron done<notice -- Sep 12 17:37:19.92239000> service smartd done<notice -- Sep 12 17:37:19.92250000> service dhcpd done<notice -- Sep 12 17:37:19.92260000> service mdadmd done<notice -- Sep 12 17:37:19.92269000> service irq_balancer done<notice -- Sep 12 17:37:19.92276000> service acpid done<notice -- Sep 12 17:37:19.92316000> service postfix stop<notice -- Sep 12 17:37:19.92436000> service purge-kernels stop<notice -- Sep 12 17:37:19.92562000> service random stop<notice -- Sep 12 17:37:19.92741000> service nscd done<notice -- Sep 12 17:37:19.92763000> service pcscd done<notice -- Sep 12 17:37:19.92775000> service fbset done<notice -- Sep 12 17:37:19.92782000> service sshd-custom done<notice -- Sep 12 17:37:19.114947000> service dkms_autoinstaller done<notice -- Sep 12 17:37:19.160637000> service xend done<notice -- Sep 12 17:37:19.205969000> service purge-kernels done<notice -- Sep 12 17:37:19.216017000> service random done<notice -- Sep 12 17:37:19.222422000> service postfix done<notice -- Sep 12 17:37:19.222572000> service mysql stop<notice -- Sep 12 17:37:19.251071000> service autofs done<notice -- Sep 12 17:37:19.251225000> service network-remotefs stop<notice -- Sep 12 17:37:19.251634000> service nfsserver stop<notice -- Sep 12 17:37:19.284303000> killproc: kill(3795,9) xend done So, atm, Xen's out of commission, and booting to Xen breaks (possibly?) the RAID so as to cause a resync on next viable boot? I'll start poking around to see what add'l info I might find. If you have any further inkling, please post. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c21 A R <ar16@imapmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |nfbrown@suse.com --- Comment #21 from A R <ar16@imapmail.org> 2012-09-14 00:52:51 UTC --- Is the Xen issue likely related, or a separate issue to this bug? What additional info, if any, can I provide to help make that determination? If it's a separate issue, I'll split if off as a separate bug as appropriate. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c22 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|nfbrown@suse.com | --- Comment #22 from Neil Brown <nfbrown@suse.com> 2012-09-14 01:29:23 UTC --- I know little about Xen, but it does look like a different issue. I would suggest openning another bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c23 --- Comment #23 from A R <ar16@imapmail.org> 2012-09-14 02:02:17 UTC --- The Xen bits have been split off to: "Bug 780368 - After 12.1->12.2 upgrade, boot to Xen hangs, and breaks root-on-RAID, forcing re-sync" https://bugzilla.novell.com/show_bug.cgi?id=780368 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c24 --- Comment #24 from A R <ar16@imapmail.org> 2012-09-19 00:11:12 UTC ---
it does look like a different issue The Xen bits have been split off to
Looks like an upgrade to release version of Xen (tentatively) fixes that.
I've got another mdadm issue that I'm awaiting confirmation of the fix for. Once that is confirmed I'll see about scheduling an update to fix this bug and that one.
Do you have a *rough* idea of timeframe? Looking for 'soon' vs 'next point release' to help with upgrade planning & testing. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c25 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |maintenance@opensuse.org --- Comment #25 from Neil Brown <nfbrown@suse.com> 2012-09-20 06:29:04 UTC --- Maybe the next month or 2 ... hopefully before 12.3! Maintenance: can we please schedule an update for mdadm in 12.2 for this bug and also bug #772286. Both affect booting when md arrays are involved. If you can provide some ball-park figure on when the release might come out too, that would be great (e.g. "this year"?). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c26 --- Comment #26 from Bernhard Wiedemann <bwiedemann@suse.com> 2012-09-24 08:01:05 CEST --- This is an autogenerated message for OBS integration: This bug (779087) was mentioned in https://build.opensuse.org/request/show/135563 Factory / mdadm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c27 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |meissner@suse.com InfoProvider|maintenance@opensuse.org | --- Comment #27 from Marcus Meissner <meissner@suse.com> 2012-09-25 07:34:38 UTC --- neil, feel free to submit a mdadm update for opensuse ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c28 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #28 from Neil Brown <nfbrown@suse.com> 2012-09-26 02:07:16 UTC --- An update has been submitted so closing the bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c29 A R <ar16@imapmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #29 from A R <ar16@imapmail.org> 2012-10-01 07:33:38 UTC --- Can we please get a test repo/package for 12.2? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c30 --- Comment #30 from Marcus Meissner <meissner@suse.com> 2012-10-01 07:55:12 UTC --- http://download.opensuse.org/update/12.2-test/ has the testupdates, including this mdadm update -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c31 A R <ar16@imapmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |meissner@suse.com --- Comment #31 from A R <ar16@imapmail.org> 2012-10-01 15:07:23 UTC --- Thanks for the repo. In the original workaround, https://bugzilla.novell.com/show_bug.cgi?id=779087#c14 I mv /lib/mkinitrd/scripts/setup-md.sh /lib/mkinitrd/scripts/setup-md.sh.ORIG and dl'd/replaced it with New /lib/mkinitrd/scripts/setup-md.sh https://bugzilla.novell.com/attachment.cgi?id=505339 That worked. In the update package, @ https://build.opensuse.org/request/show/135563, there's no update made to any "setup-md.sh", but there IS an *update* to "mkinitrd-setup.sh" which does not currently exist, and appears to be a renamed /lib/mkinitrd/scripts/setup-md.sh. Is this filename change intended? If so, should the workaround /lib/mkinitrd/scripts/setup-md.sh be manually deleted subsequent to the update? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c32 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|meissner@suse.com |nfbrown@suse.com --- Comment #32 from Marcus Meissner <meissner@suse.com> 2012-10-01 15:58:56 UTC --- more for neil? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c33 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|nfbrown@suse.com | --- Comment #33 from Neil Brown <nfbrown@suse.com> 2012-10-01 23:51:09 UTC --- Hi, it looks like you are looking at the src package rather than the binary. You could go to the "x86_64" subdirectory and down load the package mdadm-3.2.5-3.13.1.x86_64.rpm. Then use "rpm -U mdadm-3.2.5-3.13.1.x86_64.rpm" to install it. It will install a new "setup-md.sh" "mknitrd-setup.sh" is the name of the same file in the src RPM. The "mdadm.spec" file describes how that file gets installed in /lib/mkinitrd/scripts/setupd-md.sh. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c34 --- Comment #34 from A R <ar16@imapmail.org> 2012-10-02 00:05:21 UTC --- ls -al /lib/mkinitrd/scripts/setup-md.sh* -rwxr-xr-x 1 root root 2.6K Sep 11 20:19 /lib/mkinitrd/scripts/setup-md.sh* -rwxr-xr-x 1 root root 2.6K Sep 11 20:19 /lib/mkinitrd/scripts/setup-md.sh.BUGFIX* -rwxr-xr-x 1 root root 2.6K Aug 20 03:07 /lib/mkinitrd/scripts/setup-md.sh.ORIG* rpm -Uvh http://download.opensuse.org/update/12.2-test/x86_64/mdadm-3.2.5-3.13.1.x86_... Retrieving http://download.opensuse.org/update/12.2-test/x86_64/mdadm-3.2.5-3.13.1.x86_... warning: /var/tmp/rpm-tmp.TQHym2: Header V3 DSA/SHA1 Signature, key ID 55d9d78b: NOKEY Preparing... ########################################### [100%] 1:mdadm ########################################### [100%] Scanning scripts ... Resolve dependencies ... Install symlinks in /lib/mkinitrd/setup ... Install symlinks in /lib/mkinitrd/boot ... ... Kernel image: /boot/vmlinuz-3.4.6-2.10-xen Initrd image: /boot/initrd-3.4.6-2.10-xen Root device: /dev/VG0/root (mounted on / as ext4) modprobe: Module hid_generic not found. WARNING: no dependencies for kernel module 'hid-generic' found. Kernel Modules: hwmon thermal_sys thermal processor fan raid0 raid1 raid10 async_tx async_memcpy xor ... libiscsi_tcp iscsi_tcp crc32c sunrpc nfs_acl auth_rpcgss fscache lockd nfs linear Features: acpi dm plymouth block firewire usb iscsi dmraid nfs kpartx md lvm2 resume.userspace resume.kernel Updating /etc/sysconfig/mdadm... redirecting to systemctl Scanning scripts ... Resolve dependencies ... ... ls -al /lib/mkinitrd/scripts/setup-md.sh* -rwxr-xr-x 1 root root 2.6K Sep 25 04:43 /lib/mkinitrd/scripts/setup-md.sh* -rwxr-xr-x 1 root root 2.6K Sep 11 20:19 /lib/mkinitrd/scripts/setup-md.sh.BUGFIX* -rwxr-xr-x 1 root root 2.6K Aug 20 03:07 /lib/mkinitrd/scripts/setup-md.sh.ORIG* shutdown -r now ... boots with no apparent errors, uname -a Linux test 3.4.6-2.10-xen #1 SMP Thu Jul 26 09:36:26 UTC 2012 (641c197) x86_64 x86_64 x86_64 GNU/Linux all drives, in particular the "/"-containing arrays, are fine. cat /proc/mdstat Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [linear] md2 : active raid10 sdc1[0] sdf1[3] sde1[2] sdd1[1] 1953519616 blocks super 1.2 512K chunks 2 far-copies [4/4] [UUUU] bitmap: 1/466 pages [4KB], 2048KB chunk md0 : active raid1 sda1[0] sdb1[1] 200704 blocks [2/2] [UU] bitmap: 0/25 pages [0KB], 4KB chunk md126 : active raid1 sda2[0] sdb2[2] 243987048 blocks super 1.0 [2/2] [UU] unused devices: <none> looks good from here. when appropriate, pls post the package's push-to-release event info. thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c35 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #35 from Neil Brown <nfbrown@suse.com> 2012-10-02 01:09:18 UTC --- I think a comment gets automatically added when the package is made available. Setting status back to 'resolved'. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c36 --- Comment #36 from A R <ar16@imapmail.org> 2012-10-08 15:04:33 UTC ---
I think a comment gets automatically added when the package is made available.
It doesn't. Imo, it should. In any case, fyi, the fix is available, sourced from http://download.opensuse.org/update/12.2/x86_64/ mdadm-3.2.5-3.13.1.x86_64.rpm 03-Oct-2012 16:19 348K Details rpm -qa | grep -i mdadm mdadm-3.2.5-3.13.1.x86_64 rpm -q --changelog mdadm | head -n 10 * Tue Sep 25 2012 nfbrown@suse.com - mkinitrd-setup.sh: allow md device names to contain a ':'. (bnc#779087) <========================== - boot.md: make sure udev-trigger runs before boot.md. (bnc#772286) - mdadm.spec: don't create files in /run, as that is pointless (bnc#777390) * Mon Aug 20 2012 nfbrown@suse.com - mdmon-takeover.fix Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c37 --- Comment #37 from Marcus Meissner <meissner@suse.com> 2012-10-08 15:21:43 UTC --- it should actually, but only if we actually list the bug in the obs patchinfo. I missed to add this specific bug by mistake it seems, sorry. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c38 A R <ar16@imapmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #38 from A R <ar16@imapmail.org> 2012-10-09 14:57:13 UTC --- thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com