Everything, Everything

2024: J F M A M J J A S O N
2023: J F M A M J J A S O N D
2022: J F M A M J J A S O N D
2021: J F M A M J J A S O N D
2020: J F M A M J J A S O N D
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
Oh, That's Why
Wednesday 12th December, 2012 19:12 Comments: 0
For the last few days a test server of mine has been playing up. The hardware is pretty much new (bought over the summer), so I was a bit surprised that it had played up/didn't always reboot properly. Copying files over the network was causing real problems. At first I thought it was a driver issue, especially as the problem got worse when upgrading the Atheros driver from 2.1.0.4 to 2.1.07 (and appeared to get better after upgrading to 2.1.0.12). But in reality, the Atheros NIC is attached to a Hyper-V virtual machine with a hard disk stored on the main disk; while file copying over the nice Intel NIC only involved the RAID volume. Because I built this test server over the summer, and because it doesn't do anything important, I didn't bother installing any hard disk monitoring tools. My bad. Especially when the disk has an uptime of over 4 years (it came from another array that I no longer use). It looks a little bit dead:

SMART data shows disk is at 1% health
© Robert Nicholls 2002-2024
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3