What causes a 'Bootstrap Failure' on OIS43 startup?
OIS43 console failed, on power up the console monitor is reporting
(boot dka0.0.0.6.0 -flags 0,0)
block 0 of dka0.0.0.6.0 is not a valid boot block
bootstrap failure
then it keeps retrying with the same message scrolling.
Any troubleshooting help would be appreciated.
The DKA0 hard drive was replaced and same message is appearing.
I am thinking it could be the CD-ROM not reading the disk properly but I am just guessing.
(boot dka0.0.0.6.0 -flags 0,0)
block 0 of dka0.0.0.6.0 is not a valid boot block
bootstrap failure
then it keeps retrying with the same message scrolling.
Any troubleshooting help would be appreciated.
The DKA0 hard drive was replaced and same message is appearing.
I am thinking it could be the CD-ROM not reading the disk properly but I am just guessing.
Asked 1 year ago
Voted best answer
1
Hi,
Block 0 on a system disk is the boot block. It contains a pointer to the primary bootstrap image, which in turn is used to boot the system. Bootstrap failure indicates that the boot block 0 is not readable. Causes could be...
Boot device definition incorrect - The boot device is defined with environment variables. This looks Ok but check your installation manual for the OIS43 environment variables for boot device definition.
Bad boot disk - If the boot block is corrupted or damaged the machine will fail to boot because it can't find the bootstrap image.
Tape backup command syntax - If the backup to tape command was not entered correctly the saveset will not have been created correctly for an image restore. If the restore (backup to disk) did not include the /image flag DKA0 will not have been initialized during the backup process. Check the installation manual for correct syntax and always include the /verify flag even though it doubles the time taken for each operation.
If you want to verify DKA0 works as a boot volume you could do a clean system disk software install from the CDROM and see if this installation at least boots past the current point of failure. There is no need to let the machine startup completely, just far enough to verify bootstrap is successful. This also assumes that the machine is on the bench and not connected to the production system. If this is not the case then at least pull the network cable to avoid any possibility of duplicate nodes on the network. If the system still fails to boot, look at DKA0. If the system boots using the image restored from the CDROM, look at your backup tapes or command syntax.
Cheers,
Alan
Block 0 on a system disk is the boot block. It contains a pointer to the primary bootstrap image, which in turn is used to boot the system. Bootstrap failure indicates that the boot block 0 is not readable. Causes could be...
Boot device definition incorrect - The boot device is defined with environment variables. This looks Ok but check your installation manual for the OIS43 environment variables for boot device definition.
Bad boot disk - If the boot block is corrupted or damaged the machine will fail to boot because it can't find the bootstrap image.
Tape backup command syntax - If the backup to tape command was not entered correctly the saveset will not have been created correctly for an image restore. If the restore (backup to disk) did not include the /image flag DKA0 will not have been initialized during the backup process. Check the installation manual for correct syntax and always include the /verify flag even though it doubles the time taken for each operation.
If you want to verify DKA0 works as a boot volume you could do a clean system disk software install from the CDROM and see if this installation at least boots past the current point of failure. There is no need to let the machine startup completely, just far enough to verify bootstrap is successful. This also assumes that the machine is on the bench and not connected to the production system. If this is not the case then at least pull the network cable to avoid any possibility of duplicate nodes on the network. If the system still fails to boot, look at DKA0. If the system boots using the image restored from the CDROM, look at your backup tapes or command syntax.
Cheers,
Alan
Answered 1 year ago
Add new comment