Hi Rick, No issue, I was only looking for a direction to work on rather than someone give me a direct detailed approach. I was hoping there was a document somewhere that may relate to this problem that I could read. I did not detail the items involved because I had suspected it would a general issue where if anyone had upgraded from an IDE to a RAID they might have found a cure and pointed me to the page/doc. So more details... 0. Adaptec ASR-2405 ROHS RAID controller also tried Adaptec 1210A and 2420A 1. 250 GB Seagate original Drive SATA 2. Idenitcal pair of WD Black 500GB ES SATA drives (Both new) 3. Cloned using Terabyte for Linux from Terabyte Unlimited in the USA. 4. Resulting text on screen before "Kernel panic" Waiting for driver initialisation. Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group :VolGroup00" not found Trying to resume device (/dev/VolGroup00/LogVol01) 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 Switching to new root and running init. unmounting old /dev/ umounting old /proc umounting old /sys switchroot : mount failed: no such file or directory Kernel panic - not syncing: Attempted to kill init! Not trying to be facetious, but is this enough? If not, what else would you like? Thanks again. best wishes Tony White On 26/10/2013 15:54, Rick Moen wrote:
Quoting Tony White (tony@ycs.com.au):
Hello all, I am hoping someone has done this before as I am unable to locate anything on the web to help me. I have a drive that has been cloned to a RAID controller but when it boots it only gets to to "Kernel Panic". The only reason I can see is the RAID driver is not loading. Can someone tell me how/where I can make this change without having to do a full reinstall please? Not a complaint, but you aren't giving people on the mailing list much to work with. E.g., you don't detail what 'the RAID driver is not loading' means. What is it that you see happening? Moreover, what driver? What does 'cloned to a RAID controller' mean? What is 'this change'?
Here's a suggestion: Download and burn to a CD some current, recent release of a live-CD distro with very good hardware support and ability to autoprobe hardware. I personally am fond of Aptosid for such purposes. Boot it up. Assuming it doesn't kernel panic and fail to boot, have a (selective[1]) look at the details of 'dmesg | less' to observe the kernel's hardware detection and loading of driver modules during bootup, do 'lsmod' to see what kernel modules are in the running kernel after startup, and do 'lspci' to see what chipsets are present.
Perhaps some clues will stand out concerning your mass-storage subsystem. You can also (carefully) use tools like fdisk or parted to examine your filesystem partitioning.
You didn't really address what if anything has changed on this system, lately (that you're aware of). (It's possible your wording about a drive having been 'cloned to a RAID controller' refers to a recent change. If you're aware of something that's been changed immediately before the pattern of kernel panics upon startup, that would be a logical place to look.
If you're not aware of anything having changed immediately before the problem arose, be aware that there still might have been relevant hardware changes in the form of either failing hardware (failing hard drive or failing HBA) or loose cabling or something like that.
_______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main