Recovering a Seagate 1.0TB SSHD with gpart
- Inicie sesión ou rexístrese para enviar comentarios
This disk has been a troublemaker from its first use, so I set it aside.
Later,four years ago, I wrote a few hundred MB to it while preparing a
response to an inquiry about my webpage.
Today I opened the disk on a USB port and read some of the contents with
the file manager. I noticed while looking up other stuff that the disk
was getting remounted several times. Then I got serious in preparation to
add about 30GB of additional data, whereupon the file manager stated that
the main partition could not be read ... bad superblock, etc. So I set
about recovering my data with gpart, to wit: sudo gpart -i /dev/sde
with
the following results:
sudo gpart -i /dev/sde
Begin scan...
Possible partition(Linux ext2), size(38000mb), offset(1mb); Accept this guess (y,n) : y
Possible partition(SGI XFS filesystem), size(915420mb), offset(38001mb); Accept this guess (y,n) : y
End scan.
Checking partitions...
* Warning: partition(Linux ext2 filesystem) starts beyond disk end.
* Warning: partition(Linux ext2 filesystem) starts beyond disk end.
Partition(Linux ext2 filesystem): invalid primary
Partition(Linux ext2 filesystem): invalid primary
Ok.
Guessed primary partition table:
Primary partition(1)
type: 000(0x00)(unused)
size: 0mb #s(0) s(0-0)
chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r
Primary partition(2)
type: 000(0x00)(unused)
size: 0mb #s(0) s(0-0)
chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r
Primary partition(3)
type: 000(0x00)(unused)
size: 0mb #s(0) s(0-0)
chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r
Primary partition(4)
type: 000(0x00)(unused)
size: 0mb #s(0) s(0-0)
chs: (0/0/0)-(0/0/0)d (0/0/0)-(0/0/0)r
Now I'm letting GPartEd attempt data recovery ... but no file systems are found.
Anything else to try ?
TestDisk and PhotoRec. They are in a single package, testdisk, in Trisquel's repository. See https://www.cgsecurity.org/wiki/TestDisk and https://www.cgsecurity.org/wiki/PhotoRec for documentation.
Thanks for the tip.
Overnight the SSHD (actually a hybrid mix of SS & HDD) came back to life, so
I moved its files to a Flash Memory Card that I purchased from Think Penguin.
Could it be that the mixed-mode hard drive isn't supported well ?
Here's how it went with testdisk:
sudo testdisk /dev/sdc
Note: I made sure with disks that testdisk was aimed at the right place.
>Disk /dev/sdc - 1000 GB / 931 GiB - ST1000LM 014-1EJ164
>[Intel ] Intel/PC partition
>[ Analyse ] Analyse current partition structure and search for lost partitions
Disk /dev/sdc - 1000 GB / 931 GiB - CHS 121601 255 63
Current partition structure:
Partition Start End Size in sectors
1 P Linux 0 32 33 4844 114 6 77824000
3 P Linux 4844 114 7 121601 57 56 1875697664 redacted]
No partition is bootable
*=Primary bootable P=Primary L=Logical E=Extended D=Deleted
>[Quick Search] [ Backup ]
P Linux 4844 114 7 121601 57 56 1875697664 [redacted]
Structure: Ok. Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
*=Primary bootable P=Primary L=Logical E=Extended D=Deleted
Keys A: add partition, L: load backup, T: change type, P: list files,
Enter: to continue
ext4 blocksize=4096 Large_file Sparse_SB Recover, 39 GB / 37 GiB
Partition Start End Size in sectors
1 * Linux 0 32 33 4844 114 6 77824000
2 P Linux 4844 114 7 121601 57 56 1875697664 [redacted]
Write partition table, confirm ? (Y/N) ==> Y
You will have to reboot for the change to take effect.
Whereupon the drive became mountable & readable with the file manager.
Here's another one, a toshiba dt01aca200 2TB hdd, that isn't recognized by disks
with parted to no avail.
This is a last-ditch effort to recover data from a former NAS device upon which
I gave up several years ago in the days or windoze. It has no current value except
for archival material. I won't feel bad if the verdict is "hopeless" ...
Here's another one, a toshiba dt01aca200 2TB hdd, that isn't recognized by disks with parted to no avail.
Does that mean /dev contains no node for the disk? If so, you would first need to fix the hardware.
It takes a while after powering on, but disks consistently sees it as /dev/sdc:
sudo mkdir /media/george/usb-JMicron_Generic_0123456789ABCDEF-0:0
george@george-ThinkPad-T420:~$ sudo mount /dev/sdc /media/george/usb-JMicron_Generic_0123456789ABCDEF-0:0
mount: /media/george/usb-JMicron_Generic_0123456789ABCDEF-0:0: can't read superblock on /dev/sdc.
It's out of the original NAS box that was running so hot that I retired it while I was using windoze_98.
Now it's in a SATA/usb-connected external 3-1/2 inch enclosure where it beeps every ten seconds or so and still runs hot.
My recently acquired T400 gives the same results.
It takes a while after powering on, but disks consistently sees it as /dev/sdc
Then you can try TestDisk or PhotoRec or GNU ddrescue or...
ddrescue cannot be found with sudo apt-get install, and neither TestDisk nor PhotoRec
find /dev/sdc (which disks does see). All I get with sudo TestDisk > Create is
Warning: can't get size for Disk /dev/sdc - 0 B - 0 sectors, sector size=512 - JMicron Generic
ddrescue cannot be found with sudo apt-get install
It is in Trisquel's default install. If you do not have it, install the package named "gddrescue". Please read its manual. From the terminal:
$ info ddrescue
Warning: can't get size for Disk /dev/sdc - 0 B - 0 sectors, sector size=512 - JMicron Generic
I am afraid the disk itself is defective and GNU ddrescue will not do better.
After reading the online version of ddrescue's manual, I'm setting aside that 2TB foot warmer; better to try ddrescue
some day when I need to restore a whole bunch of unreadable .jpg images on a drive that is otherwise OK. My archives
are full of copies of old reports with damaged .jpg files. For most of those I have good copies of the original floppy
disks; what's gone are the image edits.
- Inicie sesión ou rexístrese para enviar comentarios