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 failed. What is the best way to handle this? Should they be using /dev/disk/by-path/ccw-0.0.010a-part1 to reference the new dasd? Thanks, Neal ---------------------------------------------------------------------- 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/
