SD Card not accessible after update

I updated to the latest version of Bazzite earlier this morning and when I tried to open an emulated game that is installed on the SD Card it didn't work. I played games from the SD Card yesterday. The Bazzite update probably did not do anything but the reboot or something else maybe affected it. Is there any way to get it working without a format? I had spent a lot of time setting up some Emulators and games from the card.

I went into desktop mode and I don't see the card in Dolphin, and the mount mount is not accessible either.. Tried to eject and insert again with no luck. It does show on Disks app but does not list all the details (screenshot). Inserted the card on my Mac and it asks for a format.

This is the output of the

lsblk

lsblk

mmcblk0p1

mmcblk0p1

is the partition and it was mounted on

/var/mnt/SDCARD

/var/mnt/SDCARD

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    1     0B  0 disk 
sdb           8:16   0 111.8G  0 disk 
├─sdb1        8:17   0   600M  0 part /run/media/mnx/131B-8852
├─sdb2        8:18   0     1G  0 part /run/media/mnx/28c631d9-ef1b-4161-ad45-e512ad86ba8a
└─sdb3        8:19   0 110.2G  0 part /var/mnt/SSD
mmcblk0     179:0    0 477.5G  0 disk 
└─mmcblk0p1 179:1    0 477.5G  0 part 
zram0       251:0    0   5.7G  0 disk [SWAP]
nvme0n1     259:0    0 953.9G  0 disk 
├─nvme0n1p1 259:1    0   600M  0 part /boot/efi
├─nvme0n1p2 259:2    0     1G  0 part /boot
└─nvme0n1p3 259:3    0 952.3G  0 part /sys/devices/pci0000:00/0000:00:03.1/0000:04:00.0/0000:05:00.0/0000:06:00.0/0000:07:00.0/0000:08:00.0/boot_vga
                                      /usr/share/wireplumber
                                      /usr/share/pipewire
                                      /var/home
                                      /var
                                      /sysroot/ostree/deploy/default/var
                                      /etc
                                      /sysroot

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    1     0B  0 disk 
sdb           8:16   0 111.8G  0 disk 
├─sdb1        8:17   0   600M  0 part /run/media/mnx/131B-8852
├─sdb2        8:18   0     1G  0 part /run/media/mnx/28c631d9-ef1b-4161-ad45-e512ad86ba8a
└─sdb3        8:19   0 110.2G  0 part /var/mnt/SSD
mmcblk0     179:0    0 477.5G  0 disk 
└─mmcblk0p1 179:1    0 477.5G  0 part 
zram0       251:0    0   5.7G  0 disk [SWAP]
nvme0n1     259:0    0 953.9G  0 disk 
├─nvme0n1p1 259:1    0   600M  0 part /boot/efi
├─nvme0n1p2 259:2    0     1G  0 part /boot
└─nvme0n1p3 259:3    0 952.3G  0 part /sys/devices/pci0000:00/0000:00:03.1/0000:04:00.0/0000:05:00.0/0000:06:00.0/0000:07:00.0/0000:08:00.0/boot_vga
                                      /usr/share/wireplumber
                                      /usr/share/pipewire
                                      /var/home
                                      /var
                                      /sysroot/ostree/deploy/default/var
                                      /etc
                                      /sysroot

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    1     0B  0 disk 
sdb           8:16   0 111.8G  0 disk 
├─sdb1        8:17   0   600M  0 part /run/media/mnx/131B-8852
├─sdb2        8:18   0     1G  0 part /run/media/mnx/28c631d9-ef1b-4161-ad45-e512ad86ba8a
└─sdb3        8:19   0 110.2G  0 part /var/mnt/SSD
mmcblk0     179:0    0 477.5G  0 disk 
└─mmcblk0p1 179:1    0 477.5G  0 part 
zram0       251:0    0   5.7G  0 disk [SWAP]
nvme0n1     259:0    0 953.9G  0 disk 
├─nvme0n1p1 259:1    0   600M  0 part /boot/efi
├─nvme0n1p2 259:2    0     1G  0 part /boot
└─nvme0n1p3 259:3    0 952.3G  0 part /sys/devices/pci0000:00/0000:00:03.1/0000:04:00.0/0000:05:00.0/0000:06:00.0/0000:07:00.0/0000:08:00.0/boot_vga
                                      /usr/share/wireplumber
                                      /usr/share/pipewire
                                      /var/home
                                      /var
                                      /sysroot/ostree/deploy/default/var
                                      /etc
                                      /sysroot

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    1     0B  0 disk 
sdb           8:16   0 111.8G  0 disk 
├─sdb1        8:17   0   600M  0 part /run/media/mnx/131B-8852
├─sdb2        8:18   0     1G  0 part /run/media/mnx/28c631d9-ef1b-4161-ad45-e512ad86ba8a
└─sdb3        8:19   0 110.2G  0 part /var/mnt/SSD
mmcblk0     179:0    0 477.5G  0 disk 
└─mmcblk0p1 179:1    0 477.5G  0 part 
zram0       251:0    0   5.7G  0 disk [SWAP]
nvme0n1     259:0    0 953.9G  0 disk 
├─nvme0n1p1 259:1    0   600M  0 part /boot/efi
├─nvme0n1p2 259:2    0     1G  0 part /boot
└─nvme0n1p3 259:3    0 952.3G  0 part /sys/devices/pci0000:00/0000:00:03.1/0000:04:00.0/0000:05:00.0/0000:06:00.0/0000:07:00.0/0000:08:00.0/boot_vga
                                      /usr/share/wireplumber
                                      /usr/share/pipewire
                                      /var/home
                                      /var
                                      /sysroot/ostree/deploy/default/var
                                      /etc
                                      /sysroot

