recover data from former RAID 1 drive

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I had a RAID1 setup (md0), mirroring two 2TB drives (sdb, sdc). When trying to remove the RAID to use the disks individually with the data on them, I ran



mdadm --stop /dev/md0
mdadm --zero-superblock /dev/sdb1
mdadm --zero-superblock /dev/sdc1
mdadm --remove /dev/md0



However, afterwards, if I want to mount /dev/sdb1, I get the following: "wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error"



On my attempts to recreate the ext4 file system, I think I already nuked sdc beyond recovery (I ran mkfs.ext4 /dev/sdc1).



Is there still hope for me to recover my data from sdb and if so how?



Thanks for your time - let me know with which additional information I can help.










share|improve this question









New contributor




gro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



















  • Very carefully make a backup of the corrupted drive. Please excercise Extreme Caution: dd if=/dev/sdb of=/dev/blankdrive Then you can play around with trying to recover the journal structure, partition tables, etc.
    – jmunsch
    1 hour ago











  • Good call, I have it backed up and hope that someone can point me to a potential way of recovery. Thanks!
    – gro
    12 mins ago










  • what's the output of mdadm --examine /dev/sdb1 ? also see: unix.stackexchange.com/a/72285/61110
    – jmunsch
    7 mins ago











  • mdadm: No md superblock detected on /dev/sdb1. EDIT: And guessing the offset didn't work :p
    – gro
    3 mins ago















up vote
1
down vote

favorite












I had a RAID1 setup (md0), mirroring two 2TB drives (sdb, sdc). When trying to remove the RAID to use the disks individually with the data on them, I ran



mdadm --stop /dev/md0
mdadm --zero-superblock /dev/sdb1
mdadm --zero-superblock /dev/sdc1
mdadm --remove /dev/md0



However, afterwards, if I want to mount /dev/sdb1, I get the following: "wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error"



On my attempts to recreate the ext4 file system, I think I already nuked sdc beyond recovery (I ran mkfs.ext4 /dev/sdc1).



Is there still hope for me to recover my data from sdb and if so how?



Thanks for your time - let me know with which additional information I can help.










share|improve this question









New contributor




gro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



















  • Very carefully make a backup of the corrupted drive. Please excercise Extreme Caution: dd if=/dev/sdb of=/dev/blankdrive Then you can play around with trying to recover the journal structure, partition tables, etc.
    – jmunsch
    1 hour ago











  • Good call, I have it backed up and hope that someone can point me to a potential way of recovery. Thanks!
    – gro
    12 mins ago










  • what's the output of mdadm --examine /dev/sdb1 ? also see: unix.stackexchange.com/a/72285/61110
    – jmunsch
    7 mins ago











  • mdadm: No md superblock detected on /dev/sdb1. EDIT: And guessing the offset didn't work :p
    – gro
    3 mins ago













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I had a RAID1 setup (md0), mirroring two 2TB drives (sdb, sdc). When trying to remove the RAID to use the disks individually with the data on them, I ran



mdadm --stop /dev/md0
mdadm --zero-superblock /dev/sdb1
mdadm --zero-superblock /dev/sdc1
mdadm --remove /dev/md0



However, afterwards, if I want to mount /dev/sdb1, I get the following: "wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error"



On my attempts to recreate the ext4 file system, I think I already nuked sdc beyond recovery (I ran mkfs.ext4 /dev/sdc1).



Is there still hope for me to recover my data from sdb and if so how?



Thanks for your time - let me know with which additional information I can help.










share|improve this question









New contributor




gro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I had a RAID1 setup (md0), mirroring two 2TB drives (sdb, sdc). When trying to remove the RAID to use the disks individually with the data on them, I ran



mdadm --stop /dev/md0
mdadm --zero-superblock /dev/sdb1
mdadm --zero-superblock /dev/sdc1
mdadm --remove /dev/md0



However, afterwards, if I want to mount /dev/sdb1, I get the following: "wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error"



On my attempts to recreate the ext4 file system, I think I already nuked sdc beyond recovery (I ran mkfs.ext4 /dev/sdc1).



Is there still hope for me to recover my data from sdb and if so how?



Thanks for your time - let me know with which additional information I can help.







mdadm raid1






share|improve this question









New contributor




gro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




gro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 18 mins ago





















New contributor




gro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 1 hour ago









gro

62




62




New contributor




gro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





gro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






gro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











  • Very carefully make a backup of the corrupted drive. Please excercise Extreme Caution: dd if=/dev/sdb of=/dev/blankdrive Then you can play around with trying to recover the journal structure, partition tables, etc.
    – jmunsch
    1 hour ago











  • Good call, I have it backed up and hope that someone can point me to a potential way of recovery. Thanks!
    – gro
    12 mins ago










  • what's the output of mdadm --examine /dev/sdb1 ? also see: unix.stackexchange.com/a/72285/61110
    – jmunsch
    7 mins ago











  • mdadm: No md superblock detected on /dev/sdb1. EDIT: And guessing the offset didn't work :p
    – gro
    3 mins ago

















  • Very carefully make a backup of the corrupted drive. Please excercise Extreme Caution: dd if=/dev/sdb of=/dev/blankdrive Then you can play around with trying to recover the journal structure, partition tables, etc.
    – jmunsch
    1 hour ago











  • Good call, I have it backed up and hope that someone can point me to a potential way of recovery. Thanks!
    – gro
    12 mins ago










  • what's the output of mdadm --examine /dev/sdb1 ? also see: unix.stackexchange.com/a/72285/61110
    – jmunsch
    7 mins ago











  • mdadm: No md superblock detected on /dev/sdb1. EDIT: And guessing the offset didn't work :p
    – gro
    3 mins ago
















Very carefully make a backup of the corrupted drive. Please excercise Extreme Caution: dd if=/dev/sdb of=/dev/blankdrive Then you can play around with trying to recover the journal structure, partition tables, etc.
– jmunsch
1 hour ago





Very carefully make a backup of the corrupted drive. Please excercise Extreme Caution: dd if=/dev/sdb of=/dev/blankdrive Then you can play around with trying to recover the journal structure, partition tables, etc.
– jmunsch
1 hour ago













Good call, I have it backed up and hope that someone can point me to a potential way of recovery. Thanks!
– gro
12 mins ago




Good call, I have it backed up and hope that someone can point me to a potential way of recovery. Thanks!
– gro
12 mins ago












what's the output of mdadm --examine /dev/sdb1 ? also see: unix.stackexchange.com/a/72285/61110
– jmunsch
7 mins ago





what's the output of mdadm --examine /dev/sdb1 ? also see: unix.stackexchange.com/a/72285/61110
– jmunsch
7 mins ago













mdadm: No md superblock detected on /dev/sdb1. EDIT: And guessing the offset didn't work :p
– gro
3 mins ago





mdadm: No md superblock detected on /dev/sdb1. EDIT: And guessing the offset didn't work :p
– gro
3 mins ago
















active

oldest

votes











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);






gro is a new contributor. Be nice, and check out our Code of Conduct.









 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f479608%2frecover-data-from-former-raid-1-drive%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes








gro is a new contributor. Be nice, and check out our Code of Conduct.









 

draft saved


draft discarded


















gro is a new contributor. Be nice, and check out our Code of Conduct.












gro is a new contributor. Be nice, and check out our Code of Conduct.











gro is a new contributor. Be nice, and check out our Code of Conduct.













 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f479608%2frecover-data-from-former-raid-1-drive%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)