Error message "No space left on device"

For diagnostic purposes please provide the output that you receive for the commands (to be executed in a terminal window):

uname -a
lsb_release -crid
df -h
dpkg -l | grep ' linux-image'

Linux HCMac 4.4.0-78-powerpc64-smp #99-Ubuntu SMP Thu Apr 27 16:02:00 UTC
2017 ppc64 ppc64 ppc64 GNU/Linux

Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial

Filesystem Size Used Avail Use% Mounted on
udev 399M 0 399M 0% /dev
tmpfs 98M 4.8M 93M 5% /run
/dev/sda5 11G 10G 0 100% /
tmpfs 487M 108K 487M 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 487M 0 487M 0% /sys/fs/cgroup
/dev/sda6 29G 734M 27G 3% /home
tmpfs 98M 40K 98M 1% /run/user/1000

i linux-image-4.4.0-45-powerpc64-smp
4.4.0-45.66 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
ii linux-image-4.4.0-47-powerpc64-smp
4.4.0-47.68 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
ii linux-image-4.4.0-53-powerpc64-smp
4.4.0-53.74 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
ii linux-image-4.4.0-57-powerpc64-smp
4.4.0-57.78 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
ii linux-image-4.4.0-59-powerpc64-smp
4.4.0-59.80 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
ii linux-image-4.4.0-62-powerpc64-smp
4.4.0-62.83 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
ii linux-image-4.4.0-66-powerpc64-smp
4.4.0-66.87 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
ii linux-image-4.4.0-72-powerpc64-smp
4.4.0-72.93 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
ii linux-image-4.4.0-75-powerpc64-smp
4.4.0-75.96 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
ii linux-image-4.4.0-77-powerpc64-smp
4.4.0-77.98 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
ii linux-image-4.4.0-78-powerpc64-smp
4.4.0-78.99 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
iF linux-image-4.4.0-87-powerpc64-smp
4.4.0-87.110 powerpc Linux kernel
image for version 4.4.0 on 64-bit PowerPC SMP
iU linux-image-powerpc64-smp
4.4.0.87.93 powerpc Linux kernel
image on PowerPC64 SMP.

On Fri, Aug 18, 2017 at 1:53 PM, Manfred Hampl <
<email address hidden>> wrote:

> Your question #656509 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/656509
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> For diagnostic purposes please provide the output that you receive for
> the commands (to be executed in a terminal window):
>
> uname -a
> lsb_release -crid
> df -h
> dpkg -l | grep ' linux-image'
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/656509
>
> You received this question notification because you asked the question.
>

harold1234; Hello;

As Manfred suspected:
"/dev/sda5 11G 10G 0 100% /"
/boot is full of old kernels .
Try the terminal command:
sudo apt autoremove
to remove old kernels - at 100% capacity there may not be the operating head room to operate in. In that event, the lower level manual tool 'dpkg' can be used .

When this situation is resolved need to get your system updated to 16.04.3 with the -92 kernel installed.

-could be a lot of work-

Having / full can have different causes. Old kernels is one of them.

For further diagnostics please provide the output of the commands

