I just replaced two md-raided (RAID1) disks with bigger ones and decided to check out how far I get with them when I put them in another machine. The kernel boots and then panics when it wants to mount the root filesystem on the disk.
md: Autodetecting RAID arrays md: autorun md: autorun DONE < not sure if this means it was successful or failed, I rather think it failed because it doesn't list any md devices? > Creating root device Mounting root filesystem EXT3-fs: unable to read superblock
I pxe-booted in rescue mode. Interestingly, the rescue mode detects and mounts the RAID partitions just fine and mdadm sees them all as healthy. It mounts them under /tmp/md0 and /tmp/md1. Shouldn't the installed system be able to do the same, mount under /dev/md0 and /dev/md1 and then find root on /dev/md1 as told by grub.conf? Or could it be that the installed system also mounts them under /tmp?
I'm not sure how I can troubleshoot this.
Kai
Kai Schaetzl wrote:
I just replaced two md-raided (RAID1) disks with bigger ones and decided to check out how far I get with them when I put them in another machine. The kernel boots and then panics when it wants to mount the root filesystem on the disk.
md: Autodetecting RAID arrays md: autorun md: autorun DONE < not sure if this means it was successful or failed, I rather think it failed because it doesn't list any md devices? > Creating root device Mounting root filesystem EXT3-fs: unable to read superblock
I pxe-booted in rescue mode. Interestingly, the rescue mode detects and mounts the RAID partitions just fine and mdadm sees them all as healthy. It mounts them under /tmp/md0 and /tmp/md1. Shouldn't the installed system be able to do the same, mount under /dev/md0 and /dev/md1 and then find root on /dev/md1 as told by grub.conf? Or could it be that the installed system also mounts them under /tmp?
I'm not sure how I can troubleshoot this.
Most likely different controller, or controller order recorded in the initrds of the drives. Rescue CD has it's own initrd, so it doesn't have this problem.
Try to either, 1) rearrange the drive order in the bios to match the old system, 2) find out what controller the new system is using and stick in a modprobe line for it while the drives are back in the old system and make an initrd, then move the drives over to the new system.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
Ross S. W. Walker wrote on Sun, 20 Jul 2008 15:14:25 -0400:
Most likely different controller,
Ah, well, right. I'm used from Windows that it doesn't matter much. ;-) The rescue system seems to use ata_piix. Unfortunately, I'm now getting a weird "Error: 0" with all of my last boots once it looks for the existing system, so I can't verify if I would get any further with ata_piix. I just start over now. Thanks for the hint, nevertheless.
Kai