Questions and Answers : Windows : work unit % went back to 0.000 after a system freeze and reboot
Message board moderation
Author | Message |
---|---|
Send message Joined: 31 Aug 04 Posts: 29 Credit: 356,174 RAC: 0 |
Hi all: My system frooze and I had to do a reboot - the % went back to 0.000 but the time stayed the same (over 20 hours - 2 trickles had been sent in). work unit name: hadsm3fub_0335_005915997_7 Work unit is now at 34:59:00 (16.17 s/TS) timestep 7795 of 259248 progress 1.00% Mark Reiss |
Send message Joined: 5 Aug 04 Posts: 1496 Credit: 95,522,203 RAC: 0 |
It\'s likely that the system problem triggered a restart. The surprising thing to me is that it didn\'t trigger a crash on Model-restart. The reported \"seconds per Time Step\" will be distorted throughout the Run but will gradually become more reasonable. You can calculate the actual rate using the time between Trickles, when Trickles resume. (You\'ll see nothing [Edit: in Your Account] until the Run reaches the Third Trickle.) "We have met the enemy and he is us." -- Pogo Greetings from coastal Washington state, the scenic US Pacific Northwest. |
Send message Joined: 29 Sep 04 Posts: 2363 Credit: 14,611,758 RAC: 0 |
Hi Mark Luckily your model hadn\'t crunched for very long when this happened so you didn\'t waste much computing time. Just in case the same thing happens again, it would be worth making regular backups. Restoring a backup would avoid most of the repeated processing. Cpdn news |
©2025 cpdn.org