Folks,
I recently received a DS20 with Factory Installed Software running Tru64 Unix
4.0F. Although it came up ok, within a day the box had memory problems. We
removed the failing memory, but couldn't boot up the FIS from either vmunix or
genvmunix due to "kernel stack errors". Booting from the CD, I ran scu "verify
media" on the system's two disks and they came up clean. I installed 4.0F to
the second disk ok and was able to mount the g partition of the FIS disk ok.
But when I tried to mount the root partition, the OS panic'ed with:
> Aug 11 20:19:22 zantar vmunix: ADVFS EXCEPTION
> Aug 11 20:19:22 zantar vmunix: Module = ftx_recovery.c, Line = 198
> Aug 11 20:19:22 zantar vmunix: ftx_bfmeta_rec_redo: got bmt page N1 instead of
> N2
> Aug 11 20:19:22 zantar vmunix: N1 = 74214508, N2 = 1
> Aug 11 20:19:22 zantar vmunix: panic (cpu 0): ftx_bfmeta_rec_redo: got bmt
> page N1 instead of N2
> Aug 11 20:19:22 zantar vmunix: N1 = 74214508, N2 = 1
> Aug 11 20:19:22 zantar vmunix: syncing disks... done
I relabeled the "bad" disk and installed Tru64 Unix successfully. So it seems
that there was nothing wrong with the disk hardware, just data corruption.
My question: what could be on a disk so that Tru64 panics instead of just
failing to mount the disk?
As an aside, is anybody else as upset as I that after paying $30,000 for a
computer including $500 for a mandatory FIS which needs to be redone anyway,
Compaq cannot include a $5 operating system CD?
--Harvey
----
Harvey Rarback phone: (650)926-3963
Stanford Linear Accelerator Ctr fax: (650)926-4100
PO Box 4349, MS 69 home phone: (650)560-9111
Stanford, CA 94309-0210 Web: ssrl.slac.stanford.edu/~rarback
rarback_at_ssrl.slac.stanford.edu ESnet: 45746::RARBACK
"Always tell the truth, that way you don't have to keep track."
Pogo
Received on Fri Aug 13 1999 - 22:27:25 NZST