DOCSLIB.ORG

Setup Software RAID1 Array on Running Centos 6.3 Using Mdadm

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Setup Software RAID1 Array on Running Centos 6.3 Using Mdadm Setup software RAID1 array on running CentOS 6.3 using mdadm. (Multiple Device Administrator) All commands run from terminal as super user. Default CentOS 6.3 installation with two hard drives, /dev/sda and /dev/sdb which are identical in size. Machine name is “serverbox.local”. /dev/sdb is currently unused, and /dev/sda has the following partitions: /dev/sda1: /boot partition, ext4; /dev/sda2: is used for LVM (volume group vg_serverbox) and contains / (volume root), swap (volume swap_1) and /home (volume home). Final RAID1 configuration: /dev/md0 (made up of /dev/sda1 and /dev/sdb1): /boot partition, ext4; /dev/md1 (made up of /dev/sda2 and /dev/sdb2): LVM (volume group vg_serverbox), contains / (volume root), swap (volume swap_1) and /home (volume home). 1. Gather information about current system. Report the current disk space usage: df -h View physical disks: fdisk -l View physical volumes on logical disk partition: pvdisplay View virtual group details: vgdisplay View Logical volumes: lvdisplay Load kernel modules (to avoid a reboot): modprobe linear modprobe raid0 modprobe raid1 Verify personalities: cat /proc/mdstat The output should look as follows: serverbox:~# cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] unused devices: <none> 2. Preparing /dev/sdb To create a RAID1 array on a running system, prepare the /dev/sdb hard drive for RAID1, then copy the contents of /dev/sda hard drive to it, and finally add /dev/sda to the RAID1 array. Copy the partition table from /dev/sda to /dev/sdb so that both disks have exactly the same layout: sfdisk -d /dev/sda | sfdisk –f /dev/sdb Verify both disks are partitioned identically: fdisk -l Change the partition type of partitions on /dev/sdb to Linux raid autodetect: fdisk /dev/sdb serverbox:~# fdisk /dev/sdb Command (m for help): t [t = change a partition's system id] Partition number (1-5): 1 Hex code (type L to list codes): fd [fd = Linux raid auto] Command (m for help): t Partition number (1-5): 2 Hex code (type L to list codes): fd Command (m for help): w [w = write changes to disk] Verify changes written successfully: fdisk -l Remove any previous RAID installations on /dev/sdb : (error displayed if none exist) mdadm --zero-superblock /dev/sdb1 mdadm --zero-superblock /dev/sdb2 3. Creating RAID Arrays Create RAID arrays /dev/md0 and /dev/md1. /dev/sdb1 will be added to /dev/md0 and/dev/sdb2 to /dev/md1. mdadm --create /dev/md0 --metadata=0.90 --level=1 --raid-disks=2 missing /dev/sdb1 mdadm --create /dev/md1 --metadata=0.90 --level=1 --raid-disks=2 missing /dev/sdb2 Verify array created: ([_U] or [U_] means that an array is degraded while [UU] means that the array is ok) cat /proc/mdstat Create a file system (ext4) on our non-LVM RAID array /dev/md0: mkfs.ext4 /dev/md0 Logical volumes: Initialize physical volume /dev/md1 for LVM: (Logical Volume Manager) pvcreate /dev/md1 Add /dev/md1 to our volume group vg_serverbox: vgextend vg_serverbox /dev/md1 Verify array /dev/md1 added to logical volume group: pvdisplay Review volume group details: (optional) vgdisplay Update configuration file /etc/mdadm.conf : cp /etc/mdadm.conf /etc/mdadm.conf_orig mdadm --examine --scan >> /etc/mdadm.conf Review the updated configuration file: (Array devices added at end.) cat /etc/mdadm.conf Modify file /etc/fstab. Replace /dev/sda1 with /dev/md0 so that the line looks as follows: gedit /etc/fstab [...] /dev/md0 /boot ext4 defaults 0 2 [...] Modify file /etc/mtab. Replace line containing /dev/sda1 with /dev/md0: gedit /etc/mtab [...] /dev/md0 /boot ext3 rw 0 0 [...] Open /boot/grub/menu.lst and add fallback 1 right after default 0: gedit /boot/grub/menu.lst [...] default 0 fallback 1 [...] Duplicate first kernel stanza [title ... savedefault]. In first stanza; replace root (hd0,0) with root (hd1,0): [...] title Vg_serverbox GNU/Linux, kernel 2.6.18-6-686 root (hd1,0) kernel /vmlinuz-2.6.18-6-686 root=/dev/mapper/vg_serverbox-root ro initrd /initrd.img-2.6.18-6-686 savedefault title Vg_serverbox GNU/Linux, kernel 2.6.18-6-686 root (hd0,0) kernel /vmlinuz-2.6.18-6-686 root=/dev/mapper/vg_serverbox-root ro initrd /initrd.img-2.6.18-6-686 savedefault [...] * REMOVE any kernel options that prevent loading md devices (not ‘dm’). Rebuild initramfs using mdadm.conf: https://wiki.ubuntu.com/Initramfs mv /boot/initramfs-$(uname –r).img /boot/initramfs-$(uname –r).img.old dracut --mdadmconf --force /boot/initramfs-$(uname –r).img $(uname –r) 4. Moving Data to the RAID Arrays Copy data from boot partition /dev/sda1 to array /dev/md0: (assuming /dev/sda1 is mounted at /boot) mkdir /mnt/raid mount /dev/md0 /mnt/raid cd /boot; find . –depth | cpio –pmd /mnt/raid touch /mnt/raid/.autorelabel sync umount /mnt/raid Move the contents of LVM partition /dev/sda2 to LVM RAID array /dev/md1: (takes approx. 45 min. for 200 GB) pvmove /dev/sda2 /dev/md1 Remove /dev/sda2 from the volume group vg_serverbox: vgreduce vg_serverbox /dev/sda2 Remove volume /dev/sda2 from LVM: pvremove /dev/sda2 Verify /dev/md1 is the only physical volume for volume group vg_serverbox: pvdisplay Change the partition type of /dev/sda2 to Linux raid autodetect: fdisk /dev/sda Command (m for help): t Partition number (1-5): 2 Hex code (type L to list codes): fd Command (m for help): w The partition table has been altered! Add /dev/sda2 to /dev/md1 array: (Takes approx. 35 min. for 200 GB array to be rebuilt) mdadm --add /dev/md1 /dev/sda2 Monitor rebuild in progress: (To leave watch, press CTRL+C.) watch –n 5 cat /proc/mdstat 5. Preparing GRUB Install the GRUB bootloader on the hard drive /dev/sda and /dev/sdb: grub grub> root (hd0,0) setup (hd0) root (hd1,0) setup (hd1) quit Verify system will boot: reboot After system reboots verify /dev/md0 is mounted at /boot: df -h Verify arrays are active: (status should be /dev/md1 [UU] and /dev/md0 [_U] ) cat /proc/mdstat Verify logical volumes using pvdisplay, vgdisplay, and lvdisplay : (optional) pvdisplay vgdisplay lvdisplay Change the partition type of /dev/sda1 to Linux raid autodetect: fdisk /dev/sda Command (m for help): t Partition number (1-5): 1 Hex code (type L to list codes): fd Command (m for help): w Add /dev/sda1 to the /dev/md0 RAID array: (takes < 1 min.) mdadm --add /dev/md0 /dev/sda1 Verify both volumes are active and running [UU]: cat /proc/mdstat Update /etc/mdadm.conf : cp /etc/mdadm.conf_orig /etc/mdadm.conf mdadm --examine --scan >> /etc/mdadm.conf Reboot the system: reboot That's it - software RAID1 array is active and running! Testing and rebuilding Physically remove drive from system, or; Simulate a hard drive failure. [ /dev/sdb ] mdadm --manage /dev/md0 --fail /dev/sdb1 mdadm --manage /dev/md1 --fail /dev/sdb2 mdadm --manage /dev/md0 --remove /dev/sdb1 mdadm --manage /dev/md1 --remove /dev/sdb2 Shut down the system: shutdown -h now Reboot: System should boot in degraded state. Verify array is active but degraded: ( [_U] or [U_] ) cat /proc/mdstat Shut down the system: shutdown -h now Put in a new /dev/sdb drive, or if failure of /dev/sda, move /dev/sdb to failed /dev/sda slot and connect the new HDD as /dev/sdb. Boot the system. Verify /dev/sda is boot device and /dev/sdb is empty. fdisk -l Copy the partition table of /dev/sda to /dev/sdb: sfdisk -d /dev/sda | sfdisk –f /dev/sdb Remove any remains of the RAID array from /dev/sdb: mdadm --zero-superblock /dev/sdb1 mdadm --zero-superblock /dev/sdb2 Add /dev/sdb to the RAID array: mdadm -a /dev/md0 /dev/sdb1 mdadm -a /dev/md1 /dev/sdb2 Monitor the rebuilding process: watch –n 5 cat /proc/mdstat Wait until the synchronization has finished: Install the bootloader on both HDDs: grub grub> root (hd0,0) setup (hd0) root (hd1,0) setup (hd1) quit That's it. Failed hard drive in RAID1 array is replaced. .
Load more

