External Hard disk not detecting in Manjaro linux

Support
, ,
1

My hard disk is not detecting what to do it does detected in fdisk -l
I used this command to generate any kind of problems available in external hdd

sudo smartctl --all /dev/sdc

Output:

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.14.2-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Elements / My Passport (USB, AF)
Device Model:     WDC WD20NMVW-11EDZS7
Serial Number:    WD-WX31A8690TTR
LU WWN Device Id: 5 0014ee 20dd84775
Firmware Version: 01.01A01
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Sep 21 21:10:41 2021 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

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: 		(37020) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					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: 	 ( 409) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x7035)	SCT Status 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   200   195   051    Pre-fail  Always       -       66
  3 Spin_Up_Time            0x0027   210   201   021    Pre-fail  Always       -       4491
  4 Start_Stop_Count        0x0032   084   084   000    Old_age   Always       -       16483
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   071   071   000    Old_age   Always       -       21577
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   097   097   000    Old_age   Always       -       3442
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       205
193 Load_Cycle_Count        0x0032   153   153   000    Old_age   Always       -       141773
194 Temperature_Celsius     0x0022   121   104   000    Old_age   Always       -       31
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 4
	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 4 occurred at disk power-on lifetime: 2023 hours (84 days + 7 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
  -- -- -- -- -- -- --
  04 61 06 38 4f c2 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 d0 06 38 4f c2 00 00      00:35:30.906  IDLE IMMEDIATE
  e0 d0 06 38 4f c2 00 00      00:31:16.315  STANDBY IMMEDIATE
  e7 d0 06 38 4f c2 00 00      00:31:16.314  FLUSH CACHE
  b0 d0 06 38 4f c2 00 00      00:29:43.403  SMART READ DATA
  b0 d0 06 38 4f c2 00 00      00:25:43.631  SMART READ DATA

Error 3 occurred at disk power-on lifetime: 2023 hours (84 days + 7 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
  -- -- -- -- -- -- --
  04 61 06 38 4f c2 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e0 d0 06 38 4f c2 00 00      00:31:16.315  STANDBY IMMEDIATE
  e7 d0 06 38 4f c2 00 00      00:31:16.314  FLUSH CACHE
  b0 d0 06 38 4f c2 00 00      00:29:43.403  SMART READ DATA
  b0 d0 06 38 4f c2 00 00      00:25:43.631  SMART READ DATA
  b0 d0 06 38 4f c2 00 00      00:21:43.859  SMART READ DATA

Error 2 occurred at disk power-on lifetime: 2023 hours (84 days + 7 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
  -- -- -- -- -- -- --
  04 61 06 38 4f c2 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e7 d0 06 38 4f c2 00 00      00:31:16.314  FLUSH CACHE
  b0 d0 06 38 4f c2 00 00      00:29:43.403  SMART READ DATA
  b0 d0 06 38 4f c2 00 00      00:25:43.631  SMART READ DATA
  b0 d0 06 38 4f c2 00 00      00:21:43.859  SMART READ DATA
  b0 d0 06 38 4f c2 00 00      00:17:44.087  SMART READ DATA

Error 1 occurred at disk power-on lifetime: 2023 hours (84 days + 7 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
  -- -- -- -- -- -- --
  04 61 06 38 4f c2 00  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 90 06 38 4f c2 00 00      00:05:44.879  SET FEATURES [Disable SATA feature]
  b0 d0 08 38 4f c2 00 00      00:05:12.802  SMART READ DATA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Conveyance offline  Completed without error       00%     21526         -
# 2  Conveyance offline  Completed without error       00%      4294         -
# 3  Conveyance offline  Completed without error       00%      3393         -
# 4  Conveyance offline  Completed without error       00%      2943         -
# 5  Conveyance offline  Completed without error       00%      2052         -
# 6  Conveyance offline  Completed without error       00%      1372         -
# 7  Conveyance offline  Completed without error       00%       958         -

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.

Can anyone help me out and tell me whats going on?

2

You have a few ATA errors already.

You never ran any short or extended SMART tests (only “conveyance” which tests for issues caused by transportation and movement.)

Run a short SMART test, and if it doesn’t abort with an error, run an extended test overnight.

sudo smartctl -t short /dev/sdc

After a few minutes, check the reults,

sudo smartctl -l selftest /dev/sdc

If it completed without any errors, run an extended test overnight,

sudo smartctl -t long /dev/sdc

Then hopefully it’s finished by then, which you can check again,

sudo smartctl -l selftest /dev/sdc

3

after short test I am getting this output:

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.14.2-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
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%     21579         -
# 2  Conveyance offline  Completed without error       00%     21526         -
# 3  Conveyance offline  Completed without error       00%      4294         -
# 4  Conveyance offline  Completed without error       00%      3393         -
# 5  Conveyance offline  Completed without error       00%      2943         -
# 6  Conveyance offline  Completed without error       00%      2052         -
# 7  Conveyance offline  Completed without error       00%      1372         -
# 8  Conveyance offline  Completed without error       00%       958         -

after long run test I got this:

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.14.2-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
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%     21579         -
# 2  Conveyance offline  Completed without error       00%     21526         -
# 3  Conveyance offline  Completed without error       00%      4294         -
# 4  Conveyance offline  Completed without error       00%      3393         -
# 5  Conveyance offline  Completed without error       00%      2943         -
# 6  Conveyance offline  Completed without error       00%      2052         -
# 7  Conveyance offline  Completed without error       00%      1372         -
# 8  Conveyance offline  Completed without error       00%       958         -
4

The long test didn’t finish.

You can run,

sudo smartctl -a /dev/sdc

Then check under,
Self-test execution status:

5 
Self-test execution status:      ( 248)	    Self-test routine in progress...
					                        80% of test remaining.

Is there any way to see the live progress of this test(I mean in real time)

6

No. It’s all internal, and unknown to the outside world. You can periodically check to see if it finished, and if it found an error, it will abort before completing the test. (You’ll see it logged.)

7

after the long test

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.14.2-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     21600         -
# 2  Short offline       Completed without error       00%     21579         -
# 3  Conveyance offline  Completed without error       00%     21526         -
# 4  Conveyance offline  Completed without error       00%      4294         -
# 5  Conveyance offline  Completed without error       00%      3393         -
# 6  Conveyance offline  Completed without error       00%      2943         -
# 7  Conveyance offline  Completed without error       00%      2052         -
# 8  Conveyance offline  Completed without error       00%      1372         -
# 9  Conveyance offline  Completed without error       00%       958         -
8

That’s actually good news, for the most part. At least you can say you ran a full extended SMART test with zero read errors.

When you plug in the drive, what messages do you see under,

sudo dmesg | tail -n 50

10 seconds or so after plugging it in?

While it’s still plugged in, what is the output of your block devices?

lsblk

9

lsblk output:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0  32.3M  1 loop /var/lib/snapd/snap/snapd/12883
loop1    7:1    0 130.2M  1 loop /var/lib/snapd/snap/strimio-desktop/58
loop2    7:2    0  65.1M  1 loop /var/lib/snapd/snap/gtk-common-themes/1515
loop3    7:3    0  55.4M  1 loop /var/lib/snapd/snap/core18/2128
loop4    7:4    0 164.8M  1 loop /var/lib/snapd/snap/gnome-3-28-1804/161
loop5    7:5    0  32.3M  1 loop /var/lib/snapd/snap/snapd/13170
loop6    7:6    0     4K  1 loop /var/lib/snapd/snap/bare/5
loop7    7:7    0  65.2M  1 loop /var/lib/snapd/snap/gtk-common-themes/1519
sda      8:0    0 465.8G  0 disk 
└─sda1   8:1    0 465.8G  0 part /
sdb      8:16   0 465.8G  0 disk 
├─sdb1   8:17   0 155.2G  0 part /media/WDBlue1
├─sdb2   8:18   0 155.5G  0 part /media/WDBlue2
└─sdb3   8:19   0   155G  0 part /media/WDBlue3
sdc      8:32   0   1.8T  0 disk 
└─sdc1   8:33   0   1.8T  0 part /run/media/brijesh/Elements
sdd      8:48   0   1.8T  0 disk 
└─sdd1   8:49   0   1.8T  0 part /run/media/brijesh/My Passport
10

This might be a known KDE issue that’s being worked on.

If you reboot and try to plug it in again, does it work?

I’ll find the bug report and link to it in here.

EDIT: Found it.

https://bugs.kde.org/show_bug.cgi?id=438874

It’s going to be fixed in KDE Plasma 5.23. Currently we’re on 5.22.

So to rule that out, reboot your computer without the drive plugged in. After you fully log in, plug in the drive and see if you can access it.

11

Update:
my disk is not detecting at all (WD Elements)
Not even in fdisk -l

12

Referring to all your external disks? Your output shows three different disks.

13

best thing to do is to wait for the update.

1 Like
14
Initial post

Can the problem be related to 2 disks (/dev/sdc and /dev/sdd) mounted under /run/ (and only /dev/sdb* mounted under the usual /media/ ) ?

EDIT: Sorry, learnt that they are external drives and are not mounted via fstab.

15

sdc and sdd is the external drive
sdb is the internal harddisk

now only the Elements drive is not detecting?

16

Can I say that this is happening due the errors which came in
sudo smartctl --all /dev/sdc

17