Closed Bug 542876 Opened 15 years ago Closed 15 years ago

n810 maintenance 20100128

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
ARM
Maemo
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mozilla, Assigned: mozilla)

Details

maemo-n810-06: ls: twistd.pid: Input/output error (assuming fs corruption) maemo-n810-10: fs corruption maemo-n810-11: fs corruption maemo-n810-12: fs corruption maemo-n810-18: down maemo-n810-20: down maemo-n810-22: fs corruption maemo-n810-26: fs corruption maemo-n810-31: down maemo-n810-33: down maemo-n810-37: down maemo-n810-40: not connecting to buildbot (human error) maemo-n810-43: fs corruption maemo-n810-44: down maemo-n810-47: fs corruption maemo-n810-48: fs corruption maemo-n810-51: fs corruption maemo-n810-54: down maemo-n810-55: fs corruption maemo-n810-57: fs corruption maemo-n810-60: fs corruption maemo-n810-62: fs corruption maemo-n810-63: down maemo-n810-64: fs corruption maemo-n810-67: not connecting to buildbot (human error) maemo-n810-71: down maemo-n810-74: fs corruption maemo-n810-77: down The down devices can sometimes be reconnected, but tend to be broken in some way. Enough that reimaging is generally helpful. The devices that aren't connecting to buildbot both had hostname issues... adding to monitoring in bug 510952 (not done yet). The filesystem corruption should hopefully be solved, or at least mitigated, by bug 525937 (for all newly imaged n810s). 28 devices that need help; time to spend some time on this.
All back up except 20, 67, 71 which have booting issues. jhford suspects the sd cards need repartitioning.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.