This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
alicebeast [2020/06/18 15:48] florido [Admin rights] |
alicebeast [2020/06/23 09:49] florido |
||
---|---|---|---|
Line 136: | Line 136: | ||
> How to detect? | > How to detect? | ||
- | > What to do | + | > What to do - FIXME: requires own page |
+ | |||
+ | 1. Identify the broken raid disk. If it is one of the U.2 disks, then the procedure is slightly easier. One can skip steps FIXME:[number of steps] | ||
+ | |||
+ | 2. Mark the RAID disk as faulty if the system did not do automatically. | ||
+ | |||
+ | 3. Remove the device from the array. | ||
+ | |||
+ | 4. Shut down the machine. | ||
+ | |||
+ | 5. Replace the broken disk. | ||
+ | |||
+ | 6. start the machine using sysrescuecd. | ||
+ | |||
+ | 7. Create the proper partitions on the disk. | ||
+ | * FIXME copy geometry and UUIDs here for reference | ||
+ | 8. Initialize the swap partition on the new disk | ||
+ | |||
+ | 9. If one of the arrays is inactive, must be restarted. Follow FIXME:[procedure for restarting] | ||
+ | |||
+ | 10. Add the new partitions to existing arrays. Wait for the arrays to rebuild. | ||
+ | |||
+ | 11. Mount the array and change the UUID of the swap partition in /etc/fstab | ||
+ | |||
+ | 12. Rebuilding the boot system | ||
+ | |||
+ | 12.1. Boot with Centos7 rescue image in troubleshooting mode | ||
+ | * FIXME: provide such image or info how to boot | ||
+ | 12.2. chroot to system, identify new disk, run grub2-install /dev/newdisk | ||
+ | |||
+ | 12.3. reboot | ||
+ | |||
+ | 13. If it worked one should see the grub boot -- it might be required to boot again | ||
+ | |||
+ | If it didn't work the disk device at step 12.2 was wrong, repeat 12 | ||
+ | |||
+ | ==== raw disks info ==== | ||
+ | |||
+ | <code bash> | ||
+ | Disk /dev/nvme0n1: 250.1 GB, 250059350016 bytes, 488397168 sectors | ||
+ | Units = sectors of 1 * 512 = 512 bytes | ||
+ | Sector size (logical/physical): 512 bytes / 512 bytes | ||
+ | I/O size (minimum/optimal): 512 bytes / 512 bytes | ||
+ | Disk label type: dos | ||
+ | Disk identifier: 0x000c07b1 | ||
+ | |||
+ | Device Boot Start End Blocks Id System | ||
+ | /dev/nvme0n1p1 * 2048 195444735 97721344 fd Linux raid autodetect | ||
+ | /dev/nvme0n1p2 195444736 390887423 97721344 fd Linux raid autodetect | ||
+ | /dev/nvme0n1p3 390887424 422135807 15624192 82 Linux swap / Solaris | ||
+ | |||
+ | Disk /dev/nvme1n1: 960.2 GB, 960197124096 bytes, 1875385008 sectors | ||
+ | Units = sectors of 1 * 512 = 512 bytes | ||
+ | Sector size (logical/physical): 512 bytes / 512 bytes | ||
+ | I/O size (minimum/optimal): 512 bytes / 512 bytes | ||
+ | Disk label type: dos | ||
+ | Disk identifier: 0x000c4c4c | ||
+ | |||
+ | Device Boot Start End Blocks Id System | ||
+ | /dev/nvme1n1p1 * 2048 195444735 97721344 fd Linux raid autodetect | ||
+ | /dev/nvme1n1p2 195444736 390887423 97721344 fd Linux raid autodetect | ||
+ | /dev/nvme1n1p3 390887424 1875384319 742248448 fd Linux raid autodetect | ||
+ | |||
+ | Disk /dev/nvme2n1: 960.2 GB, 960197124096 bytes, 1875385008 sectors | ||
+ | Units = sectors of 1 * 512 = 512 bytes | ||
+ | Sector size (logical/physical): 512 bytes / 512 bytes | ||
+ | I/O size (minimum/optimal): 512 bytes / 512 bytes | ||
+ | Disk label type: dos | ||
+ | Disk identifier: 0x000e7acc | ||
+ | |||
+ | Device Boot Start End Blocks Id System | ||
+ | /dev/nvme2n1p1 * 2048 195444735 97721344 fd Linux raid autodetect | ||
+ | /dev/nvme2n1p2 195444736 390887423 97721344 fd Linux raid autodetect | ||
+ | /dev/nvme2n1p3 390887424 1875384319 742248448 fd Linux raid autodetect | ||
+ | </code> | ||
===== Monitoring ===== | ===== Monitoring ===== |