Operating System - Linux
1828838 Members
2760 Online
109985 Solutions
New Discussion

Imaging a Itanium 2 system with RedHat AS3u4 and mkcdrec

 
marsohst
Occasional Contributor

Imaging a Itanium 2 system with RedHat AS3u4 and mkcdrec

I would like to use mkcdrec to create and restore an image of a Itanium 2 rx1600 system.
I can create an image but when I want to recover the system with the CDrec.iso file
I can't boot successfully to start the
recovery. Boot kernel complains about
missing modules sysfs and freesysfs at
modprobe.
Has anybody done a successful recovery with
mkcdrec on Itanium ? Or is there an alternative
imaging solution for Itanium 2 ?
3 REPLIES 3
Chakravarthi
Trusted Contributor

Re: Imaging a Itanium 2 system with RedHat AS3u4 and mkcdrec

hi,

if your source and destination machine hardware configuration is same then it should work, i had faced problem when the harddisk controller is different,
ex: on the source machine the HDD was on primary so the parition structure will be /dev/hda1 /dev/hda2 etc ...

but on my destination machine hard disk was on secondary so the config was /dev/hdc1 etc ..

i'm not sure this could be the reason , please check the configuration

regards
chakri
marsohst
Occasional Contributor

Re: Imaging a Itanium 2 system with RedHat AS3u4 and mkcdrec

chakri,

let me try to be more precise on the
problem I have. I have created an image
of my Itanium system with mkcdrec and this
works. I can create an CDrec.iso file
on my NFS server. I then try to boot the
same system with this image CD. During the
boot from the CD I get these problems.
Typically you boot from the CD and finally
get a Shell prompt. My boot process proceeds
beyond pivot_root and running init.
On the next line after Running init I get
modprobe: Can't locate module sysfs and freesysfs
Remounting root read write.
Then the system stops


Chakravarthi
Trusted Contributor

Re: Imaging a Itanium 2 system with RedHat AS3u4 and mkcdrec

sorry for the confusion,

after seeing your second reply i feel this is happening because of some unsupported hardware probe,

surely others will have more to add...