On Wed, 5 Dec 2018 at 00:36, Nicolas Kovacs info@microlinux.fr wrote:
Le 04/12/2018 à 23:50, Stephen John Smoogen a écrit :
In the rescue mode, recreate the partition table which was on the sdb by copying over what is on sda
sfdisk –d /dev/sda | sfdisk /dev/sdb
This will give the kernel enough to know it has things to do on rebuilding parts.
Once I made sure I retrieved all my data, I followed your suggestion, and it looks like I'm making big progress. The system booted again, though it feels a bit sluggish. Here's the current state of things.
It will because you have 1/2 the bandwidth and there can be a tiny bit of 'write to 2 disks.. nope. read from disk b, nope switch to a'.
[root@alphamule:~] # cat /proc/mdstat Personalities : [raid1] md125 : active raid1 sdb2[1] sda2[0] 512960 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk
md126 : inactive sda1[0](S) 16777216 blocks super 1.2
md127 : active raid1 sda3[0] 959323136 blocks super 1.2 [2/1] [U_] bitmap: 8/8 pages [32KB], 65536KB chunk
unused devices: <none>
Now how can I make my RAID array whole again? For the record, /dev/sda is intact, and /dev/sdb is the faulty disk. How can I force synchronization with /dev/sda?
Cheers,
Phil Perry posted all the things in a better email than I could have (pperry++)
Niki
-- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32 _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos