Which kernel are you running ? Are the dasd drivers built into the kernel or are they modules ? If they are modules, can you unpack the initrd and check the insmod parameters in the linuxrc ?
# zcat initrd.img > /tmp/initrd # mkdir /tmp/tmpdir # mount /tmp/initrd /tmp/tmpdir -o loop # less /tmp/tmpdir/linuxrc # umount /tmp/tmpdir Karsten On Fri, Jun 13, 2003 at 01:35:15PM -0400, Post, Mark K wrote: > Eric, > > Ok, so you've > - rebooted your system (maybe, maybe not, I'm only really interested in the > next item) > - the kernel command line shows > "dasd=0200,0201,0202,0203,0204,0205,0206,0207,0208,0209" (which seems to be > very different from what was in /etc/zipl.conf by the way), and > - the Q DASD command shows them all there. > > Re-issue the "cat /proc/dasd/devices" command and show us the output from > that. > Also, if you would email me offline with the entire contents of a "dmesg" > command. > > Mark Post > > -----Original Message----- > From: Wilson, Eric [mailto:[EMAIL PROTECTED] > Sent: Friday, June 13, 2003 1:27 PM > To: [EMAIL PROTECTED] > Subject: Re: adding DASD post install > > > It's all there. I'm not a VM master, so I'm not familiar with USER DIRECT. > I > can see the DASD if I echo the addrs to the kernel, after boot, so I'm > assuming > the answer is yes. > > CP Q V DASD > DASD 0092 3390 430W01 R/O 67 CYL ON DASD 12F7 SUBCHANNEL = 0017 > DASD 0190 3390 430RES R/O 107 CYL ON DASD 12F6 SUBCHANNEL = 0006 > DASD 0191 3390 LNX002 R/W 50 CYL ON DASD 12F2 SUBCHANNEL = 000C > DASD 019D 3390 430RES R/O 102 CYL ON DASD 12F6 SUBCHANNEL = 0008 > DASD 019E 3390 430RES R/O 175 CYL ON DASD 12F6 SUBCHANNEL = 0007 > DASD 0200 3390 LNX003 R/W 200 CYL ON DASD 12F3 SUBCHANNEL = 000D > DASD 0201 3390 LNX000 R/W 3338 CYL ON DASD 12F0 SUBCHANNEL = 000E > DASD 0202 3390 LNX001 R/W 3338 CYL ON DASD 12F1 SUBCHANNEL = 000F > DASD 0203 3390 LNX019 R/W 3338 CYL ON DASD 12EB SUBCHANNEL = 0010 > DASD 0204 3390 LNX020 R/W 3338 CYL ON DASD 12FB SUBCHANNEL = 0011 > DASD 0205 3390 LNX022 R/W 3338 CYL ON DASD 12FC SUBCHANNEL = 0012 > DASD 0206 3390 LNX023 R/W 3338 CYL ON DASD 12ED SUBCHANNEL = 0013 > DASD 0207 3390 LNX024 R/W 3338 CYL ON DASD 12FD SUBCHANNEL = 0014 > DASD 0208 3390 LNX025 R/W 3338 CYL ON DASD 12EE SUBCHANNEL = 0015 > DASD 0209 3390 LNX028 R/W 3338 CYL ON DASD 12FF SUBCHANNEL = 0016 > DASD 0401 3390 430RES R/O 102 CYL ON DASD 12F6 SUBCHANNEL = 000A > DASD 0402 3390 430RES R/O 102 CYL ON DASD 12F6 SUBCHANNEL = 0009 > DASD 0405 3390 430RES R/O 114 CYL ON DASD 12F6 SUBCHANNEL = 000B > > > > Cheers; > > E! > > ----------------- > > > > -----Original Message----- > From: McKown, John [mailto:[EMAIL PROTECTED] > Sent: Friday, June 13, 2003 11:19 AM > To: [EMAIL PROTECTED] > Subject: Re: adding DASD post install > > > Eric, > May I ask a silly question? What does the z/VM command "#CP Q V DASD" report > for this user? Did USER DIRECT get updated and put online (DIRECTXA)? > > > -- > John McKown > Senior Systems Programmer > UICI Insurance Center > Applications & Solutions Team > +1.817.255.3225 > > This message (including any attachments) contains confidential information > intended for a specific individual and purpose, and its' content is > protected by law. If you are not the intended recipient, you should delete > this message and are hereby notified that any disclosure, copying, or > distribution of this transmission, or taking any action based on it, is > strictly prohibited. > > > -----Original Message----- > > From: Wilson, Eric [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 13, 2003 10:51 AM > > To: [EMAIL PROTECTED] > > Subject: Re: adding DASD post install > > > > > > Mark; > > > > Yes, believe I am IPL'ing from 200. The kernel appears to see > > my dasd line > > change. I've tried several verations. The parmfile updated > > by zipl ends up > > being /boot/parmfile.1 in this case. > > > > My dmesg: > > # dmesg > > .... > > We are running under VM (64 bit mode) > > This machine has no PFIX support > > On node 0 totalpages: 32768 > > zone(0): 32768 pages. > > zone(1): 0 pages. > > zone(2): 0 pages. > > Kernel command line: > > dasd=0200,0201,0202,0203,0204,0205,0206,0207,0208,0209 root > > =LABEL=/ > > > > Highest subchannel number detected (hex) : 0017 > > Calibrating delay loop... 601.29 BogoMIPS > > Memory: 120440k/131072k available (2087k kernel code, 0k > > reserved, 723k data, 32 > > 8k init) > > .... > > dasd: initializing... > > dasd: Registered successfully to major no 94 > > dasd: initialization finished > > dasd(eckd): ECKD discipline initializing > > dasd: <devno: 0200> Add lowmem page :0000000007d4a000 > > dasd: <devno: 0200> Add lowmem page :0000000007d49000 > > dasd(eckd): /dev/dasda ( 94: 0),[EMAIL PROTECTED]: > > 3390/0A(CU:3990/04) Cyl:200 Head:15 S > > ec:224 > > dasd(eckd): /dev/dasda ( 94: 0),[EMAIL PROTECTED]: > > 3390/0A(CU:3990/04): Configuration da > > ta read > > dasd: No request IRQ > > dasd: <devno: 0201> Add lowmem page :0000000007d41000 > > dasd: <devno: 0201> Add lowmem page :0000000007d40000 > > dasd(eckd): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: > > 3390/0A(CU:3990/04) Cyl:3338 Head:15 > > Sec:224 > > dasd(eckd): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: > > 3390/0A(CU:3990/04): Configuration da > > ta read > > dasd: No request IRQ > > dasd: waiting for responses... > > dasd(eckd): /dev/dasda ( 94: 0),[EMAIL PROTECTED]: (4kB blks): > > 144000kB at 48kB/trk comp > > atible disk layout > > dasd: No request IRQ > > dasd: <devno: 0202> Add lowmem page :0000000007d36000 > > dasd: <devno: 0202> Add lowmem page :0000000007d35000 > > dasd(eckd): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: > > 3390/0A(CU:3990/04) Cyl:3338 Head:15 > > Sec:224 > > dasd(eckd): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: > > 3390/0A(CU:3990/04): Configuration da > > ta read > > dasd: No request IRQ > > dasd: waiting for responses... > > dasd(eckd): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: (4kB blks): > > 2403360kB at 48kB/trk com > > patible disk layout > > dasd: No request IRQ > > dasd: waiting for responses... > > dasd(eckd): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: (4kB blks): > > 2403360kB at 48kB/trk com > > patible disk layout > > Partition check: > > dasda:VOL1/ 0X0200: dasda1 > > dasdb:VOL1/ 0X0201: dasdb1 > > dasdc:VOL1/ 0X0202: dasdc1 > > > > but now more disk addrs.... > > > > > > > > > > Cheers; > > > > E! > > > > ----------------- > > Eric Wilson > > > > > > > > -----Original Message----- > > From: Post, Mark K [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 13, 2003 10:38 AM > > To: [EMAIL PROTECTED] > > Subject: Re: adding DASD post install > > > > > > Eric, > > > > Are you absolutely sure you are IPLing from device number 200? > > > > You're saying all the right things, that's for sure. I see > > you're IPLing > > with an initrd. Is your DASD support compiled as a module? > > If not, then > > the entries in /etc/modules.conf are ignored. > > > > When you re-IPL the system, what does the reported command > > line show? (It > > should be about the 8th line if you go back and do a "dmesg | less" > > command.) Are the new volumes in there? I'm guessing not, > > or you wouldn't > > be having this problem. > > > > Is this a VM or LPAR installation? > > > > > > Mark Post > > > > -----Original Message----- > > From: Wilson, Eric [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 13, 2003 9:48 AM > > To: [EMAIL PROTECTED] > > Subject: adding DASD post install > > > > > > All; > > > > Goofy question: How do I enable the server to see newly added DASD > > addresses > > post install. I'm sure this is something I've overlooked. > > Can anyone help > > re-gen my clue finder? > > > > hardware = z800 > > OS = RH v 7.2 > > > > > > [EMAIL PROTECTED] boot]# cat /proc/dasd/devices > > 0200(ECKD) at ( 94: 0) is dasda : active at blocksize: > > 4096, 36000 > > blocks, > > 140 MB > > 0201(ECKD) at ( 94: 4) is dasdb : active at blocksize: > > 4096, 600840 > > blocks, 2347 MB > > 0202(ECKD) at ( 94: 8) is dasdc : active at blocksize: > > 4096, 600840 > > blocks, 2347 MB > > > > [EMAIL PROTECTED] boot]# df > > Filesystem 1K-blocks Used Available Use% Mounted on > > /dev/dasdb1 2365444 894780 1350504 40% / > > /dev/dasda1 99072 12016 81944 13% /boot > > > > [EMAIL PROTECTED] boot]# swapon -s > > Filename Type Size Used > > Priority > > /dev/dasdc1 partition 261976 0 -1 > > > > > > I have added some additional DASD, and can make the kerne l see it by > > echoing > > the addresses directly to the kernel: > > > > > > [EMAIL PROTECTED] boot]# echo add range=203-206 >> /proc/dasd/devices > > > > [EMAIL PROTECTED] boot]# cat /proc/dasd/devices > > 0200(ECKD) at ( 94: 0) is dasda : active at blocksize: > > 4096, 36000 > > blocks, > > 140 MB > > 0201(ECKD) at ( 94: 4) is dasdb : active at blocksize: > > 4096, 600840 > > blocks, 2347 MB > > 0202(ECKD) at ( 94: 8) is dasdc : active at blocksize: > > 4096, 600840 > > blocks, 2347 MB > > 0203(ECKD) at ( 94: 12) is dasdd : active at blocksize: > > 4096, 600840 > > blocks, 2347 MB > > 0204(ECKD) at ( 94: 16) is dasde : active at blocksize: > > 4096, 600840 > > blocks, 2347 MB > > 0205(ECKD) at ( 94: 20) is dasdf : active at blocksize: > > 4096, 600840 > > blocks, 2347 MB > > 0206(ECKD) at ( 94: 24) is dasdg : active at blocksize: > > 4096, 600840 > > blocks, 2347 MB > > > > But ofcourse upon reboot the devices are no longer available > > to the system. > > > > I've tried adding the addresses to the modules.conf, and even to the > > zipl.conf > > (and rerun zipl) as below, to no avail. > > > > [EMAIL PROTECTED] root]# cat /etc/modules.conf > > options dasd_mod dasd=200-206 > > > > > > [EMAIL PROTECTED] root]# cat /etc/zipl.conf > > [defaultboot] > > default=linux > > target=/boot/ > > [linux] > > image=/boot/vmlinuz-2.4.20-1.1931.2.179.2.1.ent > > ramdisk=/boot/initrd-2.4.20-1.1931.2.179.2.1.ent.img > > parameters="root=LABEL=/ dasd=200-206" > > > > > > > > Cheers; > > > > E! > > > > ----------------- > > Eric Wilson > > IBM Certified Advanced Technical Expert > > RedHat Certified Engineer > > > > Anheuser-Busch Companies, Inc. > > One Busch Place > > 1CC-8 > > St. Louis, MO > > > > Voice: 314.589.7601 > > Cell: 314.486.8443 > > Facsimile 314.632.6901 > > email: [EMAIL PROTECTED] > > pager: [EMAIL PROTECTED] > > -- Karsten Hopp | Mail: [EMAIL PROTECTED] Red Hat Deutschland | Tel: +49-711-96437-0 Hauptstaetterstr.58 | Fax: +49-711-96437-111 D-70178 Stuttgart | http://www.redhat.de
