stm switch log did not generate *.raw.cur

[Godfrey Zhang]

I recently started stm to check the raw file, it said the raw.cur file corrupted. So I removed OnlineDiag and installed Jun 2004 OnlineDiag. But it still doesn't generate *.raw.cur even I do "switch log". Any ideas?

[Michael Tully · Accepted solution]

Seeing your getting the message, that the file is corrupted, have you tried to remove the file?

You might like to try and stop diagnostics running first.

# /sbin/init.d/diagnostic stop

remove the file and restart diagnostics.

# /sbin/init.d/diagnostic start

[Godfrey Zhang]

Hi Michael,

Tried to restart the diagnostics, but it still didn't generate a raw.cur. Now it's like this:
PPQ3HXU1 (util)> cd /var/stm/logs/os
PPQ3HXU1 (util)> ls -l
total 1600
-rw-r--r-- 1 root sys 508368 Jul 21 17:01 ccbootlog
-rw-r--r-- 1 root sys 2088 Jul 16 20:18 ccerrlog
-rw-r--r-- 1 root sys 0 Jul 12 18:05 log1000.raw
-rw-r--r-- 1 root sys 215924 Jul 12 18:19 log5.raw
-rw-r--r-- 1 root sys 69196 Jul 21 16:57 memlog
PPQ3HXU1 (util)>

[Andrew Merritt_2]

I'm not sure that the new *.raw.cur file will be created until there's something to put in it, so until an error is reported by one of the device drivers it may well be normal that there is no such file.

If this is a test machine, you could try something like pulling a disk drive or power supply (in a redundant situation) to see if that leads to the file being created.