On Wednesday 27 February 2019 14:43:30 Gary Stainburn wrote: > Hi folks > > I've got an old F9 server which has been running forever without any > problems has just failed to reboot. > > I have 2 x RAID1 setup > > sda and sdb are the first raid device > sdc and add are the second device. > > Also, to make life even more fun I only have 4 SATA ports so I have to > remove one HDD to get the DVD to work, and the m/b doesn't support USB DVD > > it looks like sda has failed - it doesn't even appear in the BIOS list. > > I am currently cloning sdb before doing anything, but once that's done, I > want to replace sda and rebuild the array. From memory, I do not think that > the boot partitons could be RAID'ed back then so I'm not sure what state > the boot partition is in on sdb. > > Does anyone have any instructions on how to do this based on the age of the > system? So far, Google only seems to want to give me more recent solutions. I've now cloned the good drive, and the copy has been put safe. I'm now trying to get it bootable with just this one drive. I've booted using a Fedora 16 DVD in rescue mode, and using the instructions on https://www.thegeekdiary.com/centos-rhel-how-to-assemble-a-software-raid-in-rescue-mode/ I've managed to get the RAID devices running (on 1 our of 2 drives) and have access to all four devices. /dev/md/boot /dev/md/root /dev/md/swap /dev/md/var_bacula I have mounted /dev/md/root on /mnt/sysimage and then run chroot /mnt/sysimage to go to the true root. However, when I then try to mount /boot it says no such device /dev/md/boot as this is on the pre-chrooted tree. How can I get access to /boot so that I can then run grub2-install? _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
