Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  Page 3 of 5
  [ 86 posts ]  Go to page Previous  1, 2, 3, 4, 5  Next
  Previous topic | Next topic 
Author Message
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: July 30th, 2019, 10:49 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
maximus wrote:
Quote:
Try cloning/imaging with HDDSuperClone for about 5 minutes or so, stop it and attach the log here.


Thank you for answering. I was planning to do that after trying to hook it up via TTL. But since you say HDDSuperClone can work with it I'll do this first. Is it okay if I do it with HDDSuperClone free version? Does the free version expire after a set time?
Top
 Profile  
 
maximus
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: July 30th, 2019, 16:50 
Offline

Joined: January 29th, 2012, 1:43
Posts: 704
Location: United States
Quote:
Is it okay if I do it with HDDSuperClone free version?
Yes, use the free version, there are no limitations for use. Don't worry about the paid version unless I tell you it could actually help in your case.

_________________
http://www.sdcomputingservice.com
Home of HDDSuperClone and HDDSuperTool
Top
 Profile  
 
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 9th, 2019, 11:54 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
maximus wrote:
Yes, use the free version


I am having some setbacks with the installation. I chose to use a lubuntu 19.04 persistent live usb and to install HddSuperClone on it (this could already be a bad choice).

I am following your guide.Your .deb installer seems not to work - it returns: the package system could not be initialized, your configuration may be broken.

I then tried with .tar.gz. I used

Code:
sudo gunzip /home/hddsuperclone.2.1.13.x64.tar.gz


The .gz extention disappears. I am left with hddsuperclone.2.1.13.x64.tar. Then you write to change directory (cd hddsuperclone-x.x-x.x.-xxx) but if I write

Code:
cd hddsuperclone.2.1.13.x64


the response is "No such file or directory". Perhaps it is implied I have to create it..

I'm new to Linux...
Top
 Profile  
 
maximus
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 9th, 2019, 14:10 
Offline

Joined: January 29th, 2012, 1:43
Posts: 704
Location: United States
I am not sure about the DEB installer, but for the .tar.gz you are missing this command after gunzip:
Code:
tar xf hddsuperclone-x.x-x.x.-xxx-free.tar

_________________
http://www.sdcomputingservice.com
Home of HDDSuperClone and HDDSuperTool
Top
 Profile  
 
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 11th, 2019, 4:42 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
I somehow managed to install it, but on launching I got

Code:
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo ./hddsuperclone
./hddsuperclone: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory


Then I tried

Code:
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo hddsuperclone-install-depends-deb.sh
sudo: hddsuperclone-install-depends-deb.sh: command not found
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$


Anything else I can try?
Top
 Profile  
 
HaQue
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 11th, 2019, 6:32 
Offline
User avatar

Joined: December 4th, 2012, 1:35
Posts: 3469
Location: Adelaide, Australia
try lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo ./hddsuperclone-install-depends-deb.sh

the ./ means "the current directory". *nix doesn't (or doesn't always, I don't know) just automatically add the current folder to the path to look for things.

Funny story - my first year of University I walked to the other side of the campus because I couldn't run the program I compiled from C code.. a.out as I recall.. just for lecturer to show me to use ./a.out.. I must have recompiled 10 times!

or making the .sh file executable:

from the dir the .sh file is in, do this:

Code:
chmod +x hddsuperclone-install-depends-deb.sh
Top
 Profile  
 
maximus
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 11th, 2019, 10:19 
Offline

Joined: January 29th, 2012, 1:43
Posts: 704
Location: United States
Quote:
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo ./hddsuperclone
./hddsuperclone: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory

Try manually installing libusb:
Code:
sudo apt-get install libusb-0.1 -y

Quote:
try lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo ./hddsuperclone-install-depends-deb.sh

the ./ means "the current directory". *nix doesn't (or doesn't always, I don't know) just automatically add the current folder to the path to look for things.

Whoops, may need to update that in my documentation :shock:
Edit: Just realized my documentation is correct. It says to run that after a successful install, meaning the .sh file is located in an executable directory, not the current directory. In any case the manual libusb install should fix the issue.

_________________
http://www.sdcomputingservice.com
Home of HDDSuperClone and HDDSuperTool
Top
 Profile  
 
maximus
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 11th, 2019, 11:26 
Offline

