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 for
: 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
som
ort <[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
t
I figured it out. I needed mknod, but wasn't using the correct syntax for
the command.
Steve
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
t;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 09, 2004 8:27 PM
Subject: Re: dasd isn't recognized
> 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.
> In
