> > It is helpful to know where the 390 was going to reboot into.
>
> >From iutil.py:reIPL:
>
> try:
> ipldev = anaconda.platform.bootDevice().disk.name
> except:
> ipldev = None
>
> Therefore, isn't it always going to reboot into the disk holding /boot?
> Don't you know that beforehand?
This is a visual confirmation from a different source (the /sys filesystem),
telling you where you will reboot into.
Just today, I am seeing:
[anaconda root@h0560027 root]# (read TYPE < /sys/firmware/reipl/reipl_type; echo "TYPE=$TYPE"; cat /sys/firmware/reipl/$TYPE/device;)
TYPE=fcp
0.0.3c1b
When /boot lives on:
[anaconda root@h0560027 root]# mount | egrep '( /mnt/sysimage | /mnt/sysimage/boot )'
/dev/dasdc2 on /mnt/sysimage type ext3 (rw,seclabel,relatime,errors=continue,user_xattr,acl,data="">
/dev/dasdc1 on /mnt/sysimage/boot type ext3 (rw,seclabel,relatime,errors=continue,user_xattr,acl,data="">
[anaconda root@h0560027 root]# ls -l /sys/bus/ccw/drivers/dasd-eckd/0.0.5f4f/block*
total 0
drwxr-xr-x. 10 root root 0 Dec 2 16:36 dasdc
This is a problem. Which is masked by the fact that another different version of RHEL lives on the scsi partition that is about to be booted into...
--
Mark
You must be the change you wish to see in the world. -- Mahatma Gandhi
Worrying is praying for that you do not wish to happen._______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
