DOCSLIB.ORG

A Secure and Reliable Method to Protect Usb Data

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Secure and Reliable Method to Protect Usb Data APTIKOM Journal on Computer Science and Information Technologies Vol. 4, No. 2, 2019, pp. 57~60 ISSN: 2528-2417 DOI: 10.11591/APTIKOM.J. SIT.34 57 A secure and reliable method to protect usb data Alycia Sebastian* , K. Siva Sankar2 1Research Scholar, Department of Computer Science / 0n1ineerin1, Noorul Islam 2ni3ersity Thuc5alay, TamilNadu, India 2Department of Information Technolo1y, Noorul Islam 2ni3ersity Thuc5alay, TamilNadu, India 7Correspondin1 author, e-mail: alycia.sebastian91mail.com1 Abstract With technology advancement people have started using di erent type o memory devices or storing data and keeping it secure has become concern in today#s world. Universal Serial (us )US() lash drives are leading portable storage device or storage and easy trans er o data rom one computer to another. The usage o US( has grown e,ponentially and without security the data on the disk is at risk. Nowadays US( manu acturers o er password protection and ingerprint authentication to secure the US( data. .n this paper, US( is devised as a highly secured portable boot medium with ingerprint authentication to secure the data. Keywords/ boot loader, ingerprint authentication, operating system, security universal serial bus )usb) Copyright © 2019 APTIKOM - All rights reser ed. Introduction 2S: is a small, portable stora1e medium whose size ran1es from 2G: and up to 2T: are a3ailable for end users for data stora1e. 2sers can freely mo3e data and securin1 the data from unwanted access is the 5ey concern. To secure data, 2S: offers software based protection and hardware based protection. :iometric 2S: dri3e with in-built fin1erprint scanner and password protection pro3ides the maximum security for the user?s information. So many solutions ha3e been pro3ided for securin1 2S: data a1ainst unauthorized access. :ut, there is a possibility to access information when used with computer system by e3adin1 the fin1erprint authentication thereby pro3idin1 a serious threat to the user information in 2S:. So there is a need to do authentication before loadin1 the OS. :oot Loader is responsible for initializin1 and loadin1 OS into RAM. In sin1le sta1e, boot loader executes the 5ernel directly from the boot sector. In multi sta1e, boot loader follows the below steps. Sta1e 1: boot. im1 - ode is stored in the first 466 bytes of M:R. - :IOS loads sta1e 1 to the address 0x7 00. - 2ses L:A48 addressin1 to point to sta1e 1.5. - Loads sta1e 1.5 in to the memory at address 0x2200. - Jump to entry point of Sta1e1.5. Sta1e 1.5: core. im1 - Stored in the 63 bytes after M:R. - ontains file system specific code to find the operatin1 system ima1e on the AbootB file system. - Since it contains file system dri3ers it can load sta1e 2 by directly specifyin1 file path and file name. - Loads the sta1e 2 into the memory at address 0x8000. Sta1e 2: - Initializes the 1rub shell and displays the menu and command en3ironment. - Appropriate selected 5ernel ima1e is loaded into memory. - :oot 5ernel. Received May 9, 2019; Revised June 3, 2019; Accepted July 10, 2019 58 ISSN: 2528-2417 Security of the system starts from the boot process. In this paper, 2S: is de3eloped as a boot medium and the fin1erprint authentication is done upon the boot process. On successful authorization, the operatin1 system is loaded into the memory from the 2S:. This method pro3ides a secure, reliable and portable de3ice which can be used in any system with much reDuired protection for the 2S: data. Dynamic boot loader in normal boot loaders to boot from 2S:, user has to chan1e :IOS settin1s to 2S: boot which reDuires user 5nowled1e of :IOS settin1s. These types of boot loaders are static and are dependent on :IOS. The concept of dynamic boot loader is that it automatically finds the 2S: boot medium and load OS without user inter3ention E1F. This eliminates :IOS dependency, thus pro3idin1 a user friendly system and si1nificantly reducin1 the time it ta5es in chan1in1 the :IOS settin1s. The proposed desi1n on fin1erprint security for 2S: data can be inte1rated with dynamic boot loader. The inte1ration pro3ides a user friendly, secure and hi1hly portable 2S: system. 2. Related Work Much research wor5 has been successfully done in safe1uardin1 2S: information from unauthorized access but settin1 a safe en3ironment is more important in protectin1 the data. :iometric authentication has since become popular because of successful attac5s on password and PIN?s. In 2S: to5en fin1erprint authentication system, the patterns are stored in 2S: to5en but reco1nition is done in the computer system which ma5es the entire authentication system 3ulnerable to attac5. This disad3anta1e can be o3ercome by performin1 fin1erprint matchin1 inside the 2S: to5en system E2F. 2S: with Fin1erprint authentication has an inte1rated fin1erprint scanner and a pri3ate dri3e. 2ser can enroll the fin1erprint usin1 the host system. On plu1 in, it runs the fin1erprint pro1ram and on successful authorization, it opens the pri3ate partition where the user can store data. In paper E3F, the authors successfully bypassed the fin1erprint authentication by ma5in1 binary code modification in .dll file. Also they de3eloped a pro1ram that retrie3es the fin1erprint reference templates from the dri3e which poses serious security threat to user data in the 2S:. The 2ni3ersal Serial :us (2S:I is a mass stora1e de3ice which is 3ulnerable to attac5s. In paper E4F, the authors ha3e proposed a control al1orithm for mutual authentication between host and 2S: to protect 2S: documents. 2ser has to authenticate himself with user name and password and a session 5ey is 1enerated based on the username and ID of the 2S: de3ice. The 1enerated 5ey is then used to encrypt the files bein1 stored in the 2S: de3ice. 2S: is the most popular portable stora1e de3ice. Once it is lost, the information in the 2S: is prone to theft. In paper E5F, the authors ha3e discussed the 3arious ways of securin1 2S: memories while analyzin1 its 3ulnerabilities E6F. The approaches to secure 2S: can be cate1orized under software only approach, hardware supported partitionin1 approach and Hardware based encryption approach. In 1eneral, to secure data in 2S:, it has to be protected either by software or hardware or by both. 2ser authentication method li5e password, fin1erprint are for access control to the data stored in 2S: and encryption and decryption are for protectin1 data transfer between host and 2S: de3ice. 3. Proposed Design Different approaches are in use to secure 2S: de3ice from unauthorized access. The security on stored data becomes meanin1less when secure 2S: is used with a hostile host system. The attac5ers can bypass the fin1erprint authentication system and access the stored data. To eliminate this type of attac5, the paper discusses a plu1 and play Li3e 2S: where fin1erprint authentication is done before the OS is loaded from 2S: to RAM. This method 1uarantees a safe, secure and reliable portable system for user data. So now the user can store hi1hly confidential information on his li3e 2S: and use in any host system which supports 2S: bootin1. The section 3.1 discusses the bootin1 process of the proposed method and section 3.2 shows the fin1erprint secured 2S: architecture. 3. Booting Process a. After power on, the user chan1es the :IOS settin1 to boot from 2S:. Here the dynamic boot loader concept can be used to automatically identify the Li3e 2S:. b. The boot loader partition is made read only so that :IOs can detect it at boot time. c. The boot loader in 2S: is modified to call the fin1erprint authentication pro1ram at a specified address usin1 L:A48 addressin1. APTIKOM J. CSIT Vol. 4, No. 2, 2019 : 57 C 60 APTIKOM J. CSIT ISSN: 2528-2417 59 d. The fin1erprint software prompts the user to scan the fin1erprint. The fin1erprint of the user are scanned and stored before the bootin1 process usin1 the host system. The software matches the fin1erprint and 1i3es access to the secured partition if the authorization is successful. The Fi1ure 1 shows dia1ram depicts the functional desi1n of the bootin1 process of the proposed desi1n. Fi1ure 1. :ootin1 from 2S: with fin1erprint authentication 3.2. USB Architecture The bootable 2S: used comes with fin1erprint scanner inte1rated alon1 with it. A 32 G: 2S: is used. The 2S: is di3ided in to two partitions usin1 the repartition tool. The first partition contains the boot loader, the fin1erprint software and the operatin1 system. The operatin1 system and remainin1 stora1e is secured usin1 fin1erprint. Initially only boot loader and fin1erprint software are 3isible and is read only for :IOS to detect the 2S: at boot time. The second partition is public partition for the user stora1e. The Fi1ure 2 shows dia1ram the architecture desi1n of 2S:. Fi1ure 2. 2S: architecture A secure and reliable method to protect usb data )Alycia Sebastian) 60 ISSN: 2528-2417 The 2S: first partition contains the Master boot record (M:RI which has the boot loader, FAT32 file system, partition table and Dis5 si1nature E7F and fin1er print software and the remainin1 sectors are made pri3ate. The FAT32 file system is used so that the 2S: can be used in almost all system that supports 2S:. The 2S: is hardware encrypted. The OS and the pri3ate sectors are protected with fin1erprint. The 2S: can be made bootable for Linux based system or windows based system. For Linux based system, 2netbootin can be used to ma5e the 2S: bootable with Linux distributions E8F. The 2S: is formatted with FAT32 file system for Linux bootable. For Windows based system, the 2S: is formatted with NTFS file system. The 2S: is made bootable usin1 the tool winto2S:. This tool allows installin1 the windows onto a 2S: dri3e E9F.
Load more

