Dead Hard Drive Partition

nehwl · 22 December 2020 20:57

context:

My Laptop currently is 4 years old. Mainly divided into one 500 GB partition on sda3 one 243 GB partition on sd4 and one 183 GB partition on sda5. I previously ran Windows on the aforementioned 500 GB disk. I had reinstalled windows multiple times. I then made a dual boot system with Manjaro running on sda5 on ext4. When i was ready to completely shift my system i reformatted my NTFS windows partition to ext4 and used as my main storage, but the partition was not being recognized properly. I consulted the fourm : Manjaro not recognizing other Partitions

I tweaked my Fstab and then it started working fine. After a while the hard drive crashed but after and fsck it started working but showed bad sectors.

Today when I came home, the ext4 partition was registering as an unknown partition type in Manjros Gnome Disk Utility.

I ran fsck, which was able to recognize it was an ext4 partition, but showed the following error:

username@systemname ~> sudo fsck /dev/sda3                                                                                              (base)
[sudo] password for alux:
fsck from util-linux 2.36.1
e2fsck 1.45.6 (20-Mar-2020)
fsck.ext2: Input/output error while trying to open /dev/sda3

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>

after running e2fsck -b 8193 /dev/sda3

username@systemname ~ [8]> sudo e2fsck -b 8193 /dev/sda3                                                                                (base)
e2fsck 1.45.6 (20-Mar-2020)
e2fsck: Bad magic number in super-block while trying to open /dev/sda3

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>

I tried running e2fsck -b 32768 It runs and find alot of the following type errors:

Free inodes count wrong for group #2304 (8192, counted=5109).
Fix<y>? yes
Directories count wrong for group #2304 (0, counted=600).
Fix<y>? yes

Then the following error pops:

Padding at end of inode bitmap is not set. Fix<y>? yes
Error writing block 1 (Input/output error).  Ignore error<y>? yes

/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda3: 317558/32923648 files (0.6% non-contiguous), 86272400/131664384 blocks
Error writing block 1 (Input/output error).  Ignore error<y>? yes
username@systemname ~ [1]>

and abruptly shutsdown.

I dont care about getting the partition working. I have ordered a new hard drive to replace this. There are a bunch of important pictures on this partition. Is there anyway to recover it.
Even paid services would be fine, but I wish to recover as much as i can from it.

Any methods to recover it?

nehwl · 22 December 2020 21:00

For refrence:

username@systemname ~> lsblk                                                                                                            (base)
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 931.5G  0 disk
├─sda1   8:1    0   260M  0 part /boot/efi
├─sda3   8:3    0 502.3G  0 part
├─sda4   8:4    0 243.7G  0 part
└─sda5   8:5    0 185.2G  0 part /
sr0     11:0    1  1024M  0 rom
username@systemname ~> findmnt -D                                                                                                       (base)
SOURCE    FSTYPE     SIZE  USED  AVAIL USE% TARGET
dev       devtmpfs   3.7G     0   3.7G   0% /dev
run       tmpfs      3.8G  1.4M   3.8G   0% /run
/dev/sda5 ext4     181.3G 93.4G  78.9G  52% /
tmpfs     tmpfs      3.8G     0   3.8G   0% /dev/shm
tmpfs     tmpfs        4M     0     4M   0% /sys/fs/cgroup
tmpfs     tmpfs      3.8G 23.7M   3.7G   1% /tmp
/dev/sda1 vfat       256M 41.4M 214.6M  16% /boot/efi
tmpfs     tmpfs    769.3M  120K 769.2M   0% /run/user/1000
username@systemname ~> sudo smartctl -a /dev/sda3                                                                                       (base)
[sudo] password for username:
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.80-2-MANJARO] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01ABD...
Device Model:     TOSHIBA MQ01ABD100
Serial Number:    95P8PLERT
LU WWN Device Id: 5 000039 6825073a0
Firmware Version: AX1P2C
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Dec 23 02:28:43 2020 IST
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
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x85)	Offline data collection activity
					was aborted by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
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: 			 (0x51) 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.
					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: 	 ( 203) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
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
  2 Throughput_Performance  0x0027   100   100   050    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0023   100   100   002    Pre-fail  Always       -       1735
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       13888
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   074   074   000    Old_age   Always       -       10619
 10 Spin_Retry_Count        0x0033   253   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       4679
