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

RE: [Redhat-s390-list] DASD Formatting Failure


I did not get the same error.  The dasdfmt went by too quickly, so I'm not
sure what's happened there.  The minidisk was CMS formatted (to get rid of
the CDL formatting), so that might have caused that.  But, it looks like the
fix to formatmnt is OK.

Mark Post

-----Original Message-----
From: Karsten Hopp [mailto:Karsten Hopp redhat de]
Sent: Thursday, October 18, 2001 4:13 PM
To: Post, Mark K
Cc: 'redhat390'
Subject: Re: [Redhat-s390-list] DASD Formatting Failure

I think I found the bug (variable has been set to a wrong value).

Can you please test ftp://people.redhat.com/karsten/formatmnt ?

The easiest way without having to unpack the initrd.img is this:

- download the formatmnt binary to a Linux system 
- ipl your VM
- when you're prompted to log in via ssh/telnet execute this 
  command from the Linux machine with the new binary:
  cat formatmnt | ssh root VM_to_install cat \> \/sbin\/formatmnt

  Karsten Hopp

On Thu, Oct 18, 2001 at 02:02:58PM -0400, Post, Mark K wrote:
> I'm using the latest VM initrd and kernel.  When I IPL the system, and
> rhsetup, the first thing I see is the DASD initialisation dialog.  I tell
> that I want to make /dev/dasda my root, and /dev/dasdb my /usr.  Then I'm
> asked if I want to use the cdl or ldl format.  I select ldl and hit
> which is immediately followed by:
>           Memory fault
>                        formatmnt
>                                 Stopped installation. No cleanup is done!
>                                                                          #

 Karsten Hopp        | Mail: karsten redhat de
 Red Hat Deutschland | Tel: +49-711-96437-0
 Hauptstaetterstr.58 | Fax: +49-711-96437-111
 D-70178 Stuttgart   | http://www.redhat.de 

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