Since you're running on z/VM, this won't be an issue unless you're planning on having both the current and the new DASD online to a guest at the same time. If the two sets of volumes do not need to be available at the same time, I would bring the guest down, DDR the volumes from old->new, update the CP directory with the new volumes, but using the old addresses, and re-IPL the guest.
If both sets of DASD need to be available concurrently, then bring them online without an IPL, with: echo add device range=addr1,addr2-addr3,add4 > /proc/dasd/devices Update /etc/zipl.conf and re-run zipl. I don't believe SLES8 uses an initrd, but if it does, then re-run mkinitrd. Once the "old" DASD is removed, I would update the CP directory to have the new DASD use the same device numbers as the old volumes. Then, re-updated /etc/zipl.conf and re-run zipl. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mike Lovins Sent: Tuesday, October 31, 2006 12:40 PM To: LINUX-390@VM.MARIST.EDU Subject: New DASD Can someone help me? We are currently going out for bids for new DASD for our IBM z800 processor that I have Linux running under Z/VM. The problem that I have is when we receive the new DASD the device addresses will be different than what I currently have defined to Suse Linux 8.1. I am not sure were throught out Linux the real device address is located. I know it resides in /etc/zipl.conf, but Iam not sure were else. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
