seagate central dat...
 
Notifications
Clear all

seagate central data

14 Posts
3 Users
0 Likes
1,513 Views
 dega
(@dega)
Posts: 261
Reputable Member
Topic starter
 

dear all,
I've got a Seagate Central 4TB. Before holydays the switched off the device. Then afiter holyday was dead….
The disk works I tried Paragon ExtFS to read the LVM partition with no result.
Can someone help me?
thanks

 
Posted : 28/07/2018 11:26 am
jaclaz
(@jaclaz)
Posts: 5133
Illustrious Member
 

Can someone help me?

Yes/No.
https://jdebp.eu/FGA/questions-with-yes-or-no-answers.html

Seagate seemingly use a "custom modified" LVM setup
https://www.youtube.com/watch?v=TurLKE-QdDI

Technically it reportedly uses 64 kb blocks for the LVM (which are usually non-standard), but Paragon EXTFS has been reported as working on those, so it is strange
https://web.archive.org/web/20151020163523/http//scottpannan.com/index.php/tidbits-more/13-seagate-central-nas-data-recovery-using-windows
https://www.linuxquestions.org/questions/linux-newbie-8/reading-data-from-seagate-hard-drive-extracted-from-seagate-central-4175516790/page2.html
https://discussions.apple.com/thread/8010880

HowTo's (with a Linux distro)
https://myanwyn.blogspot.com/2014/08/how-to-recover-seagate-central-data.html
http//devblog.twisted-artwork.de/seagate-central-4tb-missing-data-recovery/

Check however, maybe the distro you use already includes fuseext2.

jaclaz

 
Posted : 28/07/2018 2:15 pm
 dega
(@dega)
Posts: 261
Reputable Member
Topic starter
 

thanks for answering me. I also found few of the pages you give me.

Actually I can't try under linux. I am using paragon
In windows manager few partition few contains linux data. One is the bigger and full. If I double click on it I see nothing

 
Posted : 28/07/2018 3:18 pm
 dega
(@dega)
Posts: 261
Reputable Member
Topic starter
 

obviosly The disk is connected by a writeblocker

 
Posted : 28/07/2018 3:25 pm
jaclaz
(@jaclaz)
Posts: 5133
Illustrious Member
 

Actually I can't try under linux.

Why not? ? 😯

I am using paragon

Sure, I got that ) , and as said for other people it worked just fine, and that is the reason why I said "it's strange".

In windows manager few partition few contains linux data. One is the bigger and full. If I double click on it I see nothing

I understand, hence I suggested you to try another way.

Summing up, two distinct methods have been reported by several different people to be working to recover data from a Seagate Central
1) the first of these methods involves the use of Paragon's EXTFS on Windows
2) the second one involves the use of *any* Linux and the fuseext2 package

For *whatever* reasons the first method doesn't work for you.

Try the second one.

obviosly The disk is connected by a writeblocker

Obviously ?
I would use the adverb exceptionally instead.
You normally do not use a write blocker for data recovery, you use it for making a forensic sound image (or clone) of the original (and actually later perform the data recovery on the clone or image).
If *anything* in the filesystem (or in the actual device) has been corrupted, by using a writeblocker you are preventing (if possible) corrections to be made.

jaclaz

 
Posted : 28/07/2018 5:22 pm
JaredDM
(@jareddm)
Posts: 118
Estimable Member
 

I'm not sure about Seagate Central, but most Seagate externals do an odd sector size mutation through the adapter bridge. I'd suspect it's the same issue here. 4Tb Seagate drives all use a native 4K sector size. However, for use in desktop application with older operating systems the drive's firmware emulates 512-byte sector size(all their drives do this). However, for their external's, they do a sector size mutation back to 4K since the 512 emulation isn't needed. So they are actually using 4K > emulated to 512-byte > emulated back to 4K.

Problem is, when you take the drive out of it's external, or in your case the Central box, it's now emulating 512-byte sectors when the data was written using 4K sectors. So an OS (including Linux) doesn't know how to read the partition table or other filesystem structures since it's expecting them to be laid out differently.

Fortunately, good data recovery software such as R-Studio or R-Linux (from R-TT) won't pay any attention to sector size and should just be able to open/copy the files.

If that doesn't work, it's probably a case of a failed hard drive. Seagate drives are complete crap these days.

 
Posted : 29/07/2018 12:21 pm
jaclaz
(@jaclaz)
Posts: 5133
Illustrious Member
 

I'm not sure about Seagate Central, …. However, for their external's, they do a sector size mutation back to 4K since the 512 emulation isn't needed. So they are actually using 4K > emulated to 512-byte > emulated back to 4K.

You are talking of external USB drives.
The Seagate Central is NOT an external drive.
It is a NAS (Network Attached Storage), with a motherboard (running a *bastardized*/locked down version of Linux).
There is I believe not any "conversion" simply because there is not any SATA/ESATA or USB interface available on it, data is accessed through the network only, if the internal disk is Native 4k (and not AF) it remains Native 4 K, and if it is AF (and not 4K) it remains AF.
There is actually a USB 2.0 port on the unit, but it is not (unlike external drives) a "direct" bridge to the internal SATA disk, the port is managed by the motherboard and its software/firmware.

jaclaz

 
Posted : 29/07/2018 1:37 pm
 dega
(@dega)
Posts: 261
Reputable Member
Topic starter
 

I tried always in windoss connecting the drive direct to the sata port.
The ituation is the same. Also with r-linux no result. I suspect the drive is dead
bye

 
Posted : 29/07/2018 4:11 pm
jaclaz
(@jaclaz)
Posts: 5133
Illustrious Member
 

I tried always in windoss connecting the drive direct to the sata port.
The ituation is the same. Also with r-linux no result. I suspect the drive is dead
bye

Well, you just stated you saw the partitions

I am using paragon
In windows manager few partition few contains linux data. One is the bigger and full. If I double click on it I see nothing

but that you couldn't access them, if the drive was dead, you couldn't possibly see them.

Your previous report was about seeing the partitions but being unable to see the data in them (which is typical of a mounting/access issue), now, if you don't see the partitions anymore, it may mean that the drive is dead, but it is not the same symptom as before, another reason to first making an image/clone (if the drive is not actually dead, of course).

R-linux seemingly has support for LVM but not necessarily has the support for the non-standard 64 KB blocks , so I cannot see how it is relevant.

jaclaz

 
Posted : 29/07/2018 4:42 pm
 dega
(@dega)
Posts: 261
Reputable Member
Topic starter
 

I used linux it works thanks

 
Posted : 29/07/2018 6:45 pm
Page 1 / 2
Share: