Search below for 'logbook_sop' for help on usage.
| November 2009 | ||||||
|---|---|---|---|---|---|---|
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | |||||
By: TeX Time: 2008121 0857Z Music: None 0659Z The SPADE error email arrived: Could not write tape header file blank tape in /dev/nst0 on ic-tape. Details are available in the Tapeserver log file for this drive: ic-tape:/usr/local/spade/tapeserver/logs/tapeserver-nst0.log and in the SPADE (JBoss) log file: sps-sattx:/usr/local/icecube/jboss/server/iceboss0/log/server.log 0727Z Cindy sent: OK, so the message is bad, but the tape is probably worse. This is supposed to indicate that spade couldn't write the header file on a new tape, so all you need to do is eject it and try another blank tape. Thanks much, Cindy Around this time I did a restartTapeDrive() just to see, but that did not work, not too suprisingly. I got onto sps-sattx and did an mt -f /dev/nst0 status which returned SCSI 2 tape drive: File number=0, block number=-1, partition=0. Tape block size 0 bytes. Density code 0x42 (no translation). Soft error count since last status=0 General status bits on (5010000): WR_PROT ONLINE IM_REP_EN so the tape is obviously write protected. I went to B2, and verified this. I unwrite protected it. From my room, I did a restartTapeDrive() which failed again. A second 'mt' command showed the system still thought it was write protected. So I did: mt -f /dev/nst0 offl and went to B2 to reinsert the tape and return to my room. Then I did the restartTapeDrive(), which was successful and replied to cindy's email.
Edgar Nielsen
|
30 Apr 2008 04:01 GMT
|
SPADE
|
|