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]
