Re: Debian on a pSeries Power6 anyone?
Hello,
On Thu, Mar 05, 2009 at 08:38:41AM +1100, Tony Breeds wrote:
> On Wed, Mar 04, 2009 at 08:29:59PM +0100, Frank Fegert wrote:
> > today i tried to move a LPAR w/ Debian Lenny from a p570 (Power5+) to
> > a p550 (Power6). The system resides on VIO-mapped SAN disks, so moving
> > it wasn't a big deal. Unfortunately it bails out pretty early in the
> > boot process with:
> > "unable to open file, Invalid device"
>
> I have debian running on a variety of pSeries machines.
>
> Can you send through your
> 1) /etc/yaboot.conf
> 2) output from fdisk -l
> and 3) output from ls -l /boot/
>
> We should be able to get this going.
here you go:
# cat /etc/yaboot.conf
boot=/dev/sda1
partition=2
#root=/dev/sda2
root=/dev/mapper/mpath0-part2
timeout=50
install=/usr/lib/yaboot/yaboot
enablecdboot
default=Linux
image=/boot/vmlinux
label=Linux
read-only
initrd=/boot/initrd.img
image=/boot/vmlinux.old
label=old
read-only
initrd=/boot/initrd.img.old
# sfdisk -l
Disk /dev/sda: 36864 cylinders, 64 heads, 32 sectors/track
Warning: The partition table looks like it was made
for C/H/S=*/255/63 (instead of 36864/64/32).
For this listing I'll assume that geometry.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 0 1- 8001 41 PPC PReP Boot
/dev/sda2 1 122 122 979965 83 Linux
/dev/sda3 123 4698 4576 36756720 8e Linux LVM
/dev/sda4 0 - 0 0 0 Empty
Disk /dev/dm-0: 4699 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/dm-0p1 * 0+ 0 1- 8001 41 PPC PReP Boot
/dev/dm-0p2 1 122 122 979965 83 Linux
/dev/dm-0p3 123 4698 4576 36756720 8e Linux LVM
/dev/dm-0p4 0 - 0 0 0 Empty
# ls -l /boot/
total 51748
-rw-r--r-- 1 root root 64577 2009-02-20 12:37 config-2.6.26
-rw-r--r-- 1 root root 74736 2009-01-10 16:43 config-2.6.26-1-powerpc64
lrwxrwxrwx 1 root root 17 2009-02-20 13:53 initrd.img -> initrd.img-2.6.26
-rw-r--r-- 1 root root 7979162 2009-03-04 16:09 initrd.img-2.6.26
-rw-r--r-- 1 root root 8570731 2009-02-10 12:37 initrd.img-2.6.26-1-powerpc64
-rw-r--r-- 1 root root 8570197 2009-01-16 10:00 initrd.img-2.6.26-1-powerpc64.bak
-rw-r--r-- 1 root root 7979203 2009-03-04 15:38 initrd.img-2.6.26.bak
lrwxrwxrwx 1 root root 29 2009-01-14 12:12 initrd.img.old -> initrd.img-2.6.26-1-powerpc64
-rw-r--r-- 1 root root 1587681 2009-02-20 13:42 System.map-2.6.26
-rw-r--r-- 1 root root 1799987 2009-01-10 16:43 System.map-2.6.26-1-powerpc64
lrwxrwxrwx 1 root root 14 2009-02-20 13:53 vmlinux -> vmlinux-2.6.26
-rw-r--r-- 1 root root 7474823 2009-02-20 13:42 vmlinux-2.6.26
-rw-r--r-- 1 root root 8761890 2009-01-10 16:42 vmlinux-2.6.26-1-powerpc64
lrwxrwxrwx 1 root root 26 2009-01-14 12:12 vmlinux.old -> vmlinux-2.6.26-1-powerpc64
As you can see from the commented entry for "root=" in yaboot.conf
i already tried using the non-dm-multipathed devices, but this wasn't
the cause of the problem.
Thanks & best regards,
Frank
Reply to: