el fsck de hoy

Device     Boot  Start       End   Sectors   Size Id Type
/dev/sdb1         8192    532479    524288   256M  c W95 FAT32 (LBA)
/dev/sdb2       532480 468862127 468329648 223,3G 83 Linux
pi@raspberrypi:~ $ sudo mount /dev/sdb1 /media
pi@raspberrypi:~ $ cd /media
pi@raspberrypi:/media $ ls
bcm2708-rpi-b.dtb         cmdline.txt    kernel8.img
bcm2708-rpi-b-plus.dtb    config.txt     kernel.img
bcm2708-rpi-b-rev1.dtb    COPYING.linux  LICENCE.broadcom
bcm2708-rpi-cm.dtb        fixup4cd.dat   overlays
bcm2708-rpi-zero.dtb      fixup4.dat     start4cd.elf
bcm2708-rpi-zero-w.dtb    fixup4db.dat   start4db.elf
bcm2709-rpi-2-b.dtb       fixup4x.dat    start4.elf
bcm2710-rpi-2-b.dtb       fixup_cd.dat   start4x.elf
bcm2710-rpi-3-b.dtb       fixup.dat      start_cd.elf
bcm2710-rpi-3-b-plus.dtb  fixup_db.dat   start_db.elf
bcm2710-rpi-cm3.dtb       fixup_x.dat    start.elf
bcm2711-rpi-4-b.dtb       issue.txt      start_x.elf
bcm2711-rpi-cm4.dtb       kernel7.img
bootcode.bin              kernel7l.img
pi@raspberrypi:/media $
esto es la primera partición del ssd montada, con los ficheros que tiene.

/ $ sudo fsck /dev/sdb1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
fsck.ext2: No existe el fichero o el directorio while trying to open /dev/sdb1
Possibly non-existent device?
pi@raspberrypi:/ $ sudo lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0 465,8G  0 disk
└─sda2        8:2    0 465,5G  0 part /mnt
sdb           8:16   0 223,6G  0 disk
├─sdb1        8:17   0   256M  0 part
└─sdb2        8:18   0 223,3G  0 part
mmcblk0     179:0    0  59,5G  0 disk
├─mmcblk0p1 179:1    0   256M  0 part /boot
└─mmcblk0p2 179:2    0  59,2G  0 part /
pi@raspberrypi:/ $ sudo fsck -y /dev/sdb
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
fsck.ext2: Error de entrada/salida 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>