Your message dated Sat, 20 Jul 2013 01:02:26 +0200 with message-id <201307200102.46526.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #596760, regarding Reportbug installation-reports 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.) -- 596760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596760 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---Title: Reportbug installation-reports Package: installation-reports
- To: <submit@bugs.debian.org>
- Subject: Reportbug installation-reports
- From: RPN01 <Nix.Robert@mayo.edu>
- Date: Mon, 13 Sep 2010 15:27:56 -0500
- Message-id: <C8B3F37C.E3EC%Nix.Robert@mayo.edu>
Boot method: z/VM virtual card reader
Image version: http://ftp.nl.debian.org/debian/dists/lenny/main/installer-s390/current/images/generic/
Date: 09/13/2010 09:30am
Machine: IBM Z9 2094 2IFL
z/VM Version 5 Release 3.0, service level 0702 (64-bit)
Generated at 10/31/07 09:12:13 CDT
Processor: IBM 2094
Memory: 22GIG - 1GIG virtual machine
Partitions: (2) 6.88GIG 3390 DASD devices, (1) .09GIG DASD device
Output of lspci -knn (or lspci -nn): never got a running Debian system
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card: [O]
Configure network: O ]
Detect CD: [ ]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [E]
Install base system: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]
Comments/Problems: DASD configures, and partitions, but fails to write
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
DASD formats, and goes through the configuration. Desired setup was to have / on one larger disk, /usr on the
other, and /boot on the small disk. No swap initially (there will be vdisk for that later). Also tried setting up
a single large disk for everything. Once I accept any of the configurations, I get the following error:
┌──────────────┤ [!!] Partition disks ├──┐
│ ERROR!!! │
│ VTOC: seeking on device failed -- vtoc_write_label │
│ Could not write VTOC labels. │
│ │
│ <Go Back> <Continue> │
│ │
└──────────────────────┘
The disks are R/W. I was able to format them with CPFMTXA, and the initial Linux format works. I’ve tried
with and without both, with no change in behavior. Virtual machine definition follows:
USER DEB1ZL01 XXXXXXXX 1G 1G G
COMMAND SET VSWITCH VSWG GRANT &USERID
COMMAND COUPLE 8200 TO SYSTEM VSWG
*
IPL CMS PARM AUTOCR
MACH XA
OPTION APPLMON
*
CONSOLE 0009 3215 T
NICDEF 8200 TYPE QDIO LAN SYSTEM VSWG
SPOOL 000C 2540 READER *
SPOOL 000D 2540 PUNCH A
SPOOL 000E 1403 A
*
LINK MAINT 0190 0190 RR
LINK LINUX1 0192 0191 RR
LINK LINUX1 0191 0192 RR
LINK MAINT 019D 019D RR
LINK MAINT 019E 019E RR
MDISK 0391 3390 31283 125 VG0125 MR
MDISK 0392 3390 17701 10016 VP0133 MR
MDISK 0393 3390 1 10016 VP0136 MR
--- End Message ---
--- Begin Message ---
- To: 540724-done@bugs.debian.org, 593013-done@bugs.debian.org, 608151-done@bugs.debian.org, 598804-done@bugs.debian.org, 597854-done@bugs.debian.org, 596760-done@bugs.debian.org, 595363-done@bugs.debian.org, 592446-done@bugs.debian.org, 592003-done@bugs.debian.org, 590575-done@bugs.debian.org, 590466-done@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sat, 20 Jul 2013 01:02:26 +0200
- Message-id: <201307200102.46526.holger@layer-acht.org>
Hi, thank you for submitting installation reports, much appreciated. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they contained user errors and/or - they have been from a development phase where things were not stable and/or - they are very old, more than 2.5 years. If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---