If it looks like the others when you do a  'q v dasd'  then it is a minidisk.

Most likely, it is a "near full pack" minidisk, which means it starts
at cylinder 1 (and z/VM owns cylinder 0).  Attaching it directly means
that the guest sees the whole disk, including cyl 0.  Linux will not
know what to do with that.

Attach the disk to SYSTEM.  Then  'link owner oaddr myaddr mr'  where
"owner"  is the virtual machine which owns the minidisk, "oaddr" is
the address where it exists on the owning virtual machine, and
"myaddr" is where you want it linked/attached/connected on the virtual
machine where you want to fix it.  (Pick any random address for
"myaddr".)

Then boot Linux, bring the disk online, and try fixing things.

-- R;   <><





On Mon, Aug 30, 2010 at 10:51, Daniel Tate <[email protected]> wrote:
> Right on both accounts.   I am unsure if it is a minidisk - it
> normally shows when i do a q v dasd just like all the others (minus
> VDSK) in the original post (CYL addressing), if that tells you
> anything
>
>
> On Mon, Aug 30, 2010 at 9:43 AM, Richard Troth <[email protected]> wrote:
>> You attached the disk (the whole volume) to that other guest.  But ...
>> the guest which owns it ... is it a minidisk?  If so, then you want to
>> 'link' it instead of 'attach' it.
>>
>> That's just for starters.  Forgive me if you already know this, but it
>> sounds like  #1  you are in a minor crisis and  #2  you are new to
>> z/VM.  We'll gladly help, but it will take time to get you up to
>> speed.
>>
>> -- R;   <><
>>
>>
>>
>>
>>
>> On Mon, Aug 30, 2010 at 10:38, Daniel Tate <[email protected]> wrote:
>>> I have a user with a corrupt filesystem.  in attempting to move the
>>> DASD Containing the root disks, i detached the old disk:
>>>
>>> 00: DASD 9F80 VM6LX9
>>>
>>> I need to reattach it to the original machine, but i also need to
>>> attach it to another guest, mount it and fix the corrupted files where
>>> it can boot.
>>>
>>> When i attempt to mount it to another guest, i get (at the bottom):
>>>
>>> DASD 019E 3390 VM6RES R/O        250 CYL ON DASD  9F84 SUBCHANNEL = 000D
>>> DASD 0300 9336 (VDSK) R/W     524288 BLK ON DASD  VDSK SUBCHANNEL = 0010
>>> DASD 0301 9336 (VDSK) R/W    1048576 BLK ON DASD  VDSK SUBCHANNEL = 0011
>>> DASD 0592 3390 VM6RES R/O         70 CYL ON DASD  9F84 SUBCHANNEL = 000F
>>> DASD 9F80 ON DASD  9F80 R/W VM6LX9 SUBCHANNEL = 0012
>>>
>>> Which isn't letting me see the disk; it doesnt even look like the
>>> others.   Maybe a link was the way to go with this?  Can someone help
>>> me get this back straight?
>>>
>>
>

Reply via email to