Re: creating volumes

Eeva Häkkinen wrote:
> I need help with some simple questions I cannot seem to sort out by
> googling (lots of miscellaneous and contradictory info out there),
> neither have I found any proper docs for LVM (or eCS). With the help
> of this newsgroup, DFSee and Jan I have got far enough with eCS
> installation to get my disk accepted (disk 2 and 3 still have corrupted
> partition tables, but that is not an issue at the moment). Now
> installation process wants me to give it a volume to install on,
> but "Create new volume" complains about having no free space to
create
> the volume on. Well, it is right, I've partitioned my OS disk already
> with DFSee like this:
> 
> 10 G   Pri  NTFS   Win XP (pre-installed)
> 6 G    Pri  etx3   Linux \ (still to be installed)
> 1.5 G  Log  etx3   Linux swap
> 6 G    Log  etx3   Linux \home
> 6.5 G  Log  FAT32  shared between OSs
> 8 G    Log  HPFS   for eCS
> 7 M    Pri  BootManager (already created, good or bad idea?)
> 
> which is shown in the physical view, so there is no "free space",
but
> I have read in several places that I should be able to create a volume
> in a partition. True or False? If true, how do you do it?
> 
> A simplistic solution would be to delete eCS partition and create a
> logical volume in its space, but I'd rather do it right the first time.
> Should I also create a volume for the preceding FAT32 for eCS to be
> able to use it? (I suppose eCS has FAT32 drivers?). Does everything
> eCS needs to use be within a volume? I understood BootManager should NOT
> be within a volume, True or False ? If false, should I put the two last
> partitions into the same volume? If yes, should I first create
> the volume and then the partitions?
> 
> As I am only trying to update my Warp 4.0 to this century, I'd rather
> stay clear of LVM, but it seems I have to live with. The documentation
> that comes with eCS is real scanty, at least compared to what OS/2 used
> to have.
> 
> Thank you so much for any and all advice!
> 
> Eeva
> 
> 
Hello Eeva;
	When I set up a computer with multiple operating systems, I use DFSee
to lay out the partition setup I am looking for and then I use the
operating system I am trying to install to change those partitions. If
I install Linux, I delete the swap partition I created with DFSee and
then recreate it with Linux's disk partitioner in advanced mode. I then
delete the ext3 partition I created with DFSee and then create it again
with Linux's disk partitioner and then let it finish the install.
	Then I install Windoze and let it use the partition that I created for
it with DFSee. If Windoze complains, you have to delete that partition
and recreate it with Windoze in the free space and then let Windoze
format it and finish the install.
	And finally I install eCS and again I use the LVM manager to go in and
delete the partition I created for it in DFSee, and then create a Volume
in the free space for install. I let the installation complete and then
I go back into LVM and set the Linux ext3 partition that I installed
Linux into as Startable. I then start Linux and use Lilo to add bootable
partitions. I do not install IBM's Bootmanager, because I have never
been able to get Linux to start with it. It does work fine for booting
to Win 2000 and XP and back to eCS with no problems.
	If you want to have partitions that you can share between Linux,
Windows and eCS then leave free space and use LVM to create a non
bootable volume and then use Linux to format it to FAT32 and all three
OS's can use it. Linux doesn't like the Windoze FAT32 format but Windoze
doesn't complain about the Linux FAT32 format and eCS with FAT32 support

On 03/21/08 04:25 pm Eeva Häkkinen wrote:

