Dismissing a RAID1
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I've a task in mind that sounds simple, but I'm not sure it would be possible to complete.
I'm dismissing a server, on which I've all partitions (boot partition and others!) mirrored as RAID1 through mdadm.
My idea would be to "dismantle" the raid, keep one of the two disks as "backup copy" of the server (possibly bootable and mountable at the need) and... discard the second copy and the rest of the hardware.
But reading here and there I'm confused on how to do it and if it will work as expected.
Any advice?
Thank you in advance!
boot server partitioning raid mdadm
asked May 23 at 14:05
angelodelia
31
add a comment |Â
up vote
0
down vote
favorite
I've a task in mind that sounds simple, but I'm not sure it would be possible to complete.
I'm dismissing a server, on which I've all partitions (boot partition and others!) mirrored as RAID1 through mdadm.
My idea would be to "dismantle" the raid, keep one of the two disks as "backup copy" of the server (possibly bootable and mountable at the need) and... discard the second copy and the rest of the hardware.
But reading here and there I'm confused on how to do it and if it will work as expected.
Any advice?
Thank you in advance!
boot server partitioning raid mdadm
asked May 23 at 14:05
angelodelia
31
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've a task in mind that sounds simple, but I'm not sure it would be possible to complete.
I'm dismissing a server, on which I've all partitions (boot partition and others!) mirrored as RAID1 through mdadm.
My idea would be to "dismantle" the raid, keep one of the two disks as "backup copy" of the server (possibly bootable and mountable at the need) and... discard the second copy and the rest of the hardware.
But reading here and there I'm confused on how to do it and if it will work as expected.
Any advice?
Thank you in advance!
boot server partitioning raid mdadm
asked May 23 at 14:05
angelodelia
31
I've a task in mind that sounds simple, but I'm not sure it would be possible to complete.
I'm dismissing a server, on which I've all partitions (boot partition and others!) mirrored as RAID1 through mdadm.
My idea would be to "dismantle" the raid, keep one of the two disks as "backup copy" of the server (possibly bootable and mountable at the need) and... discard the second copy and the rest of the hardware.
But reading here and there I'm confused on how to do it and if it will work as expected.
Any advice?
Thank you in advance!
boot server partitioning raid mdadm
asked May 23 at 14:05
angelodelia
31
asked May 23 at 14:05
angelodelia
31
asked May 23 at 14:05
angelodelia
31
asked May 23 at 14:05
angelodelia
31
31
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
If the RAID is properly set up, the system should be able to start up with only one disk. That's basically what the RAID is for, to guard against disk failure. It doesn't matter if the disk failed by itself, or if someone actively got rid of it.
If you get rid of the rest of the machine as well, then you'll have to find a new machine to boot the system up from the remaining disk. That should work as long as the new system is similar enough to the old one. If you replace the disk on newer hardware, there's the risk that the old system will not have drivers for some of the hardware etc.
Though in any case, you should be able to attach the disk to another working system, restart the RAID in degraded mode, and copy any files you need.
If you only need a backup copy of some files, it might be more convenient to put them in e.g. a tar archive and store that somewhere.
If you're not looking for an extra copy of some files, but want to have a backup system to run some service, then don't get rid of the hardware, but keep the working system intact.
answered May 23 at 19:39
ilkkachu
77029
Nightly I ended up in changing plans. It's true that the idea of keeping an exact copy to boot it in the future may be more risky than the data loss itself. So I will probably make "selected" copies of data, and probably I will store them in new disks, better than in the original once that are 10 y.old. :)
– angelodelia
Jun 4 at 13:46
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
If the RAID is properly set up, the system should be able to start up with only one disk. That's basically what the RAID is for, to guard against disk failure. It doesn't matter if the disk failed by itself, or if someone actively got rid of it.
If you get rid of the rest of the machine as well, then you'll have to find a new machine to boot the system up from the remaining disk. That should work as long as the new system is similar enough to the old one. If you replace the disk on newer hardware, there's the risk that the old system will not have drivers for some of the hardware etc.
Though in any case, you should be able to attach the disk to another working system, restart the RAID in degraded mode, and copy any files you need.
If you only need a backup copy of some files, it might be more convenient to put them in e.g. a tar archive and store that somewhere.
If you're not looking for an extra copy of some files, but want to have a backup system to run some service, then don't get rid of the hardware, but keep the working system intact.
answered May 23 at 19:39
ilkkachu
77029
Nightly I ended up in changing plans. It's true that the idea of keeping an exact copy to boot it in the future may be more risky than the data loss itself. So I will probably make "selected" copies of data, and probably I will store them in new disks, better than in the original once that are 10 y.old. :)
– angelodelia
Jun 4 at 13:46
add a comment |Â
up vote
0
down vote
accepted
If the RAID is properly set up, the system should be able to start up with only one disk. That's basically what the RAID is for, to guard against disk failure. It doesn't matter if the disk failed by itself, or if someone actively got rid of it.
If you get rid of the rest of the machine as well, then you'll have to find a new machine to boot the system up from the remaining disk. That should work as long as the new system is similar enough to the old one. If you replace the disk on newer hardware, there's the risk that the old system will not have drivers for some of the hardware etc.
Though in any case, you should be able to attach the disk to another working system, restart the RAID in degraded mode, and copy any files you need.
If you only need a backup copy of some files, it might be more convenient to put them in e.g. a tar archive and store that somewhere.
If you're not looking for an extra copy of some files, but want to have a backup system to run some service, then don't get rid of the hardware, but keep the working system intact.
answered May 23 at 19:39
ilkkachu
77029
Nightly I ended up in changing plans. It's true that the idea of keeping an exact copy to boot it in the future may be more risky than the data loss itself. So I will probably make "selected" copies of data, and probably I will store them in new disks, better than in the original once that are 10 y.old. :)
– angelodelia
Jun 4 at 13:46
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
If the RAID is properly set up, the system should be able to start up with only one disk. That's basically what the RAID is for, to guard against disk failure. It doesn't matter if the disk failed by itself, or if someone actively got rid of it.
If you get rid of the rest of the machine as well, then you'll have to find a new machine to boot the system up from the remaining disk. That should work as long as the new system is similar enough to the old one. If you replace the disk on newer hardware, there's the risk that the old system will not have drivers for some of the hardware etc.
Though in any case, you should be able to attach the disk to another working system, restart the RAID in degraded mode, and copy any files you need.
If you only need a backup copy of some files, it might be more convenient to put them in e.g. a tar archive and store that somewhere.
If you're not looking for an extra copy of some files, but want to have a backup system to run some service, then don't get rid of the hardware, but keep the working system intact.
answered May 23 at 19:39
ilkkachu
77029
If the RAID is properly set up, the system should be able to start up with only one disk. That's basically what the RAID is for, to guard against disk failure. It doesn't matter if the disk failed by itself, or if someone actively got rid of it.
If you get rid of the rest of the machine as well, then you'll have to find a new machine to boot the system up from the remaining disk. That should work as long as the new system is similar enough to the old one. If you replace the disk on newer hardware, there's the risk that the old system will not have drivers for some of the hardware etc.
Though in any case, you should be able to attach the disk to another working system, restart the RAID in degraded mode, and copy any files you need.
If you only need a backup copy of some files, it might be more convenient to put them in e.g. a tar archive and store that somewhere.
If you're not looking for an extra copy of some files, but want to have a backup system to run some service, then don't get rid of the hardware, but keep the working system intact.
answered May 23 at 19:39
ilkkachu
77029
answered May 23 at 19:39
ilkkachu
77029
answered May 23 at 19:39
ilkkachu
77029
answered May 23 at 19:39
ilkkachu
77029
77029
Nightly I ended up in changing plans. It's true that the idea of keeping an exact copy to boot it in the future may be more risky than the data loss itself. So I will probably make "selected" copies of data, and probably I will store them in new disks, better than in the original once that are 10 y.old. :)
– angelodelia
Jun 4 at 13:46
add a comment |Â
Nightly I ended up in changing plans. It's true that the idea of keeping an exact copy to boot it in the future may be more risky than the data loss itself. So I will probably make "selected" copies of data, and probably I will store them in new disks, better than in the original once that are 10 y.old. :)
– angelodelia
Jun 4 at 13:46
Nightly I ended up in changing plans. It's true that the idea of keeping an exact copy to boot it in the future may be more risky than the data loss itself. So I will probably make "selected" copies of data, and probably I will store them in new disks, better than in the original once that are 10 y.old. :)
– angelodelia
Jun 4 at 13:46
Nightly I ended up in changing plans. It's true that the idea of keeping an exact copy to boot it in the future may be more risky than the data loss itself. So I will probably make "selected" copies of data, and probably I will store them in new disks, better than in the original once that are 10 y.old. :)
– angelodelia
Jun 4 at 13:46
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1039442%2fdismissing-a-raid1%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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