Closed
Bug 692749
Opened 14 years ago
Closed 14 years ago
sync14.db.scl2.svc: swap /dev/sdi
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Atoll, Assigned: jlaz)
Details
(Whiteboard: [resync of RAID1 devices underway, badblock passed, close after successful resync])
sdi failed during a resync, which locked up the entire SATA bus. removed sdi from boot/root. please swap.
started badblocks of sdi in root screen to see if we can repair it rather than swap it
Whiteboard: [badblocks of /dev/sdi underway]
| Assignee | ||
Comment 2•14 years ago
|
||
# badblocks -v -w /dev/sdi
Checking for bad blocks in read-write mode
From block 0 to 976762583
Testing with pattern 0xaa: done
Reading and comparing: done
Testing with pattern 0x55: done
Reading and comparing: done
Testing with pattern 0xff: done
Reading and comparing: done
Testing with pattern 0x00: done
Reading and comparing: done
Pass completed, 0 bad blocks found.
| Assignee | ||
Comment 3•14 years ago
|
||
Re-added /dev/sdi to both RAID1 arrays, resync in progress
Whiteboard: [badblocks of /dev/sdi underway] → [resync of RAID1 devices underway, badblock passed]
| Assignee | ||
Updated•14 years ago
|
Whiteboard: [resync of RAID1 devices underway, badblock passed] → [resync of RAID1 devices underway, badblock passed, close after successful resync]
| Assignee | ||
Comment 4•14 years ago
|
||
sync14 is now happy again.
04:17:11 < nagios-sjc1> sync14.db.scl2.svc:mdraid is OK: OK md125 status=[UUUUUUUUU]. md126 status=[UUU]. md127 status=[UUU].
Assignee: nobody → jlaz
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 5•14 years ago
|
||
Also put this back to production, woo!
Updated•10 years ago
|
Component: Operations: Hardware → Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•