[Discuss] memory stick issue

[dsr at randomstring.org (Dan Ritter)]

dan moylan wrote: 
> 
> running fc36 on lenevo thinkpad T460
> 
> moylan cmd[1051] sudo mke2fs -text4 -LBCKUP1n /dev/sdb
> [sudo] password for moylan:
> 
> mke2fs 1.46.5 (30-Dec-2021)
> /dev/sdb contains a ext4 file system labelled 'BCKUP1n'
> 	created on Mon Sep  5 10:20:13 2022
> Proceed anyway? (y,N) y
> Creating filesystem with 32768000 4k blocks and 8192000 inodes
> Filesystem UUID: 7e40cd11-4989-4274-8e56-6b6f96a3d4d2
> Superblock backups stored on blocks:
> 	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
> 	4096000, 7962624, 11239424, 20480000, 23887872
> 
> Allocating group tables: done
> Writing inode tables: done
> Creating journal (131072 blocks): done
> Writing superblocks and filesystem accounting information: done
> 
> moylan cmd[1052] sudo mount -text4 /dev/sdb /run/media/moylan/BCKUP1n
> [sudo] password for moylan:
> 
> mount: /run/media/moylan/BCKUP1n: wrong fs type, bad option, bad superblock
>        on /dev/sdb, missing codepage or helper program, or other error.
>        dmesg(1) may have more information after failed mount system call.
> 
> dmesg:
> 1102 [168206.124660] JBD2: no valid journal superblock found
> 1103 [168206.124671] EXT4-fs (sdb): error loading journal
> 
> any suggestions?

First, make sure you don't have an entry for /dev/sdb or for
/run/media/moylan/BCKUP1n in your /etc/fstab.

Then:

wipefs /dev/sdb

read the output and do the wipefs -o that it suggests.

Then redo the mkfs.

-dsr-