Closed
Bug 615744
Opened 14 years ago
Closed 14 years ago
w32-ix-slave41 possible hard drive issue?
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 596366
People
(Reporter: catlee, Assigned: zandr)
References
Details
(Whiteboard: [badslave?][buildduty])
Maybe it has a slow disk? Needs some love in any case.
Reporter | ||
Comment 1•14 years ago
|
||
Disconnected it from the master. Looks like NTFS has indexing turned on, and none of the other tweaks here: https://wiki.mozilla.org/ReferencePlatforms/Win32#Add_drive_E
Reporter | ||
Comment 2•14 years ago
|
||
Disk reformatted, tweaks applied, and re-connected to buildbot-master1:8010.
Reporter | ||
Comment 3•14 years ago
|
||
It's done a full clone of m-c since reattaching, which took 38 minutes to complete vs. 18 minutes on ix-slave32. We should probably take this down to see if the hard drive is ok.
Comment 4•14 years ago
|
||
it's also failing make upload on shadow-central builds due to host key error.
Whiteboard: [badslave?] → [badslave?][buildduty]
Comment 5•14 years ago
|
||
http://tinderbox.mozilla.org/showlog.cgi?log=TraceMonkey/1291929389.1291934569.15182.gz is it doing a mochitest-other run with something stealing focus.
Comment 6•14 years ago
|
||
I logged onto it and didn't find any dialog or focus stealing but to be safe I've taken it offline for now. It also needs the host key error for shadow-central fixed.
Comment 7•14 years ago
|
||
Forwarding this to IT to look into the hard drive - see if it's one of the 'slow' ix machines? Also please re-image if the hard drive seems fine so we can try again with this one.
Assignee: nobody → server-ops
Component: Release Engineering → Server Operations
QA Contact: release → mrz
Summary: w32-ix-slave41 is failing a lot of jobs because of hg timing out → w32-ix-slave41 possible hard drive issue?
Updated•14 years ago
|
Assignee: server-ops → jdow
Updated•14 years ago
|
Assignee: jdow → zandr
Assignee | ||
Updated•14 years ago
|
Assignee: zandr → server-ops
Assignee | ||
Comment 8•14 years ago
|
||
Please don't assign bugs directly to me. Please assign them to the default for Server Operations. They'll get noticed sooner that way. Please do cc: me if you like.
Updated•14 years ago
|
Assignee: server-ops → zandr
Assignee | ||
Comment 9•14 years ago
|
||
Presumed drive failure. Imaging at 20MB/*minute* and falling.
Assignee | ||
Updated•14 years ago
|
Blocks: ix-drive-issues
Assignee | ||
Comment 10•14 years ago
|
||
root@sysresccd /root % hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: ST3250318AS Serial Number: 6VY6XTQ3 Firmware Revision: CC38 Transport: Serial Standards: Used: unknown (minor revision code 0x0029) Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 488397168 Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 238475 MBytes device size with M = 1000*1000: 250059 MBytes (250 GB) cache/buffer size = 8192 KBytes Nominal Media Rotation Rate: 7200 Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 254, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * DOWNLOAD_MICROCODE SET_MAX security extension * Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * WRITE_{DMA|MULTIPLE}_FUA_EXT * 64-bit World wide name Write-Read-Verify feature set * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Native Command Queueing (NCQ) * Phy event counters Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Long Sector Access (AC1) * SCT LBA Segment Access (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 40min for SECURITY ERASE UNIT. 40min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000c50027ecd6c7 NAA : 5 IEEE OUI : 000c50 Unique ID : 027ecd6c7 Checksum: correct root@sysresccd /root % hdparm -tT /dev/sda /dev/sda: Timing cached reads: 12796 MB in 2.00 seconds = 6411.91 MB/sec Timing buffered disk reads: 36 MB in 3.04 seconds = 11.83 MB/sec root@sysresccd /root % hdparm -tT /dev/sda /dev/sda: Timing cached reads: 2 MB in 2.19 seconds = 937.13 kB/sec Timing buffered disk reads: 54 MB in 3.01 seconds = 17.96 MB/sec root@sysresccd /root % hdparm -tT /dev/sda /dev/sda: Timing cached reads: 2 MB in 2.85 seconds = 718.25 kB/sec Timing buffered disk reads: 50 MB in 3.03 seconds = 16.47 MB/sec root@sysresccd /root % Note that with speed numbers like that, SMART is clean.
Assignee | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•