Bug#445148: closed by Christian Perrier <bubulle@debian.org> (Closing oldbug report against debian-installer #445148)

[RPN01 <Nix.Robert@mayo.edu>]

I just tried the current download, and can't even get past formatting the
DASD. I get a window with the following:

┌──────────────┤ [!!] Partition disks ├──────────────┐
             │                      ERROR!!!                      │
             │ VTOC: seeking on device failed -- vtoc_write_label │
             │ Could not write VTOC labels.                       │
             │                                                    │
             │     <Go Back>                       <Continue>     │
             │                                                    │
             └────────────────────────────────────────────────────┘

The virtual machine has write access to the disk, so that's not the problem,
and I've tried just about every combination of formatting and not
formatting, labeling and not labeling the disks before and during the
install that I can think of.

Obviously, this works somewhere, or it wouldn't have been released in the
first place. And I don't think we have a very unique system here, so it
should be a fairly standard install. We run about 50 RedHat images, and
several SuSE images, so it's not like we're novices at this.... Any ideas
that might help, and won't take three more years to come up with?

-- 
Robert P. Nix          Mayo Foundation        .~.
RO-OC-1-18             200 First Street SW    /V\
507-284-0844           Rochester, MN 55905   /( )\
-----                                        ^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 9/11/10 2:17 AM, "Christian PERRIER" <bubulle@debian.org> wrote:

> Quoting RPN01 (Nix.Robert@mayo.edu):
>> I waited three years for ³Let us know if this happens again²?!? Gee...
> 
> I just closed 2000 installation reports, some dated much more than 3
> years.
> 
> So, yes sorry, we couldn't process all of them and some got
> ignored. Particularly trying to reproduce S/390 bugs is not as easy as
> just saying it.
> 
> In the case of such bugs, then the only option is telling people who
> had such problems to try reproducing them with the current
> installer. Particularly those who were due to partitions naming and
> ordering need to be re-examined because general changes in the
> installer behaviour wrt this. Not sure it affects S/390, though.
> 
>