The zipl did not need to be changed but we did zipl the zipl.conf twice
anyway. The minidiskdevices could be formatted (dasdfmt) without problem
but the create of the partition (fdasd) was accepted only after some
additional steps, such as zipl, "echo 1 > online" and reboot. I don't
remember what was the trigger to recognize the /dev/dasde1 and
/dev/dasdkk1 but in the end we managed to get the disks formatted and
ready to use.
 
Berry.


________________________________

        From: Quay, Jonathan (IHG) [mailto:[email protected]] 
        Sent: dinsdag 23 februari 2010 13:29
        To: van Sleeuwen, Berry
        Subject: FW: Devices disappeared from /dev
        
        
        Did you remember to the virtual devices correpsonding to dasde
and dasdkk in zipl.conf and rerun zipl?

________________________________

        From: Linux on 390 Port on behalf of van Sleeuwen, Berry
        Sent: Tue 2/23/2010 5:52 AM
        To: [email protected]
        Subject: Devices disappeared from /dev
        
        

        Hello listers,
        
        Last weekend we moved an SLES9 machine to our backup VM. After
reboot of
        the guest the guest failed the filesystemcheck. After some
research we
        found that the required entries in de /dev directories were
missing.
        
        /home and /usr have been moved to a different dasd quite some
time ago.
        /home is located on /dev/dasde1 and /usr is placed on
/dev/dasdkk1. Now,
        after the reboot, /dev contained /dev/dasde, /dev/dasde2,
/dev/dasde3
        and /dev/dasdkk. Note that both dasde1 and dasdkk1 are missing.
When the
        fsck tries to check /dev/dasde1 and /dev/dasdkk1, as stated in
the
        /etc/fstab, it fails because the devices are not in the /dev
directory.
        
        In the end we have formatted and recreated the disks so we were
able to
        repair this. But it does leave us with a bad feeling as to what
and/or
        why this had happend.
        
        Why could these entries have been removed from the /dev
directory? They
        were present before shutdown, or at least I guess they were
because
        obviously the guest did have /home and /usr available before.
        
        I found a message that stated that udev should create the
devices but
        would that also be the case here? And if so, why didn't it?
        
        Met vriendelijke groet/With kind regards,
        Berry van Sleeuwen
        Flight Forum 3000 5657 EW Eindhoven
        
        ( +31 (0)6 22564276
        
                       
        
        
        
        Atos Origin <http://www.atosorigin.com/>
        
        MO CF SC Mainframe Services
        
        
        
        
        
        
----------------------------------------------------------------------
        For LINUX-390 subscribe / signoff / archive access instructions,
        send email to [email protected] with the message: INFO
LINUX-390 or visit
        http://www.marist.edu/htbin/wlvindex?LINUX-390
        


----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
ÿþ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 
Origin 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 Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
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 Origin 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 Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to