Monday, May 20, 2024
2
rated 0 times [  2] [ 0]  / answers: 1 / hits: 1760  / 3 Years ago, sat, september 25, 2021, 8:49:21

I have a 2TB flash drive that was corrupted when I pulled it out without ejecting it first. I am trying to erase the files, delete the partition, and reformat the whole thing. All the obvious things are not working though.



Disks couldn't overwrite the data because it's read-only, GParted has 2 things it will do, if it's already unmounted then GParted simply crashes, if the drive is mounted, GParted will open and then crash when I unmount it. I even attempted to use unetbootin to overwrite the files with an Ubuntu iso and it didn't work. I tried changing the files to read/write but that didn't work either. Any suggestions?



$ sudo fsck -n /dev/sdb
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
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/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>

$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 1.9 TiB, 2097152000000 bytes, 4096000000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00095e6d

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 4095999999 4095997952 1.9T b W95 FAT32

$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 230.6G 0 part /
└─sda5 8:5 0 7.9G 0 part [SWAP]
sdb 8:16 1 1.9T 1 disk
└─sdb1 8:17 1 1.9T 1 part
sr0 11:0 1 1024M 0 rom


result of sudo dmesg | grep -E 'usb|sdb'
http://pastebin.ca/3766662



The usb says it is a Transcend but I think it's a knock off, it shows up in the results linked above as generic mass storage.


More From » partitioning

 Answers
5

The problem turned out to be a hardware issue. The people I bought the drive from were jerks and they hacked it to make it think it was 2 TB when it was only 120+ GB. I went over that data cap and the drive didn't know what to do so it crashed. There was no fixing it so I threw it away.


[#12179] Sunday, September 26, 2021, 3 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
humbire

Total Points: 55
Total Questions: 93
Total Answers: 113

Location: Oman
Member since Fri, Dec 23, 2022
1 Year ago
;