Joined: January 29th, 2012, 1:43
Posts: 704
Location: United States
Quote:
I am following your guide.Your .deb installer seems not to work - it returns: the package system could not be initialized, your configuration may be broken.

Just an FYI, this error is something with your system, not the .deb installer. I can install it on a 19.04 live CD without issue. Your issue seems to be with package manager itself, and I cannot help with that. You may want to search your issue for a solution, if you intend to keep using that persistent USB for this and other things, as it could cause future headaches.

_________________
http://www.sdcomputingservice.com
Home of HDDSuperClone and HDDSuperTool
Top
 Profile  
 
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 11th, 2019, 12:33 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
Yes, I suspected along the line it was a problem with who know what in my installation.

Here is how I solved it:

Code:
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo apt-get install libusb-0.1.so.4
Reading package lists... Error!
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco_multiverse_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco_multiverse_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_main_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_restricted_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_restricted_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_universe_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_multiverse_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_multiverse_i18n_Translation-en (1)
W: You may want to run apt-get update to correct these problems
E: The package cache file is corrupted
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo ./hddsuperclone-install-depends-deb.sh
Reading package lists... Error!
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco_multiverse_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco_multiverse_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_main_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_restricted_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_restricted_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_universe_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_multiverse_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_multiverse_i18n_Translation-en (1)
W: You may want to run apt-get update to correct these problems
E: The package cache file is corrupted
Reading package lists... Error!
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco_multiverse_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco_multiverse_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_main_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_restricted_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_restricted_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_universe_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_multiverse_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_multiverse_i18n_Translation-en (1)
W: You may want to run apt-get update to correct these problems
E: The package cache file is corrupted
Reading package lists... Error!
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco_multiverse_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco_multiverse_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_main_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_restricted_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_restricted_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_universe_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_multiverse_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_multiverse_i18n_Translation-en (1)
W: You may want to run apt-get update to correct these problems
E: The package cache file is corrupted
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo apt-get update
Ign:1 cdrom://Lubuntu 19.04 _Disco Dingo_ - Release amd64 (20190416) disco InRelease
Hit:2 cdrom://Lubuntu 19.04 _Disco Dingo_ - Release amd64 (20190416) disco Release
Hit:4 http://security.ubuntu.com/ubuntu disco-security InRelease
Hit:5 http://archive.ubuntu.com/ubuntu disco InRelease     
Hit:6 http://archive.ubuntu.com/ubuntu disco-updates InRelease
Traceback (most recent call last):
  File "/usr/lib/cnf-update-db", line 26, in <module>
    col.create(db)
  File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 93, in create
    self._fill_commands(con)
  File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 127, in _fill_commands
    self._parse_single_commands_file(con, fp)
  File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 162, in _parse_single_commands_file
    if not tagf.step():
