I'm running Clonezilla 3.1.2-9 making an image of a Fedora 19 load on a a machine with a J1900 processor. Prior to making an image I have network and can ping the machine. After the backup I can no longer ping the machine. If I restore the image I still can not ping the machine. I have an IP address, Gateway and DNS. I can't ping anything on the network from the machine. It appears to be a Gateway issue. My reason for this assumption is before backing up the machine my default Gateway actually shows the name of my router. After the backup and restore to the same machine my default Gateway is the IP address not the name. All other times when the network is working I see the name of the router and not the IP address. Any suggestions are appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's weird. Clonezilla just deals with the file system (blocks level) for you.
One possibility is maybe the firmware is buggy, and it was triggered by the Clonezilla live OS...
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running Clonezilla 3.1.2-9 making an image of a Fedora 19 load on a a machine with a J1900 processor. Prior to making an image I have network and can ping the machine. After the backup I can no longer ping the machine. If I restore the image I still can not ping the machine. I have an IP address, Gateway and DNS. I can't ping anything on the network from the machine. It appears to be a Gateway issue. My reason for this assumption is before backing up the machine my default Gateway actually shows the name of my router. After the backup and restore to the same machine my default Gateway is the IP address not the name. All other times when the network is working I see the name of the router and not the IP address. Any suggestions are appreciated.
That's weird. Clonezilla just deals with the file system (blocks level) for you.
One possibility is maybe the firmware is buggy, and it was triggered by the Clonezilla live OS...
Steven