[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#420181: marked as done (Installation report 4.0 r0 "Etch" on IBM p5 510 inside LPAR)

Your message dated Wed, 08 Sep 2010 03:58:25 +0000
with message-id <E1OtBnl-0005Zl-W9@ravel.debian.org>
and subject line Closing old installation report #420181
has caused the Debian Bug report #420181,
regarding Installation report 4.0 r0 "Etch" on IBM p5 510 inside LPAR
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
420181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420181
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports

Boot method: cdrom
Image version: debian-40r0-powerpc-CD-1.iso,07-Apr-2007,17:42,629M
Date: today

Machine: IBM p5 model 510 inside LPAR
Processor: Power5+
Memory: 1G
Partitions: not reached this stage

Output of lspci -nn and lspci -vnn:
"no output"

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

Initial boot:           [O] (only install64, install crashes on ramdisk init)
Detect network card:    [E] module ibmveth for virtual ethernet is missing
Configure network:      [ ]
Detect CD:              [O]
Load installer modules: [E] md5sum warnings, missing files
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Install base system:    [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]

Comments/Problems:
Network install without ibmveth module is not a good idea in case there is no
physical adapter attached to the lpar - p.e. usage of IVM and not HMC. Do
testing images exist, which I can use?

I tried also the netinst iso and burned it on some other writer. I checked the
md5sums of the downloaded isos - they have been ok. Thus I think, the media I
booted the lpar are ok.

/var/log/syslog shows the following entries:

Apr 18 12:56:34 cdrom-detect: CD-ROM mount succeeded:
device=/dev/scsi/host0/bus0/target2/lun0/cd
Apr 18 12:56:34 cdrom-detect: Detected CD 'Debian GNU/Linux 4.0 r0 "Etch" -
Official powerpc CD Binary-1 20070407-14:58'
Apr 18 12:56:48 cdrom-detect: Detected CD with 'stable' (etch) distribution
...
Apr 18 12:56:48 cdrom-retriever: warning: Unable to find
contrib/debian-installer/binary-powerpc/Packages in /cdrom/dists/etch/Release.
Apr 18 12:56:48 cdrom-retriever: warning: Unable to find
contrib/debian-installer/binary-powerpc/Packages.gz in /cdrom/dists/etch/Release.
...
... lot of normal installer messages
...
Apr 18 12:56:48 anna[5190]: DEBUG: resolver (yaboot-installer): accept di-utils,
already installed
Apr 18 12:56:48 anna[5190]: DEBUG: resolver (yaboot-installer): accept
archdetect, already installed
Apr 18 12:56:53 anna[5190]: WARNING **: bad md5sum
Apr 18 12:57:03 anna[5190]: WARNING **: bad md5sum
Apr 18 12:57:05 main-menu[952]: WARNING **: Configuring 'load-cdrom' failed with
error code 7
Apr 18 12:57:05 main-menu[952]: WARNING **: Menu item 'load-cdrom' failed.

On checking the integrity of the cd in the first run I get
"./dists/etch/main/binary-powerpc/Packages file failed the MD5 checksum
verification. ...".  In the second run Packages.gz fails. I did a lot more runs
and usually the run stops at Packages but sometimes it stops at Packages.gz.

The messages of loading ibmvscsi are looking good:
Apr 18 12:56:01 kernel: ibmvscsi: host srp version: 16.a, host partition vio
(1), OS 3, max io 262144
Apr 18 12:56:01 kernel:   Vendor: AIX       Model: VDASD             Rev:
Apr 18 12:56:01 kernel:   Type:   Direct-Access                      ANSI SCSI
revision: 03
Apr 18 12:56:01 kernel:   Vendor: AIX       Model: VOPTA             Rev:
Apr 18 12:56:01 kernel:   Type:   CD-ROM                             ANSI SCSI
revision: 04
Apr 18 12:56:01 kernel: SCSI device sda: 10485760 512-byte hdwr sectors (5369 MB)
Apr 18 12:56:01 kernel: sda: Write Protect is off
Apr 18 12:56:01 kernel: sda: Mode Sense: 17 00 00 08
Apr 18 12:56:01 kernel: sda: cache data unavailable
Apr 18 12:56:01 kernel: sda: assuming drive cache: write through
Apr 18 12:56:01 kernel: SCSI device sda: 10485760 512-byte hdwr sectors (5369 MB)
Apr 18 12:56:01 kernel: sda: Write Protect is off
Apr 18 12:56:01 kernel: sda: Mode Sense: 17 00 00 08
Apr 18 12:56:01 kernel: sda: cache data unavailable
Apr 18 12:56:01 kernel: sda: assuming drive cache: write through
Apr 18 12:56:01 kernel:  sda: sda1 sda2
Apr 18 12:56:01 kernel: sd 0:0:1:0: Attached scsi disk sda
Apr 18 12:56:01 kernel: sr0: scsi3-mmc drive: 24x/24x cd/rw cdda tray
Apr 18 12:56:01 kernel: Uniform CD-ROM driver Revision: 3.20
Apr 18 12:56:01 kernel: sr 0:0:2:0: Attached scsi CD-ROM sr0
Apr 18 12:56:01 kernel: sd 0:0:1:0: Attached scsi generic sg0 type 0
Apr 18 12:56:01 kernel: sr 0:0:2:0: Attached scsi generic sg1 type 5

Has anybody of you some idea what is going wrong here?

Gottfried

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


--- End Message ---
--- Begin Message --- 
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---
Reply to: