StorNext client won't mount SAN volume after RAID controller failure
I had a RAID controller die in one of the RAID units in our SAN. I was able to replace it OK and after some messing with cvlabel (the new controller was showing up as a duplicate LUN), the XSAN MDCs are happy and all of the Mac clients are happy again.
However, I have one StorNext client for a Linux system that refuses to mount the SAN volume after the change was made. The lines I found in /usr/cvfs/debug/mount.SAN.out have this to say:
Mounting filesystem SAN on /Volumes/SAN
buffers=yes, sparse=yes, protect_alloc=no, syslog=info, allowdupmount=no
timeout=100, recon=hard, retrans=12, mnt_recon=hard, mnt_retrans=1
Error mounting possibly due to unavailable disks.
mount.cvfs: Can't mount filesystem 'SAN': No such device
System log may contain additional details.
Any ideas what to try next? The only thing that has changed is the RAID controller (1 out of 6).