This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
handover:hob008 [2016/11/19 09:00] Ross Turner |
handover:hob008 [2016/11/19 12:40] Ross Turner |
||
---|---|---|---|
Line 11: | Line 11: | ||
* 0830UT - Disc pos ~200 GB behind, holding steady. (Ellen) | * 0830UT - Disc pos ~200 GB behind, holding steady. (Ellen) | ||
* 0845UT - Hg pressure still at about 4.0 (Lucas reported it had been a little high). Appears stable, probably just due to hot weather. Continuing to monitor. (Ellen) | * 0845UT - Hg pressure still at about 4.0 (Lucas reported it had been a little high). Appears stable, probably just due to hot weather. Continuing to monitor. (Ellen) | ||
- | * 0900UT -Hg pressure fallen down to 3.1 microns. (Ellen) | + | * 0900UT - Hg pressure fallen down to 3.1 microns. (Ellen) |
+ | * 1040UT - Module filled up and automatically switched to recording onto HOB+0120, which already had 9901 GB on there. First scan on module was 324-1041. 2092 GB recorded to HOB+0029. (Ellen) | ||
Line 24: | Line 25: | ||
* 0215 UT The diskpack that was being recorded to was marked as 'Faulty', and there was a lag between accepting a 'disk_record=off' command, which was longer than the 500ms window the fs allowed, thereby giving the mk5cn time-out error. Jamie was able to correct this and the alarm was un-commented. (Lucas/Jamie) | * 0215 UT The diskpack that was being recorded to was marked as 'Faulty', and there was a lag between accepting a 'disk_record=off' command, which was longer than the 500ms window the fs allowed, thereby giving the mk5cn time-out error. Jamie was able to correct this and the alarm was un-commented. (Lucas/Jamie) | ||
* 0830UT - Disc pos ~130 GB behind, holding steady. (Ellen) | * 0830UT - Disc pos ~130 GB behind, holding steady. (Ellen) | ||
+ | * 1040UT - Module filled up and automatically switched to recording onto HOB+0120, which already had 9901 GB on there. First scan on module was 324-1041. 2092 GB recorded to HOB+0029. (Ellen) | ||