183 Runtime_Bad_Block       0x0032   100   100   001    Old_age   Always       -       66
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
185 Unknown_Attribute       0x0032   100   100   001    Old_age   Always       -       65535
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       261
188 Command_Timeout         0x0032   100   088   000    Old_age   Always       -       546
189 High_Fly_Writes         0x003a   100   100   001    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   061   034   040    Old_age   Always   In_the_past 39 (Min/Max 21/41 #167)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       133620
192 Power-Off_Retract_Count 0x0022   100   100   000    Old_age   Always       -       9699476
193 Load_Cycle_Count        0x0032   094   094   000    Old_age   Always       -       67200
194 Temperature_Celsius     0x0022   061   034   040    Old_age   Always   In_the_past 39 (Min/Max 21/41 #167)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       8
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 264 (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 264 occurred at disk power-on lifetime: 10619 hours (442 days + 11 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
  -- -- -- -- -- -- --
  40 41 c0 00 28 0c 40  Error: WP at LBA = 0x000c2800 = 796672

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 08 a8 0e 52 40 00      15:26:32.841  WRITE FPDMA QUEUED
  60 08 c0 00 28 0c 40 00      15:26:32.841  READ FPDMA QUEUED
  60 00 b8 00 4c 49 40 00      15:26:32.841  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      15:26:32.841  FLUSH CACHE EXT
  ef 10 02 00 00 00 a0 00      15:26:32.840  SET FEATURES [Enable SATA feature]

Error 263 occurred at disk power-on lifetime: 10619 hours (442 days + 11 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
  -- -- -- -- -- -- --
  40 41 70 00 28 0c 40  Error: UNC at LBA = 0x000c2800 = 796672

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 f8 b8 08 7a d4 40 00      15:26:29.038  READ FPDMA QUEUED
  60 08 70 00 28 0c 40 00      15:26:29.037  READ FPDMA QUEUED
  61 40 a0 68 0e 52 40 00      15:26:29.037  WRITE FPDMA QUEUED
  60 f8 98 08 79 d4 40 00      15:26:29.037  READ FPDMA QUEUED
  60 78 90 88 78 d4 40 00      15:26:29.037  READ FPDMA QUEUED

Error 262 occurred at disk power-on lifetime: 10619 hours (442 days + 11 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
  -- -- -- -- -- -- --
  40 41 48 00 28 0c 40  Error: WP at LBA = 0x000c2800 = 796672

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 40 58 80 de 57 40 00      15:26:25.075  WRITE FPDMA QUEUED
  61 40 50 00 e7 12 40 00      15:26:25.075  WRITE FPDMA QUEUED
  60 08 48 00 28 0c 40 00      15:26:25.075  READ FPDMA QUEUED
  60 08 40 18 78 d4 40 00      15:26:25.075  READ FPDMA QUEUED
  61 08 38 f0 0d 52 40 00      15:26:25.075  WRITE FPDMA QUEUED

Error 261 occurred at disk power-on lifetime: 10619 hours (442 days + 11 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
  -- -- -- -- -- -- --
  40 41 d0 00 28 0c 40  Error: WP at LBA = 0x000c2800 = 796672

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 20 d8 d0 0d 52 40 00      15:26:21.241  WRITE FPDMA QUEUED
  60 08 d0 00 28 0c 40 00      15:26:21.241  READ FPDMA QUEUED
  60 08 c8 00 98 d4 40 00      15:26:21.241  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      15:26:21.102  FLUSH CACHE EXT
  61 08 a0 78 72 80 40 00      15:26:21.063  WRITE FPDMA QUEUED

Error 260 occurred at disk power-on lifetime: 10619 hours (442 days + 11 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
  -- -- -- -- -- -- --
  40 41 90 00 28 0c 40  Error: WP at LBA = 0x000c2800 = 796672

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 70 50 c4 4a 40 00      15:26:16.958  WRITE FPDMA QUEUED
  61 08 68 88 ac 4a 40 00      15:26:16.958  WRITE FPDMA QUEUED
  61 10 58 f0 a6 4a 40 00      15:26:16.958  WRITE FPDMA QUEUED
  61 08 50 38 a6 4a 40 00      15:26:16.958  WRITE FPDMA QUEUED
  61 08 48 b8 a5 4a 40 00      15:26:16.958  WRITE FPDMA QUEUED

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%      9857         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
111

Wollie · 22 December 2020 22:00

Sorry for you, I think you need a professional data recovery service. Good luck!

@all: I really don’t understand why still so many users don’t make backups. If someone uses a search engine of their choice they should easily find dozens of recommendations to do this right after installing a new OS - doesn’t matter whether it’s Windoze, pears or any Linux distro. What could be done to avoid these unnesseary issues for so many users?

nehwl · 22 December 2020 22:32

Thank you, I have my backups but I have some recent pictures I didn’t backup yet sadly. Do professional recovery services work on EXT4 partitions. And on my new HDD I plan to enable LUKs encryption, will this affect my recovery chances should anything happen to my new drive?

Wollie · 22 December 2020 22:54

LUKs or in general encryption could make it more difficult to recover data from defective disks. ext4 should not make it more difficult than other fs like ntfs.

merlock · 22 December 2020 22:57

You can lead a horse to water…

That’s a mighty big IF!

Since I can be an **shole, I say do absolutely nothing, and sit back and enjoy the show. If their personal data is that important, they would’ve made sure about safety. I mean, think about it for a minute:

How many posts/topics just on this forum are there asking, “What do you recommend for backups”?
You, (maybe) me, and others chime in with our preferences.
Never hear from them again; maybe they figured it out, maybe not. If they didn’t, then the odds of a fat finger/sudden hardware failure will jump up and bite them; catching them completely by surprise.

Then I would suggest that you devise a personal plan that involves keeping your source files intact, until you know that they’ve been properly backed up.

Pretty sure they do. Be prepared to fork out some cash, though.

Well, yeah…if something happens that you can’t decrypt the drive, all you’ll have is mumbo-jumbo (think about the Zodiac Killers’ cyphers…and raise that to a googolplex.

system · 6 January 2021 22:57

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.