161 reputation
116
bio website mnrva.com
location Berlin, Germany
age 27
visits member for 1 year, 6 months
seen Jul 22 at 13:02

Mar
9
awarded  Famous Question
Sep
2
awarded  Notable Question
Jul
20
awarded  Self-Learner
Jul
2
awarded  Popular Question
Feb
17
comment How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
I tried 63*512 without any luck. I tried a variety of other offsets as well. 4096 gave the best results. I used fsck and it told me that it had reverted the disk to a ext2 system since the ext3/4 was corrupted. It then went on to attempt to convert the entire disk to ext2 (I believe so) since it was saying inode # has illegal blocks.... I aborted and switched over to foremost after that. I may have lot some of the data at the start of the disk - I'll find out soon. >.<
Feb
17
awarded  Teacher
Feb
17
answered How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
Feb
17
comment How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
@Gilles Seems like I'm stuck for the moment. I've posted a hexdump if it may help anyone. I'll continue looking into this on my own as well to see if anything comes up. I'm still open to suggestions too!
Feb
17
revised How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
Added hex dump of first 63 sectors of hdd
Feb
17
awarded  Commentator
Feb
17
comment How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
@Gilles I'm currently trying to mount the disk on Ubuntu 12.04. It is a fresh install as of 2 weeks ago and I only use it for coding. I think it is more likely that the disk is messed up somehow. I can vouch that the disk is not encrypted since I had originally setup the software raid. Is it possible to force mdadm to pick up this disk and rebuild a RAID array? Or does it seem that it is too much trouble at this point?
Feb
17
revised How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
Update to add command output
Feb
17
comment How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
I cannot be completely sure the disk wasn't written to since it last worked - it was in the hands of someone else and I'm taking their word. See the update in the original question for the output of the commands.
Feb
17
comment How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
let us continue this discussion in chat
Feb
16
comment How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
The deep scan turned up the same results as the quick scan: No partitions found. I can't see anything to go on as far as testdisk is concerned. Not sure what to do at this point. All suggestions so far have led to a giant wall >.<
Feb
16
comment How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
After running an analysis on the full disk, it turned up no partitions. Currently running a deep scan now. If this doesn't turn up anything, I'm not sure where to go from here.
Feb
16
comment How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
testdisk is completely new territory for me. A basic run (Analyse) show No ext2, JFS, Reiser.. marker. Bad relative sector. No partition is bootable. It also provides the following: 1 P Linux 0 1 1 121600 254 63 1953520002 How can I make sense of that in order to help the situation?
Feb
16
comment How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
Running e2fsck /dev/sdc1?offset=2048 (I also ran offset=1985) outputs Bad magic number..Superblock invalid... as well as suggesting that the superblock is corrupt and trying to run e2fsck with an alternative superblock. Seems like I should provide it an alternative superblock to move forward.
Feb
16
comment How to mount/recover data on a disk that was part of a mdadm raid 1 on another machine?
@Gilles A mdadm -E /dev/sdc returns the following for me: /dev/sdc: MBR Magic : aa55 Partition[0] : 1953520002 sectors at 63 (type 83) but no information for /dev/sdc1 though
Feb
16
awarded  Editor