Ubuntu :: No Space Left On Partition To Install Updates?
Nov 29, 2010
So i am using xubuntu from wubi and i need more space to instal all the important security updates, How do i free up space? i think i made a mistake and did not allow it much space when i made the partition for it
Today I was installing a lot of software since I'm just setting up my Slackware system again after a fresh install, and I realized that my root partition has very little space left.
Here is the output of df -h:
Code:
As you can see, I have a 20G (19G here for some reason) root partition, 8G /var, and 86G of /home. I thought this would be plenty since many recent recommendations for / are 10-15G. Now, though, 17G are used up for some reason! How is this possible? I thought a full slackware install only had about 4G of software! I don't have any music or movies or any crazy huge files that I know of, and those would be in my /home directory anyway. Is there any way I can see which files are taking up all this space?
If it's necessary to allocate more space to my / partition, is it still possible to boot up a GParted live Cd, shrink /home a bit, move some partitions to the right, and expand my root partition? I would REALLY prefer I don't have to reinstall since I just spent a ton of time setting up my system again, but if worst comes to worst ... :'-(
My boot partition doesn't have any space left, rendering me unable to install any updates. Most space in the boot directory (85 MB) is taken by the following files:
The wubi install of Ubuntu is saying it only has 125 MB left. I gave the install 10 GB to start with. I know the OS takes about 3 GB and I didn't install 7 GB worth applications. I'm thinking some how it confused itself. I've done run the Disk Analysis And it's rather confusing, but it seems to be looking at more then its alloted 10 GB.
I have been installing Fedora 8 Linux with already having Windows Xp as my primary OS....
I have a total of 80GB Hard disk.Out of 80 GB,I have freed 8GB for Linux.But during Installation after "selecting language for keyboard" and then choosing "Create Custom Layout", while giving partitions I have alotted 4GB for '/' and 2GB for Swap.
Initially space was created for root(/)...but it is unable to create space for swap and all other boot,home etc...
It is showing the error msg as "Could not create partition as there is no space left for /(root)"...
We had a perfectly working SUSE OES netware server for some months, and wanted to create a new image backup. Using Acronis Backup and Recovery Advanced Server Software. This worked a treat on our SBS 2008 Server. We went to run it for Novell OES and a system lock up occurred and services such as Iprint then disabled. A server restart recovered the server after a few attempts. We then learnt that the server could not write files to an NTFS formatted USB drive. This was the ideal destination to test the backup. However we could not even write a simple file to the drive without an error message about permissions.
We then learnt that Linux needs a package called NTFS-3G to enable NTFS writing permissions. This did fix the writing issues. We attempted to run another back up which again failed, bringing down the server. We again attempted to reboot the server this time we fail to get to the graphical user login. At the suse Linux Enterprise boot screen we select "boot from hard disc". Which fails immediately with "GDM could not write a new authorisation entry to disk...Error no space left on drive". When the boot eventually continues, a number of things fail with the same message about "No space left on device".
The next message starts "Could not start the X server due to some internal error."
Further to the above, starting "recovery" instead, the checks of partition fail and it seems obvious that the partition definitions have become corrupted. In the expert partion manager the lines for partitions seem correct except that there are no entries for 'mount point' and 'mount by' columns. Trying to edit these lines does not appear to allow entries for mount point or mount by - they are disabled. It seems likely the server is not mounting some partitions at boot which is why the kernel thinks the server is full. Is there some simple way we can use say fdisk to repair the partition definition without loosing anything of the server OS and data ?
I originally had an Ubuntu partition on my hard drive which occupied about half of it. I installed Windows 7 in the remaining unallocated space and I was planning on doing a grub update from a live cd afterwards. BUT when I looked at my partition table, the space where the ubuntu partition used to be is now unallocated space!
cp: writing `/tmp/tmpX2KZDc/system.image': No space left on device However, when I right-click on properties, I see it has 51 items, totalling only 130.5 KB!this is a dual boot system with Win XP and Ubuntu 10.10 (~58Gb partition)Quote:
anil@anil-HP-EliteBook-8440p:/tmp$ mount /dev/sda5 on / type ext4 (rw,errors=remount-ro,commit=0) proc on /proc type proc (rw,noexec,nosuid,nodev)
I'm setting up a friend's old Thinkpad with Linux Mint 9 (or maybe 10). I would like to set it up with separate partitions for /root and /home, which would make it easier to save his data and settings should we need to reinstall later on. I picked Mint because he's not exactly computer literate, so I'm trying to make this as painless as possible for him, and since I'm going to be the guy doing the work, should the need arise, I want to make things easier on me.
Problem is that the machine only has a 40g hard drive. I know he's not going to be installing many programs, mainly a browser, some music apps, a DVD player, and OpenOffice. I'm trying to figure out how much space to allocate to /root so I dont' have to resize it in a few months.
df -h [URL] I did the following command to find everything is in /usr or /var, then tracked it down to /usr/lib and /usr/share as the main offenders, but out of all the directories none are more than 1mb or so.
du -sh /* | sort -gr | head -n 5
I tried to uninstall firefox, which is what got me in this mess in the first place, the log claims it will remove ~240 mb but failes on a "E: Write error - write (28 No space left on device)" [URL] If I could juggle something onto an external hard drive so I can uninstall firefox I would be out of the wood. Failing that I believe a new install is in order.
I recently upgraded from Lucid to Maverick, which went fairly smooth. Then I upped my RAM with some new memory sticks (4Gb to 8Gb). Since about then, I'm seeing these errors in syslog:
Code: Jun 6 22:23:52 howler console-kit-daemon[1224]: WARNING: Failed to add monitor on '/dev/tty2': No space left on device Jun 6 22:23:59 howler console-kit-daemon[1224]: WARNING: Failed to add monitor on '/dev/pts/0': No space left on device I also get errors when running "tail -f" as root:
Code: tail: cannot watch `/var/log/syslog': No space left on device
I searched around and I found some other reports of the tail -f error, with the suggestion of increasing fs.inotify.max_user_watches. I set it to 16384, and that at first resolved the tail -f problem, but now I'm getting that error again even after upping max_user_watches.
I know swap is suggested to be approx. the same size as RAM, but with this upgrade RAM is now bigger than the 5.7G of swap.
i'm using Ubuntu virtual machine.latly, i've moved the VM image to other PC. something with the user privileges got wrong. i when i edit a file using nano for example from a simple user, it says: "no space left on device" but when i use
# sudo nano filename
it works.i used
#chmod 777 filename
and it still dosent work. i cant save/write to disk while i'm in the user account. but with sudo, or root account it works.
I'm having some problems with a hosted openSUSE 11.2 server. It was running fine until I did a "zypper up" to apply patches. This included a kernel update.
On reboot the root partition does not mount the / partition giving the following error:
Unrecognized mount option "defaults.noatime", or missing value mount: wrong fs type, bad option, bad superblock on /dev/md2.
Through an Ubuntu rescue disk (this is what Hetzner provides) the disk can be mounted without problems.
( I installed a fresh openSUSE 11.2 with a similar configuration and got the same results after the update)
The server is a hosted installation from Hetzner in Germany with just the basics for LAMP setup.
The disk setup is as follows using software raid1: swap /dev/md0 (/dev/sda1 /dev/sdb1) /boot /dev/md1 (/dev/sda2 /dev/sdb2) / /dev/md2 (/dev/sda3 /dev/sdb3)
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Yes I tried 'sudo dpkg --configure -a' Should I do a reinstall.
"Setting up initramfs-tools (0.92bubuntu53) ... update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.31-17-generic
gzip: stdout: No space left on device update-initramfs: failed for /boot/initrd.img-2.6.31-17-generic dpkg: subprocess installed post-installation script returned error exit status 1"
I've just upgraded to kubuntu 9.10, and I'm getting strange errors when trying to copy files onto my MP3 player, a SANSA M250 (2GB). df claims it's at 57% capacity (and the figures make sense for that, as well as having about the quantity of music which half fills the SANSA) but when I try to copy a file - from the command line, from exaile, or with the file manager, I get a "No space left on device" error:
Code: $ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 73939452 42184580 27998880 61% / udev 512472 264 512208 1% /dev none 512472 1752 510720 1% /dev/shm none 512472 96 512376 1% /var/run none 512472 0 512472 0% /var/lock none 512472 0 512472 0% /lib/init/rw /dev/sdc 1996000 1125056 870944 57% /media/SANSA M250 $ cp test.mp3 /media/SANSA M250/ CP: cannot create regular file `/media/SANSA M250/test.mp3': No space left on device The MP3 being copied is 2MB in size so should fit easily.
There were no problems until upgrading, when I also moved from amarok to exaile - because amarok2 doesn't have the functionality I want from a player. But this happens even if exaile isn't running, so exaile shouldn't be the problem. How can I diagnose what's going on?
If I run low on free space, and I/system need to write something, then the files are just truncated. With no way to revert to their previous content.
First I installed the Windows on the VirtualBox, it sucked up all free space, so I couldn't even login to the system afterwards.
Then I, once again, silently ran out of free space, and my php editor broke. Later I discovered that it tried to write its config files, but failed, truncating them all. I lost a half a year of configurations, custom color scheme and custom code snippets.
Then one day the system just froze. Later I understood, there wasn't enough free space for it to run.
Today I was working on my php script, for like the second day, when, again, free space ran out, so with another file-save, I got a wonderfully impressing blank php-file. It was auto-reloaded from the external change, which was failure to write to file, obviously, so no ctrl-z worked, leaving me with two days work wasted and an urge to hit the monitor
My questions are: 1 How can this be fixed? Besides the obvious awesome fix "watch your free space, buddy". 2 Could somebody explain why these sorts of things happen, just so I know why the ultra-safe and durable 'nix operating system wants to destroy itself sometimes? 3 Anyone else encountered this issue?
I was saving a few pictures, and I realized that none of them were actually being saved. I went to my home folder and I noticed that I only had 0 bytes left, then I deleted everything in my trash, got some space back, then it disappeared.
I have an WD 1TB external hard disk. When I try to write any file to it - even a 1kb text file - I get the message "no space left on device". I cannot write to the disk at all anymore - not files, not directories.The drive is formatted as an NTFS drive. I use F13. I can read from the drive without any apparent problem. Would anyone know what's causing this problem?
When I boot the ubuntu live cd (9.10) and attempt to install it only gives two options at the partitioning screen. One is to use the whole disk and the other is to manualy assign partitions. I told it to resize one of my partitions and created 18GB of free space. However, it tells me this space is "unusable". It wouldn't let me do anything with it and I used windows vista disk manager to add it back to the original partition. I have one hard drive with four partitions. One is a restore partition, one windows partition, one storage partition, and one that says xp although i don't have xp installed. It might be used by the acer restore program. It's an acer aspire 6920.
I just installed Fedora on my pc with windows XP pre-installed (dual boot). I had the same setup with ubuntu before with no problems. My ntfs windows partition is of 15 gb approximately and the remaining space that was available for fedora was about 220 GB (non partitioned - I removed all the partitions excepting the windows one using gparted from liveCD prior to beginning installation) ..........after installation etc etc.....my home folder shows me only 150GB of space.....what's happening? Where has all the remaining space gone to?
I have two 250 GB drives setup with hardware RAID 1. I had on sda and sdb: 20 GB swap, 20 GB /, 198 GB /srv all was good until I started to run out of space on 20 GB /. So I booted the server with Suse 11.3 live cd and reduced the size of 20 GB swap to 10 GB and 198 GB /srv to 150 GB on sda and sdb.
All good so far, then tried to increase 20 GB / to 60 GB, but the Partition setup says the Max Size can be 20 GB, I have checked and I have 42.88 GB of Unpartitioned space. I have rescanned, rebooted, Server is still running fine by the way, but the 42.88 GB of free space is not made available for the expansion of 20 GB /.
I have noticed that the initial ordering of icons of my desktop is leaving a blank space on the top left corner. Recently I have changed my language but I am not sure when this began to happen.
I have a backup drive formatted ext4 which got filled to no space left, so I deleted some files and folders to make space on it , emptied the trash, files and folders are gone , but it stll says I got no drive space left on it and cant copy a file to it because it thinks its full lol I freed up like 15gb of space on it , have rebooted several times ..
Debian Version: 8.3 (Jessie) KDE (although this is NOT a desktop issue) Basic Hardware: Gigabyte Motherboard GA-970A-D3P AMD 8350 CPU (8 cores) 32 GB DDR3 RAM 120GB SSD SATA-6GB/s 750 WD Black SATA-6GB/s
I am getting "Error: No space left on device" regularly during updates or installs, but why. Here is data on the disks, filesystems, etc...
Seems very doubtful that inodes are the killer.I have googled and followed all the threads, and search these forums and found nothing that fits - every answer there was focused on avaiolable space and inodes..And to make the cheese even more binding, the issue has cropped up on another 8.3 system with far more disk space (larger hard drives) and lots more unused inodes
You would think it would be easy to do this (and essential to maximizing and predicting the usage of tapes), but apparently this isn't so. The program MT(1) actually had some commands that give the block positition (if supported by the drive) from which the remaining space could be deduced (even if you couldn't predict exactly how much space the next archive would take up). However I'm using MT(1L) which no longer has such commands.
my home partition is an extended one, and when i want to create an unallocated space the space will stay in that extended partition. but there is also an 7 gb unallocated space which i want to merge with the other unallocated space. I also cannot extend that partition over that 7 gb. how can i overcome that problem?
i m also uploading a screenshot of gparted.[URL]..
I'm unable to login to my Kubuntu Lucid. The login screen takes my password, blanks, then returns me to the login screen. I'm getting some graphics errors when running from recovery mode as well as the no space left on device error when attempting to start x from the terminal. Here are some outputs: When starting from recovery mode, selecting failsafeX from the Recovery Menu:
[Code]...
I've come to the conclusion that my root partition is full, but I'm not sure how to clear space, or how much to clear once I work out how to do it. I removed a few packages with apt, but it doesn't seem to have any effect. df -h shows that root is 100% full, yet it has 3GB free. I've grown comfortable with Ubuntu in the couple years I've been using it, yet this level of problem-solving is a bit nerve-wracking to me. I've been considering reinstalling (this machine is running Lucid upgraded from Karmic and Jaunty and has a few oddities), but I hate the idea of being forced to reinstall because I can't overcome this problem. If you need any other information or outputs from terminal commands, I'm happy to provide it.