Processed: Re: Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf)

2009-07-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 515249 normal
Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, 
yaboot.conf)
Severity set to `normal' from `grave'

> clone 515249 -1
Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, 
yaboot.conf)
Bug 515249 cloned as bug 537590.

> retitle -1 manual: Mention console=hvc0 for ppc?
Bug#537590: installation-reports: Various issues on IBM Power5 (lvm, multipath, 
yaboot.conf)
Changed Bug title to `manual: Mention console=hvc0 for ppc?' from 
`installation-reports: Various issues on IBM Power5 (lvm, multipath, 
yaboot.conf)'.

> reassign -1 installation-guide
Bug#537590: manual: Mention console=hvc0 for ppc?
Bug reassigned from package `installation-reports' to `installation-guide'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf)

2009-07-19 Thread Max Vozeler
severity 515249 normal
clone 515249 -1
retitle -1 manual: Mention console=hvc0 for ppc?
reassign -1 installation-guide
thanks

On Sun, Feb 15, 2009 at 10:49:36AM +, Paul McEnery wrote:
> Comments/Problems:
> 
> Initial boot: Maybe not soe much an error, I had to specify the
>   console at the boot prompt "console=hvc0,38400"

There is no mention of hvc0 in the powerpc installation guide,
so it might be useful to add a mention there.

Is it common to have hvc0 on ppc? I know it only wrt. XEN.

Max



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#515249: installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf)

2009-02-15 Thread Paul McEnery
Package: installation-reports
Severity: grave
Justification: renders package unusable



-- Package-specific info:

Boot method: Network boot using a TFTP server
Image version: 
ftp://ftp.debian.org/debian/dists/sid/main/installer-powerpc/current/images/powerpc64/netboot/vmlinuz-chrp.initrd
 ** see note below
Date: Sat Feb 14 21:00:00 GMT 2009

Machine: IBM,9117-570 (pSeries)
Partitions:

Machine: IBM,9117-570 (pSeries)
Partitions:

* sfdisk -d /dev/mapper/mpath0

# partition table of /dev/mapper/mpath0
unit: sectors

/dev/mapper/mpath0p1 : start=   63, size=16002, Id=41, bootable
/dev/mapper/mpath0p2 : start=16065, size=   498015, Id=83
/dev/mapper/mpath0p3 : start=   514080, size= 66589425, Id=8e
/dev/mapper/mpath0p4 : start=0, size=0, Id= 0



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [ ]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

Initial boot: Maybe not soe much an error, I had to specify the
  console at the boot prompt "console=hvc0,38400"

Detect had drives: During an attempt to reinstall after a failed
   install, I had to drop to a shell and remove
   any existing logical volumes before the
   disk detection process was able to detect
   the hard drive. Otherwise, it simply told
   me that there were not hard drives...

Overall install:

* Although the URL above is for the SID installer, when the
install was complete, I noticed that LENNY had been installed.
I noticed this by looking at the /etc/apt/sources.list file.

Other issues that I was not particularly happy with were:

1.
Selecting guided LVM allowed a the root filesystem to be
placed in a logical volume (which I wanted), but then the
yaboot.conf file was still writted to /etc/yaboot.conf.
I had to manually rescue the system after the install and
move /etc/yaboot.conf to /boot/etc/yaboot.conf. In my view
LVM is going to be the way forward and this configuration
file should not been located on the root filesystem. I
hope everyone is aware of this issue and has looked at
keeping files required to boot the system in /boot

2.
After fixing the location of the yaboot.conf file, the
system refused to boot. It was trying to boot the label
"old" which was invalid because the kernel has not yet
been upgraded. I therefore had to add the following to
the yaboot.conf before the correct default entry would
boot:

defaultos=Linux


3.
I also had issues with multipath root and LVM:

3.1
I had to add multipath to the lvm2 PREREQ's in order
for multipath to be started before LVM.

3.2
Debian installer was called with:

disk-detect/multipath/enable=true

However, once the install had completed, the lvm.conf
was not configured to filter out the underlying SCSI
devices. I had to add the following filter:

filter = [ "r/disk/", "r/sd.*/", "a/.*/" ]


After rebuilding the initramfs (above two changes
commited), it all worked quite nicely ;)



-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="5.0 (lenny) - installer build 20090123"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
umame -a: Linux rootvg 2.6.26-1-powerpc64 #1 SMP Sat Jan 10 14:42:07 CET 2009 
ppc64 unknown
lsmod: Module  Size  Used by
lsmod: ufs   103184  0 
lsmod: hfsplus   104520  0 
lsmod: hfs72464  0 
lsmod: md_mod119108  0 
lsmod: xfs   732616  0 
lsmod: reiserfs  334652  0 
lsmod: jfs   234180  0 
lsmod: ext3  187856  5 
lsmod: jbd79760  1 ext3
lsmod: vfat   20560  0 
lsmod: fat76656  1 vfat
lsmod: nls_base   15356  5 hfsplus,hfs,jfs,vfat,fat
lsmod: ext2  103952  1 
lsmod: mbcache16884  2 ext3,ext2
lsmod: dm_emc 11648  0 
lsmod: dm_round_robin  9176  1 
lsmod: dm_multipath   31816  3 dm_emc,dm_round_robin
lsmod: dm_mod 95016  21 dm_multipath
lsmod: sd_mod 3  2 
lsmod: