INFO LINUX-390
--
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
Hi,
yes, by-path or by-uuid is more reliable than the /dev/dasdX name.
The /dev/dasdX name depends on the order that the disks are set online
in the system.
Depending on the distribution this can not reliably be predicted.
Regards,
Stefan
On 12.12.18 17:39, Neal Scheffler wrote:
> The Linux
Thank you Alan,
*CP Q MDISK 201 LOC *
TargetID Tdev OwnerID Odev Dtype Vol-ID Rdev StartLoc Size
SLES15 0201 SLES15 0201 3390 LL631F 631F 1 10016
*Q DASD DETAILS 631F
*
631F CUTYPE = 3990-EC, DEVTYPE = 3390-0C,
On Wednesday, 12/12/2018 at 06:18 GMT, Frank Wolfe
wrote:
> Working on SLES15 installation and it was formatting my 201 disk (DASDB)
> with an end cylinder of , however the installation did finish
when
> it hit 10016... This a bug?
Assuming this is on z/VM please show the output of
-
Hi all,
Working on SLES15 installation and it was formatting my 201 disk (DASDB)
with an end cylinder of , however the installation did finish when
it hit 10016... This a bug?
[image: image.png]
--
For LINUX-390
We use /dev/disk/by-path/ccw-0.0.-part1 / in /etc/fstab for the root file
system
Not sure what distro you are on, but dasd_configure will create the appropriate
udev rules for new disks as well.
-Original Message-
From: Linux on 390 Port On Behalf Of Neal Scheffler
Sent:
The Linux group expanded the root vg to a second physical dasd volume.
Doing a pvdisplay shows the PV Name of /dev/dasdm1
zipl.conf was updated to include the parm "rd.dasd=0.0.010a" since
this is part of the root file system.
After reboot, dasd 010a is now /dev/dasdb1 so the server reboot
