[Bug 780935] New: installation produces incorrect mdadm.conf in initrd
https://bugzilla.novell.com/show_bug.cgi?id=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c0 Summary: installation produces incorrect mdadm.conf in initrd Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ben.ellis@familycourt.gov.au QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 After installation, the pc reboots and fails to load the OS saying it is waiting for partitions to wake(?). The system is configured with 4x2TB disks in RAID 5. I've booted into rescue mode and opened up the initrd and found the mdadm.conf which contains the following AUTO -all ARRAY /dev/md/imsm0 metadata=imsm UUID=1980e81b:1611decb:a93affc5:d433ba73 ARRAY /dev/md126 container=/dev/md/imsm0 member=0 UUID=dd19099b:51b09297:916172fe:5a1f6582 running "mdadm --examine --scan" provides the following ARRAY metadata=imsm UUID=1980e81b:1611decb:a93affc5:d433ba73 ARRAY /dev/md/SYSTEM container=1980e81b:1611decb:a93affc5:d433ba73 member=0 UUID=dd19099b:51b09297:916172fe:5a1f6582 ARRAY /dev/md/DATA container=1980e81b:1611decb:a93affc5:d433ba73 member=1 UUID=cf946b3b:ea30a129:e8b32923:b4a3ffce after updating the mdadm.conf in the initrd and rebooting the system starts correctly. lspci produces the following 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation Z68 Express Chipset Family LPC Controller (rev 05) 00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller [RAID mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) 02:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) 04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) 05:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) 06:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 01) parted -l shows the following Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sda: 2000GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 197kB 1078MB 1077MB primary boot, type=83 2 1078MB 270GB 268GB primary type=07 3 270GB 287GB 17.2GB primary type=82 4 287GB 537GB 250GB primary type=83 Error: /dev/sdb: unrecognised disk label Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdb: 2000GB Sector size (logical/physical): 512B/512B Partition Table: unknown Error: /dev/sdc: unrecognised disk label Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdc: 2000GB Sector size (logical/physical): 512B/512B Partition Table: unknown Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdd: 2000GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 197kB 1078MB 1077MB primary boot, type=83 2 1078MB 270GB 268GB primary type=07 3 270GB 287GB 17.2GB primary type=82 4 287GB 537GB 250GB primary type=83 Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0 has been opened read-only. Error: Can't have a partition outside the disk! Model: HL-DT-ST BDDVDRW CH12LS28 (scsi) Disk /dev/sr0: 4669MB Sector size (logical/physical): 2048B/2048B Partition Table: unknown Model: Linux Software RAID Array (md) Disk /dev/md125: 537GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 197kB 1078MB 1077MB primary ext4 boot, type=83 2 1078MB 270GB 268GB primary ntfs type=07 3 270GB 287GB 17.2GB primary linux-swap(v1) type=82 4 287GB 537GB 250GB primary ext4 type=83 Model: Linux Software RAID Array (md) Disk /dev/md126: 5464GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 197kB 1100GB 1100GB ext4 primary 2 1100GB 5464GB 4365GB ntfs primary Reproducible: Always Steps to Reproduce: 1. install opensuse 12.2 (or 12.1) 2. use the existing partitions - software choices seem irrelevant 3. use the default boot loader (this works properly) 4. reboot after OS has been installed for part 2 5. failure message appears Actual Results: unable to find the partitions to boot the system Expected Results: a running system Please let me know if you require a screenshot of the actual errors or further information. This has happened in 12.1 as well as 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c1 kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |kkzhang@suse.com InfoProvider| |ben.ellis@familycourt.gov.a | |u --- Comment #1 from kk zhang <kkzhang@suse.com> 2012-09-19 10:27:45 UTC --- Hi,could you please help to provide y2logs according to the following URL? http://en.opensuse.org/openSUSE:Bugreport_YaST -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c2 Ben Ellis <ben.ellis@familycourt.gov.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ben.ellis@familycourt.gov.a | |u | --- Comment #2 from Ben Ellis <ben.ellis@familycourt.gov.au> 2012-09-21 09:09:13 UTC --- Created an attachment (id=506538) --> (http://bugzilla.novell.com/attachment.cgi?id=506538) Logs as requested in Comment 1 Since logging the initial report I've had a total failure of the array due to dodgy SATA cables. I've replaced them and performed a total rebuild of the array with some tests along the way. Test 1 - created a RAID 5 with 520GB of the capacity available. Manually partition the array with parted. Install Windows. Install openSUSE and the installation is successful. Yast install logs are YaST.onedisk.tgz in the archive. Test 2 - Created a RAID 5 with the remaining space. Manually partitioned a GPT partition setup on the array and added /home to one of the partitions on this array. Yast install logs are YaST.twodisk.tgz in the archive. After the first phase of installation, the system reboots and hangs with the following mdadm: /dev/md126 is already in use. Trying manual resume from /dev/disk/bi-id/md-uuid/94bb8df:9bce432a:fa157cde:798e8240-part5 resume device /dev/disk/bi-id/md-uuid/94bb8df:9bce432a:fa157cde:798e8240-part5 not found (ignoring) Trying manual resume from /dev/disk/bi-id/md-uuid/94bb8df:9bce432a:fa157cde:798e8240-part5 resume device /dev/disk/bi-id/md-uuid/94bb8df:9bce432a:fa157cde:798e8240-part5 not fund (ignoring) Waiting for device /dev/root to appear: .............................Could not find /dev/root. Want me to fall back to /dev/disk/bi-id/md-uuid/94bb8df:9bce432a:fa157cde:798e8240-part6? (Y/n) Again, I booted into recovery mode, edited the initrd's mdadm config (mdadm.conf.org in the archive) and ran mdadm --examine --scan > mdadm.conf (mdadm.conf in the archive). Rebooting the system after showed it booted successfully and phase 2 of the installation succeded. After this I've run save_y2logs /tmp/y2logs.tgz and added that file to the archive 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |snwint@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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c3 Richard Bos <richard.bos@xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard.bos@xs4all.nl --- Comment #3 from Richard Bos <richard.bos@xs4all.nl> 2012-09-23 20:37:12 UTC --- I ran into this bugreport, because I've something similar after I upgraded my openSUSE_11.4 system to openSUSE_12.2 On OS_11.4 I did not have any problems related to mdadm at all, it worked just fine. On OS_12.2 I run already sometimes into this problem, although the system is only on OS_12.2 for about a day. At the moment when it happens, the system goes into the mode during initializing that one has to the the root password to be able to enter "<ctrl> - D" or just type reboot. The second time the raid is working fine. For me this is fine to execute, but the same machine is just by my children and they will be stuck, especially when I'm not at home.... Just after the boot started, after the boot login screen, that states the mdadm failed for /dev/sdb, /dev/sdc, /dev/sdb1 and /dev/sdc1. # mdadm -V mdadm - v3.2.5 - 18th May 2012 I've only 1 raid. # uname -a Linux selene 3.4.6-2.10-default Just is just by heart when more details are appreciated I can look it up. Hmm, the output of "mdadm --examine --scan", is different compared to the info in the /etc/mdadm.conf file: # mdadm --examine --scan ARRAY metadata=imsm spares=2 ARRAY /dev/md/0 metadata=1.0 UUID=<some ID> name=selene:0 # cat /etc/mdadm.conf DEVICE partitions ARRAY /dev/md0 level=raid1 UUID=<some ID> ---------------------- <some ID> is in both cases the same -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|snwint@suse.com |fehr@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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c4 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@suse.com AssignedTo|fehr@suse.com |aschnell@suse.com --- Comment #4 from Thomas Fehr <fehr@suse.com> 2012-09-24 10:14:29 UTC --- Arvin, there seem to be problems with partitioned md raids in 12.2. Especially mdadm.conf possibly needs to be adapted. Could you please have a look. -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c5 Björn Voigt <bjoernv@arcor.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjoernv@arcor.de --- Comment #5 from Björn Voigt <bjoernv@arcor.de> 2012-09-27 08:45:51 UTC --- On my system, /etc/mdadm.conf, /proc/mdstat and "mdadm --examine --scan" each have different device names after upgrading from openSUSE 12.1. Anyway, the system boots and runs fine (until now). Only the device names from /proc/mdstat really exists. $ cat /etc/mdadm.conf DEVICE containers partitions ARRAY /dev/md0 UUID=4e729993:1292c379:ea08149a:b937dcf3 ARRAY /dev/md1 UUID=f5d55e3b:22350c32:ea554159:75fa5633 $ cat /proc/mdstat Personalities : [raid1] [raid0] [raid10] [raid6] [raid5] [raid4] md1 : active raid1 sda7[0] sdb7[1] 104857472 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk md126 : active raid1 sda6[0] sdb6[1] 157286272 blocks super 1.0 [2/2] [UU] bitmap: 1/2 pages [4KB], 65536KB chunk $ mdadm --examine --scan ARRAY /dev/md/0 metadata=1.0 UUID=4e729993:1292c379:ea08149a:b937dcf3 name=linux:0 ARRAY /dev/md/1 metadata=1.0 UUID=f5d55e3b:22350c32:ea554159:75fa5633 name=linux:1 $ ls -lR /dev/md* brw-rw---- 1 root disk 9, 1 Sep 26 22:54 /dev/md1 brw-rw---- 1 root disk 9, 126 Sep 26 22:54 /dev/md126 -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c6 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |aschnell@suse.com InfoProvider| |nfbrown@suse.com --- Comment #6 from Arvin Schnell <aschnell@suse.com> 2012-10-02 13:16:53 UTC --- Unfortunately I have no working IMSM system so I cannot perform any tests. Neil, do you see a reason why the original mdadm.conf in comment #0 does not work? -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c7 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|nfbrown@suse.com | --- Comment #7 from Neil Brown <nfbrown@suse.com> 2012-10-03 01:38:25 UTC --- There were a number of problem with mdadm in 12.2. I fixed a number of issues and I believe the updated package is now available. If would help if people could install all available updates and see if the problems persist. If they do, please provide (or re-provide) details. The version of mdadm (reported by "rpm -q mdadm" that is buggy is mdadm-3.2.5-3.4.1 The version that works better is mdadm-3.2.5-3.7.1 though there is another update pending which isn't released yet, but the issues it addresses don't seem to be present in any for the above descriptions. I don't know exactly why the mdadm.conf in comment #0 doesn't work, but it is almost certainly related to it containing "/dev/md126" as a device name. Numbers like that can be allocated automatically and if allocated to the wrong thing it can cause conflicts and confusion. One of the fixes in the new mdadm is that names like that that are listed in mdadm.conf will never be used automatically. Another fix is to avoid using names like that :-) -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c8 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ben.ellis@familycourt.gov.a | |u --- Comment #8 from Arvin Schnell <aschnell@suse.com> 2012-10-04 09:26:27 UTC --- Ben, could you please provide the mdadm.conf saved by YaST in /etc/mdadm.conf? That is different from the one inside the initrd. You could also try the updated version of mdadm as Neil suggests. -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c9 Ben Ellis <ben.ellis@familycourt.gov.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ben.ellis@familycourt.gov.a | |u | --- Comment #9 from Ben Ellis <ben.ellis@familycourt.gov.au> 2012-10-06 13:08:28 UTC --- The /etc/mdadm.conf from the system is DEVICE containers partitions ARRAY metadata=imsm UUID=93fb0f57:f21188ff:51e6f81e:3890f066 ARRAY /dev/md/data container=93fb0f57:f21188ff:51e6f81e:3890f066 member=1 UUID=007ffae7:b37bccd5:a9efc5d3:8047ddce ARRAY /dev/md/system container=93fb0f57:f21188ff:51e6f81e:3890f066 member=0 UUID=94bbd8df:9bce432a:fa157cde:798e8240 I notice there is a newer mdadm version (mdadm-3.2.5-3.13.1) so I'll give that a shot as soon as I can. The last couple of times I've tried to boot the system however I've still had issues getting it started in Linux. Will let you know of progress. -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c10 --- Comment #10 from Ben Ellis <ben.ellis@familycourt.gov.au> 2012-10-07 10:53:34 UTC --- I've tried a re-install when adding the update repository as an add-on repository. I've also verified the mdadm version was that latest available as mentioned in comment 9. I'm still getting the same errors after rebooting to phase 2 of the installation. Please let me know if you need any more logs, etc and I'll gather what I can. -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c11 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aschnell@suse.com |nfbrown@suse.com --- Comment #11 from Arvin Schnell <aschnell@suse.com> 2012-10-08 08:24:43 UTC --- The mdadm.conf YaST produces during installation uses /dev/md/xyz. It's setup-md.sh that changes those during mkinitrd. -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c12 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ben.ellis@familycourt.gov.a | |u --- Comment #12 from Neil Brown <nfbrown@suse.com> 2012-10-08 09:02:02 UTC --- The current mdadm (more update to 12.2) uses /dev/md/xyz names in the initrd, so I think that is fixed. Unfortunately the current release breaks on IMSM for another reason. A fix for that is queued and should be out shortly (I don't know when). To test you could: 1/ install the latest mdadm from openSUSE:12.2:Updates 2/ edit /lib/mkinitrd/scripts/setup-md.sh Find the line: eval echo \"\$md_conf_$md\" >> $tmp_mnt/etc/mdadm.conf Near the end. Change it to: eval echo -e \"\$md_conf_$md\" >> $tmp_mnt/etc/mdadm.conf i.e. add '-e'. If it already has '-e' then it is the correct version. 3/ run mkinitrd 4/ reboot and please report results. 5/ Check the mdadm.conf in the initrd to ensure it looks correct. -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c13 Ben Ellis <ben.ellis@familycourt.gov.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ben.ellis@familycourt.gov.a | |u | --- Comment #13 from Ben Ellis <ben.ellis@familycourt.gov.au> 2012-10-08 13:27:11 UTC --- I've run zypper in mdadm and received the following output (included here only because grub throws an error and I can't tell if it's related). # zypper in mdadm Loading repository data... Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: mdadm 1 package to upgrade. Overall download size: 347.8 KiB. After the operation, additional 3.0 B will be used. Continue? [y/n/?] (y): y Retrieving package mdadm-3.2.5-3.17.1.x86_64 (1/1), 347.8 KiB ( 1.0 MiB unpacked) Retrieving delta: ./x86_64/mdadm-3.2.5-3.13.1_3.17.1.x86_64.drpm, 23.2 KiB Retrieving: mdadm-3.2.5-3.13.1_3.17.1.x86_64.drpm .................................................................[done (3.0 KiB/s)] Applying delta: ./mdadm-3.2.5-3.13.1_3.17.1.x86_64.drpm .......................................................................[done] Installing: mdadm-3.2.5-3.17.1 ................................................................................................[done] Additional rpm output: 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-desktop Initrd image: /boot/initrd-3.4.6-2.10-desktop KMS drivers: nouveau nouveau Root device: /dev/disk/by-id/md-uuid-94bbd8df:9bce432a:fa157cde:798e8240-part6 (/dev/md125p6) (mounted on / as ext4) Resume device: /dev/disk/by-id/md-uuid-94bbd8df:9bce432a:fa157cde:798e8240-part5 (/dev/md125p5) modprobe: Module hid_generic not found. WARNING: no dependencies for kernel module 'hid-generic' found. Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_rdac scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw button wmi video mxm-wmi i2c-algo-bit drm drm_kms_helper ttm nouveau xhci-hcd hid-logitech-dj raid0 raid1 raid10 async_tx async_memcpy xor async_xor raid6_pq async_pq async_raid6_recov raid456 Features: acpi kms plymouth block usb md resume.userspace resume.kernel Perl-Bootloader: 2012-10-08 23:41:04 ERROR: Command '/usr/sbin/grub2-install --force --skip-fs-probe /dev/md126p1 >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for cross-disk install. There was an error generating the initrd (1) Updating /etc/sysconfig/mdadm... redirecting to systemctl 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-desktop Initrd image: /boot/initrd-3.4.6-2.10-desktop KMS drivers: nouveau nouveau Root device: /dev/disk/by-id/md-uuid-94bbd8df:9bce432a:fa157cde:798e8240-part6 (/dev/md125p6) (mounted on / as ext4) Resume device: /dev/disk/by-id/md-uuid-94bbd8df:9bce432a:fa157cde:798e8240-part5 (/dev/md125p5) modprobe: Module hid_generic not found. WARNING: no dependencies for kernel module 'hid-generic' found. Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_rdac scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw button wmi video mxm-wmi i2c-algo-bit drm drm_kms_helper ttm nouveau xhci-hcd hid-logitech-dj raid0 raid1 raid10 async_tx async_memcpy xor async_xor raid6_pq async_pq async_raid6_recov raid456 Features: acpi kms plymouth block usb md resume.userspace resume.kernel Perl-Bootloader: 2012-10-08 23:41:17 ERROR: Command '/usr/sbin/grub2-install --force --skip-fs-probe /dev/md126p1 >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for cross-disk install. There was an error generating the initrd (1) The previous line looked like this echo -e "${md_conf["$md"]}" >> $tmp_mnt/etc/mdadm.conf it generated this in the initrd mdadm.conf AUTO -all ARRAY /dev/md/imsm0 metadata=imsm UUID=93fb0f57:f21188ff:51e6f81e:3890f066 ARRAY /dev/md/system container=/dev/md/imsm0 member=0 UUID=94bbd8df:9bce432a:fa157cde:798e8240 copying and pasting the line mentioned above only had "AUTO -all" in the initrd's mdadm.conf. I've rebooted successfully with the initrd created from the mdadm-3.2.5-3.17.1.x86_64 code. It also turns out the grub error was another issue (likely from the couple of mkinitrd attempts) as grub failed to load after the reboot. I've had to boot to a rescue environment and force a grub2-install to recover that part too. To summarise updated mdadm to 3.2.5-3.17.1 checked initrd, looked ok applied suggested patch ran mkinitrd checked initrd, looked empty reverted patch ran mkinitrd checked initrd, looked ok rebooted grub failed booted to rescue environment reinstalled grub (grub2-install /dev/md... --force) rebooted successfully logged in. -- 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=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c14 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #14 from Neil Brown <nfbrown@suse.com> 2012-10-17 23:34:04 UTC --- I think I might have confused you with the suggestion of patching an older version. 3.2.5-3.17.1 is the current version and contains the fix, and from your description it did in fact fix the problem. So I'll close this bug as 'resolved'. If 'grub' is still causing problems that would be a separate issue and you should open a separate bug if you want to pursue it. 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