vfs_mountroot panic on tru64 v5.1A
From: Tony (tony.bolton_at_geest.co.uk)
Date: 05/07/03
- Next message: George Samuelson: "For Sale on E-Bay Tru64 Unix V5.1B"
- Previous message: clintonvaugh_at_comcast.net: "Adding or Growing an LSM volumn"
- Next in thread: Tony: "Re: vfs_mountroot panic on tru64 v5.1A"
- Reply: Tony: "Re: vfs_mountroot panic on tru64 v5.1A"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 7 May 2003 08:46:24 -0700
Hi,
First of all, my apologies if this sounds a little vague.
Unfortunately the error I am getting is on the actual server console,
which is in a secure location (ie. no internet etc.)
We're running tru64 v5.1A, and I have just completed installation of
patch kit 4. On Wednesday last week, we had a new SDLT drive added to
the system, along with a new SCSI card to run the drive off. The
following 2 days, I experienced intermittent problems using the drive
- particularly with the device name 'disappearing' from within the
/dev/tape or /dev/ntape directory. I put this down to a minor issue,
and on rebooting the box it came back and worked fine.
However, I installed the patch kit on Tuesday - something I've done
many times in the past. I have never had the following happen though!
When I tried to reboot, bcheckrc hung, stating that there was a
problem with the database on line 294 (which had the string /dev/tape
within the error message - but it shot past so quickly I didn't have
time to make a note). It would then stop in single user mode, with
root mounted as ready only.
On contacting Compaq, they decided that the hardware database was the
main cause, so I was asked to delete the relevant files and reboot in
order to rebuild the database. Great, I thought.
It booted back fine - no problems, and I could see everything again
(ie. domains etc).
I thought at this stage 'time to make a backup', so decided to use the
new SDLT. This time, the SDLT drive 'remapped' itself to tape1 (it
was tape 2 before - when it worked that is). So, I started to backup
/ using vdump.
This is when the major problem kicked in - the machine hung, blue
screened, then said there was a panic on vfs_mountroot. It didn't
give any specifics, and just went back to the machine prompt (>>>).
No matter what I do - single user, different vmunix etc. - it still
panics.
My initial thoughts are that it is almost definately the new SCSI
device. The fact that I patched the system is probably just
coincidence, and so far Compaq seem to agree that it certainly looks
hardware orientated.
My question is : has anyone else had the same problem in the past -
and if so what was done to resolve the issue? We running on a DEC
ALPHA 4100, with 2 HSZ50 controllers in a storageworks cabinet. It
might also be worth mentioning it's a dual processor machine.
Another interesting point is that I can boot from a v5.1 OS Cd ok, and
get to the shell window. However, I tried to scan all devices using
'scu scan edt', but that hung and threw me out to a blue screen all
over again.
Compaq are looking into the problem as I write this, but I want to
cover all avenues and see if anyone else has had similar problems,
particularly with SDLT units.
Cheers,
Tony
Ps. We also have an additional tape drive on the system, but on
totally seperate card - it's a TZ88.....
- Next message: George Samuelson: "For Sale on E-Bay Tru64 Unix V5.1B"
- Previous message: clintonvaugh_at_comcast.net: "Adding or Growing an LSM volumn"
- Next in thread: Tony: "Re: vfs_mountroot panic on tru64 v5.1A"
- Reply: Tony: "Re: vfs_mountroot panic on tru64 v5.1A"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
