Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to build - mksquashfs: Read failed because Invalid argument #17

Closed
mfrederickson opened this issue Dec 13, 2013 · 5 comments
Closed

Comments

@mfrederickson
Copy link

@mfrederickson mfrederickson commented Dec 13, 2013

I'm following your directions to do the build, using debian 7.2.0 i386. Using the master branch with no tweaks. When I get to the make_bootable... step, it gets to 5% and then mksquashfs spouts a lot of Read failed because Invalid argument errors...

@ghost ghost assigned mfrederickson Dec 13, 2013
@mfrederickson
Copy link
Author

@mfrederickson mfrederickson commented Dec 13, 2013

It appears that the chroot directory is in use by the dbus-daemon (as reported by lsof chroot) and therefore mksquashfs fails with the error mentioned above. If I reboot the machine before I run the make_bootable... script then it works just fine. If I just log out and back in, it is still being held by the dbus-daemon. If I run fuser -k chroot then it works fine without a reboot. Maybe we need to add that line to the make_bootable... script?

@augustf
Copy link

@augustf augustf commented Dec 21, 2013

I built a fresh image from the current source on Debian 7.2 (on VirtualBox) and can't reproduce this.

@mfrederickson
Copy link
Author

@mfrederickson mfrederickson commented Dec 23, 2013

Can someone else try this on a new debian 7.2 vm and let me know if it works for you? Otherwise I might need to bug @augustf for his vm settings and debian configuration.

@mfrederickson
Copy link
Author

@mfrederickson mfrederickson commented Jan 14, 2014

@augustf when you built it on Debian 7.2 was it a new install of Debian or an existing one? I did it on a new install of Debian 7.2. I can do a screencast of the whole process, but what's the point? Can we go ahead and add the fuser command since it alleviates the problem that I'm seeing?

@augustf
Copy link

@augustf augustf commented Jan 14, 2014

Sure-go ahead and add it - though I'm not really sure how or why it's helping. I'll be building the image again sometime this week, an as long as it doesn't break that, it should be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants