Operating System - Tru64 Unix
1748198 Members
2616 Online
108759 Solutions
New Discussion юеВ

Re: bootstrap code problem

 

Re: bootstrap code problem

Does anybody have an idea... or I need to reinstall the whole box? :(

Thank you.

Regards,
Z
david puzycki
New Member

Re: bootstrap code problem

Please help, I am in the same mess as described in this thread. I also swapped disk drives and now encountered the same error message "can't open osf_boot".

I have booted under cdrom and have run "hwmgr show scsi":

HWID Device ID
59 0 disk dsk0 [0/1/0]
60 1 disk dsk1 [0/2/0]
61 2 disk dsk2 [0/3/0]
62 3 disk dsk3 [0/4/0]
63 4 disk cdrom0 [0/1/0]

The command /sbin/advfs/advscan dsk0
displays: "can't open device rdsk0a"

disklabel on rdisk shows 8 partitons, but disklabel on dsk0 or dsk0a errors.

If anyone can please help me out of this jam it would be appreciated!

Thanks Dave

Re: bootstrap code problem

Dave,

I do not want to disappoint you, but non of the ideas listed above have helped.

I was forced to reinstall the box from scratch and restore data from my latest backup.

Sorry, about the bad news. I could not believe either that this could be the only solution, but nothing else worked. :(
jim owens_1
Valued Contributor

Re: bootstrap code problem

First check to see if you have an ID conflict:

59 0 disk dsk0 [0/1/0]
63 4 disk cdrom0 [0/1/0]

The 0/1/0 is the bus/target/lun and can not be the same for real scsi devices. However, this would be OK if the cdrom is an IDE device because then hwmgr is just reporting a fake id.

Use the console "show config" to see.
david puzycki
New Member

Re: bootstrap code problem

Jim,

Interesting, the working system shows the following:

HWID Device ID
59 0 disk dsk0 [0/0/0]
60 1 disk dsk1 [0/2/0]
61 2 disk dsk2 [0/3/0]
62 3 disk dsk3 [0/4/0]
63 4 cdrom cdrom0 [1/0/0]

So there is apparently a conflict between dsk0 and the cdrom on the non-working systems, can you help me resolve it?

Best Regards...Dave

Re: bootstrap code problem

Dave,

try to plug cdrom device to another bus or change (with the jumpers on the cdrom) the scsi id to 5 or 6.
This should relove your problem.

Regards,
Z
Johan Brusche
Honored Contributor

Re: bootstrap code problem


There is no conflict at all, the cdrom is on bus #1, the other disks are on bus#0.

Get your latest vdump tape foor root, boot from CD and mkfdmn root_domain, mkfset root + vrestore.

Rgds,

___ Johan.

_JB_
Michael Schulte zur Sur
Honored Contributor

Re: bootstrap code problem

Johan,

the second output was the one that is working. The first output looks a bit different. There it seems there is a collision.

Michael
david puzycki
New Member

Re: bootstrap code problem

Yes I believe there is a scsi conflict based on the hwmgr output of the system that is working.

How can I resolve my scsi ID conflict? Is there a jumper on the cdrom to set a specfic ID or should I physically move the cdrom to a different location?

Tks..Dave
jim owens_1
Valued Contributor

Re: bootstrap code problem

The answer to change slot/cable/jumper depends on the hardware configuration and you have not told us what it is, not even the system model. I really want to see the full console "show config" output.

With no info to go on, I might guess that the easiest option is to move dsk0 to another slot so its scsi id changes.