mount external boot disc for reading - urgent!

[V. Nyga]

Hi,

I've a old hp 9000/735 and my j200 crashed.
How can I mount the external boot disc of my j200 at the 735?
The boot disc has a LVM file system.

After connecting it to the 735 I see it as unused.

What do I have to do now??

Volkmar

[Pete Randall]

vgimport?

mkdir /dev/vg01
mknod /dev/vg01/group c64 0x010000
vgimport -s -m /tmp/vg01map /dev/vg01
vgchange -a y /dev/vg01

mount the lvols


Pete

[Raj D.]

Hi Volkmar ,

Once you connected the disk and found in ioscan , go ahead.

# ioscan -fnC disk [ you should found as CLAIMED ]

# ls -l /dev/*/group
# cd /dev/
# mkdir vgxx
# cd vgxx
# mknod group c 64 0x050000 [ make sure this no ( 0x050000) is unique ]

# vgimport vgxx /dev/dsk.c?t?d?
# vgchange -a y vgxx

Mount the filesystems now you want.
# mkdir /mountpoint
# mount /dev/vgxx/lvolx /mountpoint

Cheers,
Raj.

[TwoProc]

You can run vgscan on it to bring it in.
"man vgscan" to get it.
"vgscan -apv" would do it in pseudo mode and tell you what it would do, without actually doing anything (the "p" is pseudo mode).

You can copy your /etc/lvmtab to /etc/lvmtab.bak before starting, just so you can put things back if you must.

[Pete Randall]

Oh - and I should say that if you don't have a map file (which you probably don't) - it's only necessary when your lvols had nonstandard names which, in this case, they probably didn't. The -s option probably won't work either, but you can supply the device file to the appropriate disk.


Pete

[Raj D.]

Volkmar ,

sorry to miss something,

vgxx is the vg you are going to name the new vg , on this disk. [ ex: vg02 , or vg05 ]

Cheers,
Raj.

[James R. Ferguson]

Hi Volkmar:

You need to create a unique volume group structure and 'vgimport' using that.

Construct a 'mapfile' to use with the 'vgimport' that looks like:

1 lvol1
2 lvol2
3 lvol3

This assumes that the minor numbers for lvol1-3 will parallel the numeric part of the logical volume names. Adjust according to your taste.

Create directories for mountpoints for the logical volumes; 'vgimport' using the mapfile created above and 'mount all'.

Regards!

...JRF...

[Devender Khatana]

Hi,

Suppose device file for disk is /dev/dsk/cxtydz.

See group device file of all existing VGs to find there minir number by

#ll /dev/vg*/group
crw-r----- 1 root sys 64 0x000000 Nov 17 2004 /dev/vg00/group

Select Next Unique number for your new VG.
#mkdir /dev/vgoldroot
#mknod /dev/vgoldroot/group c 64 0xNN0000

(Where NN is unique in all volume groups)

#vgimport /dev/vgoldroot /dev/dsk/cxtydz

#vgchange -a y /dev/vgoldroot

#ll /dev/vgoldroot (To confirm all device files located here)
#fstyp /dev/vgoldroot/lvol1
#mount -F hfs /dev/vgoldroot/lvol1 /oldstand
#fstyp /dev/vgoldroot/lvol3
#mount -F FS_TYPE /dev/vgoldroot/lvol3 /oldroot (FS_TYPE is the output of previous command)

HTH,
Devender

[V. Nyga]

Ups - something went wrong ...
After: /usr/sbin/vgimport vg01 /dev/dsk/c2t4d0

it said something like 'group contents 0 PVs, announced was 1'
vgimport: Quorum not existant or physicalic disc not existant.

/usr/sbin/vgchange -a y vg01 didn't work

With a new vgimport it says:
/dev/vg01 already exists in /etc/lvmtab

How can I clean lvmtab?

And JRF is right I don't have the mapfile, where should I create it?

V.

[Florian Heigl (new acc)]

"With a new vgimport it says:
/dev/vg01 already exists in /etc/lvmtab

How can I clean lvmtab?"

move it to /etc/lvmtab.old and run vgscan -v, i hope this should be enough.

[V. Nyga]

vgscan says:
volume belongs to a volume group
and something about
'Quorum not existant' ...??

[Devender Khatana]

Hi,

This means that a VG with name vg01 was allready there. Is some file system mounted from vg01? You could try importing with some other vgname.

Also to clean lvmtab for vg01.

#vgexport vg01

The quorum error indicates two disks were there in the vg in old system. You can by-pass this by activating vg like

#vgchange -a y -q n /dev/vg01

HTH,
Devender

[V. Nyga]

It still says:
volume group contains (includes?) 0 PVs

no LVM??

[Torsten.]

Hi Volkmar,

what is "vgscan -pv" is telling you? It should provide some LVM related information.

If the disk has no LVM structures (very unlikely), try to mount directly it with "-r" option.

[V. Nyga]

I have a copy of lvmtab:
^CM-h^B/dev/vg00
wK+M-H1>M-2M-"^A/dev/dsk/c0t4d0
/dev/vg00alt

wK+M-H1>M-2M-"^A/dev/dsk/c0t6d0

and of fstab:
/dev/vg00/lvol3 / hfs defaults 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1

