On Tue, Jul 18, 2006 at 09:04:35AM -0400, [EMAIL PROTECTED] wrote: > On Mon, Jul 17, 2006 at 05:21:42PM -0400, [EMAIL PROTECTED] wrote: > > On Mon, Jul 17, 2006 at 09:55:42AM -0700, Andrew Sackville-West wrote: > > > On Sun, Jul 16, 2006 at 09:26:33PM -0400, [EMAIL PROTECTED] wrote: > > > > A fresh install from the debian-testing-i386-netinst > > > > CD, donloaded 2006 07 15, on partition /dev/hda2 on my AMD64 box. > > > > It now dual-boots 32-bit or 64-bit etch. > > > > > > > > When I ask the 32-bit system to mount one of the LVs, it just > > > > complains that it can't find the special device /dev/VG2/LV1 > > > > The 64-bit system just goes ahead and mounts it. > > > > > > > > What packages/modules do I have to install/configure/modprobe or > > > > whatever to get the 32-bit system to recognise this stuff. > > > > > > just for kicks and grins, do you have lvm-common, lvm2 and lvm10 > > > installed? > > > > OK. I'm so embarassed to admit I hadn't.
:) > > It turns out that I also had to install package mdadm. > > I installed it so I could inspect the situation and maybe get a clue as > to why it did not work. But it turns out that just installing it made > the difference. > > I though it was to administer md systems -- create, adjust, and the > like. > > It turns out it is also used at boot time to recognise existing > ones. > > So the conclusion: > To get the existing software RAID to be recognised, install mdadm. > To get the existing LVM partitions on the RAID to be recognised, you > likely need lvm-common, lvm2 and lvm10. (Don't know for sure; I didn't > try uninstalling them to see it fail after I got it all working) fwiw, apt-cache says that lvm10 is for 2.2 and 2.4 kernels, and lvm2 is a total rewrite. likely you don't need lvm10 A > > -- hendrik > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
signature.asc
Description: Digital signature