<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi David,<br>
    <br>
    Sorry for the delay in replying.<br>
    <br>
    I still believe you can get your 120GB drive how you want it, so all
    is not lost yet.<br>
    <br>
    It looks like your LVM partition is the correct size now, but the
    volume with your root filesystem is still the old size. This
    suggests that you need to run:<br>
    <br>
    lvextend -l+100%FREE /dev/mapper/ubuntu--vg-root<br>
    <br>
    the first letter of lvextend is lower-case "L".<br>
    the second argument to lvextend is: "dash", lower-case "L",
    "plus"-symbol, one, zero, zero, percentage-symbol, and finally the
    word "FREE" in upper-case; all without spaces between.<br>
    <br>
    then run:<br>
    <br>
    resize2fs /dev/mapper/ubuntu--vg-root<br>
    <br>
    It is probably best to do these in a cd/dvd-booted live session to
    be sure it's as safe as possible.<br>
    <br>
    <div class="moz-cite-prefix">On 09/02/2016 14:53, David Goldsbrough
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAH728T9qOs6gN_oOo0GCDqMzhbAFWTVFckPZnCyP=E-r+YV4QQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>I am going to spare you Daniel all the details
                    and other readers of this post.<br>
                  </div>
                  Briefly I had documented everything and that is now
                  lost for reasons I can only guess. I had chosen your
                  Option 2 without success and then Option 1 with I hope
                  is success.  I did though suffer errors on re-boot and
                  so attempted another re-boot - this time it reported
                  fsck issues which I answered F to and all seemed fine.<br>
                </div>
                I then rebooted from the 60GB USB drive to grab the
                documentation and started up Firefox to get at my Google
                drve.  Firefox started as if this was the first time it
                had ever started - weird and accessing the google drive
                and trying to find my documentation file - it was not
                there! Odd!<br>
                <br>
              </div>
              So I reboted into my 120GB and again Firefox starts as if
              brand new - bookmarks and history have gone.  Cpuld dd
              have done that?<br>
              <br>
            </div>
            But forget that I think I now have a full 120GB system but
            am starting to have some doubts over some of the files. 
            What command should I run to give me confidence I have a
            full 120GB?<br>
          </div>
          Thanks<br>
        </div>
        DaveG<br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On 8 February 2016 at 22:49, Daniel
          Llewellyn <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:diddledan@gmail.com" target="_blank">diddledan@gmail.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr"><br>
              <div class="gmail_extra"><br>
                <div class="gmail_quote"><span class="">On 8 February
                    2016 at 22:32, David Goldsbrough <span dir="ltr"><<a
                        moz-do-not-send="true"
                        href="mailto:daveg@boavon.plus.com"
                        target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:daveg@boavon.plus.com">daveg@boavon.plus.com</a></a>></span>
                    wrote:
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      <div dir="ltr">
                        <div>
                          <div><span>$ sudo parted -l<br>
                              <br>
                              Model: ATA TOSHIBA MK1255GS (scsi)<br>
                              Disk /dev/sda: 120GB<br>
                              Sector size (logical/physical): 512B/512B<br>
                              Partition Table: msdos<br>
                              <br>
                              Number  Start   End    Size   Type     
                              File system  Flags<br>
                               1      1049kB  256MB  255MB  primary  
                              ext2         boot<br>
                            </span><span> 2      257MB   120GB  120GB 
                              extended<br>
                            </span> 5      258MB   120GB  120GB 
                            logical                lvm<br>
                            <br>
                            <br>
                            Model:  Mass Storage Device (scsi)<br>
                            Disk /dev/sdb: 60.0GB<span><br>
                              Sector size (logical/physical): 512B/512B<br>
                              Partition Table: msdos<br>
                              <br>
                              Number  Start   End     Size    Type     
                              File system  Flags<br>
                               1      1049kB  256MB   255MB   primary  
                              ext2         boot<br>
                            </span> 2      257MB   60.0GB  59.8GB 
                            extended<span><br>
                               5      257MB   60.0GB  59.8GB 
                              logical                lvm<br>
                            </span></div>
                        </div>
                      </div>
                    </blockquote>
                    <div><br>
                    </div>
                  </span>
                  <div>OK, from the above read-out it looks like fdisk
                    changed the start position of your partition when
                    you recreated it. We have two options as to how to
                    proceed:</div>
                  <div><br>
                  </div>
                  <div>
                    <ol>
                      <li>As you have your old LVM disk hooked-up you
                        can reblow the data across to the new larger
                        partition and then run the pvresize, lvextend
                        and resize2fs again thereafter. To reblow the
                        data use `dd if=/dev/sdb5 of=/dev/sda5 bs=1m`.</li>
                      <li>Alternatively you can try to recreate the lvm
                        partition again with a start of 257M instead of
                        the fdisk-chosen default 258M (it chose 258
                        because that's "aligned" better for your SSD;
                        but being 1MB further into the disk means that
                        the lvm metadata is dangling unaddressable at
                        257MB) and as above rerun the pvresize, lvextend
                        and resize2fs again.</li>
                    </ol>
                  </div>
                </div>
                <span class="">
                  <div><br>
                  </div>
                  -- <br>
                  <div>Regards,<br>
                        The Honeymonster Daniel Llewellyn</div>
                </span></div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>