Recovering data from a failing RAID 5 setup
I have a four disk RAID 5 array that is in the process of failing hard. One disk is completely dead and smartctl is telling me that a second disk is failing. All the data on the RAID is backed up, however about 1 TB is non trivial to restore since it is ripped CDs and DVDs and I would have to rip them again. I have a spare disk that I can swap out for the dead drive and attempt to rebuild, if that is the right term, the RAID and then backup the difficult data to a different fully healthy new RAID 6 setup. I could also backup the data from the now non-redundant RAID directly to the new RAID.
Is is gentler on a disk from a non-redundant four disk RAID to "restore" the RAID or copy the data directly.
The disks are 2 TB each giving a total RAID size of 6 TB. There is about 5 TB of data on the RAID and I would want to get 1 TB off of it.
data-recovery raid
edited 2 hours ago
Rui F Ribeiro
41.5k1483140
asked Apr 9 '14 at 10:32
StrongBadStrongBad
2,23662656
add a comment |
I have a four disk RAID 5 array that is in the process of failing hard. One disk is completely dead and smartctl is telling me that a second disk is failing. All the data on the RAID is backed up, however about 1 TB is non trivial to restore since it is ripped CDs and DVDs and I would have to rip them again. I have a spare disk that I can swap out for the dead drive and attempt to rebuild, if that is the right term, the RAID and then backup the difficult data to a different fully healthy new RAID 6 setup. I could also backup the data from the now non-redundant RAID directly to the new RAID.
Is is gentler on a disk from a non-redundant four disk RAID to "restore" the RAID or copy the data directly.
The disks are 2 TB each giving a total RAID size of 6 TB. There is about 5 TB of data on the RAID and I would want to get 1 TB off of it.
data-recovery raid
edited 2 hours ago
Rui F Ribeiro
41.5k1483140
asked Apr 9 '14 at 10:32
StrongBadStrongBad
2,23662656
add a comment |
I have a four disk RAID 5 array that is in the process of failing hard. One disk is completely dead and smartctl is telling me that a second disk is failing. All the data on the RAID is backed up, however about 1 TB is non trivial to restore since it is ripped CDs and DVDs and I would have to rip them again. I have a spare disk that I can swap out for the dead drive and attempt to rebuild, if that is the right term, the RAID and then backup the difficult data to a different fully healthy new RAID 6 setup. I could also backup the data from the now non-redundant RAID directly to the new RAID.
Is is gentler on a disk from a non-redundant four disk RAID to "restore" the RAID or copy the data directly.
The disks are 2 TB each giving a total RAID size of 6 TB. There is about 5 TB of data on the RAID and I would want to get 1 TB off of it.
data-recovery raid
edited 2 hours ago
Rui F Ribeiro
41.5k1483140
asked Apr 9 '14 at 10:32
StrongBadStrongBad
2,23662656
I have a four disk RAID 5 array that is in the process of failing hard. One disk is completely dead and smartctl is telling me that a second disk is failing. All the data on the RAID is backed up, however about 1 TB is non trivial to restore since it is ripped CDs and DVDs and I would have to rip them again. I have a spare disk that I can swap out for the dead drive and attempt to rebuild, if that is the right term, the RAID and then backup the difficult data to a different fully healthy new RAID 6 setup. I could also backup the data from the now non-redundant RAID directly to the new RAID.
Is is gentler on a disk from a non-redundant four disk RAID to "restore" the RAID or copy the data directly.
The disks are 2 TB each giving a total RAID size of 6 TB. There is about 5 TB of data on the RAID and I would want to get 1 TB off of it.
data-recovery raid
data-recovery raid
edited 2 hours ago
Rui F Ribeiro
41.5k1483140
asked Apr 9 '14 at 10:32
StrongBadStrongBad
2,23662656
edited 2 hours ago
Rui F Ribeiro
41.5k1483140
asked Apr 9 '14 at 10:32
StrongBadStrongBad
2,23662656
edited 2 hours ago
Rui F Ribeiro
41.5k1483140
edited 2 hours ago
Rui F Ribeiro
41.5k1483140
edited 2 hours ago
Rui F Ribeiro
41.5k1483140
41.5k1483140
asked Apr 9 '14 at 10:32
StrongBadStrongBad
2,23662656
asked Apr 9 '14 at 10:32
StrongBadStrongBad
2,23662656
asked Apr 9 '14 at 10:32
StrongBadStrongBad
2,23662656
2,23662656
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
"Rebuilding" a newly added disk to a RAID array or accessing a degraded ARRAY are signicantly close in term of stress on the disks. The difference here is more about the size of the data to read: 6 GB against just 1 GB.
I would advise you to copy all you can while you can on that spare disk.
The worst case scenario being that the dying disk dies before you are finishing the copy or during the RAID rebuilding attempt.
- While trying to save files: you would end with some of your "non trivial" data saved
- While rebuilding the array: you would lose everything
(the choice in then obvious)
answered Apr 9 '14 at 10:49
OukiOuki
3,86421426
But wouldn't the rebuild be sequential reads while the data copy would be more like random, although hopefully not fully random, reads?
– StrongBad
Apr 9 '14 at 10:53
It really depend on the RAID driver/card, but sequentially is not a simple concept for multi-head/platter disks. So sure, you would gain some time vs randomly, but that would not be x6, nor x6 less stress.
– Ouki
Apr 9 '14 at 10:57
This is a risk assessment here: if the dying disk failed during any operation, what you prefer: having some data saved or not ?
– Ouki
Apr 9 '14 at 10:59
add a comment |
Copy the data from the array first. Rebuilding a full RAID 5 set will involve reading all the data anyway, as new parity data has to be calculated. If you only copy the data you need, you'll be putting less strain on the failing disk.
answered Apr 9 '14 at 10:45
FlupFlup
6,10912244
add a comment |
If one disk is already gone entirely, you're left with no redundancy.
If another disk is failing then, you could duplicate that disk using ddrescue and then see what's left using the duplicate.
At this point you have silent data corruption; with some effort you could locate the affected files, by means of having ddrescue record which areas could not be read, and using filefrag to determine which files had extents in those areas.
It may be simpler to copy the files off the damaged array, provided it is still up and running at all. It's a bit dangerous though as such random access copy is more stressful to a disk than a linear ddrescue, and if the disk dies completely, everything is gone.
Good luck.
PS: You should never let things get so far. Test your disks regularly for read errors, replace disks at the first sign of trouble. Without monitoring, even a RAID6 won't help you much, if you let read errors go undetected for months...
answered Apr 9 '14 at 12:36
frostschutzfrostschutz
27.5k15589
add a comment |
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',
autoActivateHeartbeat: false,
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
});
}
});
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%2funix.stackexchange.com%2fquestions%2f123883%2frecovering-data-from-a-failing-raid-5-setup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
"Rebuilding" a newly added disk to a RAID array or accessing a degraded ARRAY are signicantly close in term of stress on the disks. The difference here is more about the size of the data to read: 6 GB against just 1 GB.
I would advise you to copy all you can while you can on that spare disk.
The worst case scenario being that the dying disk dies before you are finishing the copy or during the RAID rebuilding attempt.
- While trying to save files: you would end with some of your "non trivial" data saved
- While rebuilding the array: you would lose everything
(the choice in then obvious)
answered Apr 9 '14 at 10:49
OukiOuki
3,86421426
But wouldn't the rebuild be sequential reads while the data copy would be more like random, although hopefully not fully random, reads?
– StrongBad
Apr 9 '14 at 10:53
It really depend on the RAID driver/card, but sequentially is not a simple concept for multi-head/platter disks. So sure, you would gain some time vs randomly, but that would not be x6, nor x6 less stress.
– Ouki
Apr 9 '14 at 10:57
This is a risk assessment here: if the dying disk failed during any operation, what you prefer: having some data saved or not ?
– Ouki
Apr 9 '14 at 10:59
add a comment |
"Rebuilding" a newly added disk to a RAID array or accessing a degraded ARRAY are signicantly close in term of stress on the disks. The difference here is more about the size of the data to read: 6 GB against just 1 GB.
I would advise you to copy all you can while you can on that spare disk.
The worst case scenario being that the dying disk dies before you are finishing the copy or during the RAID rebuilding attempt.
- While trying to save files: you would end with some of your "non trivial" data saved
- While rebuilding the array: you would lose everything
(the choice in then obvious)
answered Apr 9 '14 at 10:49
OukiOuki
3,86421426
But wouldn't the rebuild be sequential reads while the data copy would be more like random, although hopefully not fully random, reads?
– StrongBad
Apr 9 '14 at 10:53
It really depend on the RAID driver/card, but sequentially is not a simple concept for multi-head/platter disks. So sure, you would gain some time vs randomly, but that would not be x6, nor x6 less stress.
– Ouki
Apr 9 '14 at 10:57
This is a risk assessment here: if the dying disk failed during any operation, what you prefer: having some data saved or not ?
– Ouki
Apr 9 '14 at 10:59
add a comment |
"Rebuilding" a newly added disk to a RAID array or accessing a degraded ARRAY are signicantly close in term of stress on the disks. The difference here is more about the size of the data to read: 6 GB against just 1 GB.
I would advise you to copy all you can while you can on that spare disk.
The worst case scenario being that the dying disk dies before you are finishing the copy or during the RAID rebuilding attempt.
- While trying to save files: you would end with some of your "non trivial" data saved
- While rebuilding the array: you would lose everything
(the choice in then obvious)
answered Apr 9 '14 at 10:49
OukiOuki
3,86421426
"Rebuilding" a newly added disk to a RAID array or accessing a degraded ARRAY are signicantly close in term of stress on the disks. The difference here is more about the size of the data to read: 6 GB against just 1 GB.
I would advise you to copy all you can while you can on that spare disk.
The worst case scenario being that the dying disk dies before you are finishing the copy or during the RAID rebuilding attempt.
- While trying to save files: you would end with some of your "non trivial" data saved
- While rebuilding the array: you would lose everything
(the choice in then obvious)
answered Apr 9 '14 at 10:49
OukiOuki
3,86421426
edited Apr 9 '14 at 10:55
answered Apr 9 '14 at 10:49
OukiOuki
3,86421426
answered Apr 9 '14 at 10:49
OukiOuki
3,86421426
answered Apr 9 '14 at 10:49
OukiOuki
3,86421426
3,86421426
But wouldn't the rebuild be sequential reads while the data copy would be more like random, although hopefully not fully random, reads?
– StrongBad
Apr 9 '14 at 10:53
It really depend on the RAID driver/card, but sequentially is not a simple concept for multi-head/platter disks. So sure, you would gain some time vs randomly, but that would not be x6, nor x6 less stress.
– Ouki
Apr 9 '14 at 10:57
This is a risk assessment here: if the dying disk failed during any operation, what you prefer: having some data saved or not ?
– Ouki
Apr 9 '14 at 10:59
add a comment |
But wouldn't the rebuild be sequential reads while the data copy would be more like random, although hopefully not fully random, reads?
– StrongBad
Apr 9 '14 at 10:53
It really depend on the RAID driver/card, but sequentially is not a simple concept for multi-head/platter disks. So sure, you would gain some time vs randomly, but that would not be x6, nor x6 less stress.
– Ouki
Apr 9 '14 at 10:57
This is a risk assessment here: if the dying disk failed during any operation, what you prefer: having some data saved or not ?
– Ouki
Apr 9 '14 at 10:59
But wouldn't the rebuild be sequential reads while the data copy would be more like random, although hopefully not fully random, reads?
– StrongBad
Apr 9 '14 at 10:53
But wouldn't the rebuild be sequential reads while the data copy would be more like random, although hopefully not fully random, reads?
– StrongBad
Apr 9 '14 at 10:53
It really depend on the RAID driver/card, but sequentially is not a simple concept for multi-head/platter disks. So sure, you would gain some time vs randomly, but that would not be x6, nor x6 less stress.
– Ouki
Apr 9 '14 at 10:57
It really depend on the RAID driver/card, but sequentially is not a simple concept for multi-head/platter disks. So sure, you would gain some time vs randomly, but that would not be x6, nor x6 less stress.
– Ouki
Apr 9 '14 at 10:57
This is a risk assessment here: if the dying disk failed during any operation, what you prefer: having some data saved or not ?
– Ouki
Apr 9 '14 at 10:59
This is a risk assessment here: if the dying disk failed during any operation, what you prefer: having some data saved or not ?
– Ouki
Apr 9 '14 at 10:59
add a comment |
Copy the data from the array first. Rebuilding a full RAID 5 set will involve reading all the data anyway, as new parity data has to be calculated. If you only copy the data you need, you'll be putting less strain on the failing disk.
answered Apr 9 '14 at 10:45
FlupFlup
6,10912244
add a comment |
Copy the data from the array first. Rebuilding a full RAID 5 set will involve reading all the data anyway, as new parity data has to be calculated. If you only copy the data you need, you'll be putting less strain on the failing disk.
answered Apr 9 '14 at 10:45
FlupFlup
6,10912244
add a comment |
Copy the data from the array first. Rebuilding a full RAID 5 set will involve reading all the data anyway, as new parity data has to be calculated. If you only copy the data you need, you'll be putting less strain on the failing disk.
answered Apr 9 '14 at 10:45
FlupFlup
6,10912244
Copy the data from the array first. Rebuilding a full RAID 5 set will involve reading all the data anyway, as new parity data has to be calculated. If you only copy the data you need, you'll be putting less strain on the failing disk.
answered Apr 9 '14 at 10:45
FlupFlup
6,10912244
answered Apr 9 '14 at 10:45
FlupFlup
6,10912244
answered Apr 9 '14 at 10:45
FlupFlup
6,10912244
answered Apr 9 '14 at 10:45
FlupFlup
6,10912244
6,10912244
add a comment |
add a comment |
If one disk is already gone entirely, you're left with no redundancy.
If another disk is failing then, you could duplicate that disk using ddrescue and then see what's left using the duplicate.
At this point you have silent data corruption; with some effort you could locate the affected files, by means of having ddrescue record which areas could not be read, and using filefrag to determine which files had extents in those areas.
It may be simpler to copy the files off the damaged array, provided it is still up and running at all. It's a bit dangerous though as such random access copy is more stressful to a disk than a linear ddrescue, and if the disk dies completely, everything is gone.
Good luck.
PS: You should never let things get so far. Test your disks regularly for read errors, replace disks at the first sign of trouble. Without monitoring, even a RAID6 won't help you much, if you let read errors go undetected for months...
answered Apr 9 '14 at 12:36
frostschutzfrostschutz
27.5k15589
add a comment |
If one disk is already gone entirely, you're left with no redundancy.
If another disk is failing then, you could duplicate that disk using ddrescue and then see what's left using the duplicate.
At this point you have silent data corruption; with some effort you could locate the affected files, by means of having ddrescue record which areas could not be read, and using filefrag to determine which files had extents in those areas.
It may be simpler to copy the files off the damaged array, provided it is still up and running at all. It's a bit dangerous though as such random access copy is more stressful to a disk than a linear ddrescue, and if the disk dies completely, everything is gone.
Good luck.
PS: You should never let things get so far. Test your disks regularly for read errors, replace disks at the first sign of trouble. Without monitoring, even a RAID6 won't help you much, if you let read errors go undetected for months...
answered Apr 9 '14 at 12:36
frostschutzfrostschutz
27.5k15589
add a comment |
If one disk is already gone entirely, you're left with no redundancy.
If another disk is failing then, you could duplicate that disk using ddrescue and then see what's left using the duplicate.
At this point you have silent data corruption; with some effort you could locate the affected files, by means of having ddrescue record which areas could not be read, and using filefrag to determine which files had extents in those areas.
It may be simpler to copy the files off the damaged array, provided it is still up and running at all. It's a bit dangerous though as such random access copy is more stressful to a disk than a linear ddrescue, and if the disk dies completely, everything is gone.
Good luck.
PS: You should never let things get so far. Test your disks regularly for read errors, replace disks at the first sign of trouble. Without monitoring, even a RAID6 won't help you much, if you let read errors go undetected for months...
answered Apr 9 '14 at 12:36
frostschutzfrostschutz
27.5k15589
If one disk is already gone entirely, you're left with no redundancy.
If another disk is failing then, you could duplicate that disk using ddrescue and then see what's left using the duplicate.
At this point you have silent data corruption; with some effort you could locate the affected files, by means of having ddrescue record which areas could not be read, and using filefrag to determine which files had extents in those areas.
It may be simpler to copy the files off the damaged array, provided it is still up and running at all. It's a bit dangerous though as such random access copy is more stressful to a disk than a linear ddrescue, and if the disk dies completely, everything is gone.
Good luck.
PS: You should never let things get so far. Test your disks regularly for read errors, replace disks at the first sign of trouble. Without monitoring, even a RAID6 won't help you much, if you let read errors go undetected for months...
answered Apr 9 '14 at 12:36
frostschutzfrostschutz
27.5k15589
answered Apr 9 '14 at 12:36
frostschutzfrostschutz
27.5k15589
answered Apr 9 '14 at 12:36
frostschutzfrostschutz
27.5k15589
answered Apr 9 '14 at 12:36
frostschutzfrostschutz
27.5k15589
27.5k15589
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f123883%2frecovering-data-from-a-failing-raid-5-setup%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
