Softraid add new disk to raid array7/22/2023 ![]() In this guide, we have discussed steps to securely add back or recover missing member disk in RAID 5 array and get back your important files without data loss. Remember, you can recover data from a broken RAID 5 array as long as you avoid applying various hit & trial methods. In such a case, anything you do such as rebuild RAID array or run disk repair utilities may destroy your data permanently. The disks were dropped from the array after the firmware update-making the RAID 5 configuration and data inaccessible. But all drivers were working fine, none failed. In an incident reported at the tech community Tomshardware, after a user upgraded motherboard firmware, 2 of 4 RAID 5 disks started to show as non-RAID drives. After the drive failure, the condition of a degraded or broken RAID 5 array could further degrade due to continued usage and during the rebuild, which can deteriorate other (older) drives faster.īeside disk errors, a RAID 5 configuration may also break due to any of the following reasons, Thus, it is critical to replace the member disk with a new one as soon as possible.īut you should do it cautiously. But the RAID 5 array’s redundancy and performance are compromised. When one disk fails, the RAID 5 enters in the degraded state-a fallback mode that allows the continued usage of the RAID 5 array. A RAID 5 configuration can withstand up to one drive crash or failure without data loss and has three different states-Operational, Degraded, and Failed. However, I'm unsure if sda will boot after installing grub on sdb and vice versa.RAID 5 is the most commonly used and inexpensive RAID configuration that offers both performance (reads equivalent to RAID 0) and redundancy. I was able to run the following commands independently: grub-install /dev/sda I do have a /boot/grub/ directory, so I know some form of grub is installed. It looks like grub has been superceded somehow in 14.04, but I can't find any information about how things have changed. Grub-install: error: will not proceed with blocklists. However, blocklists are UNRELIABLE and their use is discouraged. GRUB can only be installed in this setup by using blocklists. Grub-install: warning: Embedding is not possible. Grub-install: warning: File system `ext2' doesn't support embedding. Some modules may be missing from core image. ![]() ![]() Grub-install: warning: Couldn't find physical volume `(null)'. This was the output: # grub-install /dev/md0 The official server guide recommends (at the bottom of the "Raid Maintenance" section): grub-install /dev/md0 Getting desparate, I tried something I was pretty sure was wrong. The following NEW packages will be installed:Ġ upgraded, 1 newly installed, 3 to remove and 0 not upgraded.Īfter this operation, 438 kB of additional disk space will be used. ![]() Grub-gfxpayload-lists grub-pc grub2-common Only problem? After the first command, I get: The program 'grub' is currently not installed. The grub prompt scares me, but I was willing to try these steps: # grub -device-map=/boot/grub/device.map Some walkthroughs recommended setting up grub for the new hard drive manually. However, when I ran that, I got: grub-install: error: More than one install device?. Which is the exact same command I've seen the Ubuntu installer run a hundred times. Most walkthroughs I've found told me to run: grub-install /dev/sda /dev/sdb Note: all commands below were run as root The problem I'm running into is making sure it can boot if sda happens to fail in the future. Adding it back to the array with mdadm and resyncing was a snap. I have an Ubuntu 14.04 圆4 server with 2 500GB drives ( sda and sdb) in a software RAID 1. ![]()
0 Comments
Leave a Reply. |