https://bugzilla.novell.com/show_bug.cgi?id=727797 https://bugzilla.novell.com/show_bug.cgi?id=727797#c0 Summary: mkinitrd errors on run and fails to create kernel initrd, says: file /lib/mkinitrd/setup/11-storage.sh has syntax error on line(s) 28 & 34 ; around: 0x100000 Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jasonsmr@hotmail.com QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=459941) --> (http://bugzilla.novell.com/attachment.cgi?id=459941) log file created by command : # bash -vx /sbin/mkinitrd &>mkinitrd-log.txt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 package: mkinitrd-2.7.0-156.3.x86_64 command called: mkinitrd error displayed on terminal: start-of-error { # mkinitrd Kernel image: /boot/vmlinuz-2.6.32.12-0.7-default Initrd image: /boot/initrd-2.6.32.12-0.7-default WARNING: All config files need .conf: /etc/modprobe.d/ibm-amd, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/generic_serial-blacklist, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/pam_fp-uinput, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/infiniband, it will be ignored in a future release. KMS drivers: nvidiafb nvidia /lib/mkinitrd/setup/11-storage.sh: line 28: ( * 0x100000) + : syntax error: operand expected (error token is "* 0x100000) + ") /lib/mkinitrd/setup/11-storage.sh: line 34: / 0x100000 : syntax error: operand expected (error token is "/ 0x100000 ") Fatal storage error. Device rootfs could not be analyzed. There was an error generating the initrd (1) } end-of-error As far as I can tell the script "/lib/mkinitrd/setup/11-storage.sh" is looking into the proc filesystem for the root device or rootfs in /proc/devices. and it's not finding it. In case Im right Included is a log of my /proc/devices start-of-log { # cat /proc/devices Character devices: 1 mem 4 /dev/vc/0 4 tty 5 /dev/tty 5 /dev/console 5 /dev/ptmx 7 vcs 10 misc 13 input 14 sound/mixer 14 sound/dsp 14 sound/audio 14 sound/adsp 21 sg 29 fb 116 alsa 128 ptm 136 pts 162 raw 180 usb 188 ttyUSB 189 usb_device 195 nvidia 204 xvc 226 drm 231 infiniband_mad 231 infiniband_verbs 249 firewire 250 hidraw 251 gntdev 252 blktap 253 bsg 254 rtc Block devices: 259 blkext 7 loop 8 sd 9 md 11 sr 65 sd 66 sd 67 sd 68 sd 69 sd 70 sd 71 sd 128 sd 129 sd 130 sd 131 sd 132 sd 133 sd 134 sd 135 sd 253 device-mapper 254 mdp } end-of-log And another log for my mounted system from the mount command start-of-log { # mount devtmpfs on /dev type devtmpfs (rw,relatime,size=3054412k,nr_inodes=763603,mode=755) tmpfs on /dev/shm type tmpfs (rw,relatime,size=1062340k,nr_inodes=265585) /dev/mapper/Linux-root on / type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=journal) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) /dev/sdb3 on /boot type ext2 (rw,relatime,errors=continue) /dev/mapper/Linux-home on /home type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered) /dev/mapper/Linux-local on /local type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered) /dev/mapper/Linux-opt on /opt type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered) /dev/mapper/Linux-srv on /srv type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered) /dev/mapper/Linux-tmp on /tmp type ext3 (rw,nosuid,nodev,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered) /dev/mapper/Linux-usr on /usr type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered) /dev/mapper/Linux-var on /var type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) proc on /proc/bus/usb type usbfs (rw,relatime,devmode=666) securityfs on /sys/kernel/security type securityfs (rw,relatime) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) proc on /var/lib/named/proc type proc (ro,nosuid,nodev,noexec,relatime) novfs on /var/opt/novell/nclmnt type novfs (rw,relatime) proc on /var/lib/ntp/proc type proc (rw,relatime) proc on /var/lib/dhcp/proc type proc (ro,relatime) Reproducible: Always Steps to Reproduce: 1.upgrade to new kernel 3.2 and udev from factory repositories 2.run mkinitrd 3. Actual Results: well I had a bit of a older system setup I have come across similar issues with mkinitrd before. It was that the mkinitrd again* could not determine The correct location of the rootfs. Actually, the problem was worse, because it created a initrd file that assumed somehow* that my rootfs was located on a drive formatted with the rootfs or mounted as rootfs type*, unless I am mistaken or in a directory named /rootfs and not as I have it now as mounted on / as type ext3. Expected Results: create a initrd that finds the kernel in the /boot directory and makes a initrd for the kernel(s) there-in; automaticly updating fstab, mtab and or proc with the proper filesystems types. -- 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.