Your message dated Sun, 21 Nov 2004 21:42:42 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#281556: s390 installation report, installed system does 
not boot
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Nov 2004 16:58:06 +0000
>From [EMAIL PROTECTED] Tue Nov 16 08:58:06 2004
Return-path: <[EMAIL PROTECTED]>
Received: from boy.univ.kiev.ua (mail.univ.kiev.ua) [193.125.78.122] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CU6eb-0005cY-00; Tue, 16 Nov 2004 08:58:06 -0800
Received: from intel4.icc.univ.kiev.ua (intel4.icc.univ.kiev.ua [10.25.0.243])
        by mail.univ.kiev.ua (8.12.2/8.12.2) with ESMTP id iAGGvxC7071159;
        Tue, 16 Nov 2004 18:58:01 +0200 (EET)
Received: from eugen by intel4.icc.univ.kiev.ua with local (Exim 4.34)
        id 1CU6eV-0006Y3-6A; Tue, 16 Nov 2004 18:57:59 +0200
Date: Tue, 16 Nov 2004 18:57:59 +0200
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: s390 installation report, installed system does not boot
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="Nq2Wo0NMKNjxTN9z"
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
From: Eugeniy Meshcheryakov <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--Nq2Wo0NMKNjxTN9z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Package: installation-reports

INSTALL REPORT

Debian-installer-version: http://ftp.de.debian.org/debian/dists/unstable/main/
                installer-s390/20041027/images/generic/  
uname -a: Linux debian 2.4.27-1-s390 #1 SMP Tue Aug 17 12:18:33 CEST 2004 s390 
GNU/Linux
Date: 2004.11.15-2004.11.16
Method: ipl from tape, used ssh after

Machine: hercules, version 2.17.1-2 
Processor:
Memory:
Root Device: <IDE?  SCSI?  Name of device?>
Root Size/partition table:  Feel free to paste the full partition
      table, with notes on which partitions are mounted where.
Output of lspci and lspci -n:

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

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [O]
Detect CD:              [ ]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [E/-]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [E]

Comments/Problems:
 I was not able to format dasd using d-i (known problem, should be fixed now), 
so
I formated dasd manually and formated it with cfdisk. After successfull firts 
stage
I rebooted hercules but I was not able to boot using zipl defaul setup. Linux 
was
not able to find root partition (zipl.conf attached).
 After using google.com I found that I need to pass dasd=0120 to zipl in order
to boot. That worked. It is posible that dasd parameter is missing because I
did not use d-i for formating dasd and partitioning.
 
 

--Nq2Wo0NMKNjxTN9z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="zipl.conf"

[defaultboot]
defaultmenu = menu

:menu
target = /boot
1 = debian
2 = old
default = 1
prompt = 1
timeout = 10

[debian]
target = /boot
image = /boot/vmlinuz
parameters = ro vmpoff="LOGOFF" root=/dev/dasda1

[old]
target = /boot
image = /boot/vmlinuz.old
parameters = ro vmpoff="LOGOFF" root=/dev/dasda1
optional = 1

--Nq2Wo0NMKNjxTN9z--

---------------------------------------
Received: (at 281556-done) by bugs.debian.org; 21 Nov 2004 20:43:12 +0000
>From [EMAIL PROTECTED] Sun Nov 21 12:43:12 2004
Return-path: <[EMAIL PROTECTED]>
Received: from 195-240-184-66-mx.xdsl.tiscali.nl (elrond.fjphome.nl) 
[195.240.184.66] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CVyYB-0008Lg-00; Sun, 21 Nov 2004 12:43:12 -0800
Received: from strider.fjphome.nl ([10.19.66.86] ident=fjp)
        by elrond.fjphome.nl with esmtp (Exim 3.35 #1 (Debian))
        id 1CVyXh-000416-00
        for <[EMAIL PROTECTED]>; Sun, 21 Nov 2004 21:42:41 +0100
From: Frans Pop <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#281556: s390 installation report, installed system does not 
boot
Date: Sun, 21 Nov 2004 21:42:42 +0100
User-Agent: KMail/1.6.2
References: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

On Tuesday 16 November 2004 17:57, Eugeniy Meshcheryakov wrote:
> Comments/Problems:
>  I was not able to format dasd using d-i (known problem, should be
> fixed now), so I formated dasd manually and formated it with cfdisk.
> After successfull firts stage I rebooted hercules but I was not able to
> boot using zipl defaul setup. Linux was not able to find root partition
> (zipl.conf attached).

Closing this report as this issue has been fixed with the update of the 
dasd selection/formatting step.

Cheers,
FJP


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to