Page 4 of 7 FirstFirst ... 23456 ... LastLast
Results 31 to 40 of 64

Thread: Disk use analyzer claims almost out of space

  1. #31
    Join Date
    Jul 2009
    Beans
    240

    Re: Disk use analyzer claims almost out of space

    Is there a problem deleting the oldest backups? They are about 54 MB each and there are 80 of them. Wouldn't that be the easiest? And then do a full backup of the current system.
    If you can't take a hoof - don't stand behind the mule

  2. #32
    Join Date
    Aug 2009
    Location
    United States
    Beans
    4,486
    Distro
    Ubuntu Development Release

    Re: Disk use analyzer claims almost out of space

    Hi i would like to see screen shot of Gparted
    sudo apt-get install gparted
    gparted will tell if we can add more space to your partition
    Remember hence where you come and pass it down.
    Ubuntu Forums member #899097 and Ubuntu Member:


  3. #33
    Join Date
    Jan 2007
    Beans
    720
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Disk use analyzer claims almost out of space

    With no space left on root he won't be able to install gparted. But the command
    Code:
    sudo gdisk -l /dev/sda
    should give info on the partitioning of the drive, and gdisk should be installed by default.

    How old are the oldest backups? Maybe deleting a couple them is the key, if you don't need them.

    Quote Originally Posted by Gnusboy View Post
    This is what I get

    [sudo] password for jess:
    mkdir: cannot create directory ‘/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup’: No space left on device
    jess@ranha-system:/$ sudo mkdir homebackup
    sudo: unable to resolve host ranha-system
    [sudo] password for jess:
    jess@ranha-system:/$ sudo mkdir homebackup
    mkdir: cannot create directory ‘homebackup’: File exists
    jess@ranha-system:/$
    You werent cd-ed to /media/jess/d60... try sudo mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup and see if it creates the directory then.
    Current 'buntu systems: Server 18.04.2 LTS, Mythbuntu 16.04 LTS, Ubuntu 16.04.1 LTS / Retired: 14.04 LTS, 10.04 LTS, 8.04 LTS
    Been using ubuntu since 6.04 (13 years!)

  4. #34
    Join Date
    Jul 2009
    Beans
    240

    Re: Disk use analyzer claims almost out of space

    Is there a problem deleting the oldest backups? They are about 54 MB each and there are 80 of them. Wouldn't that be the easiest? And then do a full backup of the current system.
    If you can't take a hoof - don't stand behind the mule

  5. #35
    Join Date
    Jan 2007
    Beans
    720
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Disk use analyzer claims almost out of space

    If you don't need them, delete them. Even deleting 1 or 2 might get you unstuck so you can move the rest to the USB drive.

    And when you do a new backup, backup to the external drive instead of home.
    Current 'buntu systems: Server 18.04.2 LTS, Mythbuntu 16.04 LTS, Ubuntu 16.04.1 LTS / Retired: 14.04 LTS, 10.04 LTS, 8.04 LTS
    Been using ubuntu since 6.04 (13 years!)

  6. #36
    Join Date
    Jul 2009
    Beans
    240

    Re: Disk use analyzer claims almost out of space

    OK
    A couple of things. If I delete some of the older backups, it should give me enough working space.
    When I use this code does it create the (sudo) mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup on the 500 drive.
    and get rid of the jess@ranha-system:/$ sudo mkdir homebackup
    sudo: unable to resolve host ranha-system ?


    ‘/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup’: on the 500GB drive,?
    Or do I then (sudo) mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup': on the 500 drive?

    If I still get "cannot create directory ‘homebackup’: File exists" I will need to make a folder under the homebackup directory on the 500GB to store my new backup. Have I got this right?
    Now, saying this all works, I follow the steps you gave me before, which should and/or tell me if my main drive is healthy. Yes?
    As long as I don't mess with the boot drive, SDA9, everything should start working as it was, yes?
    If you can't take a hoof - don't stand behind the mule

  7. #37
    Join Date
    Jan 2007
    Beans
    720
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Disk use analyzer claims almost out of space

    To avoid confusion, I'd use fully-qualified paths in your commands for now. Copy and paste them from this post.

    So, use (sudo) mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup instead of mkdir homebackup.

    If you get cannot create directory ‘homebackup’: File exists that means the directory homebackup exists already. You can verify this from the file manager, or the command ls -l /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3

    Once you know homebackup exists, use this command to copy everything from home to homebackup (use sudo to get around the no space issue):
    Code:
    sudo cp -av ~/ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup
    If this works, you'll have backed up everything in home, and you can delete stuff to your heart's content (especially those big backup files!)
    Current 'buntu systems: Server 18.04.2 LTS, Mythbuntu 16.04 LTS, Ubuntu 16.04.1 LTS / Retired: 14.04 LTS, 10.04 LTS, 8.04 LTS
    Been using ubuntu since 6.04 (13 years!)

  8. #38
    Join Date
    Aug 2009
    Location
    United States
    Beans
    4,486
    Distro
    Ubuntu Development Release

    Re: Disk use analyzer claims almost out of space

    Gnusboy if in fact user doesn't have a /Home partition does it make sense to make a partition of /Home and
    move what he wants from his / to /Home partition and never have a / full again.
    I do not know if he has room on drive for new partition. He has what 4 gig of backups to move delete or keep elsewhere on different drive and
    who knows how much in Documents and such on /.
    I might be missing something user wants to accomplish without having a /Home partition.
    Last edited by garvinrick4; 6 Days Ago at 01:37 AM.
    Remember hence where you come and pass it down.
    Ubuntu Forums member #899097 and Ubuntu Member:


  9. #39
    Join Date
    Jul 2009
    Beans
    240

    Re: Disk use analyzer claims almost out of space

    Many of the saved Deja Dup backups show they we created on the same date. Weds Dec. 19 2018 They are also encrypted with "duplicity-full.20181219T220352Z.vol20.difftar.gz" Gzip archive (application/gzip) "could not open "duplicity-full.20181219T220352Z.vol18.difftar Archive type not supported and can't be opened
    They show "An error occurred while extracting files."

    /home/jess/deja-dup/duplicity-full.20181219T220352Z.vol33.difftar.gz
    If you can't take a hoof - don't stand behind the mule

  10. #40
    Join Date
    Jul 2009
    Beans
    240

    Re: Disk use analyzer claims almost out of space

    Well I just lost the last 3 hours of readable notes on trying to solve the problems
    All I have now are filled with some sort of formatting that I havenm't a clue as to fix. Maybe someone out there can fix this.


    I just checked the 500 GB external drive and the permissions are all root. Does sudo override that?<br><br>This is what I get with sudo gdisk -l /dev/sda<br><br>sudo gdisk -l /dev/sda<br>GPT fdisk (gdisk) version 1.0.1<br><br>Partition table scan:<br>&nbsp; MBR: MBR only<br>&nbsp; BSD: not present<br>&nbsp; APM: not present<br>&nbsp; GPT: not present<br><br><br>******************************* ********************************<br>Found invalid GPT and valid MBR; converting MBR to GPT format<br>in memory. <br>********************************************** *****************<br><br>Disk /dev/sda: 1250263728 sectors, 596.2 GiB<br>Logical sector size: 512 bytes<br>Disk identifier (GUID): 7D3D8303-DF28-4883-8C20-92EB535FCBDA<br>Partition table holds up to 128 entries<br>First usable sector is 34, last usable sector is 1250263694<br>Partitions will be aligned on 8-sector boundaries<br>Total free space is 13062 sectors (6.4 MiB)<br><br>Number&nbsp; Start (sector)&nbsp;&nbsp;&nbsp; End (sector)&nbsp; Size&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Code&nbsp; Name<br>&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;& nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 63&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 182342098&nbsp;&nbsp; 86.9 GiB&nbsp;&nbsp;&nbsp; 8300&nbsp; Linux filesystem<br>&nbsp;&nbsp; 5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1239736113&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1250258624&nbsp;&nbsp; 5.0 GiB&nbsp;&nbsp;&nbsp;&nbsp; 8200&nbsp; Linux swap<br>&nbsp;&nbsp; 6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 640942080&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1019336258&nbsp;&nbsp; 180.4 GiB&nbsp;&nbsp; 8300&nbsp; Linux filesystem<br>&nbsp;&nbsp; 7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 336103424&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 640940031&nbsp;&nbsp; 145.4 GiB&nbsp;&nbsp; 8300&nbsp; Linux filesystem<br>&nbsp;&nbsp; 8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1019336704&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1239734271&nbsp;&nbsp; 105.1 GiB&nbsp;&nbsp; 8300&nbsp; Linux filesystem<br>&nbsp;&nbsp; 9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 182343680&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 336101375&nbsp;&nbsp; 73.3 GiB&nbsp;&nbsp;&nbsp; 8300&nbsp; Linux filesystem<br><br>Is this an issue? <br>Found invalid GPT and valid MBR; converting MBR to GPT format<br>in memory. <br>============================================== ======<br><br>ls -l /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3<br>total 140<br>drwxr-xr-x&nbsp; 2 root root&nbsp; 4096 Jun 16&nbsp; 2014 DishArc<br>drwxrwxrwx&nbsp; 3 jess jess&nbsp; 4096 Mar 29&nbsp; 2010 home<br>drwxrwxrwx&nbsp; 3 jess jess&nbsp; 4096 Mar 29&nbsp; 2010 home2<br>drwxrwxrwx 41 jess jess 20480 Sep 18&nbsp; 2016 jess<br>-rw-rw-rw-&nbsp; 1 jess jess 70752 Dec 25&nbsp; 2012 Linux cheat sheet.pdf<br>drwx------&nbsp; 2 root root 16384 May 24&nbsp; 2014 lost+found<br>drwxrwxrwx 65 jess jess&nbsp; 8192 Mar 22&nbsp; 2016 Ranha0316<br>drwxrwxrwx&nbsp; 2 jess jess&nbsp; 4096 Dec 29&nbsp; 2012 safebrowsing<br>drwxrwxrwx&nbsp; 2 jess jess&nbsp; 4096 Sep 12&nbsp; 2014 USDA Grant forms<br>========================================= ================<br><br>sudo mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup'<br>&gt; <br>&gt; sudo mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup'<br>[sudo] password for jess: <br>mkdir: cannot create directory ‘/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup\n\nsudo mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup’: No such file or directory<br><br>sudo cp -av ~/ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup <br>[sudo] password for jess: <br>Sorry, try again.<br>[sudo] password for jess: <br>cp: cannot create directory '/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup': No space left on device<br><br>Tried all of this: <br><br><br>sudo cp -av ~/ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup' <br>&gt; <br>&gt; <br>&gt; <br>&gt;&nbsp;&nbsp; h &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp ; this h was a typing error&nbsp; ----- <br>&gt; sudo cp -av ~/ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup' <br><br>h<br>cp: cannot create directory '/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup '$'\n\n\n\n''h'$'\n''sudo cp -av ~/ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup': No such file or directory<br>h: command not found<br><br>I<br><br>Just to check,<br>Using this code: <strong>(sudo) mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup</strong><pre class="bbcode_code" style="height:36px;">One thing I noticed is a missing <span class="js-about-item-abstr">apostrophe at the end of </span><em>/homebackup</em> command<br> <br>I enter sudo mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3<strong>/</strong><em>homebackup</em><strong> without an apostrophe </strong>but the terminal returns<br><br>(sudo) mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup' <em>with an apostrophy'</em></pre><br><br>and this shows<br>(sudo) mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup' <strong>bash: syntax error near unexpected token `mkdir'<br></strong><br>I made a variety of small changes, adding an apostrophy, seeing if putting (sudo) before the command and inserting parenthises around sudo - but get nothing usable<br><br>Then there is a space followed by&nbsp; &gt;<br>And I get these variations<br>&gt; <br>&gt; sudo mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup'<br>[sudo] password for jess: <br>mkdir: cannot create directory ‘/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup\n\nsudo mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup’: No such file or directory<br>jess@ranha-system:~$ mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup<br>mkdir: cannot create directory ‘/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup’: No space left on device<br>jess@ranha-system:~$ sudo cp -av ~/ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup <br>[sudo] for jess: <br><br>cp: cannot create directory '/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup': No space left on device<br>jess@ranha-system:~$ sudo cp -av ~/ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup' <br><br>This didn't work<br>sudo cp -av ~/ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup' <br>cp: cannot create directory '/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup '$'\n\n\n\n''h'$'\n''sudo cp -av ~/ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup': No such file or directory<br><br>I tried all of this and am still where we started. I think I get the gist of what to do, with a good dose of paranoia about screwing up something drastic.. You guys have been awesome with your time and help, but I don't seem to be catching it.<br><br>mkdir: cannot create directory ‘/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup’: No space left on device<br>jess@ranha-system:~$ (sudo) mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup<br>bash: syntax error near unexpected token `mkdir'<br><br><br><br><br><br><br>
    If you can't take a hoof - don't stand behind the mule

Page 4 of 7 FirstFirst ... 23456 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •