Avatar of ricjenkins
ricjenkins
Flag for United States of America asked on

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.
LinuxDellHardware

Avatar of undefined
Last Comment
ricjenkins

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Scott Silva

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
SOLUTION
noxcho

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
ricjenkins

ASKER
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.
noxcho

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.
Scott Silva

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.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
ricjenkins

ASKER
Thanks for the help! Sorry it took so long to close, but I went on vacation... Thanks, again!