TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Paul Edwards
from: Rod Speed
date: 1996-05-18 20:52:08
subject: help!

You basically leave out crucial information. You havent actually said
explicitly what you have done about LBA support with the new drive.

PE> 1. I've managed to install Warp.  Not really sure
PE> why it is happy to install now, and not before.

Basically the usual problem with OS/2, bullet proof its never been.

PE> All I can see is that I've reorganized the disks, putting
PE> my corrupt disk as the slave of the second ide controller.

The big difference this time around is that presumably the new drive was
always with LBA enabled, FDISKed like that, and OS/2 installed like that.

PE> 2. Warp's fdisk gives me an error saying
PE> "disk 4's partition may be corrupt".

Presumably that valid given you stuffed it and lost the data.

PE> 3. Warp won't let me install on my new drive E, which
PE> is now the first logical partition on the 3rd IDE drive.
PE> The size of the partition is 1900 meg.

As usual, you dont say what 'wont let me' actually means,
whether it just refuses to do that, or trys to and fails.

I'd remove the original 2.5GB drive and see if that makes
any difference. You may well be able to add it again once
you get things installed properly on the new 2.5GB drive.

PE> 4. Warp won't let me format my G drive (3rd logical partition
PE> on the 3rd IDE) as FAT, giving me error message: The type of file
PE> system for the disk is HPFS. The new type of file system is FAT.
PE> SYS1274: The size of the requested partition exceeds 2,048MB or is
PE> beyond cylinder 1023 of your disk.

It can be a bit brain dead about that and that can vary.

PE> The second part is correct, but I thought LBA solved these problems?

Well, LBA does allow a FAT partition outside the 1023
cylinder limit, coz obvious DOS is happy to. Yes, OS/2
is having a short circuit between its ears there.

PE> 5. Warp is now showing my 4th drive as being partitioned
PE> as 10 (freespace), 500, 1897, 3 (freespace), 33 I could
PE> have sworn I set it up as 10 (freespace), 500, 1900, 33

Thats what I meant about using the same geometry numbers as you had
with the old motherboard. Looks like either you didnt, or your stuffing
around with LBA has caused a glitch on a drive which was initially
installed without LBA enabled, and things are now rather stuffed.

PE> Should I attempt to delete the 1897 and create a 1900
PE> partition instead, to see if that gets my data back?

You havent said how crucial the data is, presumably very
if you bought a new drive. You certainly dont want to go
thrashing around like that if the data is vital.

While it looks likely you have stuffed the data by CHKDSKing
that partition, the safest thing to try is to put it back with
the old motherboard with the old drive data in the cmos. And
DONT write to the damned thing, try to see whats visible.

PE> I am beginning to think that something has gone seriously wrong with LBA!

Nope, just you thrashing around. If the data was that vital, you should
have carefully checked that it was still looking good before you started
to write anything to that drive at all, coz, like I said, the act of
enabling LBA on a drive which has been FDISKed etc without that enabled
may well make the data invisible etc. Its probably to late for it now
tho, particularly the CHKDSK you did on it in that state.
@EOT:

---
* Origin: afswlw rjfilepwq (3:711/934.2)
SEEN-BY: 640/305 711/934
@PATH: 711/934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.