便携式固态硬盘损坏,检测到错误的大小,该怎么办?

便携式固态硬盘损坏,检测到错误的大小,该怎么办?

我有一台 Transcend 的 240 GB 便携式 SSD。

最近,读取数据时出现了长时间的延迟。在另一次如此长时间的延迟期间,我不安全地断开了设备。之后,一个大约 2 GB 的文件从我的磁盘上消失了。我试图通过文件系统实用程序测试磁盘,但文件丢失。

然后我尝试使用最重要的

Foremost version 1.5.7 by Jesse Kornblum, Kris Kendall, and Nick Mikus
Audit File

Foremost started at Wed Jan  3 20:38:43 2024
Invocation: foremost -w -i /dev/sdc1 -o /home/user/output
Output directory: /home/user/output
Configuration file: /etc/foremost.conf
------------------------------------------------------------------
File: /dev/sdc1
Start: Wed Jan  3 20:38:43 2024
Length: 223 GB (240022786048 bytes)
 
Num  Name (bs=512)         Size  File Offset     Comment 

重新连接几次后,磁盘完全无法正确连接。它没有安装。更糟糕的是,它的大小现在显示为 1023 MB。我还尝试将驱动器连接到另一台笔记本电脑,它也显示大约 1 GB 的大小。

$ lsblk -o name,label,size,fstype,model

sdc           1023,8M                          
$ sudo fdisk -l /dev/sdc

Disk /dev/sdc: 1023,75 MiB, 1073479680 bytes, 2096640 sectors
Disk model:                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
sudo smartctl -a /dev/sdс
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.2.0-39-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     SM2258AB-10-00M01000
Serial Number:    (03)5526888-20080228
Firmware Version: 20141211
User Capacity:    1 073 479 680 bytes [1,07 GB]
Sector Size:      512 bytes logical/physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 (minor revision not indicated)
Local Time is:    Thu Jan  4 17:12:50 2024 +06
SMART support is: Unavailable - device lacks SMART capability.

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
$ sudo smartctl -a /dev/sdc -T permissive
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.2.0-39-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     SM2258AB-10-00M01000
Serial Number:    (03)5526888-20080228
Firmware Version: 20141211
User Capacity:    1 073 479 680 bytes [1,07 GB]
Sector Size:      512 bytes logical/physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 (minor revision not indicated)
Local Time is:    Thu Jan  4 11:02:26 2024 +06
SMART support is: Unavailable - device lacks SMART capability.

SMART Disabled. Use option -s with argument 'on' to enable it.
(override with '-T permissive' option)
$ sudo smartctl -a /dev/sdс -T permissive -s on
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.2.0-39-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     SM2258AB-10-00M01000
Serial Number:    (03)5526888-20080228
Firmware Version: 20141211
User Capacity:    1 073 479 680 bytes [1,07 GB]
Sector Size:      512 bytes logical/physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 (minor revision not indicated)
Local Time is:    Thu Jan  4 17:20:39 2024 +06
SMART support is: Unavailable - device lacks SMART capability.

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Total time to complete Offline 
data collection:        (    0) seconds.
Offline data collection
capabilities:            (0x00)     Offline data collection not supported.
SMART capabilities:            (0x0000) Automatic saving of SMART data                  is not implemented.
Error logging capability:        (0x00) Error logging NOT supported.
                    No General Purpose Logging support.

SMART Error Log not supported

SMART Self-test Log not supported

Selective Self-tests/Logging not supported

我发现另一个案例SM2258AB模型产生 1023MB 的大小时。但我仍然不明白它能为我做什么。

连接驱动器后:

$ sudo dmesg

[ 1872.464166] usb 1-1.3: new high-speed USB device number 16 using ehci-pci
[ 1872.607596] usb 1-1.3: New USB device found, idVendor=2174, idProduct=2000, bcdDevice=80.00
[ 1872.607610] usb 1-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 1872.607616] usb 1-1.3: Product: StoreJet Transcend
[ 1872.607621] usb 1-1.3: Manufacturer: Transcend
[ 1872.607625] usb 1-1.3: SerialNumber: (03)5526888-20080228
[ 1872.610291] scsi host5: uas
[ 1872.611776] scsi 5:0:0:0: Direct-Access     StoreJet                  0    PQ: 0 ANSI: 6
[ 1872.616885] sd 5:0:0:0: Attached scsi generic sg3 type 0
[ 1872.617558] sd 5:0:0:0: [sdc] 2096640 512-byte logical blocks: (1.07 GB/1024 MiB)
[ 1872.618040] sd 5:0:0:0: [sdc] Write Protect is off
[ 1872.618048] sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 1872.618802] sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1872.619017] sd 5:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
[ 1872.619024] sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
[ 1872.623443] sd 5:0:0:0: [sdc] Attached SCSI disk
[ 1903.644223] sd 5:0:0:0: [sdc] tag#29 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD 
[ 1903.644237] sd 5:0:0:0: [sdc] tag#29 CDB: Read(10) 28 00 00 1f fd f0 00 00 08 00
[ 1903.672418] scsi host5: uas_eh_device_reset_handler start
[ 1903.752171] usb 1-1.3: reset high-speed USB device number 16 using ehci-pci
[ 1903.903013] scsi host5: uas_eh_device_reset_handler success
[ 1934.364272] sd 5:0:0:0: [sdc] tag#3 uas_eh_abort_handler 0 uas-tag 1 inflight: IN 
[ 1934.364288] sd 5:0:0:0: [sdc] tag#3 CDB: Read(10) 28 00 00 00 02 08 00 01 f8 00
[ 1934.388284] scsi host5: uas_eh_device_reset_handler start
[ 1934.468205] usb 1-1.3: reset high-speed USB device number 16 using ehci-pci
[ 1934.615346] scsi host5: uas_eh_device_reset_handler success
$ sudo journalctl  --follow

