Table of contents
Reconstructing a Mark5 user directory
When the user directory on a module has been corrupted for whatever reason, there are two possible ways to recover it, using utilities included in "fuseMk5". Place the problematic module as the only module into a Mark5 unit. Then:
If the module was previously imported into DiFX:
mkdir tmp; cd tmp cp -a /cluster/difx/directories/<modulename>.dir . /cluster/mark5/fuseMk5/fuseMk5-cvs/difxdirfile2userdir.py <modulename>.dir newdir.bin /cluster/mark5/fuseMk5/fuseMk5-cvs/fuseMk5 --udread newdir.bin /mnt/diskpack ls /mnt/diskpack # If files under /mnt/diskpack looked reasonable you can write newdir.bin onto module: fusermount -u /mnt/diskpack /cluster/mark5/fuseMk5/fuseMk5-cvs/writeuserdir newdir.bin
If only a FieldSystem log file exists:
mkdir tmp; cd tmp cp <fieldsystemlog>.log fslog.log (cat expt_part_2.log >> fslog.log) # if there are multiple experiments on a module (cat expt_part_3.log >> fslog.log) # ... /cluster/mark5/fuseMk5/fuseMk5-cvs/fslog2userdir.py <fieldsystemlog>.log newdir.dir /cluster/mark5/fuseMk5/fuseMk5-cvs/fuseMk5 --udread newdir.bin /mnt/diskpack ls /mnt/diskpack # If files under /mnt/diskpack looked reasonable you can write newdir.bin onto module: fusermount -u /mnt/diskpack /cluster/mark5/fuseMk5/fuseMk5-cvs/writeuserdir newdir.bin
Mark5 Module recovery
Upgrade SDK Version
insert a module into slot A
BEWARE: data on the module might become deleted, so make sure it contains no valid data !
log-into the mark5 machine as user root, then execute:
cd /usr/local/src/streamstor/linux/util/ ./ssflash -u SDK9.3.ssf
make sure no errors are reported during the flashing process
run ssopen and sstest:
./ssinfo ./sstest
make sure no errors are reported
Update the sticker on the chassis of the mark5 to indicate the new version of SDK.