> I need help with some simple questions I cannot seem to sort out by
> googling (lots of miscellaneous and contradictory info out there),
> neither have I found any proper docs for LVM (or eCS). With the help
> of this newsgroup, DFSee and Jan I have got far enough with eCS
> installation to get my disk accepted (disk 2 and 3 still have corrupted
> partition tables, but that is not an issue at the moment). Now
> installation process wants me to give it a volume to install on,
> but "Create new volume" complains about having no free space to
create
> the volume on. Well, it is right, I've partitioned my OS disk already
> with DFSee like this:
> 
> 10 G   Pri  NTFS   Win XP (pre-installed)
> 6 G    Pri  etx3   Linux \ (still to be installed)
> 1.5 G  Log  etx3   Linux swap
> 6 G    Log  etx3   Linux \home
> 6.5 G  Log  FAT32  shared between OSs
> 8 G    Log  HPFS   for eCS
> 7 M    Pri  BootManager (already created, good or bad idea?)
> 
> which is shown in the physical view, so there is no "free space",
but
> I have read in several places that I should be able to create a volume
> in a partition. True or False? If true, how do you do it?
> 
> A simplistic solution would be to delete eCS partition and create a
> logical volume in its space, but I'd rather do it right the first time.
> Should I also create a volume for the preceding FAT32 for eCS to be
> able to use it? (I suppose eCS has FAT32 drivers?). Does everything
> eCS needs to use be within a volume? I understood BootManager should NOT 
> be within a volume, True or False ? If false, should I put the two last 
> partitions into the same volume? If yes, should I first create
> the volume and then the partitions?
> 
> As I am only trying to update my Warp 4.0 to this century, I'd rather
> stay clear of LVM, but it seems I have to live with. The documentation
> that comes with eCS is real scanty, at least compared to what OS/2 used
> to have.


You can create a volume within an existing partition, but I'm not sure 
whether that works if the partition is already formatted. But AFAIK, the 
installer can handle only free space or pre-existing volumes, so I would 
advise removing that partition you've allocated for eCS and let the 
installer create the volume. And you don't need anywhere near 8GB for 
eCS -- not for the OS itself: 1GB would be plenty, then allocate the 
remaining 7GB for eCS / OS/2 applications.

BTW, if it's one of the eCS 2.0 Release Candidates you're installing, 
there's an option to have a JFS-formatted boot partition.

eCS (2.0 anyway; I don't recall about earlier versions, but you should 
be able to download the driver) does have a FAT32 driver, but I'm pretty 
sure you need to select Advanced mode in the installer to choose to 
install that driver. I've rarely used it, and I don't recall any reports 
about its speed or reliability.

Boot Manager should be OK where you have it.

-=-

I need help with some simple questions I cannot seem to sort out by
googling (lots of miscellaneous and contradictory info out there),
neither have I found any proper docs for LVM (or eCS). With the help
of this newsgroup, DFSee and Jan I have got far enough with eCS
installation to get my disk accepted (disk 2 and 3 still have corrupted
partition tables, but that is not an issue at the moment). Now
installation process wants me to give it a volume to install on,
but "Create new volume" complains about having no free space to
create
the volume on. Well, it is right, I've partitioned my OS disk already
with DFSee like this:

10 G   Pri  NTFS   Win XP (pre-installed)
6 G    Pri  etx3   Linux \ (still to be installed)
1.5 G  Log  etx3   Linux swap
6 G    Log  etx3   Linux \home
6.5 G  Log  FAT32  shared between OSs
8 G    Log  HPFS   for eCS
7 M    Pri  BootManager (already created, good or bad idea?)

which is shown in the physical view, so there is no "free space", but
I have read in several places that I should be able to create a volume
in a partition. True or False? If true, how do you do it?

A simplistic solution would be to delete eCS partition and create a
logical volume in its space, but I'd rather do it right the first time.
Should I also create a volume for the preceding FAT32 for eCS to be
able to use it? (I suppose eCS has FAT32 drivers?). Does everything
eCS needs to use be within a volume? I understood BootManager should 
NOT be within a volume, True or False ? If false, should I put the two 
last partitions into the same volume? If yes, should I first create
the volume and then the partitions?

As I am only trying to update my Warp 4.0 to this century, I'd rather
stay clear of LVM, but it seems I have to live with. The documentation
that comes with eCS is real scanty, at least compared to what OS/2 used
to have.

Thank you so much for any and all advice!

Eeva

Eeva Häkkinen wrote:
> the volume on. Well, it is right, I've partitioned my OS disk already
> with DFSee like this:
> 
> 10 G   Pri  NTFS   Win XP (pre-installed)
> 6 G    Pri  etx3   Linux \ (still to be installed)
> 1.5 G  Log  etx3   Linux swap
> 6 G    Log  etx3   Linux \home
> 6.5 G  Log  FAT32  shared between OSs
> 8 G    Log  HPFS   for eCS
> 7 M    Pri  BootManager (already created, good or bad idea?)

