search

drinkcat / chroagh

Chromium OS Archlinux Chroot Environment
BSD 3-Clause "New" or "Revised" License
241 stars 27 forks source link

error cleanup is handled poorly #16

Closed rminnich closed 11 years ago

rminnich commented 11 years ago

error: failed to commit transaction (unexpected error) Errors occurred, no packages were upgraded. ==> ERROR: Failed to install packages to new root umount: /newroot/tmp: umount failed: No such file or directory umount: /newroot/run: umount failed: No such file or directory umount: /newroot/dev/shm: umount failed: No such file or directory umount: /newroot/dev/pts: umount failed: No such file or directory umount: /newroot/dev: umount failed: No such file or directory umount: /newroot/sys: umount failed: No such file or directory umount: /newroot/proc: umount failed: No such file or directory umount: /newroot: umount failed: No such file or directory umount2: Device or resource busy umount: /tmp/main.sh.z2F: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) umount2: Device or resource busy

not a clean exit.

drinkcat commented 11 years ago

Indeed... Some of these errors might be harmless though (most of the umount ones I think, there is a bug in pacstrap), but some should not happen (especially umount: /tmp/main.sh.z2F: device is busy.), I'll look into it.

But what I'm more concerned about is what happens just before error: failed to commit transaction (unexpected error), can you paste the whole log? (or at least 10 lines before that...)

Which Chromebook are you using? And thanks for trying this out!

drinkcat commented 11 years ago

New boostrap code does not use pacstrap anymore, fixing this issue.