http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c1 --- Comment #1 from Gábor Nyers 2009-12-24 16:00:20 UTC --- See attached screenshot of the actual error -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c2 Jogchum Reitsma changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |j.reitsma@hccnet.nl --- Comment #2 from Jogchum Reitsma 2010-01-18 18:06:24 UTC --- I have the same problem, with a configuration that is comparable to th OP's: - /dev/sda1 formatted with ext2, mountpoint on /boot, 1 GB - a raid-1 array from /dev/sda2 through /dev/sdd2, 10 GB, labeled 'root', mountpoint / - a raid5 array from /dev/sda3 through /dev/sdd3, each 920 GB, net appr. 2.8 TB, labeled 'home', mountpoint /home Both raid devices are mounted by label. Partitioning and creating the arrays went during install with Yast without error messages, but during install of software I saw messages Device block!9:0 not found in sysfs flying by. When it was time for Yast to create the initrd, the message Kernel image: /boot/vmlinuz-2.6.31.5-0.1-desktop Initrd image: /boot/initrd-2.6.31.5-0.1-desktop Root device: ext4-root (/dev/block/9:0) (mounted on / as ext4) Device block!9:0 not found in sysfs was given, and it appeared no initrd was created: drwxr-xr-x 4 root root 4096 jan 15 16:35 ./ drwxr-xr-x 22 root root 4096 jan 15 16:18 ../ -rw------- 1 root root 512 jan 15 16:35 backup_mbr lrwxrwxrwx 1 root root 1 jan 15 16:18 boot -> ./ -rw-r--r-- 1 root root 1236 okt 24 04:19 boot.readme -rw-r--r-- 1 root root 103289 okt 27 12:30 config-2.6.31.5-0.1-desktop drwxr-xr-x 2 root root 4096 jan 15 16:35 grub/ lrwxrwxrwx 1 root root 27 jan 15 16:20 initrd -> initrd-2.6.31.5-0.1-desktop drwx------ 2 root root 16384 jan 15 15:56 lost+found/ -rw-r--r-- 1 root root 421376 jan 15 16:35 message -rw-r--r-- 1 root root 170143 okt 27 12:32 symvers-2.6.31.5-0.1-desktop.gz -rw-r--r-- 1 root root 1907577 okt 27 11:31 System.map-2.6.31.5-0.1-desktop lrwxrwxrwx 1 root root 28 jan 15 16:20 vmlinuz -> vmlinuz-2.6.31.5-0.1-desktop -rw-r--r-- 1 root root 4104416 okt 27 11:31 vmlinuz-2.6.31.5-0.1-desktop No need to say booting this arrangement fails. After booting the system from another disk with 11.2, and assembling and mounting the raid fs'es (with goes flawlessly; here too the content seems correct), I tried to create the initrd by hand with mount /dev/md0 /mnt/root mount /dev/sda1 /mnt/root/boot mount --bind /dev /mnt/root/dev chroot /mnt/root mount /proc mount /sys mkinitrd as suggested by the mkinitrd man page. But this gives the same error, and no initrd is created in the chrooted /boot. Hardware is Gigabyte GA-MA790FXT-UD5P mobo, AMD Phenom II X4 955 / 3.2 GHz Black Edition, memory 4GB OCZ Platinum Dual Channel DDR3 1333 MHz 1.65 V -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c5 --- Comment #5 from Gábor Nyers 2010-01-22 15:27:33 UTC --- I'd need to re-install the box, which can take a few days given my current schedule. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c7 --- Comment #7 from Gábor Nyers 2010-01-22 15:57:56 UTC --- Ok. That was not entirely clear. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c9 --- Comment #9 from Jogchum Reitsma 2010-01-22 16:08:27 UTC --- I have attached the log file. I'll be off during part of the weekend, so I'll be somewhat unresponsive. Back saterday evening regards, Jogchum -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c10 Arnold Fleischer changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent CC| |pacoleone@gmx.de OS/Version|openSUSE 10.2 |openSUSE 11.2 Severity|Normal |Critical --- Comment #10 from Arnold Fleischer 2010-01-28 09:13:01 UTC --- I have the same problem. Running 2 HDs as a raid1. /dev/md0 as / /dev/md1 as swap /dev/md2 as /srv I told fstab to use labels and grub uses mbr. During installation I get the error "Device block!9:0 not found in sysfs" and grub won't boot. I also tried Ext3 instead of Ext4. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c12 Arnold Fleischer changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None Severity|Critical |Normal --- Comment #12 from Arnold Fleischer 2010-01-28 10:36:07 UTC --- Sorry, I changed it back to the last state. I tried again a new installation with my 2 HDs and software raid1 partitions. But this time I used GPD as partition table and I told fstab to use the device names instead of the device labels. And now it works. I can also do a kernel update.Strange...I think GPD has nothing do to with it. Perhabs you need to tell fstab to use the device names. The first time I tried the installation with raid1 arrays I used DOS as partition tabel and fstab used device names. The installation was fine. Then I changed fstab to use device labels and the system was fine. I tried different RAID failures and everything worked like expected. But then I did a kernel update and after reboot I got the errors. Perhaps this information is useful. I have now a working system, but I would still like to use device labels. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c14 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Severity|Normal |Critical --- Comment #14 from Michal Marek 2010-02-05 19:55:30 UTC --- Sorry, no progress. I'm on vacation for the next week, I'll look into the mkinitrd bugs after that. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c16 --- Comment #16 from Jogchum Reitsma 2010-02-19 18:05:50 UTC --- @Michal Marek: Hope you had a good holiday! So I take it that I should change fstab to identifying the array by its device name? Which has some risks mixing the two arrays, I understand. But i'll give it a try, of course. Will the LABEL= identifier be understood by mkinitrd in the near future? regards, Jogchum -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c18 --- Comment #18 from Michal Marek 2010-02-19 20:32:32 UTC --- Yes, using the device name should be a workaround. I would like to fix LABEL= support, but I'm not giving any promise as to when it's going to happen. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c20 --- Comment #20 from Ivo Babarovic 2010-03-30 07:15:06 UTC --- Created an attachment (id=351317) --> (http://bugzilla.novell.com/attachment.cgi?id=351317) yast logs upon install -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=567225 http://bugzilla.novell.com/show_bug.cgi?id=567225#c22 --- Comment #22 from Felix Miata 2010-05-15 16:27:29 UTC --- This seems to overlap or be a dupe of bug 586044. I just installed M6 where M2 had been installed previously with success, but later updated, and initrd creation for newer kernel failed. Manual initrd creation also failed with "Device block!9:X not found in sysfs". Mkinitrd succeeded when I replaced mounting of / by-label with /dev/md3, and the initrd it created results in boot success. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.