EXT4-fs (sda2): shut down requested
EXT4-fs (sda2): shut down requested (2)
So whenever i play Star Wars Outlaws, it crashes and i get this error message. Even all my Games crash after 5-10 mins. But mostly the games that are installed on the same drive as bazzite. (sda2) is a 1,1gb ext4 partition mounted in /boot. Has someone had this issue? Or is something wrong with my install?
8 Replies
Since i have had this issue for months and nobody awnsered in all the forums i have submitted this issue. I guess nobody has a clue.
Is there a way to kind of reset the boot partition?
The problem is your using ext4 Bazzite docs specifically state BTRFS is what is recommended for bazzite installation
Not a problem. /boot is meant to be ext4, like /boot/efi is meant to be EFI system partition.
If games that are installed on different disk drives run without problems, i'm inclined to believe the bazzite drive has corrupt data, or the drive itself might be faulty. Have you experienced system crashes or force turned-off your device?
Oh yes frequently
Then i think it's a data corruption issue. It can happen when drives are force-shut down
I don't see I/O or disk errors happen often, but in the few cases i've seen it's usually a failing drive
Makes sense, i cloned the installation from a 240gb ssd to a 1tb one using a linux mint iso and gparted
Is there a way to kind of verify system integrity? I really dont wanna do a fresh install XD
Assuming you auto-partitioned and using Btrfs, you can run btrfs-check (https://btrfs.readthedocs.io/en/latest/btrfs-check.html), but if the entire system is ext4 you can use fsck. I recommend doing this when unmounted (like using a live ISO)
For /boot you want to run fsck for sure since it's ext4
But beware that this might make the drive even worse, so i advise to clone/backup the drive first. I've had this happen with an SSD before, it died right after I finished backing up the data inside it and had just ran some checks on the drive
Well, there is a possibility that the clone didn't go correctly too, in which case the drive might not be failing. But regardless you'll want a full backup of your OS drive
Update: completely wiped the drive, reinstalled ecerything, it still keeps happening…
So either the drive is fucked or would it be possible that this is a secure boot issue?