sudo /sbin/lsdasd to se what dasd is online su - (just for simplicity) lsdasd vmcp link VMUSERLX 300 300 MR = link to new disk added in VM profile chccwdev -e 300 = make it online, should now be visible with lsdasd
___________________________________________ Tore Agblad Volvo Information Technology Infrastructure Mainframe Design & Development, Linux servers Dept 4352 DA1S SE-405 08, Gothenburg Sweden Telephone: +46-31-3233569 E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Marian Gasparovic Sent: den 20 november 2009 11:26 To: LINUX-390@VM.MARIST.EDU Subject: Re: adding DASD on SUSE Mark, as dasd= parm in zipl.conf is not used now, how can I check which DASDs were supposed to be online ? Thank you =================== Marian Gasparovic =================== "The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind." --- On Fri, 11/13/09, Mark Post <mp...@novell.com> wrote: > From: Mark Post <mp...@novell.com> > Subject: Re: adding DASD on SUSE > To: LINUX-390@VM.MARIST.EDU > Date: Friday, November 13, 2009, 11:01 PM > >>> On 11/13/2009 at > 4:41 PM, Mark Ver <mark...@us.ibm.com> > wrote: > > What I was really interested in was the Linux side > configuration to add the > > disk permanently so that it would be online during > boot up. > > > > Like were most people ... > > - just running a big script calling > dasd_configure as Mark Post had > > suggested > > This brings the volume online _and_ creates the hwcfg file > for it, thus making it "permanent" in the sense it will be > online when you reach runlevel 3 at the next reboot. > Even better, it's supported. > > > - or do most just do chccwdev and then run > mkinitrd and zipl > > This will not make it permanent in any practical sense, > > > - or copy an old hwcfg-dasd-bus-ccw-* file, run > mkinitrd/zipl if needed, > > and reboot. > > Not recommended, but you get to keep all the pieces. > > > - or modify the "options dasd_mod" line with a > dasd=<dasd-list> parameter > > in the appropriate modprobe.conf > > - or add a dasd=<dasd-list> in their > kernel parameters > > - or use yast to add the disks (including > patiently adding it all one at a > > time during installation). > > Also supported, but for large numbers of volumes, certainly > not recommended. > > The thing you need to understand about the Linux 2.6 > kernels is that the system will detect any and all DASD > volumes that are accessible to it during the boot process, > or later if the volume is ATTACHed or configured online to > the LPAR. The need to have the > 'dasd="unit1,unit2,unit3"' kernel parameter isn't there any > longer, per se. If you want to have read-only disks > and the like, that is still somewhat useful. > > The real question is how do you ensure that volumes you > want online are indeed online after the next reboot. > For one or two, use YaST. For bunches, use > dasd_configure. Your fingers will thank you for it. > > > Mark Post > > ---------------------------------------------------------------------- > 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 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 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
