Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.
Post Clonezilla image restore issue
We have an old Dell PE860 server that has hosted a small portion or our website for years. It's running CentOS 2.6.18 (yes it's that old) & Apache. It had a hardware controlled RAID1 setup, until a several weeks ago, that failed. To get us back up and limping along, I just unplugged & bypassed the RAID controller and changed the BIOS to where it just basically thinks it's a single drive PC: boots straight to the single drive. Due to the advanced age of the server, we purchased a new Dell PE R330, also with hardware RAID1, and now we want to move everything from the old box to the new one.
I came in over the weekend and took an image of the old setup, intending to push it to the new server. I thought I could do this since it's a hardware RAID setup, and all it should see is the one virtual drive... Everything seemed to go fine, as it did the restore image process with no errors, however upon starting the new server, after flashing the CentOS splash screen, I get the following as my last few in the boot sequence:
....
Reading all physical volumes... This may take a while...
No volume groups found
Volume group "VolGroup00" not found
Trying to resume from /dev/VolGroup00/LogVol01
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount could not find filesystem "/dev/root"
...
Kernel panic - not syncing: Attemted to kill init!
Any ideas on what could cause all of this, since this should have been an image of a working setup?? Thanks.
I came in over the weekend and took an image of the old setup, intending to push it to the new server. I thought I could do this since it's a hardware RAID setup, and all it should see is the one virtual drive... Everything seemed to go fine, as it did the restore image process with no errors, however upon starting the new server, after flashing the CentOS splash screen, I get the following as my last few in the boot sequence:
....
Reading all physical volumes... This may take a while...
No volume groups found
Volume group "VolGroup00" not found
Trying to resume from /dev/VolGroup00/LogVol01
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount could not find filesystem "/dev/root"
...
Kernel panic - not syncing: Attemted to kill init!
Any ideas on what could cause all of this, since this should have been an image of a working setup?? Thanks.
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
The kernel of CentOS does not have the necessary driver for your new RAID conroller. You have to find a similar RIAD controller and restore over it.
But if it's hardware controlled RAID, via a dedicated RAID controller, and NOT software RAID, why would the OS need RAID drivers? It automatically sees it as just a single 500GB drive up on booting. I would understand it needing drivers if it was a software based RAID controlled by the OS, but that is not the case: the OS has no clue it's a RAID array.
You are mixing hardware and software RAIDs. Software RAID is done with OS tools. Thus it only emulates the RAID on software (OS) level. It does not need some driver then to support the RAID controller.
In case of hardware RAID controller the OS needs first of all a proper driver for this RAID controller which helps reading the configurations done on RAID level.
Software RAID done on higher level and hardware RAID is done on deeper level - just to make it simple.
Hardware RAID controller almost always requires a driver for OS if it is not already includied in kernel compilation.
In case of hardware RAID controller the OS needs first of all a proper driver for this RAID controller which helps reading the configurations done on RAID level.
Software RAID done on higher level and hardware RAID is done on deeper level - just to make it simple.
Hardware RAID controller almost always requires a driver for OS if it is not already includied in kernel compilation.
You "see" the drives in the base because they are accessible by int13 dos type calls... Those calls are too slow for modern OS's so they have drivers to allow direct memory access.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
Most likely the old image does not have drivers for the new raid controller. You would have to somehow get the drivers for the new raid into the old system before you clone it...
Or find a way to clone it independent of controllers with some sort of bootable rescue disks that have drivers for both raid controllers... Then you could basically clone it across the wire with tar.