ITB Internal SATA - Strange Boot Manager entry and Phantom drive

[Keith]

Just for info I recently purchased a 1TB SATA drive (Samsung 1TB SATA300
32MB, HD103UJ) as I was running out of disk space. I added it to my existing
eCS configuration running both Beta 3 and 6a and I can access data without
problems.

Total disk size reported is 953855

I have split the disk into two partitions first value is as reported by LVM,
second via Windows
Primary JFS 500,006M
(488,29GB)
NTFS 453,848M
(443.21GB)
Unallocated not shown by LVM (12MB)

However there are two strange things:

1. With Boot manager I have an extra entry showing

--> LVM Disk 2 D: Primary -24281M HFPS

I cannot find any method to remove this unwanted item from the boot menu.

2. A phantom drive is available. This is shown as a floppy drive in the
drives folder but is inaccessible. Selecting properties does not open the
notebook.

Via the graphical LVM (minilvm.exe) this drive M is not shown anywhere.
Using lvm.exe from the command line then drive M is shown as
[V1] *->M: Compatability 0(size)

I was thinking about resizing my partitions to see if this would make a
difference but before I do this I was wondering if anyone else had
experienced anything like this.

Keith

[Trevor Hemsley]

On Mon, 23 Feb 2009 09:40:06 UTC in comp.os.os2.setup.storage, "Keith"
<ktmering...@nospamgmail.com> wrote:

> 1. With Boot manager I have an extra entry showing
>
> --> LVM Disk 2 D: Primary -24281M HFPS

This one is probably your NTFS partition on the 2nd drive - looks like BM has a
bug that cannot handle partitions that size so displays a negative number.

> 2. A phantom drive is available

My guess is this one comes from usbmsd.add and is a reserved drive letter for a
USB floppy.

--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com

[Keith]

Hi Trevor,

yes the phantom drive was indeed a USB Floppy. Got rid of that with

BASEDEV=USBMSD.ADD /FLOPPIES:0

Strange I didn't notice it before I installed the new drive. I suppose the
trigger was the Boot manager message, and when I sav with minilcm a drive M:
I assummed it was connected.

Not sure you are right about the NTFS partiotion rhoug, as it is not
bootable, but then the JFS partition isn't either.
Via another news group I have heard that other people have had the LVM
message and the suggestion is to repartition using DFSEE etc.
I might try that although considdering the hassle I am not sure.

Thanks for your feedback
Keith

"Trevor Hemsley" <Trevor....@mytrousers.ntlworld.com> wrote in message
news:hKCgd4tKZm3DUB...@trevor2.dsl.pipex.com...