DOCSLIB.ORG

A Method for the Recovery of Data After a Computer System Failure: The

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Method for the Recovery of Data After a Computer System Failure: The Iowa State University Capstones, Theses and Retrospective Theses and Dissertations Dissertations 1992 A method for the recovery of data after a computer system failure: the development of Constant Random Access Memory (CRAM) Recovery System Renford Adolphus Benito Brevett Iowa State University Follow this and additional works at: https://lib.dr.iastate.edu/rtd Part of the Computer Sciences Commons, and the Engineering Education Commons Recommended Citation Brevett, Renford Adolphus Benito, "A method for the recovery of data after a computer system failure: the development of Constant Random Access Memory (CRAM) Recovery System " (1992). Retrospective Theses and Dissertations. 9977. https://lib.dr.iastate.edu/rtd/9977 This Dissertation is brought to you for free and open access by the Iowa State University Capstones, Theses and Dissertations at Iowa State University Digital Repository. It has been accepted for inclusion in Retrospective Theses and Dissertations by an authorized administrator of Iowa State University Digital Repository. For more information, please contact [email protected]. INFORMATION TO USERS This manuscript has been reproduced from the microfilm master. UMI films the text directly from the original or copy submitted. Thus, some thesis and dissertation copies are in typewriter face, while others may be from any type of computer printer. The quality of this reproduction is dependent upon the quality of the copy submitted. Broken or indistinct print, colored or poor quality illustrations and photographs, print bleedthrough, substandard margins, and improper alignment can adversely affect reproduction. In the unlikely event that the author did not send UMI a complete manuscript and there are missing pages, these will be noted. Also, if unauthorized copyright material had to be removed, a note will indicate the deletion. Oversize materials (e.g., maps, drawings, charts) are reproduced by sectioning the original, beginning at the upper left-hand corner and continuing from left to right in equal sections with small overlaps. Each original is also photographed in one exposure and is included in reduced form at the back of the book. Photographs included in the original manuscript have been reproduced xerographically in this copy. Higher quality 6" x 9" black and white photographic prints are available for any photographs or illustrations appearing in this copy for an additional charge. Contact UMI directly to order. University Microfilms International . A Bell & Howell Information Company 300 North Zeeb Road, Ann Arbor, Ml 48106-1346 USA 313/761-4700 800/521-0600 Order Number 9234792 A method for the recovery of data after a computer system failure: The development of Constant Random Access Memory (CRAM)® recovery system Brevett, Renford Adolphus Benito, Ph.D. Iowa State University, 1992 Copyright ©1992 by Brevett, Renford Adolphus Benito. All rights reserved. UMI 300 N. ZeebRcl. Ann Arbor, MI 48106 A method for the recovery of data after a computer system failure: The development of Constant Random Access Memory (CRAM)® Recovery System by Renford Adolphus Benito Brevett A Dissertation Submitted to the Graduate Faculty in Partial Fulfillment of the Requirement for the Degree of DOCTOR OF PHILOSOPHY Major: Industrial Education and Technology Approved: Signature was redacted for privacy. In Charge of Major Work Signature was redacted for privacy. Signature was redacted for privacy. For the Graduate College Iowa State University Ames, Iowa 1992 Copyright ® Renford A. B. Brevett, 1992. All rights reserved. ii TABLE OF CONTENTS CHAPTER L INTRODUCTION 1 Statement of the Problem 2 Purpose of the Study 3 Need for the Study 4 Delimitations of the Study 5 Limitation of the Study 6 Procedure of the Study 6 Definitions of Terms 9 CHAPTER II. LITERATURE REVIEW 12 Computer System and Software Failures 13 Software Testing 18 Computer Reliability and Validity Testing 20 Data Recovery System 23 Operating System and Software Development 26 Terminate-and Stay-Resident (TSR) Method 27 Undocumented DOS 29 CHAPTER III. DESIGN METHODS AND PROCEDURES 31 Questions of the Study 31 Hypothesis of the Study 32 Methodology of the Study 33 CHAPTER IV. RESULTS OF ANALYSIS AND HYPOTHESIS TESTING 38 Hypothesis 1 38 Installation 40 Organizing the hard disk 43 Checking for free clusters 45 Writing the FAT 49 12-Bit FAT 49 16-Bit FAT 50 Formatting CRAM 52 Protecting CRAM from DOS 53 Writing the directory area 54 CRAM'S Operation 54 Using hardware interrupt 57 Using software interrupt 59 Using the keyboard interrupt 59 iii Using the clock interrupt 60 Using the DOS idle interrupt 60 Use of Undocumented DOS 60 Using the DOS Swappable Data Area (SDA) 62 Determination of CRAM refresh period 62 Saving Memory 63 Memory Restoration 65 Context Switching 66 Working With Memory Control Blocks 69 Saving CRAM Data 73 Restoring Memory 73 Hypothesis 2 82 Results of software testing 82 Recovering from a power failure 82 Hypothesis 3 85 Time delay 85 CHAPTER V. SUMMARY AND RECOMMENDATIONS 94 Discussion to Question 1 94 Implications for future research 95 Discussion to Question 2 97 Development problems 97 Implementation problems 101 Implications for future research 101 Discussion to Question 3 102 Summary 103 REFERENCES 104 ACKNOWLEDGMENTS Ill APPENDIX A. INSTALLATION GUIDE 112 Introduction 113 System Preparation Prior to CRAM Installation 113 CRAM Installation 114 Invoking CRAM 115 Switches Used With CRAM 115 System Requirements 116 APPENDIX B. USER MANUAL 118 Introduction 120 Some DOS Error Codes Returned by CRAM 121 iv Error Codes Specific to CRAM 122 Re-installing CRAM 124 Getting Information About CRAM 126 Editing CRAM 127 Transferring CRAM To a Different Disk and/or Computer 127 Removing CRAM From the Hard Disk and System 128 APPENDIX C. CRAM SOURCE CODE 130 TSR.H 131 CRAM.H 132 DISK.C 140 CRAMUTIL.C 146 CRAMINT.C 155 CRAMMEM.C 160 CRAMTOOL.C 168 CRAM.C 182 INSTALL.C 209 APPENDIX D. SOURCE CODES FOR SOME USEFUL UTILITIES 216 GEN UTIL.C 217 CRAMINFO.C 223 V LIST OF FIGURES Figure 1. CRAM's development showing the goals assigned to each task .... 39 Figure 2. Layout of CRAM on the Hard Disk 44 Figure 3. Disk layout showing fragmented files 46 Figure 4. Disk layout after running Norton Utility disk organizing program (Speed Disk) 47 Figure 5. Installation Flow Chart 48 Figure 6. Flow diagram showing the start-up process for a DOS machine and the determination of CRAM's status 55 Figure 7. CRAM's process screen indicators 56 Figure 8. Flow Diagram showing CRAM's operations 58 Figure 9. Layout of the Program Segment Prefix (PSP) 67 Figure 10. Layout of DOS Swappable Data Area (SDA) 68 Figure 11. Code to find free clusters on the disk 70 Figure 12. Code to make a directory entry that protect CRAM from DOS ... 71 vi Figure 13. Code to write to the FAT 72 Figure 14. Code showing the main memory saving routine 74 Figure 15. Code showing the method used to restore memory 75 Figure 16. Code for the main memory loop 76 Figure 17. Code to show the calculation of memory checksum 77 Figure 18. Code to check for CRAM in memoiy to make sure it is the first program in memory after the DOS shell (COMMAND.COM) .... 79 Figure 19. MS-DOS environment after the start-up process 80 Figure 20. Layout of memory after CRAM was loaded 81 Figure 21. Software conflicts and the number of partial and full restoration of the system by CRAM 83 Figure 22. Benchmark program code 86 Figure 23. Delay times for some benchmark functions 87 Figure 24. Delay times for some benchmark functions contd 88 Figure 25. Graph of sieve numerical test 90 Figure 26. Graph of Video display test 91 vii Figure 27. Graph of random numbers generation test 92 Figure 28. Code used to set MCB 99 Figure 29. Code to get MCB 100 Figure lA. CRAM's process screen indicators 125 1 CHAPTER I. INTRODUCTION Over the past decade, much computerization has occurred in industries, schools, and homes. Computers are being used as tools, tutors, and tutee. Many people have become dependent on computers to perform a variety of calculations, bookkeeping, word processing, and other tasks. In order for the computer to reliably and continuously perform its assigned tasks the hardware and software must be designed to operate with a high degree of reliability. Since modem computers are generally reliable, most improvements by computer designers and programmers are directed towards building faster machines and higher storage capability. Although the storage capacity and speed of the machines is important, the designers neglect the area of system recovery and data loss. Data loss from a power outage can be catastrophic in that very important information, which may either be very expensive or time consuming to obtain may be lost. The following questions could be posed: 1. What are the major causes of computer system failure? 2. What methods can be used to save the system's data for easy access in case of a system failure? 3. How can data be recovered from a failed system? 4. What are the costs associated with system recovery by alternative methods? 2 5. What measurable effects do alternative systems have on system performance? 6. Can a recovery system be developed that utilizes only software in contrast to hardware solutions? 7. What are the major problems to be encountered in developing a software-based recovery system? Statement of the Problem Regardless of the computer's general reliability, unfortunate incidents, such as keyboard lock-up, software failures, and power outages, over which the user has no control, sometimes lead to the loss of data in memory. Most existing software products do not have the capability to restore data lost from memory. The user is compelled to either develop habits of frequently saving their data or repeat the work if there is a failure.
Load more

