Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #4450

Closed
Open
Created Nov 11, 2011 by Runa Sandvik@runa

New Tor image won't boot

We are using our own script called build.sh 1 to re-bundle the Ubuntu AMI with Tor and some other packages.

Building and publishing a Tor image isn't a problem, but an EC2 instance running the Tor image will fail to boot. It seems like the Tor image is given the wrong filesystem label.

When trying to boot, the system complains that it can't find the root device and then drops to a busybox shell. The filesystem label it should have is "uec-rootfs". The filesystem label it gets when we re-bundle it is "cloudimg-rootfs".

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking