June 22nd, 2019, 13:39
June 22nd, 2019, 14:24
Yes you are right but to dive in and run terminal commands, do you think that would be better?Spildit wrote:dick wrote:I still think you need to try this on another pc in ide/compatibility mode. That is because your Western Digital drive also shows a strange smart output. There might be some other unknown problem with your setup. Maybe some kind of bios incompatibility? (I'm just guessing here). I think you need to have the easy bit working before you move on to the more complicated part.
Also as you say the boot up is slow with the drive connected I would leave the computer standing for at least 20 mins to allow for the faulty drive to come ready. It might not of course. And only use sata from now on.
... Pray that the heads and/or sliders of the damaged drive are not in contact with the platter ... I don't think that leaving the drive at least 20 mins working without knowing the condition of it would be a good idea but you guys know best so ... moving on....
June 23rd, 2019, 3:06
Pray that the heads and/or sliders of the damaged drive are not in contact with the platter
That is because your Western Digital drive also shows a strange smart output.
June 24th, 2019, 4:36
June 24th, 2019, 11:53
June 24th, 2019, 12:54
June 24th, 2019, 17:29
...to make sure your adapter is working.
June 24th, 2019, 20:42
June 25th, 2019, 3:26
fzabkar wrote:FWIW, some motherboards disable a SATA port if an M.2 (NVMe or mSATA) drive is installed. It might pay to consult the manual.
June 27th, 2019, 5:47
July 29th, 2019, 15:38
oneRd wrote:Do I have any advantage in terms of processing time if I keep the amount of space in use on my test drive at minimum or what matters is the total disk's space?
.... power the drive on with the terminal connected and POST the LOG that the drive output to TTL/terminal software at power up ... Goes without saying open the terminal first and power the drive later.
July 29th, 2019, 17:29
According to my last checkups: the drive appears in the BIOS, it does not appear in Windows 10, it shows up in Lubuntu as unknown or unmountable and it does appears on terminal if I type lsblk
July 29th, 2019, 18:15
July 30th, 2019, 10:49
maximus wrote:Try cloning/imaging with HDDSuperClone for about 5 minutes or so, stop it and attach the log here.
July 30th, 2019, 16:50
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.Is it okay if I do it with HDDSuperClone free version?
August 9th, 2019, 11:54
maximus wrote:Yes, use the free version
sudo gunzip /home/hddsuperclone.2.1.13.x64.tar.gz
cd hddsuperclone.2.1.13.x64
August 9th, 2019, 14:10
tar xf hddsuperclone-x.x-x.x.-xxx-free.tar
August 11th, 2019, 4:42
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
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$
August 11th, 2019, 6:32
chmod +x hddsuperclone-install-depends-deb.sh
August 11th, 2019, 10:19
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
sudo apt-get install libusb-0.1 -y
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.
Powered by phpBB © phpBB Group.