Hello!
Yesterday my Linux stopped (froze). I simply switched off the notebook, then switched it on again. Unfortunately, the system can no longer be started. There are faulty blocks on the hard disk. I installed my Linux Mint two years ago so that the first partition (sda1) is SWAP and the second partition (sda2) is the root partition. The root partition is also the boot partition (EFI). Unfortunately, I can no longer access my data because the hard disk cannot be mounted with a Live USB.
How can I save my data? Is there a way to repair the hard drive?
Here are a few values for my hard drive:
I would be very grateful for any helpful tips and advice.
Yesterday my Linux stopped (froze). I simply switched off the notebook, then switched it on again. Unfortunately, the system can no longer be started. There are faulty blocks on the hard disk. I installed my Linux Mint two years ago so that the first partition (sda1) is SWAP and the second partition (sda2) is the root partition. The root partition is also the boot partition (EFI). Unfortunately, I can no longer access my data because the hard disk cannot be mounted with a Live USB.
How can I save my data? Is there a way to repair the hard drive?
Here are a few values for my hard drive:
mint@mint:~$ sudo fdisk -l /dev/sda
Disk /dev/sda: 238,49 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SanDisk SD8SNAT-
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000a2bf9
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 2000895 1998848 976M 82 Linux swap / Solaris
/dev/sda2 * 2000896 500118083 498117188 237,5G ef EFI (FAT-12/16/32)
mint@mint:~$ sudo fsck.ext4 /dev/sda2
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda2
Could this be a zero-length partition?
mint@mint:~$ sudo file -s /dev/sda2
/dev/sda2: Linux rev 1.0 ext4 filesystem data, UUID=1faec859-d1e0-449c-8a0f-9bd4bb8a08c2 (needs journal recovery) (extents) (64bit) (large files) (huge files)
mint@mint:~$ sudo badblocks /dev/sda2
108
109
110
111
192691596
192691597
192691598
192691599
192728880
192728881
192728882
192728883
192728884
192728885
192728886
192728887
192728888
192728889
192728890
192728891
192728892
192728893
192728894
192728895
mint@mint:~$ sudo smartctl -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-26-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: SanDisk SD8SNAT-256G-1006
Serial Number: 164299420433
LU WWN Device Id: 5 001b44 4a66fc737
Firmware Version: Z2311006
User Capacity: 256.060.514.304 bytes [256 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: Solid State Device
Form Factor: M.2
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Sep 22 20:03:51 2021 UTC
SMART support is: Available - device has SMART capability.
SMART support is: 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.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 10) minutes.
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 100 050 Pre-fail Always - 0
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 2
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 249
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1050
171 Unknown_Attribute 0x0022 100 100 000 Old_age Always - 0
172 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
173 Unknown_Attribute 0x0033 100 100 005 Pre-fail Always - 99
174 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 22
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 3
194 Temperature_Celsius 0x0022 083 055 000 Old_age Always - 17 (Min/Max 0/45)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 2
199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 2
230 Unknown_SSD_Attribute 0x0032 100 100 000 Old_age Always - 832
244 Unknown_Attribute 0x0032 000 100 000 Old_age Always - 0
SMART Error Log Version: 255
Warning: ATA error count 65535 inconsistent with error log pointer 2
ATA Error Count: 65535 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 65535 occurred at disk power-on lifetime: 65535 hours (2730 days + 15 hours)
When the command that caused the error occurred, the device was in a vendor specific state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
ff ff ff ff ff ff ff
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
Error 65534 occurred at disk power-on lifetime: 65535 hours (2730 days + 15 hours)
When the command that caused the error occurred, the device was in a vendor specific state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
ff ff ff ff ff ff ff
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
Error 65533 occurred at disk power-on lifetime: 65535 hours (2730 days + 15 hours)
When the command that caused the error occurred, the device was in a vendor specific state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
ff ff ff ff ff ff ff
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
Error 65532 occurred at disk power-on lifetime: 65535 hours (2730 days + 15 hours)
When the command that caused the error occurred, the device was in a vendor specific state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
ff ff ff ff ff ff ff
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
ff ff ff ff ff ff ff ff 49d+17:02:47.295 [VENDOR SPECIFIC]
Error 65531 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 00 80 80 1e 18 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d1 01 01 4f c2 00 08 00:00:00.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d5 01 00 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 249 -
Selective Self-tests/Logging not supported
mint@mint:~$ blkid
/dev/sda2: UUID="1faec859-d1e0-449c-8a0f-9bd4bb8a08c2" TYPE="ext4" PARTUUID="000a2bf9-02"
/dev/sdb1: UUID="2020-06-24-19-01-47-00" LABEL="Linux Mint 20 Cinnamon 64-bit" TYPE="iso9660" PTUUID="4089a39b" PTTYPE="dos" PARTUUID="4089a39b-01"
mint@mint:~$ lsblk -f
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0 squashfs 0 100% /rofs
sda
├─sda1 swap 0e36faff-1580-468c-bc41-8bdef49fcfe4 [SWAP]
└─sda2 ext4 1faec859-d1e0-449c-8a0f-9bd4bb8a08c2
sdb iso9660 Linux Mint 20 Cinnamon 64-bit 2020-06-24-19-01-47-00
├─sdb1 iso9660 Linux Mint 20 Cinnamon 64-bit 2020-06-24-19-01-47-00 0 100% /cdrom
├─sdb2 vfat 1AC3-20ED
└─sdb3 ext4 writable 4c7c3bec-2ff8-4dc5-9c2e-f3ea67fa4a7d 26G 0% /var/log
mint@mint:~$ sudo fsck /dev/sda2
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda2
Could this be a zero-length partition?
I would be very grateful for any helpful tips and advice.