Recommended publications
  • Data & Computer Recovery Guidelines
    Data & Computer Recovery Guidelines Data & Computer Recovery Guidelines This document contains general guidelines for restoring computer operating following certain types of disasters. It should be noted these guidelines will not fit every type of disaster or every organization and that you may need to seek outside help to recover and restore your operations. This document is divided into five parts. The first part provides general guidelines which are independent of the type of disaster, the next three sections deal with issues surrounding specific disaster types (flood/water damage, power surge, and physical damage). The final section deals with general recommendations to prepare for the next disaster. General Guidelines 2. Your first step is to restore the computing equipment. These are general guidelines for recovering after any type If you do try to power on the existing equipment, it of disaster or computer failure. If you have a disaster is best to remove the hard drive(s) first to make sure recovery plan, then you should be prepared; however, the system will power on. Once you have determined there may be things that were not covered to help the system powers on, you can reinstall the hard drive you recover. This section is divided into two sections and power the system back on. Hopefully, everything (computer system recovery, data recovery) works at that point. Note: this should not be tried in the case of a water or extreme heat damage. Computer System Recovery 3. If the computer will not power on then you can either The first step is to get your physical computer systems try to fix the computer or in many cases it is easier, running again.
    [Show full text]
  • Data Remanence in Non-Volatile Semiconductor Memory (Part I)
    Data remanence in non-volatile semiconductor memory (Part I) Security Group Sergei Skorobogatov Web: www.cl.cam.ac.uk/~sps32/ Email: [email protected] Introduction Data remanence is the residual physical representation of data that has UV EPROM EEPROM Flash EEPROM been erased or overwritten. In non-volatile programmable devices, such as UV EPROM, EEPROM or Flash, bits are stored as charge in the floating gate of a transistor. After each erase operation, some of this charge remains. It shifts the threshold voltage (VTH) of the transistor which can be detected by the sense amplifier while reading data. Microcontrollers use a ‘protection fuse’ bit that restricts unauthorized access to on-chip memory if activated. Very often, this fuse is embedded in the main memory array. In this case, it is erased simultaneously with the memory. Better protection can be achieved if the fuse is located close to the memory but has a separate control circuit. This allows it to be permanently monitored as well as hardware protected from being erased too early, thus making sure that by the time the fuse is reset no data is left inside the memory. In some smartcards and microcontrollers, a password-protected boot- Structure, cross-section and operation modes for different memory types loader restricts firmware updates and data access to authorized users only. Usually, the on-chip operating system erases both code and data How much residual charge is left inside the memory cells memory before uploading new code, thus preventing any new after a standard erase operation? Is it possible to recover data application from accessing previously stored secrets.
    [Show full text]
  • Databridge ETL Solution Datasheet
    DATASHEET Extract and Transform MCP Host Data for Improved KEY FEATURES Client configuration tool for Analysis and Decision Support easy customization of table layout. Fast, well-informed business decisions require access to your organization’s key performance Dynamic before-and-after indicators residing on critical database systems. But the prospect of exposing those systems images (BI-AI) based on inevitably raises concerns around security, data integrity, cost, and performance. key change. 64-bit clients. For organizations using the Unisys ClearPath MCP server and its non-relational DMSII • Client-side management database, there’s an additional challenge: Most business intelligence tools support only console. relational databases. • Ability to run the client as a service or a daemon. The Only True ETL Solution for DMSII Data • Multi-threaded clients to That’s why businesses like yours are turning to Attachmate® DATABridge™. It’s the only increase processing speed. true Extract, Transform, Load (ETL) solution that securely integrates Unisys MCP DMSII • Support for Windows Server and non-DMSII data into a secondary system. 2012. • Secure automation of Unisys With DATABridge, you can easily integrate production data into a relational database or MCP data replication. another DMSII database located on an entirely different Unisys host system. And because • Seamless integration of DATABridge clients for Oracle and Microsoft SQL Server support a breadth of operating both DMSII and non-DMSII environments (including Windows 7, Windows Server 2012, Windows Server 2008, UNIX, data with Oracle, Microsoft SQL, and other relational AIX, SUSE Linux, and Red Hat Linux), DATABridge solutions fit seamlessly into your existing databases. infrastructure.
    [Show full text]
  • Database Analyst Ii
    Recruitment No.: 20.186 Date Opened: 5/25/2021 DATABASE ANALYST II SALARY: $5,794 to $8,153 monthly (26 pay periods annually) FINAL FILING DATE: We are accepting applications until closing at 5 pm, June 8, 2021 IT IS MANDATORY THAT YOU COMPLETE THE SUPPLEMENTAL QUESTIONNAIRE. YOUR APPLICATION WILL BE REJECTED IF YOU DO NOT PROVIDE ALL NECESSARY INFORMATION. THE POSITION The Human Resources Department is accepting applications for the position of Database Analyst II. The current opening is for a limited term, benefitted and full-time position in the Information Technology department, but the list may be utilized to fill future regular and full- time vacancies for the duration of the list. The term length for the current vacancy is not guaranteed but cannot exceed 36 months. The normal work schedule is Monday through Friday, 8 – 5 pm; a flex schedule may be available. The Information Technology department is looking for a full-time, limited-term Database Analyst I/II to develop and manage the City’s Open Data platform. Initiatives include tracking city council goals, presenting data related to capital improvement projects, and measuring budget performance. This position is in the Data Intelligence Division. Our team sees data as more than rows and columns, it tells stories that yield invaluable insights that help us solve problems, make better decisions, and create solutions. This position is responsible for building and maintaining systems that unlock the power of data. The successful candidate will be able to create data analytics & business
    [Show full text]
  • Error Characterization, Mitigation, and Recovery in Flash Memory Based Solid-State Drives
    ERRORS, MITIGATION, AND RECOVERY IN FLASH MEMORY SSDS 1 Error Characterization, Mitigation, and Recovery in Flash Memory Based Solid-State Drives Yu Cai, Saugata Ghose, Erich F. Haratsch, Yixin Luo, and Onur Mutlu Abstract—NAND flash memory is ubiquitous in everyday life The transistor traps charge within its floating gate, which dic- today because its capacity has continuously increased and cost has tates the threshold voltage level at which the transistor turns on. continuously decreased over decades. This positive growth is a The threshold voltage level of the floating gate is used to de- result of two key trends: (1) effective process technology scaling, termine the value of the digital data stored inside the transistor. and (2) multi-level (e.g., MLC, TLC) cell data coding. Unfortu- When manufacturing process scales down to a smaller tech- nately, the reliability of raw data stored in flash memory has also nology node, the size of each flash memory cell, and thus the continued to become more difficult to ensure, because these two trends lead to (1) fewer electrons in the flash memory cell (floating size of the transistor, decreases, which in turn reduces the gate) to represent the data and (2) larger cell-to-cell interference amount of charge that can be trapped within the floating gate. and disturbance effects. Without mitigation, worsening reliability Thus, process scaling increases storage density by enabling can reduce the lifetime of NAND flash memory. As a result, flash more cells to be placed in a given area, but it also causes relia- memory controllers in solid-state drives (SSDs) have become bility issues, which are the focus of this article.
    [Show full text]
  • EEPROM Emulation
    ...the world's most energy friendly microcontrollers EEPROM Emulation AN0019 - Application Note Introduction This application note demonstrates a way to use the flash memory of the EFM32 to emulate single variable rewritable EEPROM memory through software. The example API provided enables reading and writing of single variables to non-volatile flash memory. The erase-rewrite algorithm distributes page erases and thereby doing wear leveling. This application note includes: • This PDF document • Source files (zip) • Example C-code • Multiple IDE projects 2013-09-16 - an0019_Rev1.09 1 www.silabs.com ...the world's most energy friendly microcontrollers 1 General Theory 1.1 EEPROM and Flash Based Memory EEPROM stands for Electrically Erasable Programmable Read-Only Memory and is a type of non- volatile memory that is byte erasable and therefore often used to store small amounts of data that must be saved when power is removed. The EFM32 microcontrollers do not include an embedded EEPROM module for byte erasable non-volatile storage, but all EFM32s do provide flash memory for non-volatile data storage. The main difference between flash memory and EEPROM is the erasable unit size. Flash memory is block-erasable which means that bytes cannot be erased individually, instead a block consisting of several bytes need to be erased at the same time. Through software however, it is possible to emulate individually erasable rewritable byte memory using block-erasable flash memory. To provide EEPROM functionality for the EFM32s in an application, there are at least two options available. The first one is to include an external EEPROM module when designing the hardware layout of the application.
    [Show full text]
  • PROTECTING DATA from RANSOMWARE and OTHER DATA LOSS EVENTS a Guide for Managed Service Providers to Conduct, Maintain and Test Backup Files
    PROTECTING DATA FROM RANSOMWARE AND OTHER DATA LOSS EVENTS A Guide for Managed Service Providers to Conduct, Maintain and Test Backup Files OVERVIEW The National Cybersecurity Center of Excellence (NCCoE) at the National Institute of Standards and Technology (NIST) developed this publication to help managed service providers (MSPs) improve their cybersecurity and the cybersecurity of their customers. MSPs have become an attractive target for cyber criminals. When an MSP is vulnerable its customers are vulnerable as well. Often, attacks take the form of ransomware. Data loss incidents—whether a ransomware attack, hardware failure, or accidental or intentional data destruction—can have catastrophic effects on MSPs and their customers. This document provides recommend- ations to help MSPs conduct, maintain, and test backup files in order to reduce the impact of these data loss incidents. A backup file is a copy of files and programs made to facilitate recovery. The recommendations support practical, effective, and efficient back-up plans that address the NIST Cybersecurity Framework Subcategory PR.IP-4: Backups of information are conducted, maintained, and tested. An organization does not need to adopt all of the recommendations, only those applicable to its unique needs. This document provides a broad set of recommendations to help an MSP determine: • items to consider when planning backups and buying a backup service/product • issues to consider to maximize the chance that the backup files are useful and available when needed • issues to consider regarding business disaster recovery CHALLENGE APPROACH Backup systems implemented and not tested or NIST Interagency Report 7621 Rev. 1, Small Business planned increase operational risk for MSPs.
    [Show full text]
  • SŁOWNIK POLSKO-ANGIELSKI ELEKTRONIKI I INFORMATYKI V.03.2010 (C) 2010 Jerzy Kazojć - Wszelkie Prawa Zastrzeżone Słownik Zawiera 18351 Słówek
    OTWARTY SŁOWNIK POLSKO-ANGIELSKI ELEKTRONIKI I INFORMATYKI V.03.2010 (c) 2010 Jerzy Kazojć - wszelkie prawa zastrzeżone Słownik zawiera 18351 słówek. Niniejszy słownik objęty jest licencją Creative Commons Uznanie autorstwa - na tych samych warunkach 3.0 Polska. Aby zobaczyć kopię niniejszej licencji przejdź na stronę http://creativecommons.org/licenses/by-sa/3.0/pl/ lub napisz do Creative Commons, 171 Second Street, Suite 300, San Francisco, California 94105, USA. Licencja UTWÓR (ZDEFINIOWANY PONIŻEJ) PODLEGA NINIEJSZEJ LICENCJI PUBLICZNEJ CREATIVE COMMONS ("CCPL" LUB "LICENCJA"). UTWÓR PODLEGA OCHRONIE PRAWA AUTORSKIEGO LUB INNYCH STOSOWNYCH PRZEPISÓW PRAWA. KORZYSTANIE Z UTWORU W SPOSÓB INNY NIŻ DOZWOLONY NA PODSTAWIE NINIEJSZEJ LICENCJI LUB PRZEPISÓW PRAWA JEST ZABRONIONE. WYKONANIE JAKIEGOKOLWIEK UPRAWNIENIA DO UTWORU OKREŚLONEGO W NINIEJSZEJ LICENCJI OZNACZA PRZYJĘCIE I ZGODĘ NA ZWIĄZANIE POSTANOWIENIAMI NINIEJSZEJ LICENCJI. 1. Definicje a."Utwór zależny" oznacza opracowanie Utworu lub Utworu i innych istniejących wcześniej utworów lub przedmiotów praw pokrewnych, z wyłączeniem materiałów stanowiących Zbiór. Dla uniknięcia wątpliwości, jeżeli Utwór jest utworem muzycznym, artystycznym wykonaniem lub fonogramem, synchronizacja Utworu w czasie z obrazem ruchomym ("synchronizacja") stanowi Utwór Zależny w rozumieniu niniejszej Licencji. b."Zbiór" oznacza zbiór, antologię, wybór lub bazę danych spełniającą cechy utworu, nawet jeżeli zawierają nie chronione materiały, o ile przyjęty w nich dobór, układ lub zestawienie ma twórczy charakter.
    [Show full text]
  • Explore IBM DS8000 Safeguarded Copy
    IBM Systems Solution Brief Safeguard against cyberthreats IBM Safeguarded Copy provides powerful data protection for mission- Highlights critical environments Whether they are caused by human error, system glitches, or • Provides immutable copies of data for Logical malicious criminal acts, data breaches are among the gravest Corruption Protection and most expensive threats to today’s businesses. The annual Cost of a Data Breach Report, conducted by the • Enables hidden, non- Ponemon Institute found that the average cost worldwide of addressable backups for additional security a data breach in the preceding 12 months was $3.9M.1 • Offers simple implementation on IBM DS8900F and DS8880/F systems • Integrates with many disaster-recovery and high- availability environments The costs of a data breach rise along with the growth in the value of data. There is also a corresponding human toll. The World Economic Forum’s (WEF) 2020 Global Risks Report rated cyberattacks as one of the top risks to human welfare. 75% of those surveyed by the WEF said they expect the risk of theft of data or money from cyberattacks to increase, while 76.1% also saw an increased risk of disruption of operations.2 IBM Systems Solution Brief Organizations affected by a breach run the risk of having their normal business operations disrupted, as well as losing valuable data, customers and reputation within their industry. Over the last decades, most organizations have concentrated on developing and implementing high availability (HA) and disaster recovery (DR) solutions to protect their enterprise data against hardware and software failures or data center outages, but these measures may no longer be enough protection against cyberattacks.
    [Show full text]
  • A Modern Approach to Backup & Recovery
    A Modern Approach to Backup & Recovery Deploy in Minutes. Search Anything. Recover Anywhere. Rubrik simplifies backup and recovery for hybrid cloud environments. It eliminates legacy backup complexity by integrating data orchestration, catalog management, and continuous data protection into a single software platform. With Rubrik, enterprises can unlock cloud for long-term data retention or DR and deliver automation with an API-first software platform. Designed to be vendor-agnostic, Rubrik supports the leading operating systems, databases, hypervisors, clouds, and SaaS applications. NEAR-ZERO RPO & RTO SIMPLE TO SCALE LOWER TCO Avoid data loss and minimize Start small and leverage Rubrik’s Deliver hard savings of up to downtime with continuous data scale-out architecture to grow-as- 30-50% with the industry’s protection and instant recovery. you go without forklift upgrades. slimmest footprint. PROTECT • Intelligent Log Management: Automate log backups with policy-based • Continuous Data Protection: Rubrik enables a continuous stream management. Quickly recover from any point-in-time snapshots. of recovery points to minimize data loss in the event of a failure or • Cloud: Use cloud for long-term data retention, test/dev, or DR. ransomware attack. Enable near-zero RPOs with a single click. For applications running in the cloud, Rubrik offers cloud-native • Rapid Parallel Ingest: Minimize impact to production and eliminate data protection. application stun for highly transactional applications. Rubrik ingests • Global Management: Use Polaris GPS for centralized management of large volumes of data rapidly by maximizing the number of parallel data your distributed Rubrik environment to monitor global activity, analyze streams processed. on-demand, and troubleshoot faster.
    [Show full text]
  • Data Remanence in Flash Memory Devices
    Data Remanence in Flash Memory Devices Sergei Skorobogatov University of Cambridge, Computer Laboratory, 15 JJ Thomson Avenue, Cambridge CB3 0FD, United Kingdom [email protected] Abstract. Data remanence is the residual physical representation of data that has been erased or overwritten. In non-volatile programmable devices, such as UV EPROM, EEPROM or Flash, bits are stored as charge in the floating gate of a transistor. After each erase operation, some of this charge remains. Security protection in microcontrollers and smartcards with EEPROM/Flash memories is based on the assumption that information from the memory disappears completely after erasing. While microcontroller manufacturers successfully hardened already their designs against a range of attacks, they still have a common problem with data remanence in floating-gate transistors. Even after an erase operation, the transistor does not return fully to its initial state, thereby allowing the attacker to distinguish between previously programmed and not programmed transistors, and thus restore information from erased memory. The research in this direction is summarised here and it is shown how much information can be extracted from some microcontrollers after their memory has been ‘erased’. 1 Introduction Data remanence as a problem was first discovered in magnetic media [1,2]. Even if the information is overwritten several times on disks and tapes, it can still be possible to extract the initial data. This led to the development of special methods for reliably removing confidential information from magnetic media. Semiconductor memory in security modules was found to have similar prob- lems with reliable data deletion [3,4]. Data remanence affects not only SRAM, but also memory types like DRAM, UV EPROM, EEPROM and Flash [5].
    [Show full text]
  • Recovering from Operating System Crashes
    Recovering from Operating System Crashes Francis David Daniel Chen Department of Computer Science Department of Electrical and Computer Engineering University of Illinois at Urbana-Champaign University of Illinois at Urbana-Champaign Urbana, USA Urbana, USA Email: [email protected] Email: [email protected] Abstract— When an operating system crashes and hangs, it timers and processor support techniques [12] are required to leaves the machine in an unusable state. All currently running detect such crashes. program state and data is lost. The usual solution is to reboot the It is accepted behavior that when an operating system machine and restart user programs. However, it is possible that after a crash, user program state and most operating system state crashes, all currently running user programs and data in is still in memory and hopefully, not corrupted. In this project, volatile memory is lost and unrecoverable because the proces- we use a watchdog timer to reset the processor on an operating sor halts and the system needs to be rebooted. This is inspite system crash. We have modified the Linux kernel and added of the fact that all of this information is available in volatile a recovery routine that is called instead of the normal boot up memory as long as there is no power failure. This paper function when the processor is reset by a watchdog. This resumes execution of user processes after killing the process that was explores the possibility of recovering the operating system executing when the watchdog fired. We have implemented this using the contents of memory in order to resume execution on the ARM architecture and we use a periodic watchdog kick of user programs without any data loss.
    [Show full text]