That's not the problem, it is already there. Linux doesn't know what to
do with it cause it doesn't have the correct label format.
Instead of thinking its an eckd as in dasd[eckd] it comes back with
dasd[diag]
David Kreuter <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
09/09/2004 01:15 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: dasd isn't recognized
did you add the virtual address dynamically?
echo add device range=0123 | >> /proc/dasd/devices
then you can modify zipl.conf to add it permanently
David
-----Original Message-----
From: Linux on 390 Port on behalf of Steve Gentry
Sent: Thu 9/9/2004 2:03 PM
To: [EMAIL PROTECTED]
Subject: dasd isn't recognized
I had this happen quite a while ago and thought I had written notes on it.
Alas, I can't find them.
I can't get linux to recognize a new disk that I've add. Lets call it
dasdc I'm pretty sure it has something to do with the volume label or
something like that.
It also seems that it has to be formatted in a CDL format or recognized as
CDL. I just can't remember.
So could someone help?
Thanks,
Steve G.
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
