Re: W4 Installation hangs at first boot-up from HD

In <AALZh.84026$2Q1.33449@xxxxxxxxxxxx>, on 05/01/2007
at 01:23 PM, Wolfi <publicalfa-ng@xxxxxxxx> said:

Hi,

Mmmh, why does FDisk/query on my W4 FP16+ system with kernel 14.104a then
still report "**BIOS:8032MB"?

Because fdisk does not know how to say anything else. Recall you are
working with fdisk which is designed for systems that can not boot beyond
the 1024 cylinder limit and that knows little about LVM or LBA addressing.

Here's the output of fdisk on the LVM-ed system I have in front of me.

[c:\showctrl\shl_wrk]oldfdisk /query /disk:1

Drive Name Partition Vtype FStype Status Start Size

1 0000003f : 1 0a 2 0 7
1 --> LVM C: 1 06 1 7 196
1 --> LVM D: 2 07 1 204 1168
1 --> LVM E: 2 07 1 1372 768
1 0042ec10 F: 2 07 0 2141 800
1 005becf6 : 2 00 0 2941 478
1 006ae0f3 G: 2 07 0 3420 494
1 007a5272 : 2 35 0 3914 6408
1 --> LVM H: 2 07 1 10323 6149
1 0202c773 K: 2 06 0 16472 1027
**BIOS:8032MB
**BIOS:8032MB
**BIOS:8032MB

The drive letters are what fdisk thinks they are, not what they are in
use, but that's to be expected.

The excess **BIOS:8032MB reports are for other drives. It appears fdisk
neglected to suppress them. This is a post-FP12 fdisk, so it has some
code that recognizes LVM data sectors, but it can not process them
correctly.

Here's what lvm has to say about this

[c:\showctrl\shl_wrk]lvm /query:bootable

Logical Volume Type Status File System Size (MB)
C: Vol C Compatibility Bootable FAT16 196
Disk Partition Size (MB) Disk Name
Part_C 196 D1 17GB
D: Vol D Compatibility Bootable HPFS 6149
Disk Partition Size (MB) Disk Name
Part D 6149 D1 17GB
E: Vol_E Compatibility Bootable HPFS 1168
Disk Partition Size (MB) Disk Name
Part E 1168 D1 17GB
F: Vol F New Compatibility Bootable HPFS 768
Disk Partition Size (MB) Disk Name
Part F Warp4 768 768 D1 17GB

It's a bit messy to correlate the fdisk and lvm volume letters, so here's
how dfsee sorts things out.

Id D A Dr Type Form Label info LVM vol,part B-cyl E-cyl Size MiB
-- - - -- ---- ---- ----------- ------------- ----- ----- --------
01 1 > P 0a BMGR I13X-aware ,[ BOOT MANAG 0 0 7.8
02 1 * C: P 06 FAT1 VOL_C Vol C,Part_C 1 25 196.1
03 1 * E: L 07 HPFS VOL_E Vol_E,Part E 26 174 1168.7
04 1 * F: L 07 HPFS VOL_F Vol F Ne,Part 175 272 768.7
05 1 K: L 07 HPFS VOL F 1_2MR Vol F 1.,Part 273 374 800.0
06 1 Free 375 435 478.4
06 1 L 07 HPFS VOL_F_OLD Vol F Ol,Part 436 498 494.1
07 1 H: L 35 JFS Vol_H Vol H,Part H 499 1315 6408.7
08 1 * D: L 07 HPFS VOL_D Vol D,Part D 1316 2099 6149.8
09 1 G: L 06 FAT SADUMP SADUMP,SADUMP 2100 2230 1027.5

Volume D: is well beyond the 8MB limit and boots just fine, regardless of
what fdisk says.

eCS/OS2 is a componet-based OS. You can mix and match things an usually
get away with it if you understand how the parts fit together.

As others have already said, to boot beyond you the 1024 cylinder limit,
you basically need the following

- a BIOS that supports the int13 extensions
- a master boot record that can detect the int13 extensions
- a boot manager that supports the int13 extensions
- a boot sector that that can detect the int13 extensions
- a boot loader that that can use the int13 extensions
- an .add driver that supports the int13 extensions

To boot a volume with lvm volume letters, you basicaaly need the following

- a bootmanager that understands lvm volume letters
- an os2ldr that understands lvm volume letters
- an os2dasd.dmd that os2lvm.dmd can attach to
- an os2dump that understands lvm or you may be unhappy
- an os2kernl that supports the KEE extensions

Steven

--
--------------------------------------------------------------------------------------------
Steven Levine <steve53@xxxxxxxxxxxxxxxxxxx> MR2/ICE 3.00 beta 04 #10183
eCS/Warp/DIY/14.103a_W4 www.scoug.com irc.ca.webbnet.info #scoug (Wed 7pm PST)
--------------------------------------------------------------------------------------------

.

Relevant Pages

  • Re: W4 Installation hangs at first boot-up from HD
    ... the 1024 cylinder limit and that knows little about LVM or LBA addressing. ... That this FDisk is capable of probing the BIOS for extINT13 ability and if available, removing the 1024cyl boot limitation.... ... Disk Partition Size Disk Name ...
    (comp.os.os2.bugs)
  • Re: Problem after converting FDisk Partitions to LVM
    ... For evaluation purposes I had created a few partitions with Warp4.0 and FDISK 14.082 on an empty test HDD and installed 3 instances of unfixed W4.0 on it. ... the other 2 in an extended partition still smaller than 8032MB. ... Then I added eCS2.0b3 to the extended one beyond the 8032MB limit, which offered to modify the existing W4.0 partitions to be usable with the LVM boot manager instead. ...
    (comp.os.os2.setup.storage)
  • Problem after converting FDisk Partitions to LVM
    ... Does the conversion of existing W4 FDisk partitions through LVM depend on a specific fix level on them or is it supposed to be successful on fresh vintage W4.0 installations as well? ... Then I added eCS2.0b3 to the extended one beyond the 8032MB limit, which offered to modify the existing W4.0 partitions to be usable with the LVM boot manager instead. ...
    (comp.os.os2.setup.storage)
  • Re: computer crash
    ... Dilbert Firestorm wrote: ... found that boot manager will not boot up. ... can't access the C: drive where OS/2 resides. ... does it sound like the LVM boot record got trashed? ...
    (comp.os.os2.misc)
  • Re: Handling boot viruses
    ... boot system with Windows 98SE installed, and if you can infect a system that ... has only Windows 2000 and/or Windows XP with NTFS installed via a methhod ... >>> Boot viruses is where AV software always did a lousy job. ... >> even have a chance at recognizing the results of fdisk /status to ensure ...
    (microsoft.public.security.virus)