#Filesystem corrupted?
29 messages · Page 1 of 1 (latest)
boot live. then do 'lsblk -f` to figure out ur partitions
then do sudo fsck /dev/<nvme1n1__> put partition number, no brackets
I've done that. It's nvme0n1p2
I can't recall setting up RAID. This is my pc.
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 ^
Fixed. I didn't know this had to be run from live. Thanks!
ok koo
Do you know why this might have happened?
It's not normal for filesystems to shit themselves right
i would like to see the details to be able to answer that possibly
.
add FSAVAIL too to that string
with a comma before it
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.