mount: disk image is incompatible with this system

[David Timberline]

I've just upgraded my backup server (N-class, rp7400) from HP-UX 11.0 to HP-UX 11.23. I'm trying this out on my backup server before tackling my production box (same specs). I did a cold-install and when the box came back up, the server didn't recognize the volume groups or logical volumes on the attached SC10. I've since gone through the steps for re-attaching at least one of the VGs:

mkdir /dev/vg01
mknod /dev/vg01/group c 64 0x020000
vgimport -v /dev/vg01 /dev/dsk/c3t0d0
vgchange -a y vg01

The output I got is:
Beginning the import process on Volume Group "/dev/vg01".
Logical volume "/dev/vg01/lvol1" has been successfully created
with lv number 1.
Logical volume "/dev/vg01/lvol2" has been successfully created
with lv number 2.
Volume group "/dev/vg01" has been successfully created.

So now I have those two lvols but when I try to mount the file systems that are on those lvols (using either the mount command or SAM), I get:
UX:vxfs mount: ERROR: V-3-21270: /dev/vg01/lvol1 disk image is incompatible with this system

What now? I'm a little befuddled. Before the upgrade, the names of the lvols were lvol01 and lvol02 -- is this enough to mess things up? Did I miss a step somewhere?

I saw that there was a HP-UX 11.11 patch that addressed a problem where this error was thrown, but nothing for 11.23.

I have two main questions are: are these lvols lost and gone forever and I need to re-setup this box and reinstall all the software? and, this situation isn't causing too much heartache since this is my backup server but is there a better way to handle this when I go to upgrade my production box?

Thanks in advance for any insight!

[Pete Randall]

I can answer your question about "Before the upgrade, the names of the lvols were lvol01 and lvol02 -- is this enough to mess things up?". The answer is no. Your lvol01 and lvol02 are non-standard names. When importing without a map file to account for non-standard names, the lvols get named by default: lvol1, lvol2, etc. This is perfectly normal and certainly not a cause for your predicament.


Pete

[Pete Randall]

Concerning your predicament itself, I have to wonder it this is related to the version of VxFS installed. The release notes state that both 3.5 and 4.1 are available and the user can choose which they want at install time. I'm thinking you ended up with 4.1 and your FS was originally 3.5.

See:

http://h18000.www1.hp.com/products/quickspecs/12079_div/12079_div.HTML#Overview


Pete

[Henk Geurts]

hi Dave.
just a guess but anyway:
you could try renameing the lvols to there original names "lvol01" and "lvol02":

mv /dev/vg01/lvol1 /dev/vg01/lvol01
mv /dev/vg01/lvol2 /dev/vg01/lvol02

check /etc/fstab for correct names.
mount -a ...

let me know..

[David Timberline]

Thanks for the quick replies.

Changing the names didn't solve the problem, but did change the error! Here's what I get now:

UX:vxfs mount: ERROR: V-3-20027: Cannot deduce character device name
for /dev/vg01/lvol01
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version

As to Pete's ideas:
Based on a swlist on my production server (which the backup mirrored), the box before upgrade was just using the OnlineJFS version of VxFS:
B3929BA B.11.00 HP OnLineJFS (Advanced VxFS)

After upgrade, I see this:
B3929EA 4.1.007 HP OnLineJFS (Server)
and this:
Base-VXFS 4.1.002 VERITAS File System Bundle 4.1 for HP-UX
Base-VXVM B.04.10.011 Base VERITAS Volume Manager Bundle 4.1 for HP-UX

So might it be that VxFS is not backwards compatible? That would make me very sad...

[IT_2007]

Did you take map file like this or not?

vgexport -m vg01.map -s -p -v vg01

did you tried to do vgimport like this?

vgimport -m vg01.map -s -v vg01

My question is why do you want to do vgimport with one physical disk name in the command? If you already taken map with vgexport then you don't need to specify physical volume name.

[David Timberline]

I didn't make a map file, having no clue that I would lose my disks after upgrade (yes, I am a newbie!) so I don't have one to work from for the vgimport.

[Pete Randall]

David,

Forget the map file - the names of the lvols have nothing to do with your problem.

Take a look at this thread, paying particular attention to the response from Chauhan Amit:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=999765


It looks like you need to run vxfsconvert.


Pete

[Yang Qin_1]

Hi, Dave

If you have a backup for that server b/4 you upgrade it you can restore /dev/vg## to /tmp/restore and then create a map file manually.

A map file looks like this:

1 lvol1
2 lvol2
3 lvol3
4 lvol4

the first number (1 2 3 4 ...) is taken from LV device file minor number last digit

the device files for above example is:

brw-r----- 1 root sys 64 0x02000(1) Feb 11 2006 lvol1
brw-r----- 1 root sys 64 0x02000(2) Feb 11 2006 lvol2
brw-r----- 1 root sys 64 0x02000(3) Feb 11 2006 lvol3
brw-r----- 1 root sys 64 0x02000(4) Feb 11 2006 lvol4

Normally, lvol10 will have a minor number 0x02000a and lvol11 0x02000b ... you should use 10, 11 but not a b in your map file.

Regards,
Yang

[Patrick Wallek]

When you renamed the LV did you remember to do both sets of device files (the lvol? and rlvol?)?

mv /dev/vg01/lvol1 /dev/vg01/lvol01
mv /dev/vg01/rlvol1 /dev/vg01/rlvol01
mv /dev/vg01/lvol2 /dev/vg01/lvol02
mv /dev/vg01/rlvol2 /dev/vg01/rlvol02

[David Timberline]

I hadn't renamed the rlvols. I just did and it changed the error back to the original "disk image incompatible" message. I will be exploring the vxfsconvert tomorrow and will report back the results. Thanks everyone.

[David Timberline]

OK, so I dug back into this and essentially had the same problem. Here's what I did:

1. Using my Ignite backup, went back to HP-UX 11.0. All the lvols and filesystems were there and available.

2. Created map files for all of the vgs.

3. Followed the instructions for a clean dismount for all of the vgs. That is:
# umount
# echo "8192B.p S" | fsdb -F vxfs /dev/vgXX/rlvolXX | grep clean
# fsck -F vxfs /dev/vg01/rlvolXX
# mount -F vxfs /dev/vgXX/lvolXX
# umount

4. Did the cold install again.

5. Recreated steps above (mkdir, mknod, vgimport, etc.)

6. Tried to mount the file system and got the same error (UX:vxfs mount: ERROR: V-3-21270: /dev/vg01/lvol1 disk image is incompatible with this system).

At this point, it is seeming like I will need to recreate all of my file systems. Not the end of the world but definitely feels like work...

Anyone have any additional insights?
Thanks in advance.