Been Googling/searching around for an answer to this question to no avail...
We use Clonezilla to image our workstations/servers.
Recently, we had been using CentOS 6.0 until some unforseen issues with our storage system... After deploying my image across most of the organization, I've had to roll back... sigh.
Using the same system I had to build my base image for 6.0, I built a CentOS 5.7 x86_64 image from scratch to be used universally across all systems. My source system was a Dell desktop with a simple 80GB hard drive.
I can deploy this image just fine on any desktop or server that doesn't have a hardware RAID.
However, when I tried to deploy it on a RAID1 and RAID5, I get this annoying error... see attached.
My initial searches directed me here: http://www.xssist.com/blog/
However, I didn't try it as it doesn't seem like something I should have to/want to do. I would prefer not to reconfigure the kernel on each machine as I deploy it AND reconfigure it after each kernel update.
I ended up building my image from scratch on a RAID5 configured server and grabbing it. I then proceeded to try to drop it on a RAID1/workstation, and it fails in similar fashion.
Some simple things I've tried doing to troubleshoot the issue:
Tried vanilla install w/o updates
Tried to rename volumes are /dev/sda# instead of LABEL=X (got this idea from seeing the fstab on centos 6)
Tried vanilla install w/LVM partition
Tried vanilla install w/2 EXT3 partitions and no swap space
Tried regular version of Clonezilla (usually use the alternative version)
Tried Symantec Ghost, fails because of RAID
Tried full nutbar install of all features in installer
Compared /boot/grub/grub.conf between the server and desktop, they are exactly the same
I'm quite certain it's the hardware RAID. It's disheartening since CentOS 6.X works just fine with a similarly simple setup. Is there something I can do or am missing here in the OS setup?
I know we have had a working Clonezilla image for CentOS 5.X in the past built by our ex-Linux Admin, but he and it are gone. His image just worked and even after updates. I'm quite certain he didn't have to mess with the kernel's config.
Thanks in advance!