Timeline for How to replace faulty disk in software raid using lvm
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 2, 2019 at 7:25 | history | edited | telcoM | CC BY-SA 4.0 |
added 380 characters in body
|
| May 2, 2019 at 7:18 | comment | added | telcoM |
Hmm... grub-install probes all the disks, so perhaps the errors appeared because your /dev/sda is failing... and the result certainly looks like it might have worked despite that. Nevertheless, it might be a good idea to familiarize yourself with how to use SuSE rescue mode, just in case. If it turns out the system won't boot after removing the faulty disk, you'd need to perform the procedure in that doc, then run grub-install /dev/sda again.
|
|
| May 2, 2019 at 7:07 | comment | added | user3615834 | No problem. Please check the original post for the update. Looks fine now? | |
| May 2, 2019 at 6:39 | comment | added | telcoM | Sorry, I accidentally tabbed to the "Add Comment" button and caused an incomplete comment to be posted. Edited. | |
| May 2, 2019 at 6:37 | comment | added | user3615834 | Sorry. I didnt get it. | |
| May 2, 2019 at 6:36 | comment | added | telcoM |
No, the GRUB configuration file /boot/grub/grub.cfg should be fine as is: it seems to be using RAID and LVM UUIDs to identify the necessary partitions, so it probably will auto-detect everything it needs.
|
|
| May 2, 2019 at 6:34 | comment | added | user3615834 | Do I have to change the boot order in grub after I run grub2-install /dev/sdb? | |
| Apr 30, 2019 at 14:45 | comment | added | telcoM |
Yes, it is safe. If you don't do it and /dev/sda fails completely or is removed, your system won't boot. That would be fixable by booting into rescue mode using the installation media, and then activating the RAID + LVM from /dev/sdb (which might have become /dev/sda at that point), mounting the filesystem(s) and chrooting into the installed system, then use grub-install /dev/sda. It's quite number of steps you can avoid by installing the bootloader also to /dev/sdb now while the system is still running normally.
|
|
| Apr 30, 2019 at 13:58 | comment | added | user3615834 | I did run the command for /dev/sdb but it did not give any results. So looks like grub is not installed on sdb. Or am I missing something. If it is really not installed , as per your recommendations , before rebooting this host I should run grub-install /dev/sdb .. is this a safe command? I mean now the system is up and running and I do not wish to disturb it until I have a disk or system replacement plan. | |
| Apr 30, 2019 at 13:15 | comment | added | telcoM |
That command will look into /dev/sda, which is your faulty disk. It is also probably the disk you've been booting from until this moment. You'll want to ensure that the other half of the mirror, /dev/sdb, also has a valid GRUB installation. Other than that, your command looks workable.
|
|
| Apr 30, 2019 at 13:12 | comment | added | user3615834 | Or maybe this command? # dd bs=512 count=1 if=/dev/sda 2>/dev/null| strings ZRrK D|f1 GRUB Geom Hard Disk Read Error | |
| Apr 30, 2019 at 13:02 | history | edited | telcoM | CC BY-SA 4.0 |
how to detect the presence of GRUB in MBR
|
| Apr 30, 2019 at 12:40 | comment | added | user3615834 | Since this is a production system, I would like to first check if grub is already present on the disk /dev/sdb. So then I do not have to reinstall grub on it. Secondly the original grub.conf is now appended in main post. Thanks in advance. | |
| Apr 30, 2019 at 10:27 | history | answered | telcoM | CC BY-SA 4.0 |