Optimized the description of parameters related to RAID array configuration.Īdded the description about the Mini-SAS port on some RAID controller cards. ![]() Optimized the "Common Commands" section for each RAID controller card. Modified RAID Controller Card Not Healthy in Device Manager.Īdded precautions for capacity expansion by adding drives. Optimized the description of the drive strip size.Optimized the LSI SAS3108 RAID controller card.Added the expandarray parameter and its description for RAID array capacity expansion.Modified section "Importing or Clearing a Foreign Configuration" for each RAID controller card.If you edit the wiki article, please do not add yourself here your contributions are recorded on each article's associated history page. They are listed here because wiki history does not allow for any external attribution. The following people contributed to the original document: Xavier Neys, nightmorph This page is based on a document formerly found on our main website. Only in certain cases will the subsequent installation steps need to be redone. if /etc/fstab changed, exit the chrooted environment and rebootįor most recovery operations, a reboot may be done immediately.if the kernel has been recompiled, just make sure that the bootloader configuration points to the correct kernel image (double-check that /boot is mounted!), then exit the chrooted environment and reboot.if /boot/grub/nf has been altered, it is possible to immediately exit the chrooted environment and reboot as no subsequent steps are depending on nf.if a variable inside nf has been changed, all subsequent compiling since those depend on the settings inside nf will need to be redone.If the subsequent steps are depending on this latest change, they will need to be redone. Once a different approach has been tried, consider how much of the subsequent steps need to be performed again. Don't redo all the steps like bootstrapping and such unless that is the place where things might have gone wrong.įor instance, if suspecting a wrongly configured nf, fire up an editor to update /boot/grub/nf. Once chrooted inside the Gentoo Linux environment, immediately go to the step where it is thought a different approach should be tried. Ignore the steps about stage extraction and modifying nf - so as to not overwrite files. It is possible to immediately mount those partitions at /mnt/gentoo. Follow the instructions again, but ignore the partitioning steps as the partitions are already created and even populated. ![]() Instead, it is possible to safely "go" to the point where an issue occurred (or where it might be suspected the instructions are flawed) and try a different approach.įirst of all chroot back into the Gentoo Linux environment. If for some reason Gentoo installation fails, it is not required to redo the installation all over again. ![]() Root # mke2fs -j -c /dev/sda3 Recovering from a malfunctioning installation Substitute the /dev/sda examples in the installation with this path.īefore chrooting, bind-mount the /dev structure in the new environment: Write down the various /dev/ataraid/disc*/* device files that used to install Gentoo on. An entire disk is displayed as disc while partitions are part*. It should contain various disc* directories for each hard disk available in the ATA RAID. Once booted, check the contents of /dev/ataraid. Make sure to boot the Installation CD using the doataraid option. When configuring the bootloader, make sure it gets installed in the MBR of both disks if using mirroring. Note that this isn't available on all Installation CDs so it might not be possible to install Gentoo on a Software RAID when using a networkless installation! When installing extra tools, emerge sys-fs/mdadm as well. ![]() When configuring the kernel, make sure to have the appropriate RAID support in the kernel and not as module. Right before chrooting, don't forget to copy over /etc/nf to /mnt/gentoo/etc. Root # mdadm -detail -scan > /etc/nfįrom now onwards, use /dev/md1 for the boot partition, /dev/md2 for the swap partition and /dev/md3 for the root partition.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |