Opened 9 years ago

Closed 9 years ago

Last modified 3 years ago

#4450 closed defect (fixed)

New Tor image won't boot

Reported by: runa Owned by: runa
Priority: Immediate Milestone:
Component: Archived/Tor Cloud Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


We are using our own script called [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".


Child Tickets

Change History (2)

comment:1 Changed 9 years ago by runa

Resolution: fixed
Status: newclosed

Turns out, cloudimg-rootfs was the correct filesystem label. I've updated this in the build script, and fixed some other bugs as well.

comment:2 Changed 3 years ago by teor

Severity: Normal

Set all tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.