Danielss89 2017-03-03 20:48:10
Hi, i'm fairly new to linux, so this might be a dumb question. I'm trying to run apt-update but i'm getting "gzip: stdout: No space left on device"
Shadow_7 2017-03-03 20:48:30
Danielss89: df
Danielss89 2017-03-03 20:48:32
When i run df i get: http://take.ms/QBrON
Danielss89 2017-03-03 20:48:44
is apt using /dev/md1 ?
Shadow_7 2017-03-03 20:49:40
if there's a kernel update it will use /boot/
Shadow_7 2017-03-03 20:49:46
or grub updates
Shadow_7 2017-03-03 20:50:00
otherwise most of apt downloads go to /var/cache/apt/archives
Danielss89 2017-03-03 20:51:31
ok, any idea why i get the no space left?
kingsley 2017-03-03 20:51:49
Danielss89: Yeah, "gzip: stdout: No space left on device" looks a lot to me like apt-update failed trying to write data to a full frive.
kingsley 2017-03-03 20:52:39
Danielss89: Oops! Sorry! I meant to write "...trying to write data to a full Drive".
Danielss89 2017-03-03 20:53:08
but as i can see, only the boot one is full
Danielss89 2017-03-03 20:53:14
and if it doesn't try to write that
Danielss89 2017-03-03 20:53:30
actually
Danielss89 2017-03-03 20:53:31
update-initramfs: Generating /boot/initrd.img-4.8.0-40-generic
Danielss89 2017-03-03 20:53:50
can i assign more space to boot?
Danielss89 2017-03-03 20:53:51
:D
kingsley 2017-03-03 20:54:27
Danielss89: Why? I suspect a.) The drive is full. It happens. Just like Shadow_7 suggested, the "df" command should reveal full drives. b.) Maybe apt-update is writing to the wrong drive.
SPF 2017-03-03 20:54:41
Danielss89: maybe you can try apt-get autoremove, in case you have multiple old kernels in /boot
Danielss89 2017-03-03 20:54:53
http://take.ms/TBM7M i'll try
borsin 2017-03-03 20:56:42
does /var exist - is /var on a partition not mounted? do you see a lost+found when ls -l /var?
Danielss89 2017-03-03 20:57:24
that helped a lot
Danielss89 2017-03-03 20:57:27
thanks guys
Danielss89 2017-03-03 20:57:32
35% used on boot now
