Have you manually checked to see if the DASD is online? i.e.  QUERY DASD  volid   or  QUERY dasd_addr
If they are not online, check your SYSTEM CONFIG file to be sure they either are not coded as OFFLINE  or use an ONLINE statement to put them on line at IPL.
If they are online check again to be sure VOLID names are correct for those DASD in question vs. the user directory entry or however you maintain the user directory.
You make no mention if you have multiple LPARS.  I know DASD can be shared across LPARS but I am not versed in that subject.
Steve

-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.M...] On Behalf Of van Sleeuwen, Berry
Sent: Tuesday, February 07, 2012 10:01 AM
To: LINUX-390@VM.M...
Subject: Missing DASD after reboot

Hi Listers,

After a reboot not all dasd is online and not all dasd is available for Oracle. I guess it has to do with udev but I can't find the logic behind it.

We run a guest on SUSE 11 SP1, Oracle 11. Minidisks 213-285 are in use for Oracle ASM.

The udev rule for disk 213 looks like:
# Configure DASD device at 0.0.0213 (ECKD mode) ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.0213", IMPORT{program}="collect 0.0.0213 %k 0.0.0213 dasd-eckd"
ACTION=="add", SUBSYSTEM=="drivers", KERNEL=="dasd-eckd", IMPORT{program}="collect 0.0.0213 %k 0.0.0213 dasd-eckd"
ACTION=="add", ENV{COLLECT_0.0.0213}=="0", ATTR{[ccw/0.0.0213]online}="1", GROUP="oinstall", OWNER="oracle"

The remaining (214-285) look like:
# Configure DASD device at 0.0.0214 (ECKD mode) ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.0214", IMPORT{program}="collect 0.0.0214 %k 0.0.0214 dasd-eckd"
ACTION=="add", SUBSYSTEM=="drivers", KERNEL=="dasd-eckd", IMPORT{program}="collect 0.0.0214 %k 0.0.0214 dasd-eckd"
ACTION=="add", ENV{COLLECT_0.0.0214}=="0", ATTR{[ccw/0.0.0214]online}="1"

After reboot all DASD is online except 213.

Next, all disk partitions are owner root except 213, oracle apparently can't use these devices.

In /dev/ the owner for the dasd is changed. But not quite the way I expected it. A group of devices is still owned by root. A group of devices is owned by root while its partitions are owned by oracle and there is a group of devices where both device and partition is owned by oracle. Even so, Oracle now is able to start.

So now I'm lost. I can set 213 online using chccwdev but why wasn't it activated during boot? And why the strange behavior in Oracle? I would expect to need either all devices for root or all devices for Oracle. Any thoughts on this? Is there a manual I can find the udev behavior, especially related to the device ownership during boot?

Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven
* +31 (0)6 22564276
[Description: atos]              [Description: cid:325312309@02022011-28C8]






Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien de integriteit van het bericht niet veilig gesteld is middels verzending via internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos toegezonden.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Nederland B.V. group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to LISTSERV@VM.M... with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.M... with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/