a highly peculiar lvm behavior

Let me start by saying I have a damaged (data-wise I think) disk.
I think the Part table is ok The BM comes up and OS2 loads and
appears to be ok. The  FAT32 partition with XP is damaged and
will not load - linkely the disk boot sector (not MBR) but this
is not the area of my question.

If I invoke LVM I get two messages that tell me that 2 disks
may be bad (data-wise) The LVM display shows 2 disks the second
of which is very small.

Howver I have only ONE disk attached to this system. Other
software show only one disk though with a bad FAT32.

ANy idea as to wht weakness LVM is showing?

On Wed, 9 Aug 2006 17:11:31 UTC, Leo Tick <tick@cs.nyu.edu> wrote:

> Let me start by saying I have a damaged (data-wise I think) disk.
> I think the Part table is ok The BM comes up and OS2 loads and
> appears to be ok. The  FAT32 partition with XP is damaged and
> will not load - linkely the disk boot sector (not MBR) but this
> is not the area of my question.
> 
> If I invoke LVM I get two messages that tell me that 2 disks
> may be bad (data-wise) The LVM display shows 2 disks the second
> of which is very small.
> 
> Howver I have only ONE disk attached to this system. Other
> software show only one disk though with a bad FAT32.
> 
> ANy idea as to wht weakness LVM is showing?
> Thanks

You will see that, if you have USB, and/or PCCard disk devices 
(perhaps other things too) defined in CONFIG.SYS, with no device 
mounted to use the driver slot. The default size is 96 MiB (the size 
of the old ZIP drives), and that is what you will see, if nothing else
has ever been mounted for that driver slot. LVM really should say that
the device is not mounted, but the message (Partiton table may be 
corrupt) is, technically correct, since there is no partition table, 
when there is no device to hold one.

I think there is a new LVM being worked on, to correct the wording, 
but that could take a while. Meanwhile, just ignore those things.

On the other hand, if LVM is complaining about your hard disk, you 
should be able to fix the problem. From what you say, it does sound 
like something messed with the MBR. Simply replacing the MBR may fix 
it. Use LVM /NEWMBR to create a new MBR. If that doesn't work, you may
need the services of DFSEE:

> http://www.dfsee.com/dfsee/

Hope this helps...
-- 
From the eComStation 1.2 of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)