108 FIle system Routine Test Error 1

[pedroskie]

Anyone know how I may be able to clear this alarm,have changed the backup optical drive and disk.Able to write/ backup to optical drive ok no problem.
Anyone have any ideas.
Thanks

 

[fouesnant]

Hi

ADD INFO 1 and ADD INFO 2 in the alarm 108 are inmportant. Could you post the whole information you have in ALARM 108?
Could you do also a FISCP on the IODEV and post the result?

 

[pedroskie]

Here is the info you requested,thanks for your help.

CLASS:3
108 FILE SYSTEM ROUTINE TEST ERROR
DATE TIME ALP NOIF EQU BRDID INF1 INF2
03FEB06 10:27:00 4 1 001-0-60-00 69 3 2

<FISCP:IODEV=SAFETY-DSK;
FILE SYSTEM CAPACITY DATA
TOTAL DISK SPACE: 217 MBYTES
SUBFS: SAFETY-SF
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
NOT ACCEPTED
NODE NOT FOUND

 

[fouesnant]

Hi pedroski

Here is the analysis of INF informations :
INF1 = 3 mean Disk used for storing of a safety backup copy is not accessible.
INF2 = 2 mean SCSI position 2

Also FISCP indicated that the node is not found :
Either the disk is switched off, or the SCSI position on that disk is not 2, or the disk is dead.

Could you post an IODDP printout?

 

[pedroskie]

<IODDP;
I/O DEVICE DATA
NODE IODEV/SUBFS EQU/BPOS SIPOS VEND/USAGE STATUS
SYSN - 001-0-60 - - IN SERVICE
SYSN SAFETY-DSK 001-0-60-0 2 FUJITSU SAFETY
SAFETY-SF
SYSN SYSDISK1 001-0-60-0 3 SEAGATE IN SERVICE
SYSSUBFS11
SYSSUBFS21
TMFS
SYSN SYSTERMINAL 001-0-60-1 - MML -
SYSN SYSTERMINAL1 001-0-60-2 - MML -
SYSN SYSTERMINAL2 001-0-60-3 - MML -
END

 

[fouesnant]

Hi pedroskie

Make sure that your saefty-dsk is up and working. According to the alarm, it is not the case.

 

[pedroskie]

I take your point,the alarms indicate disk/scsi cable or scsi drive failure but for some reason I am still able to write/backup to the disk.Plus I have already swapped out the drive and disk.Thanks for your help,I will let you if I find the problem.

 

[alsavs]

Hi pedroskie

Had a similiar problem some time ago i had to reseat ipu card.Hope this is of use.

 

[rokane]

Hi,

I am also experiencing almost identical problem as shown by printouts below but when I check the file system it is okay. Can any knows which one is causing the problem? I tried replacing the NIU & the HDU7 but the alarm is still
there.


Rokane


DATE: 07FEB06 TIME: 08:29:20
CLASS: 3
106 FAULTY I/O BOARD OR CONNECTED I/O DEVICE
DATE TIME ALP NOIF EQU BRDID INF1 INF2
07FEB06 08:18:26 5 1 001-0-60-00 106 9 3


<FISCP:IODEV=SYSDISK1; FILE SYSTEM CAPACITY DATA
TOTAL DISK SPACE: 8063 MBYTES
SUBFS: SYSSUBFS11
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
65536 23083 19200 /SYSN/USR1
SUBFS: SYSSUBFS12
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
65536 60324 19200 /SYSN/USR1/SES/DR/REL1/S2
SUBFS: SYSSUBFS21
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
65536 23214 19200 /SYSN/USR2
SUBFS: SYSSUBFS22
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
65536 60324 19200 /SYSN/USR2/SES/DR/REL2/S2
END

 

[fouesnant]

Hi

Which revision is you NIU?
Have you tried FIFTI on the SUBFS: this command solve a lot of error, but in some cases, it cannot perfom the correction and you are obliged to format you partitions on that disk.

Best regards

 

[rokane]

fouesnant,

The NIU revision is R17A.I already did FIFTI & partitions formating but just the same the problem is still there. The
last thing I did was to do RFEXI during weekend & the problem dissapeared but the really reasons what caused it
still unknown to me.


rokane

 

[fouesnant]

Hi rokane

Hmmmm, some problems could be related to NIP or FIP PU.
It could also be related to the NIF loaded into the NIU. I have problems at the moment with NIU in R13A when I simply cannot have access to the system via V24.

Which BC release are you running?

 

[rokane]

fouesnant,

It is running on BC11 SP9.




rokane

 

[fouesnant]

Hi Rokane

Exactly what I am expecting. I will move my NIU into the latest FW available and see if it improve the situation; I suggest you to do the same. The most strange thing is that my NIU FW R13A does not create problems on BC12, while it does on BC11

Best regards