Recommended publications
  • Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4
    SUSE Linux Enterprise Server 12 SP4 Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4 Provides information about how to manage storage devices on a SUSE Linux Enterprise Server. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xii 1 Available Documentation xii 2 Giving Feedback xiv 3 Documentation Conventions xiv 4 Product Life Cycle and Support xvi Support Statement for SUSE Linux Enterprise Server xvii • Technology Previews xviii I FILE SYSTEMS AND MOUNTING 1 1 Overview
    [Show full text]
  • NVIDIA Magnum IO Gpudirect Storage
    NVIDIA Magnum IO GPUDirect Storage Installation and Troubleshooting Guide TB-10112-001_v1.0.0 | August 2021 Table of Contents Chapter 1. Introduction........................................................................................................ 1 Chapter 2. Installing GPUDirect Storage.............................................................................2 2.1. Before You Install GDS.............................................................................................................2 2.2. Installing GDS............................................................................................................................3 2.2.1. Removal of Prior GDS Installation on Ubuntu Systems...................................................3 2.2.2. Preparing the OS................................................................................................................3 2.2.3. GDS Package Installation.................................................................................................. 4 2.2.4. Verifying the Package Installation.....................................................................................4 2.2.5. Verifying a Successful GDS Installation............................................................................5 2.3. Installed GDS Libraries and Tools...........................................................................................6 2.4. Uninstalling GPUDirect Storage...............................................................................................7 2.5. Environment
    [Show full text]
  • How Netflix Tunes EC2 Instances for Performance
    CMP325 How Netflix Tunes EC2 Instances for Performance Brendan Gregg, Performance and OS Engineering Team November 28, 2017 © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Netflix performance and operating systems team • Evaluate technology - Instance types, Amazon Elastic Compute Cloud (EC2) options • Recommendations and best practices - Instance kernel tuning, assist app tuning • Develop performance tools - Develop tools for observability and analysis • Project support - New database, programming language, software change • Incident response - Performance issues, scalability issues © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Agenda 1. Instance selection 2. Amazon EC2 features 3. Kernel tuning 4. Methodologies 5. Observability © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Warnings • This is what’s in our medicine cabinet • Consider these “best before: 2018” • Take only if prescribed by a performance engineer © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. 1. Instance selection © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. The Netflix cloud Many application workloads: Compute, storage, caching… EC2 Applications (services) S3 ELB Elasticsearch Cassandra EVCache SES SQS © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Netflix AWS environment • Elastic Load Balancing ASG Cluster allows real load testing prod1 ELB 1. Single instance canary, then, Canary 2. Auto scaling group • Much better than micro- ASG-v010 ASG-v011 benchmarking alone, which … … is error prone Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
    [Show full text]
  • Setting up Software RAID in Ubuntu Server | Secu
    Setting up software RAID in Ubuntu Server | Secu... http://advosys.ca/viewpoints/2007/04/setting-up-so... Setting up software RAID in Ubuntu Server April 24th, 2007 Posted by Derrick Webber Updated Mar 13 2009 to reflect improvements in Ubuntu 8.04 and later. Linux has excellent software-based RAID built into the kernel. Unfortunately information on configuring and maintaining it is sparse. Back in 2003, O’Reilly published Managing RAID on Linux and that book is still mostly up to date, but finding clear instructions on the web for setting up RAID has become a chore. Here is how to install Ubuntu Server with software RAID 1 (disk mirroring). This guide has been tested on Ubuntu Server 8.04 LTS (Hardy Heron). I strongly recommend using Ubuntu Hardy or later if you want to boot from RAID1. Software RAID vs. hardware RAID Some system administrators still sneer at the idea of software RAID. Years ago CPUs didn’t have the speed to manage both a busy server and RAID activities. That’s not true any more, especially when all you want to do is mirror a drive with RAID1. Linux software RAID is ideal for mirroring, and due to kernel disk caching and buffering it can actually be faster than RAID1 on lower end RAID hardware. However, for larger requirements like RAID 5, the CPU can still get bogged down with software RAID. Software RAID is inexpensive to implement: no need for expensive controllers or identical drives. Software RAID works 1 de 23 27/09/09 13:41 Setting up software RAID in Ubuntu Server | Secu..
    [Show full text]
  • Ubuntu Server Guide Basic Installation Preparing to Install
    Ubuntu Server Guide Welcome to the Ubuntu Server Guide! This site includes information on using Ubuntu Server for the latest LTS release, Ubuntu 20.04 LTS (Focal Fossa). For an offline version as well as versions for previous releases see below. Improving the Documentation If you find any errors or have suggestions for improvements to pages, please use the link at thebottomof each topic titled: “Help improve this document in the forum.” This link will take you to the Server Discourse forum for the specific page you are viewing. There you can share your comments or let us know aboutbugs with any page. PDFs and Previous Releases Below are links to the previous Ubuntu Server release server guides as well as an offline copy of the current version of this site: Ubuntu 20.04 LTS (Focal Fossa): PDF Ubuntu 18.04 LTS (Bionic Beaver): Web and PDF Ubuntu 16.04 LTS (Xenial Xerus): Web and PDF Support There are a couple of different ways that the Ubuntu Server edition is supported: commercial support and community support. The main commercial support (and development funding) is available from Canonical, Ltd. They supply reasonably- priced support contracts on a per desktop or per-server basis. For more information see the Ubuntu Advantage page. Community support is also provided by dedicated individuals and companies that wish to make Ubuntu the best distribution possible. Support is provided through multiple mailing lists, IRC channels, forums, blogs, wikis, etc. The large amount of information available can be overwhelming, but a good search engine query can usually provide an answer to your questions.
    [Show full text]
  • Software-RAID-HOWTO.Pdf
    Software-RAID-HOWTO Software-RAID-HOWTO Table of Contents The Software-RAID HOWTO...........................................................................................................................1 Jakob Østergaard [email protected] and Emilio Bueso [email protected] 1. Introduction..........................................................................................................................................1 2. Why RAID?.........................................................................................................................................1 3. Devices.................................................................................................................................................1 4. Hardware issues...................................................................................................................................1 5. RAID setup..........................................................................................................................................1 6. Detecting, querying and testing...........................................................................................................2 7. Tweaking, tuning and troubleshooting................................................................................................2 8. Reconstruction.....................................................................................................................................2 9. Performance.........................................................................................................................................2
    [Show full text]
  • Quick Reference 11 Unix Linux Troubleshooting
    Quick Reference Card 11 Linux Troubleshooting Your? host logo Boot Process #Boot steps: Recover from an unknown root password BIOS #EFI is successor for e.g. IA64, #1) Start single user mode, then passwd #Extensible Firmware Interface #2) Boot from a Linux CD, su -, mount / partition: mount /dev/hda3 /mnt mbr #Create backup (if is input file, of=output) # Remove the x in the /mnt/etc/passwd file (second field on the root line) dd if=/dev/hda of=/tmp/mbr bs=512 count=1 #3) Run passwd in the Rescue Mode file /tmp/mbr #Check -> x86 boot sector #4) Add kernel boot parameter: init=/bin/sh hexdump /tmp/mbr #See inside copied mbr #See also: Lab ad endum at Roberts_Quick_References khexdump /tmp/mbr #Install via: yast2 -i kdeutils-extra, or ghex2 /tmp/mbr #Package: rpm -qf $(which ghex2) Fix bootloader #Last 2 Bytes 'magic number': 55 AA #Start in Rescue Mode, and at the first prompt: boot loader #GRUB or LILO. #Type zast or yast #German keyboard work around :-) #GRUB supports TFTP network boot, serial console, shell: #System, Boot Loader Configuration, Reset <Alt-e>, #In bootgui: press <Esc>, <C> grub command line, or grub from Linux CLI #Propose New Configuration, Finish <Alt-f> help #Show GRUB commands find /boot/vmlinuz #Returns partition with kernel YaST boot into system #To live with a damaged boot loader find /etc/fstab #Returns / partition (Starts with 0, not 1) #Start from (any version) CD1 #Tip: Hardcode IDE disks in BIOS, not on 'automatic' #Start Installation, License Agreement, Language, Boot Installed System #Kernel options: less /usr/src/linux/Documentation/kernel-parameters.txt Rescue Mode #Change setup of a non bootable machine: vi /boot/grub/device.map #Map GRUB names to Linux names, e.g.: #Boot from CD1 (any version, highest SP for driver support) (hd0) /dev/hda #Select Rescue System, and login as root grub-md5-crypt #Create encrypted password for menu.lst grub #Find the / partition: init #PID 1 find /etc/fstab exit Software RAID #Mirror of /boot: LILO only, not GRUB! mount /dev/hda3 /mnt #Mount / partition #Hardware RAID is prefer., if not SATA, e.g.
    [Show full text]
  • A Secure, Reliable and Performance-Enhancing Storage Architecture Integrating Local and Cloud-Based Storage
    Brigham Young University BYU ScholarsArchive Theses and Dissertations 2016-12-01 A Secure, Reliable and Performance-Enhancing Storage Architecture Integrating Local and Cloud-Based Storage Christopher Glenn Hansen Brigham Young University Follow this and additional works at: https://scholarsarchive.byu.edu/etd Part of the Electrical and Computer Engineering Commons BYU ScholarsArchive Citation Hansen, Christopher Glenn, "A Secure, Reliable and Performance-Enhancing Storage Architecture Integrating Local and Cloud-Based Storage" (2016). Theses and Dissertations. 6470. https://scholarsarchive.byu.edu/etd/6470 This Thesis is brought to you for free and open access by BYU ScholarsArchive. It has been accepted for inclusion in Theses and Dissertations by an authorized administrator of BYU ScholarsArchive. For more information, please contact [email protected], [email protected]. A Secure, Reliable and Performance-Enhancing Storage Architecture Integrating Local and Cloud-Based Storage Christopher Glenn Hansen A thesis submitted to the faculty of Brigham Young University in partial fulfillment of the requirements for the degree of Master of Science James Archibald, Chair Doran Wilde Michael Wirthlin Department of Electrical and Computer Engineering Brigham Young University Copyright © 2016 Christopher Glenn Hansen All Rights Reserved ABSTRACT A Secure, Reliable and Performance-Enhancing Storage Architecture Integrating Local and Cloud-Based Storage Christopher Glenn Hansen Department of Electrical and Computer Engineering, BYU Master of Science The constant evolution of new varieties of computing systems - cloud computing, mobile devices, and Internet of Things, to name a few - have necessitated a growing need for highly reliable, available, secure, and high-performing storage systems. While CPU performance has typically scaled with Moore’s Law, data storage is much less consistent in how quickly perfor- mance increases over time.
    [Show full text]
  • Lustre 1.8 Operations Manual
    Lustre™ 1.8 Operations Manual Part No. 821-0035-12 Lustre manual version: Lustre_1.8_man_v1.4 June 2011 Copyright© 2007-2010 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Sun, Sun Microsystems, the Sun logo and Lustre are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Products covered by and information contained in this service manual are controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited. DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License. To view a copy of this license and obtain more information about Creative Commons licensing, visit Creative Commons Attribution-Share Alike 3.0 United States or send a letter to Creative Commons, 171 2nd Street, Suite 300, San Francisco, California 94105, USA.
    [Show full text]
  • Discover and Tame Long-Running Idling Processes in Enterprise Systems
    Discover and Tame Long-running Idling Processes in Enterprise Systems Jun Wang1, Zhiyun Qain2, Zhichun Li3, Zhenyu Wu3, Junghwan Rhee3, Xia Ning4, Peng Liu1, Guofei Jiang3 1Penn State University, 2University of California, Riverside, 3NEC Labs America, Inc. 4IUPUI 1{jow5222, pliu}@ist.psu.edu, [email protected], 3{zhichun, adamwu, rhee, gfj}@nec-labs.com, [email protected] ABSTRACT day's enterprise systems are so complex that it is hard to un- Reducing attack surface is an effective preventive measure to derstand which program/process can be the weakest links. strengthen security in large systems. However, it is challeng- Many security breaches start with the compromise of pro- ing to apply this idea in an enterprise environment where cesses running on an inconspicuous workstation. Therefore, systems are complex and evolving over time. In this pa- it is beneficial to turn off unused services to reduce their cor- per, we empirically analyze and measure a real enterprise to responding attack surface. Anecdotally, many security best identify unused services that expose attack surface. Inter- practice guidelines [12,9] suggest system administrators to estingly, such unused services are known to exist and sum- reduce attack surface by disabling unused services. How- marized by security best practices, yet such solutions require ever, such knowledge needs to be constantly updated and it significant manual effort. is unfortunate that no formal approach has been studied to We propose an automated approach to accurately detect automatically identify such services. the idling (most likely unused) services that are in either Prior research has mostly focused on the line of anomaly blocked or bookkeeping states.
    [Show full text]
  • DGX Software with Centos
    DGX Software with CentOS Installation Guide RN-09301-002 _v04 | May 2021 Table of Contents Chapter 1. Introduction........................................................................................................ 1 1.1. Related Documentation............................................................................................................ 1 1.2. Prerequisites............................................................................................................................. 1 1.2.1. Access to Repositories.......................................................................................................2 1.2.1.1. NVIDIA Repositories.....................................................................................................2 1.2.1.2. CentOS Repositories....................................................................................................2 1.2.2. Network File System..........................................................................................................2 1.2.3. BMC Password................................................................................................................... 2 Chapter 2. Installing CentOS................................................................................................4 2.1. Obtaining CentOS...................................................................................................................... 4 2.2. Booting CentOS ISO Locally....................................................................................................
    [Show full text]
  • Gl615 Linux for Unix Administrators Rhel7 Sles12
    EVALUATION COPY Unauthorized Reproduction or Distribution Linux for Unix AdministratorsProhibited Student Workbook EVALUATION COPY Unauthorized Reproduction GL615 LINUX FOR UNIX ADMINISTRATORS RHEL7 SLES12 or Distribution The contents of this course and all its modules and related materials, including handouts to audience members, are copyright ©2017 Guru Labs L.C. No part of this publication may be stored in a retrieval system, transmitted or reproduced in any way, including, but not limited to, photocopy, photograph, magnetic, electronic or other record, without the prior written permission of Guru Labs. This curriculum contains proprietary information which is for the exclusive use of customers of Guru Labs L.C., and is not to be shared with personnel other than those in attendance at this course. This instructional program, including all material provided herein, is supplied without any guarantees from Guru Labs L.C. Guru Labs L.C. assumes no liability for damages or legal action arising from Prohibited the use or misuse of contents or details contained herein. Photocopying any part of this manual without prior written consent of Guru Labs L.C. is a violation of federal law. This manual should not appear to be a photocopy. If you believe that Guru Labs training materials are being photocopied without permission, please email [email protected] or call 1-801-298-5227. Guru Labs L.C. accepts no liability for any claims, demands, losses, damages, costs or expenses suffered or incurred howsoever arising from or in connection with the
    [Show full text]