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.
|
|
|
05-30-2020, 07:26 AM
|
#16
|
Member
Registered: Apr 2017
Location: Nowhere
Distribution: Plenties found in my signatures :)
Posts: 268
Original Poster
Rep:
|
Contact a professional recovery service? What if they’re clueless at Linux? On Windows Linux partitions are invisible, then you need to provide your own Linux rescue CD’s for them to fix for you.
Quote:
Originally Posted by Ser Olmy
Then it's not an SSD, and you're dealing with a mechanical Seagate drive, most likely one of the infamous Rosewoods.
If you absolutely need the data back, you should disconnect the drive immediately and contact a professional recovery service.
|
|
|
|
05-30-2020, 01:29 PM
|
#17
|
Senior Member
Registered: Jan 2012
Distribution: Slackware
Posts: 3,348
Rep:
|
Quote:
Originally Posted by hd_scania
Contact a professional recovery service? What if they’re clueless at Linux?
|
1. They're not, believe me, and besides
2. The OS/filesystem on the drive is actually completely irrelevant, as a professional recovery technician will be accessing the drive on a block level, using software like PC-3000.
|
|
|
05-30-2020, 11:24 PM
|
#18
|
Member
Registered: Apr 2017
Location: Nowhere
Distribution: Plenties found in my signatures :)
Posts: 268
Original Poster
Rep:
|
Wait ... Software like PC-3000?? I’ve researched that PC-3000 is well known USB cards or PCI cards designed and tailored for professional hard drive recoveries thanks? And those ‘‘PC-3000 software’’ are its drivers thanks?
Quote:
Originally Posted by Ser Olmy
1. They're not, believe me, and besides
2. The OS/filesystem on the drive is actually completely irrelevant, as a professional recovery technician will be accessing the drive on a block level, using software like PC-3000.
|
Last edited by hd_scania; 05-30-2020 at 11:27 PM.
|
|
|
06-02-2020, 07:50 AM
|
#19
|
Member
Registered: Apr 2017
Location: Nowhere
Distribution: Plenties found in my signatures :)
Posts: 268
Original Poster
Rep:
|
Checked SMART status again and always being failed,
Code:
smartctl 7.1 2019-12-30 r5022 [FreeBSD 13.0-CURRENT-HBSD amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: SAT command failed
=== START OF INFORMATION SECTION ===
Device Model: [No Information Found]
Serial Number: [No Information Found]
Firmware Version: [No Information Found]
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: [No Information Found]
Local Time is: Tue Jun 2 19:48:24 2020 HKT
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Code:
smartctl 7.1 2019-12-30 r5022 [FreeBSD 13.0-CURRENT-HBSD amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: SAT command failed
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
|
|
|
All times are GMT -5. The time now is 11:38 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
|
|