> One of our clients has a 4.0 system with several dozen ldevs
> in mpexl_system_volume_set (yes, we've told them that isn't a good
> idea).  8 drives are on one HPFL string (the rest are non-HPFL).
> One of those went "bad" (red fault light), but now appears to be working.
>
> However, when they boot up, and do a DSTAT ALL, they see
> most of the disks are ok, but all 8 drives on the HPFL string are
> in the LONER state (and can't be accessed via file system).
>
> The boot-time "mount" messages and XM recovery messages show the drives
> as normal ... there's no real clue anything is wrong until the system
> finishes booting and we then try to use the drives.
>
> The 8 drives are on ldevs 32..39, with names MEMBER34..MEMBER39, and
> ldev 34 (MEMBER34) was the one that was temporarily bad.
>
> Yes, we've looked at the first 2 sectors of each of the 8 HPFL drives...
> they look like valid entries (e.g., MPEXL_SYSTEM_VOLUME_SET, MEMBER32).
>
> We've power cycled ... no success.
> We've replaced the HPFL controller card ... no sucess.
> We've searched HPSL ... no success.
> We've booted up with drive 34 turned off ... no sucess.
>
> Any ideas?
>
  Start with the base unit.  Take the terminator out of the top unit,
and terminate ldev 32 all by itself.  Reboot the system and see if
the drive is recognized.  If so, move up a drive at a time.
 
  If one of the other drives has the FL connector, and the above
doesn't work, make it the drive the FL is connected to by itself.
 
  Was the red fault light on the lowest drive (suspect fl controller
card in drive).
 
  I've seen lots of strange problems when something goes wrong with
the first drive in the chain.
 
Jim
 
 
--
=====================================================================
          M-Net -- America's First Public Access Unix System
                   Now running BSD/386 Version 1.1
       (313) 996-4644 (14400-8N1) -or- telnet m-net.arbornet.org
[log in to unmask]                             [log in to unmask]