General TC > General TC Talk
Data Recovery from bad SSD
Rich:
Hi MTCAT
The difference between 40 and 44 pins is the latter also brings in power on the IDE connector.
Adapters are available. It's just a small board with a 44 pin connector on one end and two
connectors at the other end, one 40 pin and a 4 pin power connector. Or the power connection
might be a pigtail that hangs off of the board.
MTCAT:
Hi Rich,
Thanks, I slowly clued into that as well, I have one of those adapters coming, but it won't be here until Thursday, the 2.5 inch external enclosure I got yesterday was just for 40 pin IDE...sigh, so, have to wait to Thursday now before I can try imaging the entire SSD with my Slackware desktop...
For my own education, can you tell me why we can't make an image of a single partition by itself ?, i.e., just hda3 as I was attempting before. I read online that it's actually easier to do that since when mounting the image of a single partition you don't need to worry about block offsets when mounting.
I do understand that if we want to try to repair the disk that we need to image the whole drive, to be able to possibly repair the partition table, but otherwise, is it possible to just mount an image of one partition by itself ?
Thanks,
David
Rich:
Hi MTCAT
--- Quote from: MTCAT on September 13, 2022, 07:27:02 AM --- ... For my own education, can you tell me why we can't make an image of a single partition by itself ?, ...
--- End quote ---
You can, but what you get will be based on how big the partition table says that partition is. If the table says
your 300 Meg partition is only 17 Megs, thats all you'll get.
--- Quote --- ... I read online that it's actually easier to do that since when mounting the image of a single partition you don't need to worry about block offsets when mounting.
--- End quote ---
I read online that it's easy to do without worrying about block offsets. I saw it in reply #7:
--- Quote from: Rich on September 08, 2022, 11:57:40 PM --- ... Assign a device to the image file:
--- Code: ---sudo losetup --show --find --partscan base.img
/dev/loop241
--- End code ---
In this example the operating system returned /dev/loop241 for the image file.
Use fdisk to get a partition list:
--- Code: ---fdisk -l /dev/loop241
----- Snip -----
Device Boot Start End Sectors Size Id Type
/dev/loop241p1 2048 206847 204800 100M 83 Linux
/dev/loop241p2 206848 309247 102400 50M 83 Linux
/dev/loop241p3 309248 923647 614400 300M 83 Linux
--- End code ---
In this example there are 3 partitions.
If you want to try looking at partition 3:
--- Code: ---mkdir P3
sudo mount /dev/loop241p3 P3
cd P3
ls -l
--- End code ---
...
--- End quote ---
All you need to do is create a mount point (subdirectory) and mount it:
--- Code: ---mkdir PickAnyName
sudo mount /dev/loop241p1 PickAnyName
--- End code ---
patrikg:
And as default, Linux mounts partitions with write permissions.
And don't write any data to some bad ssd/hd.
So if you try to mount the partition you should just mount it as read only.
And many Linux systems also auto mount, that rely bad.
Because when mounting a ssd/hd it's also write's some data to it.
MTCAT:
Hi Rich, curaga and patrikg,
Okay, thanks for the explanation with the single partition image...sorry for not realizing what you were showing me there Rich, I just haven't got that far yet, I will definitely follow along your post 7 if I can get an image made of the entire disk.
I managed to get an external enclosure today that fits the 44 pin 2.5 inch SSD (with a USB connection to the desktop) but neither one of my Slackware desktops can see the external drive, when I type "fdisk -l" all the devices get listed as usual but at the end the terminal prompt hangs (with just a blinking cursor) until I unplug the USB cable for the external hard-drive enclosure, then I get the command prompt back.
This happened on both 2.6.37.4 and 4.4.14.
I do have an 44 pin to 40 pin adapter coming as well, which would allow me to hook up to my older desktop internally, with the extra CD/DVD pigtail as Rich suggested, but it won't be here until Thursday.
So not sure, maybe could try booting up TInyCore 3.0 on one of the desktops as well ? TC 3.0 was able to see hda at least (when booting the PC104 stack), but so far I've had no luck with Slackware.
Thanks,
David
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version