Unable to Mount Partition from NAS RAID Array to Recover Data
Ubuntu newbie question. Similar questions are asked here but that relates to motherboard and here, but that does not address "mounting" issues.
I have one disk of a 2 disk raid1 array that failed in the raid device. The manufacturer and subsequent investigation indicates it is formatted as a linux disk.
fdisk -l displays
Device Start End Sectors Size Type
/dev/sdb1 41 1953 1913 956.5K Microsoft basic data
/dev/sdb2 ...
...
/dev/sdb9 6504448 8503295 1998848 976M Microsoft basic data
/dev/sdb10 8503296 7814035254 7805531959 3.6T Microsoft basic data
I run
sudo mount /dev/sdb10 /media/seagate
and get
mount: /media/seagate: unknown filesystem type 'linux_raid_member'.
Following the advice here I ran
sudo mdadm --assemble --run /dev/md0 /dev/sdb10
producing:
mdadm: /dev/sdb10 is busy - skipping
mdadm --examine produces
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e733e938:772dc035:5c104e46:4d4fe2da
Name : BA-001075384F44:8
Creation Time : Wed Apr 24 18:37:09 2013
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 7805529911 (3721.97 GiB 3996.43 GB)
Array Size : 3902764819 (3721.97 GiB 3996.43 GB)
Used Dev Size : 7805529638 (3721.97 GiB 3996.43 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=273 sectors
State : clean
Device UUID : b8ca69f9:bba3bbc2:33f7033e:67308d4f
Update Time : Fri Dec 14 13:54:41 2018
Checksum : a891168f - correct
Events : 2
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
One final question was posted here but according to @Ian, the question was never answered satisfactorily.
I am at an impasse it seems. Can anyone point me in the right direction for mounting this partition and (hopefully) recovering the data on it?
Thanks in advance.
Well, made some headway. Used these instructions and I can see the LVM both in terminal window and in GUI interface.
But then:
mount /dev/vg8/lv8 /mnt/sd1
Generates:
“Wrong fs type, bad option, bad superblock on /dev/mapper/vg8-lv8,
missing codepage or helper program, or other error”
Followed the advice and used
mkfs.ext4 /dev/vg8/lv8
But got message
/dev/vg8/lv8 contains a ext4 file system
last mounted on /shares/public on Tue Sept 16 20:00:52 1975
Proceed anyway?
JerryFrey suggested using a file recovery such as foremost. But don't I have to mount the partition first?
ubuntu hard-drive raid data-recovery nas
asked Dec 21 '18 at 19:12
PhillipOReillyPhillipOReilly
137210
add a comment |
Ubuntu newbie question. Similar questions are asked here but that relates to motherboard and here, but that does not address "mounting" issues.
I have one disk of a 2 disk raid1 array that failed in the raid device. The manufacturer and subsequent investigation indicates it is formatted as a linux disk.
fdisk -l displays
Device Start End Sectors Size Type
/dev/sdb1 41 1953 1913 956.5K Microsoft basic data
/dev/sdb2 ...
...
/dev/sdb9 6504448 8503295 1998848 976M Microsoft basic data
/dev/sdb10 8503296 7814035254 7805531959 3.6T Microsoft basic data
I run
sudo mount /dev/sdb10 /media/seagate
and get
mount: /media/seagate: unknown filesystem type 'linux_raid_member'.
Following the advice here I ran
sudo mdadm --assemble --run /dev/md0 /dev/sdb10
producing:
mdadm: /dev/sdb10 is busy - skipping
mdadm --examine produces
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e733e938:772dc035:5c104e46:4d4fe2da
Name : BA-001075384F44:8
Creation Time : Wed Apr 24 18:37:09 2013
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 7805529911 (3721.97 GiB 3996.43 GB)
Array Size : 3902764819 (3721.97 GiB 3996.43 GB)
Used Dev Size : 7805529638 (3721.97 GiB 3996.43 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=273 sectors
State : clean
Device UUID : b8ca69f9:bba3bbc2:33f7033e:67308d4f
Update Time : Fri Dec 14 13:54:41 2018
Checksum : a891168f - correct
Events : 2
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
One final question was posted here but according to @Ian, the question was never answered satisfactorily.
I am at an impasse it seems. Can anyone point me in the right direction for mounting this partition and (hopefully) recovering the data on it?
Thanks in advance.
Well, made some headway. Used these instructions and I can see the LVM both in terminal window and in GUI interface.
But then:
mount /dev/vg8/lv8 /mnt/sd1
Generates:
“Wrong fs type, bad option, bad superblock on /dev/mapper/vg8-lv8,
missing codepage or helper program, or other error”
Followed the advice and used
mkfs.ext4 /dev/vg8/lv8
But got message
/dev/vg8/lv8 contains a ext4 file system
last mounted on /shares/public on Tue Sept 16 20:00:52 1975
Proceed anyway?
JerryFrey suggested using a file recovery such as foremost. But don't I have to mount the partition first?
ubuntu hard-drive raid data-recovery nas
asked Dec 21 '18 at 19:12
PhillipOReillyPhillipOReilly
137210
add a comment |
Ubuntu newbie question. Similar questions are asked here but that relates to motherboard and here, but that does not address "mounting" issues.
I have one disk of a 2 disk raid1 array that failed in the raid device. The manufacturer and subsequent investigation indicates it is formatted as a linux disk.
fdisk -l displays
Device Start End Sectors Size Type
/dev/sdb1 41 1953 1913 956.5K Microsoft basic data
/dev/sdb2 ...
...
/dev/sdb9 6504448 8503295 1998848 976M Microsoft basic data
/dev/sdb10 8503296 7814035254 7805531959 3.6T Microsoft basic data
I run
sudo mount /dev/sdb10 /media/seagate
and get
mount: /media/seagate: unknown filesystem type 'linux_raid_member'.
Following the advice here I ran
sudo mdadm --assemble --run /dev/md0 /dev/sdb10
producing:
mdadm: /dev/sdb10 is busy - skipping
mdadm --examine produces
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e733e938:772dc035:5c104e46:4d4fe2da
Name : BA-001075384F44:8
Creation Time : Wed Apr 24 18:37:09 2013
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 7805529911 (3721.97 GiB 3996.43 GB)
Array Size : 3902764819 (3721.97 GiB 3996.43 GB)
Used Dev Size : 7805529638 (3721.97 GiB 3996.43 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=273 sectors
State : clean
Device UUID : b8ca69f9:bba3bbc2:33f7033e:67308d4f
Update Time : Fri Dec 14 13:54:41 2018
Checksum : a891168f - correct
Events : 2
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
One final question was posted here but according to @Ian, the question was never answered satisfactorily.
I am at an impasse it seems. Can anyone point me in the right direction for mounting this partition and (hopefully) recovering the data on it?
Thanks in advance.
Well, made some headway. Used these instructions and I can see the LVM both in terminal window and in GUI interface.
But then:
mount /dev/vg8/lv8 /mnt/sd1
Generates:
“Wrong fs type, bad option, bad superblock on /dev/mapper/vg8-lv8,
missing codepage or helper program, or other error”
Followed the advice and used
mkfs.ext4 /dev/vg8/lv8
But got message
/dev/vg8/lv8 contains a ext4 file system
last mounted on /shares/public on Tue Sept 16 20:00:52 1975
Proceed anyway?
JerryFrey suggested using a file recovery such as foremost. But don't I have to mount the partition first?
ubuntu hard-drive raid data-recovery nas
asked Dec 21 '18 at 19:12
PhillipOReillyPhillipOReilly
137210
Ubuntu newbie question. Similar questions are asked here but that relates to motherboard and here, but that does not address "mounting" issues.
I have one disk of a 2 disk raid1 array that failed in the raid device. The manufacturer and subsequent investigation indicates it is formatted as a linux disk.
fdisk -l displays
Device Start End Sectors Size Type
/dev/sdb1 41 1953 1913 956.5K Microsoft basic data
/dev/sdb2 ...
...
/dev/sdb9 6504448 8503295 1998848 976M Microsoft basic data
/dev/sdb10 8503296 7814035254 7805531959 3.6T Microsoft basic data
I run
sudo mount /dev/sdb10 /media/seagate
and get
mount: /media/seagate: unknown filesystem type 'linux_raid_member'.
Following the advice here I ran
sudo mdadm --assemble --run /dev/md0 /dev/sdb10
producing:
mdadm: /dev/sdb10 is busy - skipping
mdadm --examine produces
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e733e938:772dc035:5c104e46:4d4fe2da
Name : BA-001075384F44:8
Creation Time : Wed Apr 24 18:37:09 2013
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 7805529911 (3721.97 GiB 3996.43 GB)
Array Size : 3902764819 (3721.97 GiB 3996.43 GB)
Used Dev Size : 7805529638 (3721.97 GiB 3996.43 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=273 sectors
State : clean
Device UUID : b8ca69f9:bba3bbc2:33f7033e:67308d4f
Update Time : Fri Dec 14 13:54:41 2018
Checksum : a891168f - correct
Events : 2
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
One final question was posted here but according to @Ian, the question was never answered satisfactorily.
I am at an impasse it seems. Can anyone point me in the right direction for mounting this partition and (hopefully) recovering the data on it?
Thanks in advance.
Well, made some headway. Used these instructions and I can see the LVM both in terminal window and in GUI interface.
But then:
mount /dev/vg8/lv8 /mnt/sd1
Generates:
“Wrong fs type, bad option, bad superblock on /dev/mapper/vg8-lv8,
missing codepage or helper program, or other error”
Followed the advice and used
mkfs.ext4 /dev/vg8/lv8
But got message
/dev/vg8/lv8 contains a ext4 file system
last mounted on /shares/public on Tue Sept 16 20:00:52 1975
Proceed anyway?
JerryFrey suggested using a file recovery such as foremost. But don't I have to mount the partition first?
ubuntu hard-drive raid data-recovery nas
ubuntu hard-drive raid data-recovery nas
asked Dec 21 '18 at 19:12
PhillipOReillyPhillipOReilly
137210
asked Dec 21 '18 at 19:12
PhillipOReillyPhillipOReilly
137210
edited Dec 28 '18 at 6:09
PhillipOReilly
asked Dec 21 '18 at 19:12
PhillipOReillyPhillipOReilly
137210
asked Dec 21 '18 at 19:12
PhillipOReillyPhillipOReilly
137210
asked Dec 21 '18 at 19:12
PhillipOReillyPhillipOReilly
137210
137210
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Answers mentioned here https://unix.stackexchange.com/questions/64889/how-to-mount-recover-data-on-a-disk-that-was-part-of-a-mdadm-raid-1-on-another-m may help you.
There is one more option to recover data, use Data Recovery software. The software can ease you task and avoid the risk of losing data.
But, try to mount the partition first.
answered Dec 27 '18 at 5:42
JerryFreyJerryFrey
611
thanks for the pointer. I made some progress. See my additional notes in question. . I was going to try foremost, but it appears that I still need to mount the partition first. You know whether that is correct?
– PhillipOReilly
Dec 28 '18 at 5:57
You got me on the right track, so I marked your answer as correct. Thanks.
– PhillipOReilly
Jan 1 at 16:34
1
Did you find the solution? If yes, Please mention which one helped you. So that it will help other users as well with relevant query.
– JerryFrey
Jan 2 at 5:42
yes I did. I detail some of this in the update to the question above. The rest I detail here: askubuntu.com/a/1106046/906115
– PhillipOReilly
Jan 2 at 21:18
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1386748%2funable-to-mount-partition-from-nas-raid-array-to-recover-data%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Answers mentioned here https://unix.stackexchange.com/questions/64889/how-to-mount-recover-data-on-a-disk-that-was-part-of-a-mdadm-raid-1-on-another-m may help you.
There is one more option to recover data, use Data Recovery software. The software can ease you task and avoid the risk of losing data.
But, try to mount the partition first.
answered Dec 27 '18 at 5:42
JerryFreyJerryFrey
611
thanks for the pointer. I made some progress. See my additional notes in question. . I was going to try foremost, but it appears that I still need to mount the partition first. You know whether that is correct?
– PhillipOReilly
Dec 28 '18 at 5:57
You got me on the right track, so I marked your answer as correct. Thanks.
– PhillipOReilly
Jan 1 at 16:34
1
Did you find the solution? If yes, Please mention which one helped you. So that it will help other users as well with relevant query.
– JerryFrey
Jan 2 at 5:42
yes I did. I detail some of this in the update to the question above. The rest I detail here: askubuntu.com/a/1106046/906115
– PhillipOReilly
Jan 2 at 21:18
add a comment |
Answers mentioned here https://unix.stackexchange.com/questions/64889/how-to-mount-recover-data-on-a-disk-that-was-part-of-a-mdadm-raid-1-on-another-m may help you.
There is one more option to recover data, use Data Recovery software. The software can ease you task and avoid the risk of losing data.
But, try to mount the partition first.
answered Dec 27 '18 at 5:42
JerryFreyJerryFrey
611
thanks for the pointer. I made some progress. See my additional notes in question. . I was going to try foremost, but it appears that I still need to mount the partition first. You know whether that is correct?
– PhillipOReilly
Dec 28 '18 at 5:57
You got me on the right track, so I marked your answer as correct. Thanks.
– PhillipOReilly
Jan 1 at 16:34
1
Did you find the solution? If yes, Please mention which one helped you. So that it will help other users as well with relevant query.
– JerryFrey
Jan 2 at 5:42
yes I did. I detail some of this in the update to the question above. The rest I detail here: askubuntu.com/a/1106046/906115
– PhillipOReilly
Jan 2 at 21:18
add a comment |
Answers mentioned here https://unix.stackexchange.com/questions/64889/how-to-mount-recover-data-on-a-disk-that-was-part-of-a-mdadm-raid-1-on-another-m may help you.
There is one more option to recover data, use Data Recovery software. The software can ease you task and avoid the risk of losing data.
But, try to mount the partition first.
answered Dec 27 '18 at 5:42
JerryFreyJerryFrey
611
Answers mentioned here https://unix.stackexchange.com/questions/64889/how-to-mount-recover-data-on-a-disk-that-was-part-of-a-mdadm-raid-1-on-another-m may help you.
There is one more option to recover data, use Data Recovery software. The software can ease you task and avoid the risk of losing data.
But, try to mount the partition first.
answered Dec 27 '18 at 5:42
JerryFreyJerryFrey
611
answered Dec 27 '18 at 5:42
JerryFreyJerryFrey
611
answered Dec 27 '18 at 5:42
JerryFreyJerryFrey
611
answered Dec 27 '18 at 5:42
JerryFreyJerryFrey
611
611
thanks for the pointer. I made some progress. See my additional notes in question. . I was going to try foremost, but it appears that I still need to mount the partition first. You know whether that is correct?
– PhillipOReilly
Dec 28 '18 at 5:57
You got me on the right track, so I marked your answer as correct. Thanks.
– PhillipOReilly
Jan 1 at 16:34
1
Did you find the solution? If yes, Please mention which one helped you. So that it will help other users as well with relevant query.
– JerryFrey
Jan 2 at 5:42
yes I did. I detail some of this in the update to the question above. The rest I detail here: askubuntu.com/a/1106046/906115
– PhillipOReilly
Jan 2 at 21:18
add a comment |
thanks for the pointer. I made some progress. See my additional notes in question. . I was going to try foremost, but it appears that I still need to mount the partition first. You know whether that is correct?
– PhillipOReilly
Dec 28 '18 at 5:57
You got me on the right track, so I marked your answer as correct. Thanks.
– PhillipOReilly
Jan 1 at 16:34
1
Did you find the solution? If yes, Please mention which one helped you. So that it will help other users as well with relevant query.
– JerryFrey
Jan 2 at 5:42
yes I did. I detail some of this in the update to the question above. The rest I detail here: askubuntu.com/a/1106046/906115
– PhillipOReilly
Jan 2 at 21:18
thanks for the pointer. I made some progress. See my additional notes in question. . I was going to try foremost, but it appears that I still need to mount the partition first. You know whether that is correct?
– PhillipOReilly
Dec 28 '18 at 5:57
thanks for the pointer. I made some progress. See my additional notes in question. . I was going to try foremost, but it appears that I still need to mount the partition first. You know whether that is correct?
– PhillipOReilly
Dec 28 '18 at 5:57
You got me on the right track, so I marked your answer as correct. Thanks.
– PhillipOReilly
Jan 1 at 16:34
You got me on the right track, so I marked your answer as correct. Thanks.
– PhillipOReilly
Jan 1 at 16:34
1
1
Did you find the solution? If yes, Please mention which one helped you. So that it will help other users as well with relevant query.
– JerryFrey
Jan 2 at 5:42
Did you find the solution? If yes, Please mention which one helped you. So that it will help other users as well with relevant query.
– JerryFrey
Jan 2 at 5:42
yes I did. I detail some of this in the update to the question above. The rest I detail here: askubuntu.com/a/1106046/906115
– PhillipOReilly
Jan 2 at 21:18
yes I did. I detail some of this in the update to the question above. The rest I detail here: askubuntu.com/a/1106046/906115
– PhillipOReilly
Jan 2 at 21:18
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1386748%2funable-to-mount-partition-from-nas-raid-array-to-recover-data%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