Jan 04 10:34:27 user-notebook kernel: usb 1-1.3: new high-speed USB device number 17 using ehci-pci
Jan 04 10:34:27 user-notebook kernel: usb 1-1.3: New USB device found, idVendor=2174, idProduct=2000, bcdDevice=80.00
Jan 04 10:34:27 user-notebook kernel: usb 1-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Jan 04 10:34:27 user-notebook kernel: usb 1-1.3: Product: StoreJet Transcend
Jan 04 10:34:27 user-notebook kernel: usb 1-1.3: Manufacturer: Transcend
Jan 04 10:34:27 user-notebook kernel: usb 1-1.3: SerialNumber: (03)5526888-20080228
Jan 04 10:34:27 user-notebook kernel: scsi host5: uas
Jan 04 10:34:27 user-notebook kernel: scsi 5:0:0:0: Direct-Access     StoreJet                  0    PQ: 0 ANSI: 6
Jan 04 10:34:27 user-notebook mtp-probe[7783]: checking bus 1, device 17: "/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3"
Jan 04 10:34:27 user-notebook mtp-probe[7783]: bus: 1, device: 17 was not an MTP device
Jan 04 10:34:27 user-notebook kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
Jan 04 10:34:27 user-notebook kernel: sd 5:0:0:0: [sdc] 2096640 512-byte logical blocks: (1.07 GB/1024 MiB)
Jan 04 10:34:27 user-notebook kernel: sd 5:0:0:0: [sdc] Write Protect is off
Jan 04 10:34:27 user-notebook kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
Jan 04 10:34:27 user-notebook kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 04 10:34:27 user-notebook kernel: sd 5:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
Jan 04 10:34:27 user-notebook kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
Jan 04 10:34:27 user-notebook kernel: sd 5:0:0:0: [sdc] Attached SCSI disk
Jan 04 10:34:27 user-notebook systemd-udevd[7782]: 1-1.3:1.0: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_cupsd /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0 0:0' failed with exit code 1.
Jan 04 10:34:27 user-notebook systemd-udevd[7782]: 1-1.3:1.0: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_ippeveprinter /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0 0:0' failed with exit code 1.
Jan 04 10:34:27 user-notebook mtp-probe[7795]: checking bus 1, device 17: "/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3"
Jan 04 10:34:27 user-notebook mtp-probe[7795]: bus: 1, device: 17 was not an MTP device
Jan 04 10:34:27 user-notebook systemd-udevd[7782]: 1-1.3: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_cupsd /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3 189:16' failed with exit code 1.
Jan 04 10:34:27 user-notebook systemd-udevd[7782]: 1-1.3: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_ippeveprinter /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3 189:16' failed with exit code 1.
Jan 04 10:34:58 user-notebook kernel: sd 5:0:0:0: [sdc] tag#20 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD 
Jan 04 10:34:58 user-notebook kernel: sd 5:0:0:0: [sdc] tag#20 CDB: Read(10) 28 00 00 1f fd f0 00 00 08 00
Jan 04 10:34:58 user-notebook kernel: scsi host5: uas_eh_device_reset_handler start
Jan 04 10:34:58 user-notebook kernel: usb 1-1.3: reset high-speed USB device number 17 using ehci-pci
Jan 04 10:34:59 user-notebook kernel: scsi host5: uas_eh_device_reset_handler success

我还能尝试用它做什么?

假设:

也许我可以切换一些模式?也许有一些具有最低限度功能的安全模式,但哪种模式可以让我读取磁盘?例如,尝试在 USB 1/2/3 模式下工作?或者尝试一些其他驱动程序?

如果磁盘谎报了其大小,是否可以以某种方式向系统指示真实大小并仍尝试读取数据。例如,指定磁盘大小为 200 GB,并强制它逐字节读取磁盘信息,直到读完为止?

不幸的是,我对磁盘以前的结构了解甚少。但我还有启动日志文图伊,也许我可以以某种方式恢复分区。

sudo ./Ventoy2Disk.sh -I -s -g -L Data /dev/sdc

**********************************************
      Ventoy: 1.0.64  x86_64
      longpanda [email protected]
      https://www.ventoy.net
**********************************************

Disk : /dev/sdc
Model: StoreJet  (scsi)
Size : 223 GB
Style: GPT


Attention:
You will install Ventoy to /dev/sdc.
All the data on the disk /dev/sdc will be lost!!!

Continue? (y/n) y

All the data on the disk /dev/sdc will be lost!!!
Double-check. Continue? (y/n) y

Create partitions on /dev/sdc by parted in GPT style ...
Done
Wait for partitions ...
partition exist OK
create efi fat fs /dev/sdc2 ...
mkfs.fat 4.1 (2017-01-24)
success
Wait for partitions ...
/dev/sdc1 exist OK
/dev/sdc2 exist OK
partition exist OK
Format partition 1 /dev/sdc1 ...
mkexfatfs 1.3.0
Creating... done.
Flushing... done.
File system created successfully.
mkexfatfs success
writing data to disk ...
sync data ...
esp partition processing ...

Install Ventoy to /dev/sdc successfully finished.

相关内容