Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
06-09-2022, 02:15 PM
|
#1
|
Member
Registered: Dec 2014
Posts: 37
Rep: 
|
is hdd dead?
my hdd is detected using both lsblk+uefirmware but is showing (0) bytes
i'd installed arch latest kernel and up to date all packages
is a 500 GB seagate... anybody else experienced this issue? is it dead?
i'm trying to access it using system-rescue usb but no luck using 'photorec'/'testdisk'
any advice will be appreciated
|
|
|
06-09-2022, 02:47 PM
|
#2
|
LQ Guru
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 11,380
|
You don't give enough information ... "the devil is in the details."
Maybe start by using the smartctl command to see if you can get any information out of the drive's on-board diagnostics.
|
|
|
06-09-2022, 03:47 PM
|
#3
|
Member
Registered: Dec 2014
Posts: 37
Original Poster
Rep: 
|
Quote:
Originally Posted by sundialsvcs
You don't give enough information ... "the devil is in the details."
Maybe start by using the smartctl command to see if you can get any information out of the drive's on-board diagnostics.
|
Code:
[root@sysrescue ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 631.9M 1 loop /run/archiso/sfs/airootfs
sda 8:0 0 0B 0 disk
sdb 8:16 1 3.7G 0 disk
├─sdb1 8:17 1 703M 0 part /run/archiso/bootmnt
└─sdb2 8:18 1 1.4M 0 part
sr0 11:0 1 1024M 0 rom
[root@sysrescue ~]# smartctl -i -H /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.22-1-lts] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Laptop HDD
Device Model: ST500LT012-1DG142
Serial Number: SBY3F5Z8
LU WWN Device Id: 5 000c50 08c87aeba
Firmware Version: 0003
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Jun 9 20:44:25 2022 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Read SMART Data failed: scsi error badly formed scsi parameters
=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error badly formed scsi parameters
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.
[root@sysrescue ~]# smartctl -P show /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.22-1-lts] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Drive found in smartmontools Database. Drive identity strings:
MODEL: ST500LT012-1DG142
FIRMWARE: 0003
match smartmontools Drive Database entry:
MODEL REGEXP: ST((25|32|50)0LT0(12|15|25)|(32|50)0LM0(10|21)|[34]000LM016)-.*
FIRMWARE REGEXP: .*
MODEL FAMILY: Seagate Laptop HDD
ATTRIBUTE OPTIONS: None preset; no -v options are required.
thxs! it's my first time in linux with a broken hdd
|
|
|
06-09-2022, 04:34 PM
|
#4
|
Member
Registered: Jan 2022
Location: Earth
Distribution: Debian
Posts: 249
Rep: 
|
Try checking the drive for errors:
If you manage to get the drive working, you should back up the data on it immediately.
|
|
|
06-09-2022, 04:48 PM
|
#5
|
Member
Registered: Dec 2014
Posts: 37
Original Poster
Rep: 
|
Quote:
Originally Posted by suramya
Try checking the drive for errors:
If you manage to get the drive working, you should back up the data on it immediately.
|
there is no partition as you can see the lsblk output
|
|
|
06-09-2022, 05:24 PM
|
#6
|
Member
Registered: Jan 2022
Location: Earth
Distribution: Debian
Posts: 249
Rep: 
|
Quote:
Originally Posted by tendouser
there is no partition as you can see the lsblk output
|
Ah... I had missed that reading the post on my phone.
What error messages (if any) do you get when you tried using testdisk/photorec?
Last edited by suramya; 06-09-2022 at 05:25 PM.
|
|
|
06-09-2022, 05:40 PM
|
#7
|
Member
Registered: Dec 2014
Posts: 37
Original Poster
Rep: 
|
Quote:
What error messages (if any) do you get when you tried using testdisk/photorec?
|
is just not detecting /dev/sda... i guess is because there are no partitions in that hdd.... is showing (0) bytes in the uefi/bios utility too
Last edited by tendouser; 06-09-2022 at 05:41 PM.
|
|
|
06-09-2022, 05:59 PM
|
#8
|
Member
Registered: Jan 2022
Location: Earth
Distribution: Debian
Posts: 249
Rep: 
|
When you plug it in, do you see any error messages in any of the logs under /var/log? Also, try running 'dmesg' (without the quotes) as root and look for any USB/disk errors in the output. If possible share the output here as well.
|
|
|
06-09-2022, 06:15 PM
|
#9
|
Member
Registered: Dec 2014
Posts: 37
Original Poster
Rep: 
|
Quote:
Originally Posted by suramya
When you plug it in, do you see any error messages in any of the logs under /var/log? Also, try running 'dmesg' (without the quotes) as root and look for any USB/disk errors in the output. If possible share the output here as well.
|
i'm using 'system-rescue' usb and i don't know if any log files will be saved to the flashdrive
it's the unique internal hdd of an asus laptop
Code:
[root@sysrescue ~]# dmesg | grep disk
[root@sysrescue ~]# dmesg | grep usb
[17468.410589] usb 1-3: USB disconnect, device number 3
[17468.825807] usb 1-3: new full-speed USB device number 5 using xhci_hcd
[17469.008044] usb 1-3: New USB device found, idVendor=0bda, idProduct=b721, bcdDevice= 2.00
[17469.008081] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17469.008100] usb 1-3: Product: Bluetooth Radio
[17469.008114] usb 1-3: Manufacturer: Realtek
[17469.008127] usb 1-3: SerialNumber: 00e04c000001
[18149.754577] usb 1-3: USB disconnect, device number 5
[18150.158943] usb 1-3: new full-speed USB device number 6 using xhci_hcd
[18160.598897] usb 1-3: device descriptor read/64, error -110
[18160.900736] usb 1-3: New USB device found, idVendor=0bda, idProduct=b721, bcdDevice= 2.00
[18160.900748] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[18160.900752] usb 1-3: Product: Bluetooth Radio
[18160.900755] usb 1-3: Manufacturer: Realtek
[18160.900758] usb 1-3: SerialNumber: 00e04c000001
[20106.241236] usb 1-3: USB disconnect, device number 6
[20106.605020] usb 1-3: new full-speed USB device number 7 using xhci_hcd
[20106.787109] usb 1-3: New USB device found, idVendor=0bda, idProduct=b721, bcdDevice= 2.00
[20106.787147] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[20106.787166] usb 1-3: Product: Bluetooth Radio
[20106.787179] usb 1-3: Manufacturer: Realtek
[20106.787195] usb 1-3: SerialNumber: 00e04c000001
Last edited by tendouser; 06-09-2022 at 06:16 PM.
|
|
|
06-09-2022, 06:57 PM
|
#10
|
Member
Registered: Jan 2022
Location: Earth
Distribution: Debian
Posts: 249
Rep: 
|
Can you share the full output for the dmesg command?
This error is interesting:
Quote:
[18160.598897] usb 1-3: device descriptor read/64, error -110
|
But its hard to tell if this corresponds to the hard disk. Searching for this error gives me: https://stackoverflow.com/questions/...d-64-error-110 which seems to think the problem is because power was exceeded as the host could not provide enough electric power for the device/drive to operate.
|
|
|
06-10-2022, 12:08 AM
|
#11
|
Member
Registered: Dec 2014
Posts: 37
Original Poster
Rep: 
|
Quote:
Originally Posted by suramya
Can you share the full output for the dmesg command?
This error is interesting:
But its hard to tell if this corresponds to the hard disk. Searching for this error gives me: https://stackoverflow.com/questions/...d-64-error-110 which seems to think the problem is because power was exceeded as the host could not provide enough electric power for the device/drive to operate.
|
https://pastebin.com/Dd7TASFc
.....and yes, here in my country there are outages, not every day but at least 1-2 times a week... and probably fluctuations too
Last edited by tendouser; 06-10-2022 at 12:12 AM.
|
|
|
06-10-2022, 12:51 AM
|
#12
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE & OS/2 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 6,612
|
Use smartctl -t short /dev/sdX to run a quick drive self-test.
Use smartctl -t long /dev/sdX to run a long drive self-test.
Use smartctl -x /dev/sdX to get better information, including results from running -t.
|
|
|
06-10-2022, 01:09 AM
|
#13
|
Member
Registered: Dec 2014
Posts: 37
Original Poster
Rep: 
|
Quote:
Originally Posted by mrmazda
Use smartctl -t short /dev/sdX to run a quick drive self-test.
Use smartctl -t long /dev/sdX to run a long drive self-test.
Use smartctl -x /dev/sdX to get better information, including results from running -t.
|
i've tried before the issue for long test like 4 different times and showed no errors
|
|
|
06-10-2022, 01:27 AM
|
#14
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE & OS/2 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 6,612
|
Do you have a way to test the drive in some other computer? At least try removing it and reconnecting it. If it was in a PC I would suggest try a different SATA cable.
|
|
|
06-10-2022, 01:49 AM
|
#15
|
Member
Registered: Dec 2014
Posts: 37
Original Poster
Rep: 
|
Quote:
Originally Posted by mrmazda
Do you have a way to test the drive in some other computer? At least try removing it and reconnecting it. If it was in a PC I would suggest try a different SATA cable.
|
not really
i only have the asus laptop
|
|
|
All times are GMT -5. The time now is 11:19 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|