[coLinux-devel] SOLVED: Problems with \Device\HarddiskVolumeX

[Clemmitt M. S. <sig...@bl...>]

Hi Sean,

Well, I was unusually dense on this problem, I'm afraid :^(  Short
version -- all is well.  There was no problem for me except the
end-user was screwing up!

I can access and mount raw devices like \Device\HarddiskVolume1, 
\Device\Harddisk0\Partition1, \Device\CdRom0, just fine.

What was causing my confusion?  Well, in the boot-time messages
coLinux/the Linux kernel prints, if a block_device entry refers
to a filesystem image (like a root filesystem image file or a swap
file), a line is printed out like this:

cobd0 size: 1048576 kb
cobd1 size: 262080 kb

*BUT* if a block_device refers to a raw partition or device,
there is no message printed.  I'm afraid I was dumb and thought
that these block_devices weren't "connecting" on boot-up.

I hope these hints will help others with raw device access :^)

On Fri, 19 Mar 2004, Sean Brook wrote:
> If you cannot boot from a native partion then
> there does seem to be an issue there (I have this problem)
> though I can boot ie it does in fact recognise the partition.

I'm afraid I can't help with this because I just have Windows
partitions on the workstation I'm using (at my office).  Might
the entry in the Wiki on TopologiLinux help?

> - I think I sussed the \Device\HarddiskVolume? convention. It
> also seems quite simple. Looking at logical disk manager
> literally count the partitions starting from 1 from the first 
> disk left to right and down through the second etc to the partition
> you want. All partitions should be included in the count.

I did a quick test that I believe confirms your analysis of how
\Device\HarddiskVolumeX names are assigned by the Logical Disk
Manager.  Well done :^)

					Clemmitt