Closed Bug 692749 Opened 14 years ago Closed 14 years ago

sync14.db.scl2.svc: swap /dev/sdi

Categories

(Cloud Services :: Operations: Miscellaneous, task)

x86
macOS
task
Not set
normal

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]
# 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.
Re-added /dev/sdi to both RAID1 arrays, resync in progress
Whiteboard: [badblocks of /dev/sdi underway] → [resync of RAID1 devices underway, badblock passed]
Whiteboard: [resync of RAID1 devices underway, badblock passed] → [resync of RAID1 devices underway, badblock passed, close after successful resync]
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
Also put this back to production, woo!
Component: Operations: Hardware → Operations
You need to log in before you can comment on or make changes to this bug.