I suppose that Partition type 0x7 is "compatibility Volume" and Partition type 0x35 is "LVM volume".
This is only relevant for JFS as only JFS can be either "compatibility" or "LVM" volume (everything else needs to be "compatibility"):
A "compatibility" and also a "LVM" JFS volume has a DLAT sector as the last sector of the first track of a partition. It saves stuff like disk Name, Partition Name and volume Name and drive letter.
In addition , a "LVM" JFS volume also has a "LVM signature area (BBR)" right inside the JFS Partition that contains "DriveLink" and "BadBlock" Information. Obviously, the DriveLink info is needed if an "LVM" volume spans multiple partitions, possibly across multiple physical drives. It will allow LVM to figure out what partitions on what drives belong to that one JFS volume.
"BadBlock" adds additional functionality to remember which sector/block was broken so that the filesystem can avoid using that sector/block. I don't think that is too valuable as modern hard disks do a bad sector remapping in HW, completely transparent to any SW.
Thinking about the fact that the DLAT sector saves the drive letter, I would say there is some cross-dependency between the BBR and the DLAT sector (the DLAT sector needs to list the very same drive letter for all partitions belonging to the same volume).
Taken from here:
http://www.dfsee.com/present/pcpartit/pcpartit.pdfThat said I'd suspect that there is some problem with the BBR and/or the dependency to the DLAT sector.
Why are you using "LVM" volumes anyway ? They cannot be booted from and they have no added benefit unless you intend to span a volume across multiple partitions/drives. With today's large disks (and "home user" requirements) I cannot see why you would want to do that.