On 12/30/21 04:04, cen wrote:
On 26. 12. 21 04:20, Sam Varshavchik wrote:
cen writes:
On 25. 12. 21 01:16, Sam Varshavchik wrote:
cen writes:
# copy partition map from good disk to new disk
sfdisk -d /dev/sde | sfdisk /dev/sdd
This only works if the new disk is identical to the old one,
On 26. 12. 21 04:20, Sam Varshavchik wrote:
cen writes:
On 25. 12. 21 01:16, Sam Varshavchik wrote:
cen writes:
# copy partition map from good disk to new disk
sfdisk -d /dev/sde | sfdisk /dev/sdd
This only works if the new disk is identical to the old one,
geometry-wise.
Otherwise you
cen writes:
On 25. 12. 21 01:16, Sam Varshavchik wrote:
cen writes:
# copy partition map from good disk to new disk
sfdisk -d /dev/sde | sfdisk /dev/sdd
This only works if the new disk is identical to the old one, geometry-wise.
Otherwise you can simply create partitions of the same size
On 25. 12. 21 01:16, Sam Varshavchik wrote:
cen writes:
# copy partition map from good disk to new disk
sfdisk -d /dev/sde | sfdisk /dev/sdd
This only works if the new disk is identical to the old one,
geometry-wise.
Otherwise you can simply create partitions of the same size using
On 24. 12. 21 19:22, Doug Herr wrote:
On Fri, Dec 24, 2021, at 6:38 AM, cen wrote:
I recently had to replace a bad disk in raid1 array and finding proper
docs was not a good experience.
Looking at my notes, I can add some of my notes. These may or may not apply to
you...
(Should not be
On 24. 12. 21 17:46, Michael D. Setzer II via users wrote:
Did have our Admin have a System that was running SCO
and it had a failure in a 3 disk system. It kept working
fine after failure, but when they replace the bad drive the
rebuild that was suppose to be automatic failed. Some
how it mixed
On 12/24/21 14:29, Cameron Simpson wrote:
On 24Dec2021 12:09, Gordon Messmer wrote:
Additionally, it should be performed *after* adding the replacement
disk to the RAID set, not before.
Is that true? My (blurry) mental model for this issue is that the boot
block isn't in the area maintained
cen writes:
# copy partition map from good disk to new disk
sfdisk -d /dev/sde | sfdisk /dev/sdd
This only works if the new disk is identical to the old one, geometry-wise.
Otherwise you can simply create partitions of the same size using parted, on
the new drive.
# install bootloader
On 24Dec2021 12:09, Gordon Messmer wrote:
>># install bootloader on new disk
>>grub2-install /dev/sdd1
>
>That looks wrong, it should probably be 'grub2-install /dev/sdd'.
>Additionally, it should be performed *after* adding the replacement
>disk to the RAID set, not before.
Is that true? My
On 12/24/21 06:38, cen wrote:
# remove raid metadata
mdadm --zero-superblock /dev/sdd1
Assuming the new disk hasn't been used, that step is probably unnecessary.
# install bootloader on new disk
grub2-install /dev/sdd1
That looks wrong, it should probably be 'grub2-install /dev/sdd'.
On Fri, Dec 24, 2021, at 6:38 AM, cen wrote:
> I recently had to replace a bad disk in raid1 array and finding proper
> docs was not a good experience.
Looking at my notes, I can add some of my notes. These may or may not apply to
you...
(Should not be needed since you are not changing the
On 24 Dec 2021 at 12:11, George N. White III wrote:
From: "George N. White III"
Date sent: Fri, 24 Dec 2021 12:11:03 -0400
Subject:Re: The definitive guide to replacing a disk in raid1?
To: Community support for Fedora users
Send reply to: Community support for Fedora users
On Fri, 24 Dec 2021 at 10:50, Tom Horsley wrote:
> On Fri, 24 Dec 2021 15:38:05 +0100
> cen wrote:
>
> > I recently had to replace a bad disk in raid1 array and finding proper
> > docs was not a good experience.
>
> I've always noticed that about raid in general. Thousands of internet
> pages
On Fri, 24 Dec 2021 15:38:05 +0100
cen wrote:
> I recently had to replace a bad disk in raid1 array and finding proper
> docs was not a good experience.
I've always noticed that about raid in general. Thousands of internet
pages telling you how redundant arrays protect you from disk failures
I recently had to replace a bad disk in raid1 array and finding proper
docs was not a good experience.
There is apparently also a trap with not having a bootloader installed
on the replacement disk which can make the system unbootable in cause of
array degradation. Some of the guides don't
15 matches
Mail list logo