sudo du -schx /*
apt-get --simulate autoremove

16M /bin
799M /boot
0 /dev
14M /etc
625M /home
1.2G /kayakqt1.mov
3.1G /lib
16K /lost+found
8.0K /media
4.0K /mnt
4.0K /opt
du: cannot access '/proc/2072/task/2072/fd/4': No such file or directory
du: cannot access '/proc/2072/task/2072/fdinfo/4': No such file or directory
du: cannot access '/proc/2072/fd/4': No such file or directory
du: cannot access '/proc/2072/fdinfo/4': No such file or directory
0 /proc
96K /root
4.8M /run
17M /sbin
4.0K /snap
4.0K /srv
0 /sys
44K /tmp

NOTE: This is only a simulation!
      apt-get needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  libbonobo2-0 libbonobo2-common libgnome-2-0 libgnome2-common
libgnomevfs2-0
  libgnomevfs2-common liborbit-2-0 libphonon4qt5-4 libqt5script5
  linux-headers-4.4.0-45 linux-headers-4.4.0-45-powerpc64-smp
  linux-headers-4.4.0-47 linux-headers-4.4.0-47-powerpc64-smp
  linux-headers-4.4.0-53 linux-headers-4.4.0-53-powerpc64-smp
  linux-headers-4.4.0-57 linux-headers-4.4.0-57-powerpc64-smp
  linux-headers-4.4.0-59 linux-headers-4.4.0-59-powerpc64-smp
  linux-headers-4.4.0-62 linux-headers-4.4.0-62-powerpc64-smp
  linux-headers-4.4.0-66 linux-headers-4.4.0-66-powerpc64-smp
  linux-headers-4.4.0-72 linux-headers-4.4.0-72-powerpc64-smp
  linux-headers-4.4.0-75 linux-headers-4.4.0-75-powerpc64-smp
  linux-headers-4.4.0-77 linux-headers-4.4.0-77-powerpc64-smp
  linux-image-4.4.0-45-powerpc64-smp linux-image-4.4.0-47-powerpc64-smp
  linux-image-4.4.0-53-powerpc64-smp linux-image-4.4.0-57-powerpc64-smp
  linux-image-4.4.0-59-powerpc64-smp linux-image-4.4.0-62-powerpc64-smp
  linux-image-4.4.0-66-powerpc64-smp linux-image-4.4.0-72-powerpc64-smp
  linux-image-4.4.0-75-powerpc64-smp linux-image-4.4.0-77-powerpc64-smp
  python-gobject python-gobject-2 python-gtk2 python-xklavier python3-xlib
  snap-confine
0 upgraded, 0 newly installed, 45 to remove and 79 not upgraded.
3 not fully installed or removed.
Remv libgnome-2-0 [2.32.1-5ubuntu1]
Remv libbonobo2-0 [2.32.1-3]
Remv libbonobo2-common [2.32.1-3]
Remv libgnome2-common [2.32.1-5ubuntu1]
Remv libgnomevfs2-0 [1:2.24.4-6.1ubuntu1]
Remv libgnomevfs2-common [1:2.24.4-6.1ubuntu1]
Remv liborbit-2-0 [1:2.14.19-1build1]
Remv libphonon4qt5-4 [4:4.8.3-0ubuntu3]
Remv libqt5script5 [5.5.1+dfsg-2build1]
Remv linux-headers-4.4.0-45-powerpc64-smp [4.4.0-45.66]
Remv linux-headers-4.4.0-45 [4.4.0-45.66]
Remv linux-headers-4.4.0-47-powerpc64-smp [4.4.0-47.68]
Remv linux-headers-4.4.0-47 [4.4.0-47.68]
Remv linux-headers-4.4.0-53-powerpc64-smp [4.4.0-53.74]
Remv linux-headers-4.4.0-53 [4.4.0-53.74]
Remv linux-headers-4.4.0-57-powerpc64-smp [4.4.0-57.78]
Remv linux-headers-4.4.0-57 [4.4.0-57.78]
Remv linux-headers-4.4.0-59-powerpc64-smp [4.4.0-59.80]
Remv linux-headers-4.4.0-59 [4.4.0-59.80]
Remv linux-headers-4.4.0-62-powerpc64-smp [4.4.0-62.83]
Remv linux-headers-4.4.0-62 [4.4.0-62.83]
Remv linux-headers-4.4.0-66-powerpc64-smp [4.4.0-66.87]
Remv linux-headers-4.4.0-66 [4.4.0-66.87]
Remv linux-headers-4.4.0-72-powerpc64-smp [4.4.0-72.93]
Remv linux-headers-4.4.0-72 [4.4.0-72.93]
Remv linux-headers-4.4.0-75-powerpc64-smp [4.4.0-75.96]
Remv linux-headers-4.4.0-75 [4.4.0-75.96]
Remv linux-headers-4.4.0-77-powerpc64-smp [4.4.0-77.98]
Remv linux-headers-4.4.0-77 [4.4.0-77.98]
Remv linux-image-4.4.0-45-powerpc64-smp [4.4.0-45.66]
Remv linux-image-4.4.0-47-powerpc64-smp [4.4.0-47.68]
Remv linux-image-4.4.0-53-powerpc64-smp [4.4.0-53.74]
Remv linux-image-4.4.0-57-powerpc64-smp [4.4.0-57.78]
Remv linux-image-4.4.0-59-powerpc64-smp [4.4.0-59.80]
Remv linux-image-4.4.0-62-powerpc64-smp [4.4.0-62.83]
Remv linux-image-4.4.0-66-powerpc64-smp [4.4.0-66.87]
Remv linux-image-4.4.0-72-powerpc64-smp [4.4.0-72.93]
Remv linux-image-4.4.0-75-powerpc64-smp [4.4.0-75.96]
Remv linux-image-4.4.0-77-powerpc64-smp [4.4.0-77.98]
Remv python-xklavier [0.4-4]
Remv python-gobject [3.20.0-0ubuntu1]
Remv python-gtk2 [2.24.0-4ubuntu1]
Remv python-gobject-2 [2.28.6-12ubuntu1]
Remv python3-xlib [0.14+20091101-5]
Remv snap-confine [2.25]
Conf linux-image-4.4.0-87-powerpc64-smp (4.4.0-87.110
Ubuntu:16.04/xenial-security, Ubuntu:16.04/xenial-updates [powerpc])
Conf linux-image-powerpc64-smp (4.4.0.87.93 Ubuntu:16.04/xenial-security,
Ubuntu:16.04/xenial-updates [powerpc])
Conf linux-powerpc64-smp (4.4.0.87.93 Ubuntu:16.04/xenial-security,
Ubuntu:16.04/xenial-updates [powerpc])

On Sat, Aug 19, 2017 at 1:13 PM, Manfred Hampl <
<email address hidden>> wrote:

> Your question #656509 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/656509
>
> Manfred Hampl requested more information:
> Having / full can have different causes. Old kernels is one of them.
>
> For further diagnostics please provide the output of the commands
>
> sudo du -schx /*
> apt-get --simulate autoremove
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/656509
>
> You received this question notification because you asked the question.
>

Please repeat the command

sudo du -schx /*

and provide its full output. What you provided above looks incomplete.

Additionally please run the command

sudo dpkg --purge linux-headers-4.4.0-45-powerpc64-smp linux-headers-4.4.0-45

and copy/paste all output that we can see.

16M /bin
799M /boot
0 /dev
14M /etc
661M /home
1.2G /kayakqt1.mov
3.1G /lib
16K /lost+found
8.0K /media
4.0K /mnt
4.0K /opt
du: cannot access '/proc/1832/task/1832/fd/4': No such file or directory
du: cannot access '/proc/1832/task/1832/fdinfo/4': No such file or directory
du: cannot access '/proc/1832/fd/4': No such file or directory
du: cannot access '/proc/1832/fdinfo/4': No such file or directory
0 /proc
96K /root
4.8M /run
17M /sbin
4.0K /snap
4.0K /srv
0 /sys
44K /tmp
4.3G /usr
624M /var
11G total
There was a delay of a minute or two before the last 3 lines of output
appeared and the terminal prompt appeared.

 hcheyney@HCMac:~$ sudo dpkg --purge linux-headers-4.4.0-45-powerpc64-smp
linux-
(Reading database ... 503847 files and directories currently installed.)
Removing linux-headers-4.4.0-45-powerpc64-smp (4.4.0-45.66) ...
dpkg: warning: ignoring request to remove linux- which isn't installed
hcheyney@HCMac:~$ headers-4.4.0-45

Something else that may be significant: The menu selected shutdown has not
worked for some time. I have been using "shutdown now" in an terminal
emulator window to power down the computer.

Harold

On Sat, Aug 19, 2017 at 2:48 PM, Manfred Hampl <
<email address hidden>> wrote:

> Your question #656509 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/656509
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Please repeat the command
>
> sudo du -schx /*
>
> and provide its full output. What you provided above looks incomplete.
>
> Additionally please run the command
>
> sudo dpkg --purge linux-headers-4.4.0-45-powerpc64-smp linux-
> headers-4.4.0-45
>
> and copy/paste all output that we can see.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/656509
>
> You received this question notification because you asked the question.
>

1. Please do not look at the e-mail response that you get, but copy commands directly from your question document on launchpad https://answers.launchpad.net/ubuntu/+question/656509

As you can see from your last output, the e-mail system has chopped the long command that I gave into pieces, and consequently the command partly failed.

2. There is a big file (or directory) /kayakqt1.mov in the root directory .
If you move that below your home directory (where you have 27 GB free space), this will immediate help for the "no space left" status on the root directory.

3. You should run the command
sudo apt-get --purge autoremove
This command will uninstall obsolete packages and also will free more space.

4. The command
sudo apt-get autoclean
might also give some more free space by deleting package files for previous installation that are not needed any more.

Autoremove and autoclean freed up 4.0GB of space. No space error messages
are gone now. I have not been able to remove kayakqt1.mov file which is no
longer needed. Shutdown function in menu still does not work.

Thanks for your help
Harold

On Sun, Aug 20, 2017 at 12:18 PM, Manfred Hampl <
<email address hidden>> wrote:

> Your question #656509 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/656509
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> 1. Please do not look at the e-mail response that you get, but copy
> commands directly from your question document on launchpad
> https://answers.launchpad.net/ubuntu/+question/656509
>
> As you can see from your last output, the e-mail system has chopped the
> long command that I gave into pieces, and consequently the command
> partly failed.
>
> 2. There is a big file (or directory) /kayakqt1.mov in the root directory .
> If you move that below your home directory (where you have 27 GB free
> space), this will immediate help for the "no space left" status on the root
> directory.
>
> 3. You should run the command
> sudo apt-get --purge autoremove
> This command will uninstall obsolete packages and also will free more
> space.
>
> 4. The command
> sudo apt-get autoclean
> might also give some more free space by deleting package files for
> previous installation that are not needed any more.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/656509/+confirm?answer_id=7
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/656509
>
> You received this question notification because you asked the question.
>

After a couple of startup shutdown cycles the shutdown function is now
working and performance is generally improved. It would be useful to know
if I could prevent this file system fillup from happening again. If not
then I'll make note of the solutions that worked.

Thanks for the help.

Harold

On Sun, Aug 20, 2017 at 12:18 PM, Manfred Hampl <
<email address hidden>> wrote:

> Your question #656509 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/656509
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> 1. Please do not look at the e-mail response that you get, but copy
> commands directly from your question document on launchpad
> https://answers.launchpad.net/ubuntu/+question/656509
>
> As you can see from your last output, the e-mail system has chopped the
> long command that I gave into pieces, and consequently the command
> partly failed.
>
> 2. There is a big file (or directory) /kayakqt1.mov in the root directory .
> If you move that below your home directory (where you have 27 GB free
> space), this will immediate help for the "no space left" status on the root
> directory.
>
> 3. You should run the command
> sudo apt-get --purge autoremove
> This command will uninstall obsolete packages and also will free more
> space.
>
> 4. The command
> sudo apt-get autoclean
> might also give some more free space by deleting package files for
> previous installation that are not needed any more.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/656509/+confirm?answer_id=7
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/656509
>
> You received this question notification because you asked the question.
>

If you want to delete that /kayakqt1.mov you could use the command
sudo rm /kayakqt1.mov
or if you want to move it to your home directory (with 27GB free space) you could use the commands
sudo mv /kayakqt1.mov ~/Downloads/
sudo chown $USER:$USER ~/Downloads/kayakqt1.mov

General advice:
Whenever the package update processes have installed a new version of the kernel packages (about once or twice a month) you should do housekeeping with the commands
sudo apt-get --purge autoremove
sudo apt-get autoclean

You cannot really prevent that the root partition fills up, but regular removal of obsolete package (with the commands above) should care that you will not run into the "no space left" problem again.