2018-01-29 13:47 GMT-05:00 Mark Post <mp...@suse.com>:
> >>> On 1/28/2018 at 09:51 PM, Csaba Polgar <csaba_pol...@hu.ibm.com>
> wrote:
> > Hello,
> >
> > I'm newbie on this forum, but I would like to ask your help. (Sorry, if
> I
> > brake any protocol/usage guideline.)
> > Could someone please help to solve the below issue?
> >
> -snip-
> >
> > How can it be online (active) before the Linux boot? Or what is missing
> > from the configuration?
>
> There's not nearly enough information to know what's going on, yet.
> First, what distribution is this? What maintenance level?
>
> Next, is this an LVM setup, or something else? If LVM, then some output
> from things like "vgs" "pvs" "vgdisplay -v" and so on would be helpful.
>
Probably that's an LVM with many dasds as PVs (judging by "dm-28" device
name) and some of them haven't been online-d in a permanent way.
If this is suse then as far as I remember just activate them using yast and
on exit it should save it. There also was another way. Just run
"dasd_configure 0.0.0400 1" and it should do the trick. I don't think you
need to run mkinitrd unless this this device is a part of a root filesystem
but probably it is not otherwise you wouldn't complete the boot at all.
If this is redhat then you can add these to dasd.conf for example:
cat /etc/dasd.conf
0.0.0200
0.0.0201
0.0.0210
If this a really old redhat you might need to add these to /etc/zipl.com
for example like this(in redhat 6 and 7 you can either way) :
[root@lin00 ~]# cat /etc/zipl.conf
[defaultboot]
defaultauto
prompt=1
timeout=5
default=linux
target=/boot
[linux]
image=/boot/vmlinuz-3.10.0-123.el7.s390x
parameters="cio_ignore=all,!condev root=/dev/mapper/rhel_lin00-root
crashkernel=auto rd.lvm.lv=rhel_lin00/root vconsole.keymap=us
vconsole.font=latarcyrheb-sun16 rd.dasd=0.0.0200 rd.dasd=0.0.0201
rd.dasd=0.0.0210 rd.dasd=0.0.0211 rd.dasd=0.0.0192 rd.lvm.lv=rhel_lin00/boot
LANG=en_US.UTF-8"
ramdisk=/boot/initramfs-3.10.0-123.el7.s390x.img
see above list of rd.dasd= with addresses? After adding these you need to
run zipl to save it in the ipl record (you can do zipl --dry-run -V to
verify that it does what it should)
Regards
Gregory
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
