search

twobitcircus / rpi-build-and-boot

165 stars 44 forks source link

boot image not mounting #10

Closed lostinplace closed 9 years ago

lostinplace commented 9 years ago

vagrant provision yields the following error

TASK: [mount src="/vagrant/image.img" name="/opt/raspberrypi/boot" fstype="auto"  opts="loop,offset={{offset_boot}},noauto" state="mounted"] ***
failed: [default] => {"failed": true}
msg: Error mounting /opt/raspberrypi/boot: mount: you must specify the filesystem type

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
           to retry, use: --limit @/Users/cwheeler/playbook.retry

default                    : ok=13   changed=1    unreachable=0    failed=1

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
egradman commented 9 years ago

No, it's because you need to substitute an actual byte offset for "{{offset_boot}}"

On Wednesday, December 17, 2014, Chris Wheeler notifications@github.com wrote:

upon further investigation it's clear that the reason for this is that mount doesn't have a "fstype" parameter

— Reply to this email directly or view it on GitHub https://github.com/twobitcircus/rpi-build-and-boot/issues/10#issuecomment-67359723 .

Eric Gradman CTO & Mad Inventor P: 213-268-6253 | W: twobitcircus.com http://www.twobitcircus.com/ TW: @egradman http://www.twitter.com/egradman

TWO BIT CIRCUS Engineering Entertainment

Inventors | Developers | Performers

lostinplace commented 9 years ago

....oops.... this was because I had downloaded the wheezy image and left it compressed rather than unzipping it before the symlink

Thanks