Timecounter "i8254" frequency 1193182 Hz quality 0Įvent timer "i8254" frequency 1193182 Hz quality 100Įvent timer "RTC" frequency 32768 Hz quality 0 WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.Īcpi0: reservation of 0, a0000 (3) failedĪcpi0: reservation of 100000, bff00000 (3) failed TSC: P-state invariant, performance statisticsįreeBSD/SMP: Multiprocessor System Detected: 16 CPUsįreeBSD/SMP: 2 package(s) x 4 core(s) x 2 SMT threads Origin = "GenuineIntel" Id = 0x106a5 Family = 0圆 Model = 0x1a Stepping = 5 All rights reserved.įreeBSD is a registered trademark of The FreeBSD Foundation.įreeBSD 9.2-RELEASE-p10 #0 r262572+4fb5adc: Wed Aug 6 17:07:16 PDT amd64 The Regents of the University of California. Given that the errors on the disk appear to be minimal (at the moment) I’m moving cautiously regarding changes.Ĭopyright (c) 1992-2013 The FreeBSD Project.Ĭopyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 I have completed a very simple “backup” of data (duplicated the file sets in their most critical shares to a separate and now off-line disk, so losing the file system would not result in huge data loss – but it would seriously impact productivity until I get things back up. The system in question contains ALL of the businesses critical data (including years of work product).
I’ve purchased a replacement disk as a precaution. The disk in question reports 46 unresolved errors.
The system in question is an HP DL180 G6 with 12 X 2TB SAS disks. I finish the scrub and get the same message.ġ) I am unable to offline the offending disk to replace it…Ģ) I suspect that this may be a function of how the file system was mapped to the disks and that the disks appear to be set up as RAID 0 devices as opposed to JBOD – but I’m not sure. Numerous sources suggest running a scrub and retrying – which I have done without any change in behavior (I’ve also scheduled a weekly scrub as there was nothing of that nature in place).
0 kommentar(er)
