Image creation failed

[john.ou...@gmail.com]

I got the following error output when trying to create an image; can anyone tell me what it means (and what I need to do to fix it)?

About to: '/usr/testbed/bin/sshtb -n -o ConnectTimeout=5 -host er102 /usr/local/bin/imagezip -i -F 0 -s 0 /dev/nvd0'
About to: '/usr/testbed/bin/sshtb -n -o ConnectTimeout=5 -host er102 df -k /dev/nvd0'
Restarting dhcpd on subboss subboss2
reboot (er102): Attempting to reboot ...
Emulab scheduling tbprepare to run via systemd.
reboot (er102): Successful!
reboot: Done. There were 0 failures.
   er102
Waiting up to 360 seconds for nodes to come up.
All nodes are up.
About to: '/usr/testbed/bin/sshtb -n -o ConnectTimeout=5 -host er102 /usr/local/bin/imagezip -h'
About to: '/usr/testbed/bin/sshtb -n -host er102 /usr/local/bin/create-versioned-image METHOD=frisbee SERVER=128.110.156.34 IMAGENAME=/proj/homa-PG0/images/homa6178/homa6178.ndz:8.tmp DISK=/dev/nvd0 IZOPTS=N,B=3' as uid 0
er102: started image capture for '/proj/homa-PG0/images/homa6178/homa6178.ndz:8.tmp', waiting up to 120 minutes total or 8 minutes idle.
/usr/local/bin/imagezip: No GPT or MBR partition table found!
* * * Aborting * * *
Upload from stdin, waiting for data availability...
...data ready, continuing.
/proj/homa-PG0/images/homa6178/homa6178.ndz:8.tmp: upload to 128.110.156.34:21780 from -
/proj/homa-PG0/images/homa6178/homa6178.ndz:8.tmp: upload completed after 0 bytes in 0.000 seconds
*** Failed to create image!
    command:   '(  /usr/local/bin/imagezip -N -B 3 /dev/nvme0n1 - || echo $? > /local/imagezip.stat ) | /usr/local/bin/frisupload -S 128.110.156.34 -F /proj/homa-PG0/images/homa6178/homa6178.ndz:8.tmp - '
    status:    0x0000
    izstatus:  0x0001
Image creation failed, status=256
Restarting dhcpd on subboss subboss2
Restored startup cmd from virt_nodes for er102
reboot (er102): Attempting to reboot ...
reboot (er102): Successful!
reboot: Done. There were 0 failures.
   er102
FAILED: Returned error code 1 generating image ...

[Mike Hibler]

Linux naming of NVMe devices is non-deterministic and because of that, we added
a script to help identify the drive we are using as the boot disk. But that
script was missing from the MFS that captures images and it was misidentifying
the boot disk, hence the "No GPT or MBR partition table found!"

I have added that script to the MFS.

> --
> You received this message because you are subscribed to the Google Groups
> "cloudlab-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to cloudlab-user...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/cloudlab-users/
> 1bd83b31-4ea5-4e14-a338-544fd69a7a71n%40googlegroups.com.

[John Ousterhout]

Thanks.

-John-

To view this discussion visit https://groups.google.com/d/msgid/cloudlab-users/apRN_LJIttkYPNUb%40emulab.net.