Recommended publications
  • Oracle® Linux 7 Release Notes for Oracle Linux 7.2
    Oracle® Linux 7 Release Notes for Oracle Linux 7.2 E67200-22 March 2021 Oracle Legal Notices Copyright © 2015, 2021 Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Developer Guide（KAE Encryption & Decryption）
    Kunpeng Acceleration Engine Developer Guide（KAE Encryption & Decryption） Issue 15 Date 2021-08-06 HUAWEI TECHNOLOGIES CO., LTD. Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Issue 15 (2021-08-06) Copyright © Huawei Technologies Co., Ltd. i Kunpeng Acceleration Engine Developer Guide（KAE Encryption & Decryption） Contents Contents 1 Overview....................................................................................................................................1
    [Show full text]
  • Practical Migration from IBM X86 to Linux on IBM System Z
    Front cover Practical Migration from x86 to Linux on IBM System z A guide to migrating popular applications and services from Linux on x86 to Linux on System z Practical guidance on planning, analysis, and TCO Comprehensive hands-on migration case study Lydia Parziale Eduardo Simoes Franco Craig Gardner Berthold Gunreben Tito Ogando Serkan Sahin ibm.com/redbooks International Technical Support Organization Practical Migration from x86 to Linux on IBM System z September 2014 SG24-8217-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (September 2014) This edition applies to z/VM Version 6.3, DB2 Version 10.5, SUSE Linux Enterprise Server Version 11, and Red Hat Enterprise Linux Version 6. Versions of other software components are incident to the versions available from the respective distributions referenced above. © Copyright International Business Machines Corporation 2014. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Now you can become a published author, too! . xi Comments welcome. xii Stay connected to IBM Redbooks . xii Chapter 1. Benefits of migrating workloads to Linux on System z . 1 1.1 Benefits . 2 1.2 Reasons to select Linux on System z . 3 1.2.1 System z strengths . 3 1.3 A new type of information technology: Workload centric . 5 1.4 Workload-centric cloud . 7 1.5 Enterprise cloud computing blueprint for System z. 9 1.5.1 Empowered virtualization management: IBM Wave for z/VM.
    [Show full text]
  • Oracle® Linux 7 Release Notes for Oracle Linux 7
    Oracle® Linux 7 Release Notes for Oracle Linux 7 E53499-20 March 2021 Oracle Legal Notices Copyright © 2011,2021 Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Navigating Linux Systems
    Navigating Linux Systems Amit Jain, Luke Hindman, and John Rickerd Last Revised: August 6, 2018 c 2018 Amit Jain, Luke Hindman, and John Rickerd Acknowledgments This material is based upon work supported by the National Science Foundation under Award No. 1623189. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation The authors would especially like to thank Ariel Marvasti and Phil Gore for their proof reading and suggestions. 2 Contents 1 Departmental Computing Facilities 7 2 Whom to ask for help? 8 3 Beginner’s Guide 9 3.1 Getting started ....................................... 10 3.1.1 Logging in ...................................... 10 3.1.2 Changing your password .............................. 10 3.1.3 Logging out of the system ............................. 10 3.2 Some basics ......................................... 10 3.2.1 Correcting your typing ............................... 10 3.2.2 Special keys ..................................... 10 3.2.3 Case sensitivity ................................... 11 3.2.4 How to find information? ............................. 11 3.3 Files and directories .................................... 13 3.3.1 File names ..................................... 13 3.3.2 Creating files and directories ........................... 14 3.3.3 Your current directory ............................... 14 3.3.4 Changing directories ................................ 14 3.3.5 Your home directory ................................ 14 3.3.6 Special directories ................................. 14 3.3.7 Special files ..................................... 15 3.3.8 Viewing the contents of a text file ........................ 15 3.3.9 Listing files and directories ............................ 15 3.3.10 Wild-cards and file name completion ....................... 16 3.3.11 Copying files or directories ............................ 16 3.3.12 Renaming a file or directory: ..........................
    [Show full text]
  • Lab Worksheet and Assignment Twelve Disks, Partitions, and File Systems
    CST8207: GNU/Linux Operating Systems I Lab Worksheet and Assignment Twelve Disks, Partitions, and File Systems This is Worksheet and Assignment 12 This is a combined Worksheet and Assignment.. Quizzes and tests may refer to work done in this Worksheet and Assignment; save your answers. You will use a checking program at the end of the assignment to verify the correctness of your work. You must upload the check program results before the due date. Before you get started - REMEMBER TO READ ALL THE WORDS You must have your own Fedora 12 virtual machine (with root permissions) running to do this lab. You cannot do this assignment on the Course Linux Server because you do not have root permissions on that machine. Disks, Partitions, and File Systems 1 Commands, topics, and features covered Use the on-line help (man command) for the commands listed below for more information. ➢ df – show mounted partitions and amount of used/free space ➢ du – recursively display disk usage in directories ➢ eject – unmount and eject a CDROM ➢ fdisk – to display, create, delete, and manage partitions; option -l is very useful ➢ file – determine what kind of thing a pathname is. Can show partition file system types using option -s and will follow (dereference) symbolic links using option -L (upper case) ➢ mkfs – create a file system on a device, usually a hard disk partition. ➢ mkswap – initialize a partition for use as a Linux swap partition. ➢ mount – mount a file system existing on some device into the main file system tree. ➢ swapon – tell the Linux kernel to use an initialized swap partition.
    [Show full text]
  • Aligning Partitions to Maximize Storage Performance
    An Oracle Technical White Paper November 2012 Aligning Partitions to Maximize Storage Performance Aligning Partitions to Maximize Storage Performance Table of Contents Introduction ......................................................................................... 4 Preparing to Use a Hard Disk ............................................................. 6 How Disks Work.............................................................................. 6 Disk Addressing Methods ............................................................... 7 Hard Disk Interfaces ....................................................................... 7 Advanced Technology Attachment (ATA) ..............................................8 Serial ATA (SATA)..................................................................................8 Small Computer System Interface (SCSI) ..............................................8 Serial Attached SCSI (SAS) ...................................................................8 Fibre Channel (FC).................................................................................8 iSCSI ......................................................................................................8 Storage Natural Block Sizes ........................................................... 9 Applying Partitions to Disk Drives ..................................................... 10 Changing Standards for Partitioning ............................................. 10 How Changing Standards Affect Partition Tools and Alignment... 11 Using
    [Show full text]
  • Red Hat Enterprise Linux 4 System Administration Guide
    Red Hat Enterprise Linux 4 System Administration Guide Red Hat Enterprise Linux 4: System Administration Guide Copyright © 2005 Red Hat, Inc. Red Hat, Inc. 1801 Varsity Drive Raleigh NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park NC 27709 USA rhel-sag(EN)-4-Print-RHI (2005-06-06T17:10U1) Copyright © 2005 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other countries. All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the [email protected] key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E Table of Contents Introduction.......................................................................................................................................... i 1. Changes To This Manual ....................................................................................................... i 2.
    [Show full text]
  • Managing ZFS File Systems in Oracle® Solaris 11.4
    ® Managing ZFS File Systems in Oracle Solaris 11.4 Part No: E61017 February 2021 Managing ZFS File Systems in Oracle Solaris 11.4 Part No: E61017 Copyright © 2006, 2021, Oracle and/or its affiliates. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or
    [Show full text]
  • Design of a Dynamic Boot Loader for Loading an Operating System
    Journal of Computer Science Original Research Paper Design of a Dynamic Boot Loader for Loading an Operating System 1Alycia Sebastian and 2Dr. K. Siva Sankar 1Research Scholar, Department of Computer Science and Engineering, Noorul Islam Centre for Higher Education, Tamil Nadu, India 2Department of Information Technology, Noorul Islam Centre for Higher Education, Tamil Nadu, India Article history Abstract: Boot Loader is the crucial program that loads the operating Received: 26-08-2018 system in memory and initializes the system. In today’s world people are Revised: 22-09-2018 constantly on move and portable system are in demand specially the Accepted: 25-01-2019 USB devices due to its portability and accessibility compared to CD/DVD drives. The purpose of this paper is to design a dynamic boot loader which Corresponding Author: Alycia Sebastian removes the BIOS dependency and allow user to boot from USB without Department of Computer changing CMOS settings. The USB is devised as plug and play portable Science and Engineering, Noorul system with puppy Linux and newly developed dynamic boot loader. The Islam Centre for Higher device is experimented on a computer machine with 8 GB RAM, i5 Education, Tamil Nadu, India processor, 64-bit Operating system and windows 7 and observed that nearly Email: [email protected] 50% reduction in booting time i.e., the time spent in changing the boot order is eliminated compared to the static boot loader. The time spent in the BIOS is dependent on the user knowledge in changing the boot priority. The portable system allows the user to work in ease in any environment with minimum requirement of Windows XP and USB 2.0 compatible system.
    [Show full text]
  • Storage & File Systems
    6.2. HDDS 61 to them as pages). A reading/writing head per surface allows storing and reading data. Chapter 6 25 24 26 23 12 11 3 10 22 13 4 21 0 2 9 1 5 14 8 20 6 7 15 Storage & File Systems 19 16 18 17 How does your computer persistently store your data? 6.1 Storage Interface Figure 6.4: Left: schematic of an HDD with 3 platters. Right: geometry of a single platter with 3 tracks and a total of 27 pages. Definition 6.1 (Storage Device, Pages, Address Space). A storage device consists of n pages (also known as sectors or blocks in the literature) of fixed Remarks: size, e.g. 512 bytes per page. The address space of the device is 0 to n 1. To write to or read from a storage device, the OS specifies the address(es) of− the • One could put multiple read/write heads per surface into the HDD, page(s) it wants to access, and in case of a write, it also specifies the data to be or give each head its own motor to move independently of the others. written. Neither of these options is put into practice in modern HDDs. • Since inner tracks closer to the spindle cover less area than outer Remarks: tracks further away, inner tracks have fewer pages per track. • There are many different types of storage devices: HDDs, SSDs, tapes, • On real HDDs, the platter is often subdivided into zones of tracks DVDs, etc. where all tracks in a zone have the same number of pages.
    [Show full text]
  • Freenas® 11.1-U7 User Guide
    FreeNAS® 11.1-U7 User Guide January 2019 Edition FreeNAS® is © 2011-2019 iXsystems FreeNAS® and the FreeNAS® logo are registered trademarks of iXsystems FreeBSD® is a registered trademark of the FreeBSD Foundation Written by users of the FreeNAS® network-attached storage operating system. Version 11.1 Copyright © 2011-2019 iXsystems (https://www.ixsystems.com/) CONTENTS Welcome .............................................................. 8 Typographic Conventions ..................................................... 10 1 Introduction 11 1.1 New Features in 11.1 .................................................... 11 1.2 Changes Since 11.1 ..................................................... 13 1.2.1 U1 .......................................................... 13 1.2.2 U2 .......................................................... 13 1.2.3 U3 .......................................................... 14 1.2.4 U5 .......................................................... 14 1.2.5 U6 .......................................................... 14 1.2.6 U6.3 ......................................................... 14 1.2.7 U7 .......................................................... 14 1.3 Path and Name Lengths .................................................. 15 1.4 Hardware Recommendations ............................................... 16 1.4.1 RAM ......................................................... 16 1.4.2 The Operating System Device ........................................... 17 1.4.3 Storage Disks and Controllers ..........................................
    [Show full text]