Usb 3 tikun alustus ei onnistu

[Frank Zappa]

Palataan taas kivikaudelle ( viime vuosituhannen aiheisiin  )  uusilla usb3 tikuilla. Tikulla on fat32 systeemi, mutta sitä ei saa kokonaan poistettu ja siis jää herja suberblockista tms ongelmasta.
Yritin viimeksi  clear -toimintoa gpartedilla, mutta sekään ei pure tikkuun.  Ainoastaan  voi formatoida  takaisin fat32:ksi ja tikku toimii taas ok. 

Eli pitäis  formatoida tikku ext4ksi, mutta mikään temppu ei pure.        Pitäs löytää joku  syvätekniikka  jolla  käsitellä tikku ?

-------------------------------------------------------------

gparted:
Unable to detect file system! Possible reasons are:
- The file system is damaged
- The file system is unknown to GParted
- There is no file system available (unformatted)
- The device entry /dev/sdb1 is missing

---------------------

ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sdb

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>

Found a dos partition table in /dev/sdb

---------------------------------------------------------

T: Frank Zappa 

[nm]

Luo tikulle uusi msdos- tai Guid-osiotaulu Gpartedilla ja luo sen jälkeen  ext4-osio.

[Frank Zappa]

Juu ei toimi.    Tuloksena  seuravaa:


qparted toistaa muutaman kerran ja ohjelmaa käynnistäessä aina:
   The backup GPT table is corrupt, but the primary appears ok, so that will be used.

------------------------------

qparted: warning.

<i>Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          56840c87-1c4e-42e7-a94a-5f89e4aa07e4
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              3842048
Block count:              15359488
Reserved block count:     767974
Overhead clusters:        319927
Free blocks:              15039555
Free inodes:              3842037
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      1020
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Fri Dec  5 20:06:08 2025
Last mount time:          n/a
Last write time:          Fri Dec  5 20:06:31 2025
Mount count:              0
Maximum mount count:      -1
Last checked:             Fri Dec  5 20:06:08 2025
Check interval:           0 (<none>)
Lifetime writes:          4226 kB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:             256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      cd3d68f7-ccdc-4319-96d5-0b8e88f8d9d3
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0x4d532ce5</i>

<i>dumpe2fs 1.46.5 (30-Dec-2021)
Journal superblock magic number invalid!</i>

<i>Unable to read the contents of this file system!
Because of this some operations may be unavailable.
The cause might be a missing software package.
The following list of software packages is required for ext4 file system support:  e2fsprogs v1.41+.</i>

----------------------------------

Tuloksena:
Unable to mount 63 gb volume

Error mounting /dev/sda1 at /media/user/4334-device:
wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program or other error.

Eli  gparted ei pääse eroon  backup corruptiosta, vaikka käyttää primary juttua. ?

T; Frank Zappa