Originally Posted by jayakumar_c
My system had a different primary SAS controller from a secondary SAS controller. The primary controller had the linux OS volume. The drivers for the primary and secondary controller are different.
I am finding the OS is not booting (it says "kernel panic - logical volume not found" error) when I moved (disconnected and connected) the hard disks from primary controller to secondary controller.
I wanted to know the necessary steps to be done when I migrate the linux os hard disks to a new controller which has a different driver.
One possibility is that the drives and their placement are the issue. When you move a drive from one controller to another, especially of a different design, you need to pay attention the the jumpers on the drive. Some older interface cables are not self-selecting for primary and secondary drives, which means you have to physically set jumpers on the drive to identify them yourself.
For example, if you take a drive that was set to be secondary and move it to a controller where it is the only drive, it will fail to function until you reset its jumpers. Some systems have cable-select, but not all. And even the cable-select arrangement needs to be specified with jumpers.
Another possibility is that grub is on one drive and the target partition is on another, and by moving the drive you have changed its device number mapping. This would also give the described error message.