https://bugzilla.novell.com/show_bug.cgi?id=655145
https://bugzilla.novell.com/show_bug.cgi?id=655145#c4
--- Comment #4 from Kevin Wendzel 2010-11-23 19:13:37 UTC ---
I'm getting closer in my own debug. I did manage to get the system up by
copying the new directory in /etc/modules to the old directory of the same
name, and so can now access it remotely.
When I first installed the system, I created a boot partition on /dev/sda1 and
/dev/sdb1 as a RAID configuration. However, now I see the following on the
system:
sysmanagerdev:/mnt # ls -l /mnt/sda1
total 58380
-rwxr-xr-x 1 root root 6941862 Nov 19 22:11 initrd.001
-rwxr-xr-x 1 root root 7153551 Nov 19 22:11 initrd.002
-rwxr-xr-x 1 root root 7153551 Nov 19 22:11 initrd.003
drwxr-xr-x 3 root root 4096 Nov 19 22:11 ppc
-rwxr-xr-x 1 root root 19056806 Nov 19 22:11 vmlinux.001
-rwxr-xr-x 1 root root 19053606 Nov 19 22:11 vmlinux.002
-rwxr-xr-x 1 root root 405028 Nov 19 22:11 yaboot
-rwxr-xr-x 1 root root 640 Nov 19 22:11 yaboot.cnf
sysmanagerdev:/mnt # ls -l /mnt/sdb1
total 58380
-rwxr-xr-x 1 root root 6941862 Nov 19 22:11 initrd.001
-rwxr-xr-x 1 root root 7153551 Nov 19 22:11 initrd.002
-rwxr-xr-x 1 root root 7153551 Nov 19 22:11 initrd.003
drwxr-xr-x 3 root root 4096 Nov 19 22:11 ppc
-rwxr-xr-x 1 root root 19056806 Nov 19 22:11 vmlinux.001
-rwxr-xr-x 1 root root 19053606 Nov 19 22:11 vmlinux.002
-rwxr-xr-x 1 root root 405028 Nov 19 22:11 yaboot
-rwxr-xr-x 1 root root 640 Nov 19 22:11 yaboot.cnf
sysmanagerdev:/mnt # ls -l /boot
total 48436
-rw-r--r-- 1 root root 2437695 Nov 2 11:35 System.map-2.6.32.24-0.2-ppc64
-rw-r--r-- 1 root root 1236 Jun 2 09:32 boot.readme
-rw-r--r-- 1 root root 90921 Nov 2 11:52 config-2.6.32.24-0.2-ppc64
lrwxrwxrwx 1 root root 26 Nov 23 10:08 initrd ->
initrd-2.6.32.24-0.2-ppc64
-rw------- 1 root root 10311348 Jun 8 21:49 initrd-2.6.32.12-0.7-ppc64-kdump
-rw-r--r-- 1 root root 7142692 Nov 23 10:08 initrd-2.6.32.24-0.2-ppc64
-rw------- 1 root root 10303089 Nov 23 08:50 initrd-2.6.32.24-0.2-ppc64-kdump
-rw-r--r-- 1 root root 155537 Nov 2 11:55 symvers-2.6.32.24-0.2-ppc64.gz
lrwxrwxrwx 1 root root 27 Nov 19 22:12 vmlinux ->
vmlinux-2.6.32.24-0.2-ppc64
-rw-r--r-- 1 root root 19056806 Nov 2 12:12 vmlinux-2.6.32.24-0.2-ppc64
It looks like the new kernel was installed directly in the "boot" folder on the
root file system instead of in the root of the boot file system which should
have been mounted on /boot. How did this happen? Yaboot is still very
obviously trying to boot off of sd*1, which is certainly causing the 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.
