Hi,
I recently activated and started using the basic hvc0 terminal driver in
SLES11. Its great to lose that last dependancy on 3215 line mode when fixing
bootup problems! I'm happy with the way it's set up now, but trying to get my
brain around the console=hvc0 zipl parameter. Since I can
We're walking through the IBM doc Sharing and Maintaining SLES11 Linux
under z/VM using DCSSs and an NSS but using EDEV FBA devices instead of
native CKD devices. We've move to the point where we are making our first
cloned copy and are running into issues.
The original script identifies the CKD
Craig,
We've altered the script to identify the FBA devices,
format them with 'mkfs' and then use the 'dd' to perform
the block copy. When we try to boot the cloned copy
Just some thoughts - after you dd them, but before you try to IPL, are you
able to mount the new targets as file systems?
Hi, Craig, --
For FBA, you are correct to dispense with 'dasdfmt'. (Will detail
that in a following note.)
You still need to stamp a bootstrap onto the FBA disk, and the
bootstrap is different for FBA than for CKD.
... We've altered the script to
identify the FBA devices, format them
There is a lot of confusion about 'dasdfmt' versus 'mkfs'. If you
already know the difference, please excuse this note. The water is
muddier for mainframers because in z/OS land the concept of
filesystem and volume is blurred. z/OS uses the low level
structure (tracks, blocks, records, even
Hi,
I noticed that in my boot log (dmesg) I see a return code of -5 when reading
device features for each minidisk on this system. I am not using the DIAG
module or PAV.
dasd-eckd.637cf1: 0.0.0150: Reading device feature codes failed with rc=-5
dasd-eckd.90fb0d: 0.0.0150: New DASD 3390/0A
Answered my own question! Found the error codes in the Kernel Messages on
SUSE Linux manual here:
http://public.dhe.ibm.com/software/dw/linux390/docu/l26ekm00.pdf
The explanation states: The device feature codes state which
advanced features are supported by a device.
Examples for
