Daniel, This looks kind of like a new CHP and devices were added to the LPAR, and the equivalent of an MVS "config online" wasn't done. The reason I say that is that when you add devices this way, and they're not detected, you get the symptoms you're seeing. One of the few situations where this happens is when a brand new channel path is added to an LPAR without either doing a power-on reset, or configuring it online to the LPAR. If that is the case, you should be able to do that from the service console. If that isn't the case, then I would have to think about it some more.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Jarboe Sent: Monday, December 09, 2002 10:54 AM To: [EMAIL PROTECTED] Subject: Problems with adding dasd device (2.4 kernel) RH 7.2 in an LPAR (2.4.9-38tape) Does anyone see the mistake here? # echo -n "add device range=7675-7677 ">>/proc/dasd/devices (/var/log/messages says: kernel: dasd:/proc/dasd/devices: 'add device range=7675-7677 ') # cat /proc/dasd/devices 6b40(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 601020 blocks, 2347 MB 6b41(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 601020 blocks, 2347 MB 6b42(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 601020 blocks, 2347 MB 6b43(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc0(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc1(ECKD) at ( 94: 20) is dasdf : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc2(ECKD) at ( 94: 24) is dasdg : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc3(ECKD) at ( 94: 28) is dasdh : active at blocksize: 4096, 601020 blocks, 2347 MB 7675(none) at ( 94: 32) is dasdi : unknown 7676(none) at ( 94: 36) is dasdj : unknown 7677(none) at ( 94: 40) is dasdk : unknown # dasdfmt --label=LNX001 --device=/dev/dasdi Please enter the blocksize of the formatting [4096]: dasdfmt: error opening device /dev/dasdi: No such device (/var/log/messages says: kernel: dasd:No device registered as (94:32)) # ls -l /dev/dasdi brw-rw---- 1 root disk 94, 32 Sep 23 2001 /dev/dasdi # echo -n "set device range=7675-7677 on ">>/proc/dasd/devices # cat /proc/dasd/devices 6b40(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 601020 blocks, 2347 MB 6b41(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 601020 blocks, 2347 MB 6b42(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 601020 blocks, 2347 MB 6b43(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc0(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc1(ECKD) at ( 94: 20) is dasdf : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc2(ECKD) at ( 94: 24) is dasdg : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc3(ECKD) at ( 94: 28) is dasdh : active at blocksize: 4096, 601020 blocks, 2347 MB 7675(none) at ( 94: 32) is dasdi : unknown 7676(none) at ( 94: 36) is dasdj : unknown 7677(none) at ( 94: 40) is dasdk : unknown For more background info, the new address range is carved up as Mod-9's. I plan on moving from the 8 volumes to the 3. What does it take to "register" these devices? Thanks ~ Daniel ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
