I had an issue recently with a server with two drives in software raid 1. /dev/sda and /dev/sdb. /dev/sda (sata port 0) died. I took the server offline and replaced it with a new drive. Server wouldn't boot.
So I figured grub needed to be installed on /dev/sdb. I booted to a rescue environment and installed grub on /dev/sdb. Tried to boot and got:
Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Swithing to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! So I went back to rescue mode, cloned the partition table from the good drive to the new drive with sfdisk and was able to get mdadm to rebuild offline. I mounted the md device from rescue mode and was able to chroot and start networking and sshd.
This was for a colocation client at the datacenter I work for. This client was able to fix everything instantly once he had ssh access. Rebooted, and everything was fine. I suspect that he rebuilt the initrd image, but that's just from googling the issue and guessing -- I have no clue what he did or what the real problem was.
We don't use software raid internally so it's not something I deal with on an everyday basis. I'm considering just asking him what he did to fix the issue, but I thought I'd ask here first. Any ideas on what he might have done to make this server boot?
[link][10 comments]
