Need Periodic Write in Log File

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

vajiggle

specified; this will replace the title
Sep 19, 2020
10
10
2020's Hellscape
I've had 2 separate PC's crash (shut down) during some long 48+ hr Level 3+ jobs.

Not sure why. i'm assuming power supply failure, cobwebs, bad ram, or some other built-in safety protocols.

Unfortunately the Log Files for the jobs are blank. File created with date stamp name, but blank.

Is there a way to turn on 'periodic write' to the logs?

My temp solution is going to be a camera in front of the monitor set for time-lapse to capture pre crash data.
 
Periodic writes to a log file is SpinRite’s default.

See: Main Menu> 2 View or Change Settings > 2 Log system reports and activity > Yes

Please be sure this is set to Yes

There are two (2) exceptions:

- The boot media is not writable (e.g. CD or DVD). The data log will be accumulated in RAM during the test, viewable via the L-R keys (to the Real Time Activities (RTA) screen) during the test or at the end of the test before exiting SpinRite.

- The writable USB flash boot drive is being scanned. The data log will be accumulated in RAM during the test, viewable via the L-R keys (to the RTA screen) during the test . When the scan is complete, the log will then be written to the boot drive.

In either case a crash during the test would result in the loss of all log data accumulated in RAM.
 
  • Like
Reactions: vajiggle
In my case, logs set to yes.
I've reviewed completed successful and unsuccessful scans.
Also I don't scan the booting drive.

Am I right in understanding, logs are stored/written only in RAM until completion?
 
Logs should be written incrementally as events are completed. As a minimum I would expect to see the enumeration data, and the detailed drive data for the drive being scanned.

The GSD and S.M.A.R.T. data would not be written until the scan is successfully completed. A crash during the scan would lose this data.