From: Dustin Marquess (dmarquess@gmail.com)
Date: Mon Jan 15 2007 - 01:09:27 EST
All,
I'm having a weird issue. I have an AlphaServer 800 running Tru64 V5.1B-3.
Today there was a power outage and the UPS died before the machine was
shut down.
It appears to have come up cleanly. Since the machine already took
the hit, I went ahead and put the V5.1B-4 patch on it. Once I
rebooted, I got the following errors:
vm_swap_init: warning UNSPECIFIED swap device not found
lsm:new_disk: Cannot open disk dsk0a: kernel error 16
lsm:vold: WARNING: Disk root01 in group rootdg: Disk device not found
dsfmgr: NOTE: updating kernel basenames for system at /
Mounting / (root)
msfs_mount: The mount device does not match the linked device.
Check linked device in /etc/fdmns/domain
vmunix: lsm:new_disk: Cannot open disk dsk0a: kernel error 16
dsk0a is not only the boot drive, but that drive is part of a RAID-0
stripe. The machine come up completely, which I thought was strange.
I went ahead and shut the machine down, reseated the drives, pressed
the halt button, and brought it back up:
Halt Button pressed during powerup
powerup script not exectuted
Halt Button is IN, AUTO_ACTION ignored
>>>show dev
dka0.0.0.5.0 DKA0 SEAGATE SX150176LC BA12
dka100.1.0.5.0 DKA100 SEAGATE SX150176LC BA08
dka200.2.0.5.0 DKA200 SEAGATE SX150176LC BA12
dka300.3.0.5.0 DKA300 SEAGATE SX150176LC BA11
dka400.4.0.5.0 DKA400 RRD46 1337
dva0.0.0.1000.0 DVA0
ewa0.0.0.11.0 EWA0 00-00-F8-09-34-E0
pka0.7.0.5.0 PKA0 SCSI Bus ID 7 5.57
So the drives show up.
Booted, same errors. I know the drive works, since bootup has:
(boot dka0.0.0.5.0 -flags A)
block 0 of dka0.0.0.5.0 is a valid boot block
reading 19 blocks from dka0.0.0.5.0
After the machine came up, I checked scu:
CAM Equipment Device Table (EDT) Information:
Bus/Target/Lun Device Type ANSI Vendor ID Product ID Revision N/W
-------------- ----------- ------ --------- ---------------- -------- ---
0 0 0 Direct SCSI-2 SEAGATE SX150176LC BA12 W
0 1 0 Direct SCSI-2 SEAGATE SX150176LC BA08 W
0 2 0 Direct SCSI-2 SEAGATE SX150176LC BA12 W
0 3 0 Direct SCSI-2 SEAGATE SX150176LC BA11 W
0 4 0 CD-ROM SCSI-2 DEC RRD46 (C) DEC 1337 N
It still sees the drive. So I make sure the device entry is still there:
brw------- 1 root system 19, 17 Oct 16 2003 /dev/disk/dsk0a
And it's there!
While the system was coming up I could see the activity LED under the
drive flashing. I checked the evm logs and I don't see any SCSI
errors. I grep'd for dsk0a in the system logs, and it looks like the
system came up cleanly after the power outage. The problem started
showing up after the patch.
I tried booting off the PrePatch kernel, but that didn't help. I'm
thinking either some binary changed, or some config file changed. I
know the patch complained about sysconfigtab needing to be manually
merged, but I didn't see any obvious problems with it.
I'm sorry if this is a stupid/obvious problem. I haven't seen this
issue before. Since it's a non-commercial machine/license, so I don't
have support from HP.
Thanks for any help!
-Dustin
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:33 EDT