Which eCS are you planning to install?  if it is RC4, I would suggest 
installing it on a 1.5G or 2G JFS partition and put your eCS 
applications on a separate partition (HPFS or JFS).

On Fri, 21 Mar 2008 20:25:03 UTC, eeva.hakkinen@gmail.com (Eeva 
Häkkinen) wrote:

> I need help with some simple questions I cannot seem to sort out by
> googling (lots of miscellaneous and contradictory info out there),
> neither have I found any proper docs for LVM (or eCS). With the help
> of this newsgroup, DFSee and Jan I have got far enough with eCS
> installation to get my disk accepted (disk 2 and 3 still have corrupted
> partition tables, but that is not an issue at the moment). Now
> installation process wants me to give it a volume to install on,
> but "Create new volume" complains about having no free space to
create
> the volume on. Well, it is right, I've partitioned my OS disk already
> with DFSee like this:
> 
> 10 G   Pri  NTFS   Win XP (pre-installed)
> 6 G    Pri  etx3   Linux \ (still to be installed)
> 1.5 G  Log  etx3   Linux swap
> 6 G    Log  etx3   Linux \home
> 6.5 G  Log  FAT32  shared between OSs
> 8 G    Log  HPFS   for eCS
> 7 M    Pri  BootManager (already created, good or bad idea?)

Here is one problem. Depending on the BIOS you may or even may not 
fall in problems because there is a primary partiton after the 
extended one.

I prefere the following:

Drive  type     size        comment
BM     Primary  1 zylinder  Bootmanager gets created on free space
                            on primary master
C:     Primary  > 8 GB      windows 9x/NT/W2K/XP/Vista....
/boot  Primary  100 MB      linux boot partiton e.g. GRUB
D:     extended any         Win Data/procs (optionally)
                            should be the first logical drive
                            because having this later on the disk
                            windows may destroy anything on the disk
e:     extended any         FAT32 shareable with other OSes (opt.)
f:     extended 2GB         OS2/eCS 1.x/eCS 2.x
                            only things installable from boot CD
g:     extended any         OS2/eCS data, procs
h:     extended any         ", optionally
/      extended any         linux root
/swap  extended 2 x RAM     linux swap

Uppercase driveletters are mandatory. Lower case driveletters are 
freely selectable because LVM lets you select them as you likes from a
list of available assignable letters.

Create all partitons using OS/2 fdisk when installing WARP or LVM when
eCS should run on this mashine.

With LVM (mandatory when eCS!) you would startup with logical view to 
create BM, swith over to physical view to create plain partitions in 
the order of the list above from top to bottom.

Then switch back to logical view to create volumes from existent 
partitons:
C:    must be of volume type compatible, bootable,
        else windows can't be installed
/boot must be of volume type compatible, bootable
e:    must be of volume type compatible, non bootable
        no need to have it bootable because there is no need to
        boot from. It must be LVMed else it will be invisible to eCS
f:    prior to eCS 2.0: only possible partiton types
               compatible, bootable
                    only filesystem allowed: HPFS
                       later extension impossibe
      starting with eCS 2.0:
               LVM, bootable
                    allows later to format to HPFS or JFS
g:,h: volume type LVM, not bootable; preferred
               allows you to format JFS or HPFS
               allows you later to extend the volumes 
               later on with more partitions on
               same or other physical drives
      optionally: volume type compatible
               impossible to format to JFS
               impossible to extend later on

You'll do not assign drive letters to /, /swap because there shluld no
need to access them from outside linux.

All the bootable volumes you create are magically attached to BM. 
After they are attached you can hide them fom eCS anyway because BM 
will list them anyway.

On linux install your job is use extended install to hinder linux to 
overwrite the bootsector but assign GRUB (or whatever linux 
bootmanager) you will select to the partiton named /boot above. It 
lefts to you to use linux fdisk to assign the right linux filesystem 
to the other linux partitions without touching the partiton size.

After you've installed the other OSes you'll have to boot from 
eCS(os2) install medium to awake BM again.

-- 
Tschau/Bye
Herbert

Visit http://www.ecomstation.de the home of german eComStation