crontab has been corrupted? @^@^@^@^@^ after clone

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












So I have created the following cronjob to run after the VM clones first boot



@reboot sleep 30 && sudo bash /root/first.sh
@reboot sleep 30 && sudo bash /root/first2.sh


However after I clone the VM and boot it back up the scripts don't run and crontab -e shows the following



enter image description here



I am doing the same process on CentOS 6/Ubuntu 14.04 / Ubuntu 16.04 with no problem. Only CentOS 7 is causing an issue.







share|improve this question



















  • yes, those are probably NUL characters. as to how they got there, we'd need to know a lot more about your process
    – thrig
    May 28 at 2:23










  • The scripts? If so I don't think it's them. The screenshot taken was within the first 30 seconds of boot.
    – masterq
    May 28 at 3:02










  • There's a whole lot of missing information that this question assumes that we telepathically have, starting with "the" VM clone. There's no information about how this clone operation was done, not even how the machine was shut down in order to clone it.
    – JdeBP
    May 28 at 3:44










  • NUL characters. So the filesystem metadata is there, but the actual data is not. Are you cloning filesystems of an active VM without at least a minimal "flush buffers and quiesce" procedure first? Note that CentOS 7 has XFS as a default filesystem type, unlike CentOS 6 and probably the Ubuntus: your cloning procedure may need some tweaking for it.
    – telcoM
    May 28 at 5:03














up vote
0
down vote

favorite












So I have created the following cronjob to run after the VM clones first boot



@reboot sleep 30 && sudo bash /root/first.sh
@reboot sleep 30 && sudo bash /root/first2.sh


However after I clone the VM and boot it back up the scripts don't run and crontab -e shows the following



enter image description here



I am doing the same process on CentOS 6/Ubuntu 14.04 / Ubuntu 16.04 with no problem. Only CentOS 7 is causing an issue.







share|improve this question



















  • yes, those are probably NUL characters. as to how they got there, we'd need to know a lot more about your process
    – thrig
    May 28 at 2:23










  • The scripts? If so I don't think it's them. The screenshot taken was within the first 30 seconds of boot.
    – masterq
    May 28 at 3:02










  • There's a whole lot of missing information that this question assumes that we telepathically have, starting with "the" VM clone. There's no information about how this clone operation was done, not even how the machine was shut down in order to clone it.
    – JdeBP
    May 28 at 3:44










  • NUL characters. So the filesystem metadata is there, but the actual data is not. Are you cloning filesystems of an active VM without at least a minimal "flush buffers and quiesce" procedure first? Note that CentOS 7 has XFS as a default filesystem type, unlike CentOS 6 and probably the Ubuntus: your cloning procedure may need some tweaking for it.
    – telcoM
    May 28 at 5:03












up vote
0
down vote

favorite









up vote
0
down vote

favorite











So I have created the following cronjob to run after the VM clones first boot



@reboot sleep 30 && sudo bash /root/first.sh
@reboot sleep 30 && sudo bash /root/first2.sh


However after I clone the VM and boot it back up the scripts don't run and crontab -e shows the following



enter image description here



I am doing the same process on CentOS 6/Ubuntu 14.04 / Ubuntu 16.04 with no problem. Only CentOS 7 is causing an issue.







share|improve this question











So I have created the following cronjob to run after the VM clones first boot



@reboot sleep 30 && sudo bash /root/first.sh
@reboot sleep 30 && sudo bash /root/first2.sh


However after I clone the VM and boot it back up the scripts don't run and crontab -e shows the following



enter image description here



I am doing the same process on CentOS 6/Ubuntu 14.04 / Ubuntu 16.04 with no problem. Only CentOS 7 is causing an issue.









share|improve this question










share|improve this question




share|improve this question









asked May 28 at 2:05









masterq

165




165











  • yes, those are probably NUL characters. as to how they got there, we'd need to know a lot more about your process
    – thrig
    May 28 at 2:23










  • The scripts? If so I don't think it's them. The screenshot taken was within the first 30 seconds of boot.
    – masterq
    May 28 at 3:02










  • There's a whole lot of missing information that this question assumes that we telepathically have, starting with "the" VM clone. There's no information about how this clone operation was done, not even how the machine was shut down in order to clone it.
    – JdeBP
    May 28 at 3:44










  • NUL characters. So the filesystem metadata is there, but the actual data is not. Are you cloning filesystems of an active VM without at least a minimal "flush buffers and quiesce" procedure first? Note that CentOS 7 has XFS as a default filesystem type, unlike CentOS 6 and probably the Ubuntus: your cloning procedure may need some tweaking for it.
    – telcoM
    May 28 at 5:03
















  • yes, those are probably NUL characters. as to how they got there, we'd need to know a lot more about your process
    – thrig
    May 28 at 2:23










  • The scripts? If so I don't think it's them. The screenshot taken was within the first 30 seconds of boot.
    – masterq
    May 28 at 3:02










  • There's a whole lot of missing information that this question assumes that we telepathically have, starting with "the" VM clone. There's no information about how this clone operation was done, not even how the machine was shut down in order to clone it.
    – JdeBP
    May 28 at 3:44










  • NUL characters. So the filesystem metadata is there, but the actual data is not. Are you cloning filesystems of an active VM without at least a minimal "flush buffers and quiesce" procedure first? Note that CentOS 7 has XFS as a default filesystem type, unlike CentOS 6 and probably the Ubuntus: your cloning procedure may need some tweaking for it.
    – telcoM
    May 28 at 5:03















yes, those are probably NUL characters. as to how they got there, we'd need to know a lot more about your process
– thrig
May 28 at 2:23




yes, those are probably NUL characters. as to how they got there, we'd need to know a lot more about your process
– thrig
May 28 at 2:23












The scripts? If so I don't think it's them. The screenshot taken was within the first 30 seconds of boot.
– masterq
May 28 at 3:02




The scripts? If so I don't think it's them. The screenshot taken was within the first 30 seconds of boot.
– masterq
May 28 at 3:02












There's a whole lot of missing information that this question assumes that we telepathically have, starting with "the" VM clone. There's no information about how this clone operation was done, not even how the machine was shut down in order to clone it.
– JdeBP
May 28 at 3:44




There's a whole lot of missing information that this question assumes that we telepathically have, starting with "the" VM clone. There's no information about how this clone operation was done, not even how the machine was shut down in order to clone it.
– JdeBP
May 28 at 3:44












NUL characters. So the filesystem metadata is there, but the actual data is not. Are you cloning filesystems of an active VM without at least a minimal "flush buffers and quiesce" procedure first? Note that CentOS 7 has XFS as a default filesystem type, unlike CentOS 6 and probably the Ubuntus: your cloning procedure may need some tweaking for it.
– telcoM
May 28 at 5:03




NUL characters. So the filesystem metadata is there, but the actual data is not. Are you cloning filesystems of an active VM without at least a minimal "flush buffers and quiesce" procedure first? Note that CentOS 7 has XFS as a default filesystem type, unlike CentOS 6 and probably the Ubuntus: your cloning procedure may need some tweaking for it.
– telcoM
May 28 at 5:03















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446379%2fcrontab-has-been-corrupted-after-clone%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446379%2fcrontab-has-been-corrupted-after-clone%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?