Attempt using 'scanner' against the FTD to see if it also reports an issue.  If it does, then the file system may be suspect.  Can you run a fsck against that filesystem to validate it is not the cause?

Duncan

both scanner and e2fsck is clean.  Any other ideas?

/usr/sbin/scanner -v /nsrdata/10

8909:scanner: using '/nsrdata/10' as the device name
8360:scanner: Reading the file label
8936:scanner: scanning file disk SIUMED.010 on /nsrdata/10
8937:scanner: volume id 2710613 record size 32768
  created  6/05/09 12:56:37 expires  6/05/11 12:56:37
8761:scanner: done with file disk SIUMED.010

/sbin/e2fsck -fy /dev/sda1
e2fsck 1.35 (28-Feb-2004)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
NSRDATA10: 13/2002688 files (15.4% non-contiguous), 125078/512687355 blocks

After these checks you still can't mount volume?  In such case, make sure it is unmounted, make a backup copy of the volume and delete it from NW.  Then delete device.  Restart NW and make sure nsrck -m does not report any errors.  The create device, copy the content from your backup and scan it.  After that you should be able to mount it.  If not, something with that data within volume is broken.