mindxpertOP•9/8/25, 12:50 PM

This is on a Rog Ally X if it makes any difference.

Mmindxpert This is on a Rog Ally X if it makes any difference.

nagito || Knight of Emilia•9/8/25, 12:57 PM

you tried

sudo fsck -y /dev/mmcblk0p1

sudo fsck -y /dev/mmcblk0p1

Nnagito || Knight of Emilia you tried `sudo fsck -y /dev/mmcblk0p1`?

mindxpertOP•9/8/25, 12:58 PM

mnx@bazzite:~$ sudo fsck -y /dev/mmcblk0p1
[sudo] password for mnx:         
fsck from util-linux 2.40.4
e2fsck 1.47.2 (1-Jan-2025)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0p1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

mnx@bazzite:~$ sudo fsck -y /dev/mmcblk0p1
[sudo] password for mnx:         
fsck from util-linux 2.40.4
e2fsck 1.47.2 (1-Jan-2025)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0p1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Mmindxpert ``` mnx@bazzite:~$ sudo fsck -y /dev/mmcblk0p1 [sudo] password for mnx: ...

nagito || Knight of Emilia•9/8/25, 1:01 PM

whoops looks like it was badly corrupted
was it EXT4 or NTFS
NTFS doesn't really sipport non Windows OSes

mindxpertOP•9/8/25, 1:02 PM

I believe it was ext4 as it was accessible from Windows (back when I was dual booting).

mindxpertOP•9/8/25, 1:02 PM

So my option would be to format it, right? Whats the suggested filesystem? btrfs?

Mmindxpert I believe it was ext4 as it was accessible from Windows (back when I was dual bo...

nagito || Knight of Emilia•9/8/25, 1:03 PM

Windows by default doesn't support anything other than fat32 XFAT & NTFS

nagito || Knight of Emilia•9/8/25, 1:05 PM

so unless you installed an EXT driver on Windows Windows wouldn't be able to access it

Mmindxpert So my option would be to format it, right? Whats the suggested filesystem? btrfs...

nagito || Knight of Emilia•9/8/25, 1:07 PM

ext4 is the most mature filesystem on Linux

nagito || Knight of Emilia•9/8/25, 1:07 PM

it's what Android uses as well

mindxpertOP•9/8/25, 1:11 PM

Thanks, appreciate your help!

nagito || Knight of Emilia•9/8/25, 1:13 PM

if you can plug the card into a Windows PC & it was NTFS/FAT/EXFAT Windows may be able to fix it

mindxpertOP•9/8/25, 1:13 PM

Maybe this could be the culprit: recently I switched the app and the configs paths of the Emulators to all be in the SD Card. Could it be that they tried to do a ton of reads/writes and caused the corruption? Before the configs were under NVMe in

$HOME/.config

$HOME/.config

dir and I symlinked those to the

/mnt/SDCARD/emulator

/mnt/SDCARD/emulator

directory.

Nnagito || Knight of Emilia if you can plug the card into a Windows PC & it was NTFS/FAT/EXFAT Windows may b...

mindxpertOP•9/8/25, 1:14 PM

I don't have a Windows machine and the virtualised Windows on my Mac did not pick it up at all.

Mmindxpert I don't have a Windows machine and the virtualised Windows on my Mac did not pic...

nagito || Knight of Emilia•9/8/25, 1:14 PM

hmm VM should have assuming it was passed in

mindxpertOP•9/8/25, 1:21 PM

You're right it was not being passed it. I can see it now, but if I try to open it it asks me to format it.

mindxpertOP•9/8/25, 1:21 PM

mindxpertOP•9/8/25, 1:23 PM

I have a feeling I don't get a chance to fix it right

Original message was deleted

nagito || Knight of Emilia•9/8/25, 1:44 PM

dang it

mnx@bazzite:~$ sudo fsck -y /dev/mmcblk0p1 [sudo] password for mnx: fsck from util-linux 2.40.4 e2fsck 1.47.2 (1-Jan-2025) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0p1 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>

SD Card not accessible after update

Similar Threads

Similar Threads

Similar Threads