After today's downtime ended, this VM was throwing errors on powerup, and failing to boot. Phong was able to manually start running fsck; getting lots of errors: ... Unattached inode nnnnnn. Connect to /lost+found? ... I'm still working through these inode errors.
While filing bug, I finally also made it past those questions boot sequence. Now have buildbot running *something* and see it reporting on tinderbox. Lets watch this overnight.
Assignee: nobody → joduinn
Severity: normal → major
still working like a charm.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
OS: Mac OS X → Linux
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.