Edmund,

  Thanks for replying to my inquiry.

We are running kernel 2.4.19-3 on an LPAR with no VM.  I issued the
commands you had suggested after determining that we are on kernel 2.4

        echo set 2734-273d on > /proc/dasd/devices

I then reissued the DASD LIST command. Showing the following...

273e(ECKD) at ( 94:  0) is dasda      : active at blocksize: 4096,
601020 blocks, 2347 MB
273f(ECKD) at ( 94:  4) is dasdb      : active at blocksize: 4096,
601020 blocks, 2347 MB
283e(ECKD) at ( 94:  8) is dasdc      : active at blocksize: 4096,
601020 blocks, 2347 MB
283f(ECKD) at ( 94: 12) is dasdd      : active at blocksize: 4096,
601020 blocks, 2347 MB
2734(none) at ( 94: 16) is dasde      : unknown
2735(none) at ( 94: 20) is dasdf      : unknown
2736(none) at ( 94: 24) is dasdg      : unknown
2737(none) at ( 94: 28) is dasdh      : unknown
2738(none) at ( 94: 32) is dasdi      : unknown
2739(none) at ( 94: 36) is dasdj      : unknown
273a(none) at ( 94: 40) is dasdk      : unknown
273b(none) at ( 94: 44) is dasdl      : unknown
273c(none) at ( 94: 48) is dasdm      : unknown
273d(none) at ( 94: 52) is dasdn      : unknown
2834(none) at ( 94: 56) is dasdo      : unknown
2835(none) at ( 94: 60) is dasdp      : unknown
2836(none) at ( 94: 64) is dasdq      : unknown
2837(none) at ( 94: 68) is dasdr      : unknown
2838(none) at ( 94: 72) is dasds      : unknown
2839(none) at ( 94: 76) is dasdt      : unknown
283a(none) at ( 94: 80) is dasdu      : unknown
283b(none) at ( 94: 84) is dasdv      : unknown
283c(none) at ( 94: 88) is dasdw      : unknown
283d(none) at ( 94: 92) is dasdx      : unknown

So I looked in /var/log/warn and found the following message again 
        Feb 22 13:02:34 mflinux kernel: dasd: No device registered as
(94:16)


Kind regards,

Lance Longstreth
Bandag Inc
1-(563)-262-2927
[EMAIL PROTECTED]


-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Edmund R. MacKenty
Sent: Wednesday, February 22, 2006 12:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: dasdfmt: Unable to open device /dev/dasde: No such device

On Wednesday 22 February 2006 12:21, Longstreth, Lance wrote:
>In need of help formating some DASD..We have some DASD we want to 
>format to be used by LVM. But when we try to format the volumes it does

>recognize them. ...

The VM guest has the DASD linked to it, but Linux doesn't know anything
about them.  You need to tell Linux to put them online.  That "unknown"
status for all your new DASD means that the dasd_mod device driver knows
that something was linked at that virtual device number at one time, but
it doesn't know anything about it anymore.  You need to get it to say
"active" there.

How this is done depends on which kernel you're running.  For 2.4, I
know it off the top of my head:

    echo set 2734-273d on > /proc/dasd/devices
    echo set 2834-283d on > /proc/dasd/devices

You can specify individual virtual device numbers or whatever ranges you
want.
After that, you should see that they are in the "active" state.

For 2.6 kernels, you have to have an entry for each DASD device in the
/etc/sysconfig/hardware directory.  These can be copies of the files
that are already there for other DASD devices.  You then use the hwup
command to put the DASD online.  So you could, for example, do this:

    cd /etc/sysconfig/hardware
    copy dasd-bus-ccw-0.0.273e dasd-bus-ccw-0.0.2734
    hwup dasd-bus-ccw-0.0.2734

And again check that your DASD is in the "active" state.  Once the DASD
is active, then you can run dasdfmt on it.
        - MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software, Inc.
Newton, MA USA

>
>1. we have ran the zipl
>2. shutdown the LINUX LPAR
>3. did an inactivate using the HMC to refresh 4. Reactivated LPAR using

>HMC 5. After system was up logon on an did a DASD LIST to see if the 
>new ones were showing. Yes they were from address 2735 on down on the 
>list
>
>273e(ECKD) at ( 94:  0) is dasda      : active at blocksize: 4096,
>601020 blocks, 2347 MB
>273f(ECKD) at ( 94:  4) is dasdb      : active at blocksize: 4096,
>601020 blocks, 2347 MB
>283e(ECKD) at ( 94:  8) is dasdc      : active at blocksize: 4096,
>601020 blocks, 2347 MB
>283f(ECKD) at ( 94: 12) is dasdd      : active at blocksize: 4096,
>601020 blocks, 2347 MB
>2734(none) at ( 94: 16) is dasde      : unknown
>2735(none) at ( 94: 20) is dasdf      : unknown
>2736(none) at ( 94: 24) is dasdg      : unknown
>2737(none) at ( 94: 28) is dasdh      : unknown
>2738(none) at ( 94: 32) is dasdi      : unknown
>2739(none) at ( 94: 36) is dasdj      : unknown
>273a(none) at ( 94: 40) is dasdk      : unknown
>273b(none) at ( 94: 44) is dasdl      : unknown
>273c(none) at ( 94: 48) is dasdm      : unknown
>273d(none) at ( 94: 52) is dasdn      : unknown
>2834(none) at ( 94: 56) is dasdo      : unknown
>2835(none) at ( 94: 60) is dasdp      : unknown
>2836(none) at ( 94: 64) is dasdq      : unknown
>2837(none) at ( 94: 68) is dasdr      : unknown
>2838(none) at ( 94: 72) is dasds      : unknown
>2839(none) at ( 94: 76) is dasdt      : unknown
>283a(none) at ( 94: 80) is dasdu      : unknown
>283b(none) at ( 94: 84) is dasdv      : unknown
>283c(none) at ( 94: 88) is dasdw      : unknown
>283d(none) at ( 94: 92) is dasdx      : unknown
>
>6. Next tried to format the volumes with command - dasdfmt -f 
>/dev/dasdx -d cdl -l LNX024 -p -t
>
>mflinux:/var/log # dasdfmt -f /dev/dasde -d cdl -l LNX005 -p -t Please 
>enter the blocksize of the formatting [4096]:
>dasdfmt: Unable to open device /dev/dasde: No such device 
>mflinux:/var/log # dasdfmt: Unable to open device /dev/dasde: No such 
>device
>
>7. Display coming out of /var/log/warn
>
>Feb 22 11:08:18 mflinux kernel: dasd: No device registered as (94:16) 
>Feb 22 11:09:22 mflinux kernel: dasd: No device registered as (94:92) 
>Feb 22 11:12:21 mflinux inetd[535]: smtp/tcp: bind: Address already in 
>use Feb 22 11:15:48 mflinux kernel: dasd: No device registered as 
>(94:16)
>
>8. I have reverified that they are not being used by anyother system
>
>Can anyone give some guidance on this problem
>
>Lance Longstreth
>Bandag Inc
>GITS Infrastructure Security and Engineering zOS systems/Linux 
>[EMAIL PROTECTED]
>
>
>
>
>----------------------------------------------------------------------
>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

Reply via email to