I had a problem with a 16GB memory stick today - it went wrong as I
was copying a file to it. It was not possible to umount it and
Konqueror crashed when I unplugged it. I thought it might be a
permanent hardware failure, but took it to a public library and tried
it in a Windows machine. It worked perfectly well with that, I was
able to write a test file to it. However, on my own machine (Debian)
it is not possible to mount it. Following an internet search, I tried
a few things. Here are relevant lines from the results:
lsusb
Bus 001 Device 014: ID 0781:556b SanDisk Corp. Cruzer Edge
dmesg
[ 1918.142092] sd 7:0:0:0: [sdf] Attached SCSI removable disk
lsblk
sdf 8:80 1 14.6G 0 disk
└─sdf1 8:81 1 14.6G 0 part
root@debian:/# sudo mke2fs -n /dev/sdf1
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 3824380 4k blocks and 956592 inodes
Filesystem UUID: 5a8d4690-0877-4723-ab84-1ded34ce852a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
root@debian:/# sudo fsck -b 32768 /dev/sdf1
fsck from util-linux 2.36.1
e2fsck 1.46.2 (28-Feb-2021)
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdf1
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>
(and the same result with other block numbers and sudo e2fsck)
Is there anything else I could try?
Failing that, how might I re-format it so that it can be used with
Linux and Windows?
I would be grateful for any advice.
Peter Alefounder.
--
Please post to: Hampshire@???
Manage subscription:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG website:
http://www.hantslug.org.uk
--------------------------------------------------------------
