Check the archives, Mark posted a number of responses to this around 2/11

Ken Dreger




At 08:48 AM 6/13/2003 -0500, Wilson, Eric wrote:
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]

Kenneth G. Dreger


Sr. Systems Programmer

z/OS Systems & support,
z/OS & OS390 Capacity & Performance reporting,
Linux 390 systems support, Web page consulting,
Systems Security
Member Southern California HTCIA
Personal Home page:
http://www.ken.dreger.com
Contact: [EMAIL PROTECTED]

Reply via email to