apt_pkg.Error: E:Unable to parse package file  (1)
Reading package lists... Error!
E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi'
E: Sub-process returned an error code
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco_multiverse_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco_multiverse_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_main_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_restricted_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_restricted_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_universe_i18n_Translation-en (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_multiverse_binary-amd64_Packages (1)
E: Unable to parse package file /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_disco-updates_multiverse_i18n_Translation-en (1)
W: You may want to run apt-get update to correct these problems
E: The package cache file is corrupted
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo rm -rf /var/lib/apt/lists/*
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo apt update
Ign:1 cdrom://Lubuntu 19.04 _Disco Dingo_ - Release amd64 (20190416) disco InRelease
Err:2 cdrom://Lubuntu 19.04 _Disco Dingo_ - Release amd64 (20190416) disco Release
  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
Get:3 http://security.ubuntu.com/ubuntu disco-security InRelease [97.5 kB]
Get:4 http://archive.ubuntu.com/ubuntu disco InRelease [257 kB]
Get:5 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages [173 kB]
Get:6 http://archive.ubuntu.com/ubuntu disco-updates InRelease [97.5 kB]
Get:7 http://security.ubuntu.com/ubuntu disco-security/main Translation-en [63.2 kB]
Get:8 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages [995 kB]
Get:9 http://security.ubuntu.com/ubuntu disco-security/main amd64 DEP-11 Metadata [33.9 kB]
Get:10 http://security.ubuntu.com/ubuntu disco-security/main DEP-11 48x48 Icons [8743 B]         
Get:11 http://security.ubuntu.com/ubuntu disco-security/main DEP-11 64x64 Icons [21.4 kB]         
Get:12 http://security.ubuntu.com/ubuntu disco-security/main DEP-11 64x64@2 Icons [29 B]         
Get:13 http://security.ubuntu.com/ubuntu disco-security/main DEP-11 128x128 Icons [52.0 kB]
Get:14 http://security.ubuntu.com/ubuntu disco-security/main amd64 c-n-f Metadata [2196 B]       
Get:15 http://security.ubuntu.com/ubuntu disco-security/restricted amd64 Packages [2616 B]
Get:16 http://security.ubuntu.com/ubuntu disco-security/restricted Translation-en [800 B]
Get:17 http://security.ubuntu.com/ubuntu disco-security/restricted amd64 c-n-f Metadata [116 B]
Get:18 http://security.ubuntu.com/ubuntu disco-security/universe amd64 Packages [223 kB]
Get:19 http://security.ubuntu.com/ubuntu disco-security/universe Translation-en [57.2 kB]         
Get:20 http://security.ubuntu.com/ubuntu disco-security/universe amd64 DEP-11 Metadata [14.6 kB] 
Get:21 http://security.ubuntu.com/ubuntu disco-security/universe DEP-11 48x48 Icons [14.3 kB]
Get:22 http://security.ubuntu.com/ubuntu disco-security/universe DEP-11 64x64 Icons [35.9 kB]     
Get:23 http://security.ubuntu.com/ubuntu disco-security/universe DEP-11 64x64@2 Icons [29 B]   
Get:24 http://security.ubuntu.com/ubuntu disco-security/universe DEP-11 128x128 Icons [105 kB]
Get:25 http://security.ubuntu.com/ubuntu disco-security/universe amd64 c-n-f Metadata [1260 B]   
Get:26 http://security.ubuntu.com/ubuntu disco-security/multiverse amd64 Packages [1172 B]
Get:27 http://security.ubuntu.com/ubuntu disco-security/multiverse Translation-en [632 B]
Get:28 http://security.ubuntu.com/ubuntu disco-security/multiverse amd64 c-n-f Metadata [116 B]
Get:29 http://archive.ubuntu.com/ubuntu disco/main Translation-en [509 kB]           
Get:30 http://archive.ubuntu.com/ubuntu disco/main amd64 DEP-11 Metadata [499 kB]
Get:31 http://archive.ubuntu.com/ubuntu disco/main DEP-11 48x48 Icons [97.2 kB]
Get:32 http://archive.ubuntu.com/ubuntu disco/main DEP-11 64x64 Icons [179 kB]
Get:33 http://archive.ubuntu.com/ubuntu disco/main DEP-11 64x64@2 Icons [2962 B]
Get:34 http://archive.ubuntu.com/ubuntu disco/main DEP-11 128x128 Icons [417 kB]
Get:35 http://archive.ubuntu.com/ubuntu disco/main amd64 c-n-f Metadata [30.0 kB]
Get:36 http://archive.ubuntu.com/ubuntu disco/restricted amd64 Packages [14.0 kB]
Get:37 http://archive.ubuntu.com/ubuntu disco/restricted Translation-en [4960 B]
Get:38 http://archive.ubuntu.com/ubuntu disco/restricted amd64 c-n-f Metadata [348 B]
Get:39 http://archive.ubuntu.com/ubuntu disco/universe amd64 Packages [9065 kB]
Get:40 http://archive.ubuntu.com/ubuntu disco/universe Translation-en [5251 kB]                   
Get:41 http://archive.ubuntu.com/ubuntu disco/universe amd64 DEP-11 Metadata [3546 kB]           
Get:42 http://archive.ubuntu.com/ubuntu disco/universe DEP-11 48x48 Icons [2759 kB]               
Get:43 http://archive.ubuntu.com/ubuntu disco/universe DEP-11 64x64 Icons [8369 kB]               
Get:44 http://archive.ubuntu.com/ubuntu disco/universe DEP-11 64x64@2 Icons [21.4 kB]             
Get:45 http://archive.ubuntu.com/ubuntu disco/universe DEP-11 128x128 Icons [16.1 MB]             
Get:46 http://archive.ubuntu.com/ubuntu disco/universe amd64 c-n-f Metadata [277 kB]             
Get:47 http://archive.ubuntu.com/ubuntu disco/multiverse amd64 Packages [157 kB]                 
Get:48 http://archive.ubuntu.com/ubuntu disco/multiverse Translation-en [112 kB]                 
Get:49 http://archive.ubuntu.com/ubuntu disco/multiverse amd64 DEP-11 Metadata [51.3 kB]         
Get:50 http://archive.ubuntu.com/ubuntu disco/multiverse DEP-11 48x48 Icons [10.8 kB]             
Get:51 http://archive.ubuntu.com/ubuntu disco/multiverse DEP-11 64x64 Icons [221 kB]             
Get:52 http://archive.ubuntu.com/ubuntu disco/multiverse DEP-11 64x64@2 Icons [1160 B]           
Get:53 http://archive.ubuntu.com/ubuntu disco/multiverse DEP-11 128x128 Icons [421 kB]           
Get:54 http://archive.ubuntu.com/ubuntu disco/multiverse amd64 c-n-f Metadata [9348 B]           
Get:55 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages [228 kB]               
Get:56 http://archive.ubuntu.com/ubuntu disco-updates/main Translation-en [89.2 kB]               
Get:57 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 DEP-11 Metadata [131 kB]         
Get:58 http://archive.ubuntu.com/ubuntu disco-updates/main DEP-11 48x48 Icons [15.2 kB]           
Get:59 http://archive.ubuntu.com/ubuntu disco-updates/main DEP-11 64x64 Icons [38.2 kB]           
Get:60 http://archive.ubuntu.com/ubuntu disco-updates/main DEP-11 64x64@2 Icons [29 B]           
Get:61 http://archive.ubuntu.com/ubuntu disco-updates/main DEP-11 128x128 Icons [92.8 kB]         
Get:62 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 c-n-f Metadata [2996 B]         
Get:63 http://archive.ubuntu.com/ubuntu disco-updates/restricted amd64 Packages [3012 B]         
Get:64 http://archive.ubuntu.com/ubuntu disco-updates/restricted Translation-en [840 B]           
Get:65 http://archive.ubuntu.com/ubuntu disco-updates/restricted amd64 c-n-f Metadata [116 B]     
Get:66 http://archive.ubuntu.com/ubuntu disco-updates/universe amd64 Packages [258 kB]           
Get:67 http://archive.ubuntu.com/ubuntu disco-updates/universe Translation-en [82.3 kB]           
Get:68 http://archive.ubuntu.com/ubuntu disco-updates/universe amd64 DEP-11 Metadata [59.6 kB]   
Get:69 http://archive.ubuntu.com/ubuntu disco-updates/universe DEP-11 48x48 Icons [32.6 kB]       
Get:70 http://archive.ubuntu.com/ubuntu disco-updates/universe DEP-11 64x64 Icons [84.1 kB]       
Get:71 http://archive.ubuntu.com/ubuntu disco-updates/universe DEP-11 64x64@2 Icons [29 B]       
Get:72 http://archive.ubuntu.com/ubuntu disco-updates/universe DEP-11 128x128 Icons [228 kB]     
Get:73 http://archive.ubuntu.com/ubuntu disco-updates/universe amd64 c-n-f Metadata [1780 B]     
Get:74 http://archive.ubuntu.com/ubuntu disco-updates/multiverse amd64 Packages [1172 B]         
Get:75 http://archive.ubuntu.com/ubuntu disco-updates/multiverse Translation-en [632 B]           
Get:76 http://archive.ubuntu.com/ubuntu disco-updates/multiverse amd64 c-n-f Metadata [116 B]     
Reading package lists... Done                                                                     
E: The repository 'cdrom://Lubuntu 19.04 _Disco Dingo_ - Release amd64 (20190416) disco Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo apt-get install libusb-0.1.so.4
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package libusb-0.1.so.4
E: Couldn't find any package by glob 'libusb-0.1.so.4'
E: Couldn't find any package by regex 'libusb-0.1.so.4'
lubuntu@lubuntu:~/hddsuperclone.2.1.13.x64$ sudo ./hddsuperclone-install-depends-deb.sh
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'libusb-0.1-4' for regex 'libusb-0.1'
The following NEW packages will be installed:
  libusb-0.1-4
0 upgraded, 1 newly installed, 0 to remove and 222 not upgraded.
Need to get 17.4 kB of archives.
After this operation, 58.4 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu disco/main amd64 libusb-0.1-4 amd64 2:0.1.12-32 [17.4 kB]
Fetched 17.4 kB in 0s (53.4 kB/s)   
Selecting previously unselected package libusb-0.1-4:amd64.
(Reading database ... 215664 files and directories currently installed.)
Preparing to unpack .../libusb-0.1-4_2%3a0.1.12-32_amd64.deb ...
Unpacking libusb-0.1-4:amd64 (2:0.1.12-32) ...
Setting up libusb-0.1-4:amd64 (2:0.1.12-32) ...
Processing triggers for libc-bin (2.29-0ubuntu2) ...
Reading package lists... Done
Building dependency tree       
Reading state information... Done
make is already the newest version (4.2.1-1.2).
make set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 222 not upgraded.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
gcc is already the newest version (4:8.3.0-1ubuntu3).
gcc set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 222 not upgraded.


Up and running now!!
I'll test the software on a test drive first and then shoot the 5 min log on the real one
Top
 Profile  
 
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 12th, 2019, 6:11 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
It looks grim...

Attachment:
d.png
d.png [ 8.94 KiB | Viewed 8185 times ]


This might help assessing the status of the drive.

Attachment:
20190812_115308.jpg
20190812_115308.jpg [ 1.68 MiB | Viewed 8185 times ]


Top
 Profile  
 
maximus
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 12th, 2019, 18:14 
Offline

Joined: January 29th, 2012, 1:43
Posts: 704
Location: United States
I based the idea that hddsuperclone could read it from the post where you showed that the drive listed with lsblk as having partitions, which would mean it identified and read at least sector 0. If this is still true (the screenshot would indicate that is likely still true), then the drive is locking up / going offline after that, which would likely indicate a firmware issue for some sort of busy / non-responding issue. That means it is time to get into the terminal connection and commands, which I don't do. Others here would need to help you with that.

_________________
http://www.sdcomputingservice.com
Home of HDDSuperClone and HDDSuperTool
Top
 Profile  
 
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 13th, 2019, 4:04 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
maximus wrote:
I based the idea that hddsuperclone could read it from the post where you showed that the drive listed with lsblk as having partitions


I was expecting that too :(
Top
 Profile  
 
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 13th, 2019, 4:45 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
Thank you maximus and HaQue for your time
Top
 Profile  
 
maximus
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 13th, 2019, 18:01 
Offline

Joined: January 29th, 2012, 1:43
Posts: 704
Location: United States
oneRd wrote:
maximus wrote:
I based the idea that hddsuperclone could read it from the post where you showed that the drive listed with lsblk as having partitions


I was expecting that too :(

Well, at least all hope is not lost. Since it does appear to actually at least read sector 0 and get the partition table, it means it is still alive (or at least not totally dead). It probably has bad sectors, maybe a bad head, but there is still more that can be done DIY using the TTL adapter. If the firmware issues can be fixed, you should hopefully be able to get some data off it. Just don't send the wrong commands to it, or you could kill it for good.

_________________
http://www.sdcomputingservice.com
Home of HDDSuperClone and HDDSuperTool
Top
 Profile  
 
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 14th, 2019, 12:37 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
Thank you for your reassurance. It seems I do not have other choice that to dive in - i am terrified :lol:
I haven't yet understood if and when is safe to power up or down the drive though. I know SATA supports hot plugging and it is clear I do have to power up the drive at some point after setting up the terminal, but when am I supposed to power it down? Powering it down while it is still processing some information is the last thing I want to happen and my worst fear at the moment. I've read that some commands might take time to show responses on terminal and that until then you shouldn't power down the drive.
Top
 Profile  
 
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 21st, 2019, 8:47 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
I have taken my chances and plugged my test drive trough TTL.
Naturally I couldn't get the terminal to work. Not surprising..

I followed the instructions on how to connect the TTL adapter to the drive Spildit kindly gave me in his first post. I used Putty with the following settings:

Baud - 38400
Data Bits - 8
Parity - None
Stop Bits - 1
Flow Control - None

I have two TTL adapters:

Attachment:
20190820_170909.jpg
20190820_170909.jpg [ 1.76 MiB | Viewed 7847 times ]


Based on the CH340 module (https://www.aliexpress.com/item/3276142 ... 4c4dLsQxbf).

Attachment:
20190820_170551.jpg
20190820_170551.jpg [ 1.91 MiB | Viewed 7847 times ]


Based on CP2102 (https://www.aliexpress.com/item/3250301 ... 4c4dLsQxbf).

Both of them have two handy LEDs (one for transmission, one for reception) that show you what's happening. I anyway shorted RX and TX on both and tried them directly on terminal. They work!
I made sure both gave 3.3V (the first one can be manually switched to 5V).
I isolated with tape and slightly flatten the connectors to make sure they would adhere to the HDD pins without interference.

I read somewhere Spildit was recommending CP2104 for better compatibility, which seems close to my second adapter, at least name-wise.

So, I open the terminal with the aforementioned settings and then power up the drive. The terminal stays blank. In a following post Spildit was saying to check what log the HDD would be displaying on the terminal.

I had planned to input a few commands listed here: https://www.data-medics.com/forum/seaga ... 3242a6b8a1. Like Ctrl + a or Ctrl + l which seem to be harmless. Needless to say nothing is showed on terminal when I input those commands. I also tried to give Ctrl + z first and then any other command, but nothing happen. I noticed that when I type ctrl no light is shown on the TX corresponding LED unlike say the z key if I have to input Ctrl + z. Is that normal?

I am still not sure about when to power down the HDD. I assume anytime if nothing is showed on terminal and the heads are parked. I do not know whether I have to wait before or after inputting anything and if yes how long..

Perhaps some of you guys know already what I am doing wrong and if yes hope you can point me in the right direction.

Thank you :mrgreen:
Top
 Profile  
 
maximus
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 21st, 2019, 17:20 
Offline

Joined: January 29th, 2012, 1:43
Posts: 704
Location: United States
Since there are no other replies yet, I will say a couple of things to try.

First and foremost, make sure those connectors on the hard drive are not shorting together at all. I did some testing with connectors just like that, and I had to be real careful to make sure the wires were positioned just right to keep them separated.

Second, try reversing the TX and RX on one end. My first attempt to connect to a Seagate drive failed because it was backwards. It shouldn't hurt if they are accidentally backwards, at least it didn't hurt anything in my case.

_________________
http://www.sdcomputingservice.com
Home of HDDSuperClone and HDDSuperTool
Top
 Profile  
 
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 21st, 2019, 19:06 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
Thanks for replying maximus. I am positive connectors cannot touch one another, they are completely wrapped with thin transparent tape. As for inverting RX and TX I haven't tried it yet. Will try it tomorrow..
Top
 Profile  
 
oneRd
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 23rd, 2019, 11:43 
Offline

Joined: May 15th, 2019, 13:14
Posts: 55
Location: Italy
Quote:
try reversing the TX and RX on one end


Something actually happened as soon as I gave power

With CP2102 (some very quick head movements)

Code:
▒▒xx▒x▒xx▒x▒▒▒▒x▒▒▒▒x▒▒▒▒▒x▒xx▒x▒▒▒x▒xxxx▒▒▒▒xx▒▒▒xx▒▒x▒xx▒▒▒
▒▒xxx▒▒▒▒▒▒▒▒xx▒▒▒x▒xx▒▒▒▒x▒▒▒▒▒▒▒x▒x▒x▒▒xxx▒x▒▒▒x▒▒▒x▒x▒▒x▒▒▒x▒xx
xx▒xxx▒▒▒xx▒x▒xx▒x▒▒x▒x▒x▒xxx▒▒▒xx▒x▒xx▒x▒▒▒▒▒x▒x▒▒x▒▒x▒x▒xx▒


With CH340 (head movements negligible)

Code:
▒▒▒▒▒▒▒▒▒▒.@xr▒¤


Futile my attempts to get anything else out with Ctrl + a, l or z
Top
 Profile  
 
maximus
 Post subject: Re: Old Maxtor recovery - I/O error
PostPosted: August 23rd, 2019, 18:09 
Offline

Joined: January 29th, 2012, 1:43
Posts: 704
Location: United States
Back when I was playing around with the terminal connection, I seem to remember two things that caused garbage data like that. One was having the wrong baud rate, and the other was a ground issue.

_________________
http://www.sdcomputingservice.com
Home of HDDSuperClone and HDDSuperTool
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 3 of 5
  [ 86 posts ]  Go to page Previous  1, 2, 3, 4, 5  Next

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: Google [Bot], Google Adsense [Bot] and 42 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Switch to mobile style
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group