Welcome to the Linux Foundation Forum!

Chapter 9 Lab 9.3

I got through lab 91 and 9.2 fine.

I was not sure what was meant by 'better still, zero it out'

I deleted the imagefile and did the dd command to create it again and then did a mkfs as in lab 9.1

There was no loop devices on my system so my parted command was:

sudo parted -s /dev/loop0 mklabel msdos

This gave me the following error

Warning: Error fsyncing/closing /dev/loop0:Input/output error

Not sure what I did wrong.

Comments

  • NYCJacob
    NYCJacob Posts: 19
    I also tried this on a fedora system and after the parted command I got
    Parted: invalid token: primary
  • coop
    coop Posts: 916
    did you do

    losetup -f

    first (to show first available loop device?)

    also do

    ls -l /dev/loop

    Everything has worked fine for me on Fedora 22

  • I am having trouble with Step 5:

    With Linux CentOS 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

    sudo ln -s /dev/mapper/loop1p1 /dev/loop1p1

    I get a return of:
    ln: failed to create symbolic link ‘/dev/loop1p1’: File exists

    But ls -la /dev/mapper/loop1* returns:
    ls: cannot access /dev/mapper/loop1*: No such file or directory

    With Linux Ubuntu-Server 3.16.0-51-generic #69~14.04.1-Ubuntu SMP Wed Oct 7 15:32:41 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

    sudo kpartx -lv /dev/loop1
    sudo: kpartx: command not found

    and

    sudo ln -s /dev/mapper/loop1p1 /dev/loop1p1
    ln: failed to create symbolic link ‘/dev/loop1p1’: File exists

    I tried apt-get install kpartx and util-linux but no packages are found.

    Linux opensus-server 3.16.6-2-desktop #1 SMP PREEMPT Mon Oct 20 13:47:22 UTC 2014 (feb42ea) x86_64 x86_64 x86_64 GNU/Linux

    ls -l /dev/mapper/loop*
    ls: cannot access /dev/mapper/loop*: No such file or directory
    jes001@opensus-server-64:~> ls -l /dev/mapper/loop1*
    ls: cannot access /dev/mapper/loop1*: No such file or directory



    Any ideas?



Categories

Upcoming Training