I don't know for sure but I think it even was the 0213 that was created with dasd_configure. The others were created by copying, as it turned out, the wrong configfile. I didn't remember to take the owner data into account. Hence, one file contains the owner data (213) and the others do not contain the owner.

Unfortunately the problem was 'fixed' and the server is now in production. So it might be a problem to just test some options. May be we can get a window to test it.

Thanks for now.

Regards, Berry.

> -----Original Message-----
> From: Linux on 390 Port [mailto:LINUX-390@VM.M...] On Behalf Of
> Mark Post
> Sent: woensdag 8 februari 2012 16:59
> To: LINUX-390@VM.M...
> Subject: Re: Missing DASD after reboot
>
> >>> On 2/8/2012 at 03:18 AM, "van Sleeuwen, Berry"
> >>> <Berry.vanSleeuwen@atos...>
> wrote:
> > That was what I expected. So when I edit the 51-dasd.0.0.0213.rules
> > myself that would be basically the same as using dasd_configure.
>
> It would be, assuming you got it _exactly_ right, but clearly that doesn't
> seem to be the case.  Which is why the tool was written in the first place.
> Hand editing udev rules is fraught with potential for error.
>
> If using dasd_configure doesn't fix your problem, it's probably time to open
> up a service request with your service provider.
>
>
> Mark Post
>
> ----------------------------------------------------------------------
> 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/






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/