Re: Boot from USB PRM (Partitioned Removable Media ) failed after loading OS2LVM.DMD error: "OS/2 is unable to operate your hard disk or diskette drive"

Doug Bissett schrieb:

On Sun, 13 Aug 2006 11:32:08 UTC, Rainer Stroebel <RainerStroebel@xxxxxxxxxxx> wrote:



Doug Bissett schrieb:



On Fri, 11 Aug 2006 22:34:27 UTC, Rainer Stroebel <RainerStroebel@xxxxxxxxxxx> wrote:





Hardware: IBM ThinkPad T23

Software: OS/2 MCP2 with current fix pak and driver level


1. create a maintance partiton on my primary HDD with bootabel 4.3

minium features: only boot to cmd prompt, no wps support
USB Support basic and USBMSD.ADD

Test the system - system is in Boot Manager Menue

2. take a CF 1 GB Card and create a partiton on the medium

How to it: readme.tx from LVM fixpak / Update 14.105 (XR0L002)

3. the PRM partition has a drive letter of C: in my configuration

4. xcopy y:*.* c:*.* /H /O /T /S /E /R /V

y: is the drive letter of the mini maintance system

5. \os2\install\bootdisks\sysinstx c:

6. modify the config.sys

1. drive letter Y: --> C:

2. Change USB statments in sequence and parm according
booting from USB diskette
souce of instructions:
- usbbasic package: USBBASIC.txt 14.162
- mcp2: Technote.txt

3. create an alternative config.sys with the original usb from
primary min maint partiton config.sys

7. boot from PRM

7.1 Activate USB BIOS support

7.2 change the startup/ boot seq in bios

The PRM is an Harddrive for the bios

set the primary hdd to the T23 inacitce in boot menue

8. The system boots from the PRM

8.1 OS/2 blob

8.2 Warp logo

8.3 the loaded driver are recorded

8.4 .
.
os2dasd.dmd
os2lvm.dmd

8.5 full screen mode

meassages from usb driver

meassages form dani driver

9. Error "OS/2 is unable to operate your hard disk or diskette drive"


Ths error shows up with config.sys

- with modified usb sequence

- with "normal, standard usb" statements

- with or without dani driver preasent e.g no driver for the primary HDD


any ideas ????????? need help

Rainer








Hello Doug,

thanks for your comments and ideas.
Your message does help me a lot to do big step
in analyzing the problem and bring it to a solution.

Here are the details:



...snip...

Some things, that might help:

1) Use LVM, or DFSEE, to permanently attach a drive letter to your USB
drive. If you don't do that, the drive letter will, likely, change, when the USB drivers do get loaded, and LVM takes control. The result will be exactly what you describe.





The media (compacted flash card) is installed as PRM with a drive letter c: in the
LVM DLAT Table. I use a FAT file system to keep it simple.



I think you would still need to use LVM to fix the drive letter, so it
cannot change when the system switched from the INT13 support, to the full USB driver support. It may also be possible to NOT install any USB driver support, so the device keeps on using the INT13 support.



2) Let bootAble build the whole system on the USB drive for you. I have no idea why you would need to change what it builds. Doing a copy
of a system built on Y:, to C:, then expecting to simply change the drive letter in CONFIG.SYS, misses about 90% of what needs to be changed.





I built a maintenance system with bootable on HDD drive Y: to do test boot.
Again to keep it simple, the system a stripped down to minimum e.g.
no wps, no cdrom support, no udf, no hpfs - just boot to command prompt.

So the change from y: to C: in config.sys for the system on the PRM should do the
job.

Do I miss something?



I think so. There are still some INI entries, that could be pointing to the wrong place (Y:).




I am a bit confused about your statements about the ini files/entries.

The mini maintenance system for command prompt built by bootable does not
built/generate any os2.ini or os2sys.ini files in the /os2 directory.

My understanding is:

The ini files are needed by the WPS and application programms

( and the USBprint.sys driver )



3) I remember, at one time, that OS/2 could NOT be booted from a removable device (other than diskette). In the past, when I built bootable systems on a removable device (an ORB disk), I used the /!RMV
parameter on the DANIS506.ADD line. That parameter tells the Dani driver to report that the device is not removable. I don't know of any
similar parameter for the USB support drivers (if they need it).





Right, I agree - this is the key problem !

os2dasd.dmd and os2lvm.dmd does not support removables as boot devices!

For cdroms this is solved by the DANIBOOT.FLT by changing the device type
from removable to fixed disk ( and do I13 support reading from cdrom and loading the CDROM drivers
in protected mode.



Daniboot is only used with the El-torito boot method, AFAIK. You should be building a maintenance partition, on the device, which would
not use that, at all.



This is very well discussed / documented at

http://www.ami.com.au/BootableOS2CD.htm

"Creating a Bootable CD-ROM *for OS/2" *Copyright 1998 by Allen Dermody

Conclusion:

Handle the PRM as fixed device and the system should boot to command prompt!



That is an ancient article, and many things have changed since then...



How to do it?

1.Add an parameter to usbmsd.add to handle removable device as fixed device
e,g, pass the "right" device type to os2dasd.dmd and os2lvm.dmd



Unless IBM releases the "latest" USB driver code, I doubt if this will
ever happen.



2. Ask very polite Chis for a modification of CWUSBMSD.add :-)



Possible, but Chris' driver is still based on old code, which might just break a lot of newer devices.



3. Built a filter driver to switch the device type form removable to fixed
as done in CD_boot.FLT, DANIBoot.FLT and DANIS506.ADD with the device parameter /!RMV

This is probably the most general solution and could enable the booting from other removable devices
in the future e..g. firewire HDDs



This is the most likely to work properly.



I have start the process to the bounty system at os2word to promote the building of the flt driver

I will ask Dani very polite about it :-)



She may not have the tme, or the interest, to do it, but it can't hurt
to ask.



4) You would, likely, want to make the USB drive startable, and put



the USB device boot before the hard disk boot, in the BIOS settings, so that the USB device will boot, without needing the Boot Manager, that may be on a non-working hard disk, at some point.





See the bios mod in the problem description - already done



I saw that, after I posted...



LVM GUI does not allow a bootmanager on a PMR and
does not reserve the 7,x MB at the beginning of the drive space



You really shouldn't need boot manager on the device, but you would need to make it startable (active, in Windows terms), so it would immediately try to boot the code that is on the device. Unfortunately,
doing that with any of the current tools (except, possibly, DFSEE), will make Boot Manager not startable on the hard disk (that can be fixed, after you remove the USB device).


The BMR does not see the PRM device .

By booting from HDD the BMR gets control -
the BMR does not look / start the PRM via I13
even if there is an entry in the BMR tables for the system on the PRM. ( the USB drive LED is not green )

By booting from the PRM ( via bios start up pointing first to the USB in start up boot list )
the BMR does not get control - the system is directly loaded from the primary partition on the
PRM




Hope this helps...




Indeed it does help a lot :-)




kind regards



Rainer


Good luck...



I truly need it :-)


Kind regard


Rainer

.

Relevant Pages