so shouldn't it work?

Can I force to mount the (new) /dev/dsk/c2t4d0?

V.

[James R. Ferguson]

Hi (again) Volkmar:

First, you MUST choose a unique minor number for the /dev/group file that you are going to create. DO:

# ls -l /dev/vg*/group

Note the minor numbers that are in use and choose a number that is NOT listed. If you see "0x010000" and "0x02000" in addition to "0x000000", then minor numbers 0, 1 and 2 are already in use. You could use the value three (3) for NN below.

# mkdir /dev/vg03
# mknod /dev/vg03/group c 64 0x030000

Do NOT try to modify your current /etc/lvmtab. There should be nothing wrong with it.

I presume that your other system's external disk consisted of only one physical volume. If not, you need to attach it too just as you have already done for one disk. Make sure that you correctly specify the physical path for the disk you are going to import.

I probably unnecessarily compilicated things by suggesting that you could name your logical volumes by building your own mapfile. If your only purpose is to recover your data, then you may not care what names the logical volumes are given. A mapfile allows you the ability to choose non-default names. This is purely optional. You can build the mapfile in any directory you choose if you want to use it.

Either do:

# vgimport /dev/vgNN -m /tmp/vgNN.map /dev/dsk/cXtYdZ

...or:

# vgimport /dev/vgNN /dev/dsk/cXtYdZ
# vgchange -a y vgNN

Substitute the minor number of the 'group' file you built above for "NN", and use the correct pv_path for "cXtYdZ".

You can edit '/etc/fstab' with mountpoints for your logical volumes and 'mount all' or issue individual mount commands at the commandline for each logical volume mountpoint.

Again, you MUST use UNIQUE minor numbers regardless of what they were on the dead system.

Regards!

...JRF...

[V. Nyga]

@Torsten:

vgscan sagt:
Die folgenden physichen Datenträger gehören zu einer Datenträgergruppe.
Diese physikalischen Datenträger können nicht in eine Datenträgergruppe gestellt werden.
Mit dem Befehl "vgimport" kann der Prozeà abgeschlossen werden.
/dev/dsk/c2t4d0

[Raj D.]

Hi Volkmar ,

You can try importing with another name as vg01 is exists.

And after successful vgimport , before mounting you may need to run fsck on that lvol , if it give error while mounting.

Run a full fsck and then it can be mount successfully,

# fsck -F vxfs -o full /dev/vgXX/rlvolx
# mount -F vxfs /dev/vgXX/lvolx /mountpoint


hth ,
Raj.

[V. Nyga]

@ all:

vgscan says that there are no infos for the other two discs - /dev/dsk/c2tx0d includes no LVM information

Could a add disc in SAM destroy the old informations of the disc?

I tried to add this disc in SAM 'using the logical volume manger', but canceled it again.

??????

Can I mount it in another way?

V.

[V. Nyga]

If I hve no vg** now - then I can create a vg00?
and a vg00/group with 0x000000?

[V. Nyga]

Torsten - mount -r?

[V. Nyga]

vgimport says:
vgimport: Warnung: Datenträgergruppe enthält 0 PVs, angegeben wurde "1".

Verarbeitung wird fortgesetzt.
< process continues>
vgimport: Quorum nicht vorhanden oder physikalische Datenträger fehlen.

Warnung: Vielleicht existiert für diese Datenträgergruppe keine
Datensicherung auf diesem Rechner.
< maybe="" no="" backup="" for="" this="" volume="" group="" at="" this="" workstation="">
Denken Sie daran, nach dem Aktivieren der Datenträgergruppe eine Datensicherung
mit dem Befehl vgcfgbackup durchzuführen.


What's wrong?

[Torsten.]

Please tell us about the existing disks first. There are 2 disks belong to the old 735? Different vg's? Now you are going to connect the j200 boot disk. I can't imagine that this disk was configured without lvm. There is a vg with 3 lvols at least (stand, root, swap). Clean up all unused vg information, e.g. /dev/vg03/group ...
This may happen, if other people used the system for the same reason (connect disk, vgimport, copy some data, just disconnect without removing vg). Not that unusual.

Now create a new vg and import the disk. Any errors?

[Torsten.]

"mount -r" mounts a bootable disk (e.g. a bootable CD).
The "don't forget a vgcfgbackup" meens, there is no autobackup after this operation.
This is normal.
Is the "vgchange -a y vgxx" possible?

(I'm confused about the german OS messages)

[V. Nyga]

vgchange doesn't work:

vgchange: Warnung: Physikalischer Datenträger "/dev/dsk/c2t4d0" konnte nicht an Datenträgergruppe angekoppelt werden:
Cross-Gerät-Verweis

vgchange: Warnung: Physikalischer Datenträger "/dev/dsk/c2t4d0" konnte nicht abgefragt werden:
Der angegebene Pfad entspricht nicht dem an diese Datenträgergruppe angekoppelten physikalischen Datenträger

vgchange: Liste physikalischer Datenträger konnte nicht abgefragt werden.
vgchange: Datenträgergruppe "/dev/vg00" konnte nicht aktiviert werden:
Quorum nicht vorhanden oder physikalische Datenträger fehlen.

:-(