HELP, NOW, before I do something rash!! Out of disk space message!!

[Daniel~]

Um... that's a very roundabout way of looking at things, and I'm a little concerned about wine being able to see /boot... but anyway

sudo mount /boot
sudo ls /boot

What are the results?

daniel@daniel-Sabertooth-Mint-18-DaVoid ~ $ sudo mount /boot
[sudo] password for daniel:
mount: /etc/fstab: parse error: ignore entry at line 10.
mount: can't find /boot in /etc/fstab
daniel@daniel-Sabertooth-Mint-18-DaVoid ~ $ sudo ls /boot
abi-4.13.0-36-generic    
memtest86+.bin
config-4.13.0-36-generic  
memtest86+.elf
efi        
memtest86+_multiboot.bin
grub        
retpoline-4.13.0-36-generic
initrd.img-4.13.0-36-generic  
System.map-4.13.0-36-generic
lost+found      
vmlinuz-4.13.0-36-generic
daniel@daniel-Sabertooth-Mint-18-DaVoid ~ $

 

[Daniel~]

Show us this as well as 'ls /boot':

sudo dpkg -l linux* | grep ^ii | awk '{ print $2 }'

daniel@daniel-Sabertooth-Mint-18-DaVoid ~ $ sudo dpkg -l linux* | grep ^ii | awk '{ print $2 }'
linux-base
linux-firmware
linux-headers-4.13.0-36
linux-headers-4.13.0-36-generic
linux-image-4.13.0-36-generic
linux-image-extra-4.13.0-36-generic
linux-libc-dev:amd64
linux-sound-base
linuxmint-keyring

 

[Daniel~]

I think /boot is always mounted in Mint/Debian, etc; it's not like Gentoo where you have to mount first.

I'm pretty sure ls will show us that the package manager didn't COMPLETELY remove the kernel files in /boot for some reason. See post #4 above. We'll probably have to delete the old stuff manually.

Daniel~, are you sure you deleted all but the current running kernel? Remember for the future, it's a good idea to keep the running kernel *+1* as I said in an earlier post...

Yeah, sorry I didn't leave one, there was a mess of them and I thought I had one more than I did.

 

[Gizmo]

Kernels don't have to sit in /boot, they just traditionally do.

I suspect this is related to the fact that grub and lilo have not traditionally supported the plethora of file systems that linux in general has. Having the kernel and the initrd on /boot makes it much easier to ensure that the booted partition has a file system that the booter can read, while still leaving the sysadmin the ability to use whatever file system is most appropriate for use elsewhere on the machine.

 

[Gizmo]

Daniel, can you show the output of:

df -h

 

[Daniel~]

Daniel, can you show the output of:

df -h

daniel@daniel-Sabertooth-Mint-18-DaVoid ~ $ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 9.3M 1.6G 1% /run
/dev/mapper/mint--vg-root 218G 130G 78G 63% /
tmpfs 7.9G 38M 7.8G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
/dev/sda2 473M 73M 377M 17% /boot
/dev/sda1 511M 511M 40K 100% /boot/efi
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 1.6G 64K 1.6G 1% /run/user/1000
/dev/sde1 1.8T 178G 1.6T 11% /media/daniel/T2 Back-up
/dev/sdd1 294G 90G 189G 33% /media/daniel/Extension Drive
daniel@daniel-Sabertooth-Mint-18-DaVoid ~ $

 

[Gizmo]

Ok, now give me the output of:

ls -al /boot/efi

 

[Daniel~]

 

[Gizmo]

Ok, now show me the output of:

du /boot/efi

 

[Daniel~]

Ok, now show me the output of:

du /boot/efi

 

[ThunderRd]

Err...that looks strange, but everything in /boot looks good now.

Gizmo, why did those directories in /boot/efi not show up with ls? Are they hidden or something?

 

[Daniel~]

Yeah, why didn't they Gizmo, your not going French on us now... are you? ":O}

 

[Gizmo]

Err...that looks strange, but everything in /boot looks good now.

Gizmo, why did those directories in /boot/efi not show up with ls? Are they hidden or something?

ls isn't recursive. If you look at post #22 above (HELP, NOW, before I do something rash!! Out of disk space message!!) you'll see that the efi directory was listed in the output, but it wasn't obvious it was a directory. This is one of the reasons I tend to prefer 'ls -l' or 'ls -al'.

 

[Gizmo]

Yeah, why didn't they Gizmo, your not going French on us now... are you? ":O}

Nah. I don't like the French; they ain't got no idea how to properly spell them words. I mean seriously, have you ever tried to spell a french word based on how it's pronounced?!

 

[Daniel~]

AND just what did you think you were doing spelling French. Friends don't let friends...if you catch my drift Mon ami

 

[Daniel~]

And yet View attachment 15813 it persists

 

[Daniel~]

But as it's doing no harm let's not burn any midnight oil.
Just whenever you can":O}

 

[Kaitain]

What on Earth is /boot/EFI/2017-06-03-02-img? That's huge and also doesn't appear to belong. It looks like a backup file that's been misplaced.

 

[ThunderRd]

ls isn't recursive. If you look at post #22 above (HELP, NOW, before I do something rash!! Out of disk space message!!) you'll see that the efi directory was listed in the output, but it wasn't obvious it was a directory. This is one of the reasons I tend to prefer 'ls -l' or 'ls -al'.

I asked a dumb question there. In post #4 I asked Daniel for 'ls -la /boot', and missed the efi directory in the output. When he ran the command, it was quite clearly a directory.

 

[ThunderRd]

What on Earth is /boot/EFI/2017-06-03-02-img? That's huge and also doesn't appear to belong. It looks like a backup file that's been misplaced.

That's likely the problem, right there:

/dev/sda1 511M 511M 40K 100% /boot/efi

That -img directory filled it up all on its own. I don't know enough about efi and how it works, though; I'm going to shut up now and listen.