btcreate error/problem

[Paul_504]

Hi

I'm trying to create a bootable tape using the btcreate utility. The whole process executes perfectly, but when I try booting of the tape it gives the following error:

jumping to bootstrap code

halted CPU 0

halt code = 2
kernel stack not valid halt
PC = 20000004
P00>>>

Could this be that the partition chosen for the miniroot location is automatically picked as part of btcreate, and it takes a mounted disk partition, thus not creating a correct kernel?

Any input would seriously be appreciated, as my thought patern is at an end.

Thank you in advance
Paul

[Michael Schulte zur Sur]

Paul,

how did you create the tape?

greetings,

Michael

[Paul_504]

Hi Michael

I ran the /usr/sys/bin/btcreate command. This takes you to an interactive command line interface. It prompts you for the kernel file, where the default is correct, whether you want to use MFS, etc. The tape creation process runs without any errors though, just when the boot-up from tape comes around that it complains.

Paul

[Erich Wimmer]

Paul,
did you use a MFS filesystem for your miniroot?
If not, try to use it.
I've attached a screen copy of btcreate I have done some times ago.
Hope this helps, Erich.

[Paul_504]

Hi Erich

I tried your way, but the boot still fails with the same error:

jumping to bootstrap code

halted CPU 0

halt code = 2
kernel stack not valid halt
PC = 20000004
P00>>>

Did your bootable tape work? Could the error be a result of device inconsistencies as during my btcreate process it doesn't give the following lines:

Creating device files on mfs...
procprod: using MfsBase 0x140010000
procprod: pid 5351, MfsBase 140010000, 30720 sectors, output ==> "/var/tmp/procprod/mfsImage"

It says something else after the "Create device files on mfs..." prompt.

[Michael Schulte zur Sur]

Hi,

please post os version, patch kit, what machine are you using and the complete output of btcreate as attachment.

Thanks,

Michael

[Paul_504]

Hi Michael

The system details are below:

Hardware: Alpha 4100
OS: Tru64 UNIX V5.1B
Patch Kit: PK4

Attached is also the complete output of the btcreate process.

I hope this helps you to help me :-). Thank you.

Paul

[Erich Wimmer]

Paul,
did you use the "nc" boot flags for booting your tape ?
>>>> boot -fl "nc"

Erich.

[Paul_504]

Erich, hi

I did use the "nc" flag yes. I'm not sure what it means though :-)

[Erich Wimmer]

Paul,
I don't know the meaning of these flags. I have created a test boot-tape and booted successfully, Tru64 V5.1b, Patchkit 3. If not using the "nc" flags, boot fails, but not with the same error codes you have.
Erich.

[Paul_504]

Erich

Do you think it could have anything to do with updates or limits caused by PK4 though. Currently all our systems are on PK4, and we've tried on a number of systems to create a bootable tape without any success. If I recall correctly, they all seem to fail with the same error.

Paul

[Erich Wimmer]

Paul,
I have tried it also with patchkit 4 installed and it works. Btcreate is populating the mfs filesystem (25 mb default size) and if it becomes full it may lead to problems during boot from tape (hangs etc.), but not at the place you described (jumping to bootstrap code) and with halt code. Also in this case you should get errors during btcreate (file system full). I have no idea what else can lead to your error.
Check if you have the latest firmware installed and if your tape device is meeting the requirements
(http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51A_HTML/ARH9FDTE/TITLE.HTM, chapter 9.10) and the restrictions described in "man btcreate. If you call the HP support hotline, I'm sure someone in our supportchannel can help.
Erich.

[Aaron Biver_2 · Accepted solution]

Paul,

We have just noticed this with the newer PK5 which is still under development. However, we did not know it was reproducible with PK4.

The basic problem is that btcreate is creating a kernel that is too big for the SRM firmware to boot. There is a firmware limitation of 32 MB on the size of the bootable kernel.

To solve this, you need a smaller kernel. If you recall, when you ran btcreate, it asked you for a kernel config file, and then it built a tape-bootable kernel according to that config file.

You apparently had previously built your kernel with all options included. This makes for a big kernel.

If you rebuild with no options (mandatory is the default), or just select the few that you feel you need, you should be able to boot. Remember, this is a bootable tape kernel, most likely used to restore your filesystem after a disaster. Most people don't need the options like "IP tunnelling" or "IP over ATM" in this type of kernel.

To change the options built into your kernel, just run doconfig again (without the "-c" options"). When you are done run btcreate again and point it to the kerenl config file name you just created.

A fix for btcreate is in the works for PK5 so customers would never see this (or so we thought).

If you still have trouble after applying this workaround, let us know.

[Paul_504]

I just want to say thank you to everyone for their input. Aaron, I'd reconfigured the kernel, built it, ran btcreate and with the stripped down kernel the boot worked perfectly.

Thank you for any and all help given. I truly appreciate it.

Paul