#Filesystem corrupted?

29 messages · Page 1 of 1 (latest)

ebon river
#

I was working on stuff, then I got a low space warning, then everything started shutting down. When I restarted, I was put into initramfs. I tried deleting some unneeded files from a live boot, but that didn't help. Here's what I get.

heavy pagoda
#

boot live. then do 'lsblk -f` to figure out ur partitions

#

then do sudo fsck /dev/<nvme1n1__> put partition number, no brackets

ebon river
heavy pagoda
#

why so many RAID things?

#

looks like very complicated setup

ebon river
ebon river
heavy pagoda
#

do from live environment terminal how I said

#

when u boot live, open DISKS app, then click play button on EVERY partition of nvme1n1 then open terminal, then show this result of command

#

lsblk -o NAME,TYPE,MODEL,LABEL,SIZE,FSSIZE,FSTYPE,FSUSED,MOUNTPOINT

#

@ebon river ^

ebon river
heavy pagoda
#

ok koo

ebon river
#

Do you know why this might have happened?

#

It's not normal for filesystems to shit themselves right

heavy pagoda
#

i would like to see the details to be able to answer that possibly

heavy pagoda
#

add FSAVAIL too to that string

#

with a comma before it

ebon river
heavy pagoda
#

one moment

#

only 1.4 GiB left on your boot drive on p2

#

any reason it's so full?

ebon river
#

Just full

heavy pagoda
#

so that may have led to the issue possibly. Are there any virtual machines set up on this linux system?

#

if so, adjust the VM setup for each so they're not having 'dynamically-allocated' drive space, since this may cause one of them to balloon out infinitely til drive fills right up.