Disk Kernell Latency

Ive been trying to understand DiskKernellLatency.
We have a new configuration with 10 hosts, 128GB of RAM each, two 8 core CPUS each.
We have >100 VMs running on them.
CPUs never go above 30%
Memory on each host is about 80% utilized
We are connected from the hosts to an 8GB fiber switch that is also connected to the SANS.
Ive run ESXTOP a few times - HBAs are 0
I looked at the fiber switches yesterday and the channels are all showing < 1% utilization with total throughput of < 100MB/s
Looking at the SANS write latency is almost 0ms
read latency fluctuates between 1ms and 40-50ms with bursts at 150ms that are never really sustained.
diskkernellLatency however is a constant 46ms to 56ms.
I have PRTG running and its taking a reading every 5 min. For the last 576 values, averages are:
CPU - 24%, Disk Read 16Mbits/s, Disk write 25Mbit/s, datastore Read latency, 1.9ms, network received 23, 000 kbits/s, disk device latency 2 ms, memory swap 0Mbytes, disk.kernellLatency 49Msec
Everything Ive read says disk.kernellLatency should be 1-2ms and never higher.
How can I figure out what is causing this?
Our SAN has 34 7200rpm drives configured RAID 10 and I don't see a lot of data passing from the SANS - the calculations we did showed we should have enough IOPS.
Thanks,
Steve

Hello,
at first: PRTG is nor very useful for ESXi performance troubleshooting...
I checked your ESXTOP output.
- CPU and Network looks OK
- Memory doesn’t look good
-> do you have enabled NUMA optimization in BIOS? Or do you have AMD CPU's?
- Storage looks strange...
-> I think a few more detailer are helpful:
- SAN HBA Model?
- SAN HBA Firmware Version?
- SAN HBA Driver Version?
- Zoning is ok?
- Which array are using?
- FW or Software Version of the Array?
- It looks like you are utilizing only one HBA
- Which path policy are you using?
There are some Device latency Peaks under load. But that’s ok when you have SATA / NLSAS Disks…
The high Kernel and Queue Latency is strange. Especially because no IO is queued at this moment and no IO is processed on this LUN.
In this special situation is can be a measurement failure…

Similar Messages

DRDY ERR I/O Errors only occur with KDE. HDD or kernel related?

This isn't too urgent since I'm not having this problem anymore, but I would like to know what caused it in the first place.
A few months ago, I think it was in May, when I was booting into KDE, the desktop wouldnt load. After logging in it goes to a black screen with a cursor. I check my tty consoles and they are all spammed with DRDY and I/O errors.
Today my log files don't go back to that time, but I apparantly wrote them down:
[timestamp] ata1.00: irq_stat 0x40000001
[timestamp] ata1: SError: { CommWake }
[timestamp] ata1.00: failed command: READ FPDMA QUEUED
[timestamp] ata1.00: cmd 60/08:00:79:c5:e9/00:00:38:00:00/40 tag 0 ncq 4096 in
[timestamp] res 41/40:08:7c:c5:e9/00:00:38:00:00/60 Emast 0x409 (media error) <F>
[timestamp] ata1.00: status {DRDY ERR }
[timestamp] error: { UNC }
[timestamp] end_request: I/O error, dev sda, sector 9540445540
It repeats this over and over again on all 7 consoles. I believe the hex numbers and sector # change slightly each time it repeats.
I restart the computer and it does the same thing. Then one day it booted into the desktop after sitting at a black screen with a cursor for 10 minutes.
When I saw Media and I/O error, I immediately thought it was my hard drive failing (which sucks because I had this computer for less than a year). But the weird thing was that once it finally boots into a desktop enviroment, everything works fine. I can access any file without any error, I can boot into my windows partition perfectly, and everything runs as fast as it did before. I ran fschk and chksdk several times, I passed with 0 bad sectors. SMART tests come out perfect.
The strangest thing about this is that the errors only come about when I boot into KDE. If I boot into any other enviroment I do not get these errors. Completely reinstalling KDE did not fix it. I don't remember updating or changing anything before these errors started appearing. I did do a full system update once I was actually able to get into my KDE session, but it didnt do anything. I eventually solved it by using another desktop enviroment, which was xfice at the time but now its cinnamon. I never got those errors ever since.
I posted something similar to this on KDE's forum, and no one could figure it out. One of the admins told me its very unusual that something like this would happen only with KDE, and the READ FPDMA/DRDY ERRs "are sourced from the kernel - and are disk/kernel related according to https://bugs.launchpad.net/ubuntu/+sour ... bug/550559."
As of now I can install KDE perfectly without any sort of issue, but I know several kernel updates occured since then. So could this be a issue with the kernel? Or is my hdd really starting to fail? I backed up the computer already, but I record music constantly and don't "aggresively" run backups (i.e not every day, but every month or so). Should I start doing so?
Thanks

68flag wrote:
@lspci
Those links you sent me were VERY helpful! I used the online SMART test using SpeedFan on windows; I never thought of using smartctl --all /dev/sda.
Heres what it gave me:
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.4.9-1-ARCH] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MK..76GSX
Device Model: TOSHIBA MK5076GSX
Serial Number: 91OHT43CT
LU WWN Device Id: 5 000039 3818077b6
Firmware Version: GS002D
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Tue Aug 28 00:22:51 2012 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 163) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 128
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1756
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
9 Power_On_Minutes 0x0032 092 092 000 Old_age Always - 3277h+14m
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1072
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 2191
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 133
193 Load_Cycle_Count 0x0032 094 094 000 Old_age Always - 61036
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 45 (Min/Max 15/53)
199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 25758112
200 Multi_Zone_Error_Rate 0x0032 100 100 000 Old_age Always - 56684070
240 Head_Flying_Hours 0x0032 094 094 000 Old_age Always - 153507
241 Total_LBAs_Written 0x0032 100 100 000 Old_age Always - 5471510246
242 Total_LBAs_Read 0x0032 100 100 000 Old_age Always - 7806093714
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 558 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 558 occurred at disk power-on lifetime: 2148 hours (89 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 7c c5 e9 68 Error: UNC at LBA = 0x08e9c57c = 149538172
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 79 c5 e9 40 00 00:06:08.673 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:06:08.673 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:06:08.673 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:06:08.672 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:06:08.672 SET FEATURES [Set transfer mode]
Error 557 occurred at disk power-on lifetime: 2148 hours (89 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 7c c5 e9 68 Error: UNC at LBA = 0x08e9c57c = 149538172
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 79 c5 e9 40 00 00:06:04.673 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:06:04.673 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:06:04.673 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:06:04.672 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:06:04.672 SET FEATURES [Set transfer mode]
Error 556 occurred at disk power-on lifetime: 2148 hours (89 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 7c c5 e9 68 Error: UNC at LBA = 0x08e9c57c = 149538172
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 79 c5 e9 40 00 00:06:00.673 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:06:00.673 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:06:00.673 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:06:00.672 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:06:00.672 SET FEATURES [Set transfer mode]
Error 555 occurred at disk power-on lifetime: 2148 hours (89 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 7c c5 e9 68 Error: UNC at LBA = 0x08e9c57c = 149538172
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 79 c5 e9 40 00 00:05:56.673 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:05:56.673 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:05:56.672 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:05:56.672 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:05:56.672 SET FEATURES [Set transfer mode]
Error 554 occurred at disk power-on lifetime: 2148 hours (89 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 7c c5 e9 68 Error: WP at LBA = 0x08e9c57c = 149538172
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
61 08 18 d1 d8 e7 40 00 00:05:52.624 WRITE FPDMA QUEUED
61 08 10 89 d8 e7 40 00 00:05:52.624 WRITE FPDMA QUEUED
61 08 40 51 d8 e7 40 00 00:05:52.624 WRITE FPDMA QUEUED
61 10 38 01 d8 e7 40 00 00:05:52.623 WRITE FPDMA QUEUED
61 08 30 e1 d7 e7 40 00 00:05:52.623 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 2320 -
# 2 Extended offline Aborted by host 90% 2075 -
# 3 Short offline Completed without error 00% 1900 -
# 4 Short offline Completed without error 00% 1574 -
# 5 Short offline Completed without error 00% 1415 -
# 6 Short offline Completed without error 00% 1081 -
# 7 Short offline Completed without error 00% 637 -
# 8 Short offline Completed without error 00% 248 -
# 9 Short offline Completed without error 00% 0 -
#10 Short offline Completed without error 00% 0 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
The READ FPDMA QUEUED errors come up in SMART's log, so those problems I had have to be HDD related, not kernel. Other than that I really don't know what I'm looking at here. I don't like the numbers for UDMA_CRC_Error Count or Multi Zone Error rate, but I don't know what those mean. Until someone explains to me what I'm dealing with here, I'm going to assume it is an HDD problem and start furiously backing stuff up.
bart_b wrote:Some of these issues are related to interference of the Spread Spectrum Clocking (SSC), SSC is a way of eliminating interference. Now some BIOSes let you tweak this setting and some harddisks like WD have a jumper setting to disable/enable the spread spectrum frequency. But since it is more of a RF issue rearranging your sata cables might help or replace them with a better quality cable could do the trick to reduce interference. If you have overclocked your PC, try to re-tweak it to a more sane level.
I forgot to mention that my computer is a Dell Inspiron n5110. Its a piece of garbage, its the only computer I am aware off that has programs that PREVENT you from connecting to the internet when you don't buy their stupid extended warranty. I'm saving up for a thinkpad t420 but thats another story
Woah. Radio signals interfering with data passing through the SATA cables? I've had poorly sheilded guitar cables that pick up odd AM stations, but SATA cables? Thats bizzare. I don't own a PC yet, but I'm going to build one for my brothers once the parts come in, and I'll definitely make a note of that. I didn't even know you could overclock a CPU to the point where it GENERATES RF signals powerful enough to interfere with the HDD. Thats really interesting.
Another note I should mention is that the motherboard on my dell died maybe a month or 2 after the I/O errors. Gotta love dell. Every single dell computer I owned died of mobo failure without any warning. Even their printers. Good god.
Anyway, could the mobo have been a factor? I know the tech that replaced the mobo told me that the LCD cable wasn't seated correctly, so could the SATA cables have been bad as well? I really doubt it though, but who knows
Edited for embarrassing spelling mistakes
I think it's rather interesting that both you and I have Toshiba hard drives. I've heard that they're supposed to be as delicate as glass, but mine's held up all right, until these weird errors and stuff.
As for motherboards. If the motherboard is messed up, everything will seem messed up, but may or may not.

Super Slow Load Times

I am having ridiculously long load times under Logic 9.1.1... up to five minutes for some projects. This is happening in both 32 and 64 bit modes. Anyone have a similar experience or a workaround?

I am sorry that you are experiencing that problem. based on my research I found that a user was experiencing the same problems and he/she states that it is a hard disk's latency problem.
Read it more here:
http://www.sonicstate.com/news/2010/01/17/wnamm10-synthogy-ivory-version-2/
Let me know if you found this information helpful.
Vicente Tulliano

High thread count on store.exe

I understand that the mdb store process utilizes as much memory as is available. My question is regarding the thread count on the process. One of the three mailbox servers tends to have a higher thread count than the other two. It
usually ranges from 150 to 200 (while the other two are usually 130 to 150) but today it is a little over 300. The rpc thread count on all the mailbox servers stays pretty low (60 or under) and the rpc thread count on the CAS servers usually
hang out around 55-65, so that's all good. All three mailbox servers also use VERY close to the same amount of memory all the time, so that doesn't seem to be making a difference. I am just trying to determine why the thread count is noticably
higher. This server and one of other mailbox servers replicate the public folder database, and I can understand why that would account for some additional activity, but you would think the thread count would be higher on the other server with the public
folder database as well, but it stays pretty low. Hardware-wise these servers are all identical. So is there something I can monitor in perf mon for instance? I don't want to use experfwiz because that monitors everything under the sun and
I need it a bit more centralized. I have googled all over the place and the only thing I can find is that with newer versions of exchange this thread count ranges from 200-300 on heavy usage, and exch07 can handle up to 500 threads, so I can't even find
which specific things to monitor that directly correlate with this issue. So while I understand that it's not really too high, I would like to find out why it deviates from the norm if the other two servers are equal for all intents and purposes (same
hardware, balanced DAG. etc). I would like to mitigate any potential issues. Thank you.

Hi pchw,
Thank you for your question.
I am sorry that we could not find the specific things to monitor this issuer directly, because there are many reason which caused it. For example: virus, big size attachment in queue, hardware performance and so on. We could refer to the following steps
to troubleshoot:
Restart the service of “Microsoft Exchange transport”;
Create a new database and move mailbox to new mailbox;
We could do some disk health check if the load test is normal;
Collect related application log and system log to
[email protected] for our troubleshooting.
We could run SDP on Exchange server and send it to
[email protected] for our troubleshooting.
http://blogs.msdn.com/b/askie/archive/2012/05/22/introduction-to-support-diagnostics-platform-sdp.aspx
We could use tools and logs to analysis if there are anything wrong or abnormal on Exchange server 2013. our bottle neck is disk IO latency, store.exe do require some CPU usage, but if our disk IO speed can keep in a normal range, the
CPU usage will be smaller. Exchange is highly rely on disk IO performance because it need lots of IO operation regarding to transaction log and database file. If Disk IO has a high latency, I will definitely impact store.exe, if it`s getting seriously sometimes
it may cause store.exe no response.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/ee832791(v=exchg.141).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Cannot upgrade to snow leopard

I have a late 2007 iMac (2GHz core 2 Duo). Since I purchased it, it has run Tiger, then Leopard flawlessly. I recently bought a Magic Trackpad which required me to upgrade to Snow Leopard. Unfortunately, 10.6 seems to kernel panic almost as soon as it boots up. If I downgrade back to 10.5, all works fine again. I have tried the following:
1. Clean install of 10.6 = kernel panic once the OS boots
2. Clean install using another 10.6 installation disk = kernel panic once the OS boots
3. Swap out RAM = kernel panic once the OS boots
4. Boot from an external 10.6 disk = kernel panic once the OS boots
More often than not, I can boot into safe mode with Airport disabled although sometimes (seemingly random) that also kernel panics. I am completely stumped here and would appreciate any help please. I don't want to be stuck in Leopard for all eternity! BTW I did take it into the Apple Store, and the "geniuses" claimed it was fixed - took it home and it wasn't. Below is the output from the kernel panic log:
Tue Dec 14 15:55:27 2010
Machine-check capabilities (cpu 1) 0x0000000000000806:
family: 6 model: 15 stepping: 10 microcode: 146
Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
6 error-reporting banks
threshold-based error status present
Machine-check status 0x0000000000000005:
restart IP valid
machine-check in progress
MCA error-reporting registers:
IA32MC0STATUS(0x401): 0x1000000000000000 invalid
IA32MC1STATUS(0x405): 0x0000000000000000 invalid
IA32MC2STATUS(0x409): 0x0000000000000000 invalid
IA32MC3STATUS(0x40d): 0x0020000000000000 invalid
IA32MC4STATUS(0x411): 0x0000000000000011 invalid
IA32MC5STATUS(0x415): 0xb200001802000e0f valid
MCA error code: 0x0e0f
Model specific error code: 0x0200
Other information: 0x00000018
Threshold-based status: No tracking
Status bits:
Processor context corrupt
Error enabled
Uncorrected error
panic(cpu 1 caller 0x2a9d27): Machine Check at 0x1c9b958d, thread:0x416ab7c, trapno:0x12, err:0x0,registers:
CR0: 0x80010033, CR2: 0x1d6ba000, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x00000010, EBX: 0x03d07440, ECX: 0x00000001, EDX: 0x00000000
ESP: 0x225e3b60, EBP: 0x225e3b98, ESI: 0x03dd5000, EDI: 0x1c9c4490
EFL: 0x00000006, EIP: 0x1c9b958d
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x1c8effb8 : 0x21b50c (0x5d42fc 0x1c8effec 0x223974 0x0)
0x1c8f0008 : 0x2a9d27 (0x595e34 0x595f21 0x1c9b958d 0x416ab7c)
0x1c8f00f8 : 0x2a1912 (0x1 0x1ff4ab4 0x3fe9568 0x7fd2ad0)
0x225e3b98 : 0x1c9aefc0 (0x1c8ed0a4 0x2 0x3dd5000 0x0)
0x225e3c88 : 0x1c9b051c (0xdc93b9a6 0x8000002c 0x0 0x0)
0x225e3d48 : 0x2abb32 (0xffffffff 0x7fffffff 0x225e3da8 0x1c936000)
0x225e3d68 : 0x22584d (0x1c93649c 0xdc93b749 0x2c 0x1c936488)
0x225e3dc8 : 0x22661f (0x1 0x416ab7c 0x40db4b0 0x2a358d)
0x225e3e38 : 0x227243 (0x416ab98 0x0 0x225e3e68 0xffffffff)
0x225e3ea8 : 0x2272e7 (0x210ce6 0x0 0x0 0x416ab7c)
0x225e3ec8 : 0x211b53 (0x210ce6 0x3000002 0x94 0x0)
0x225e3ef8 : 0x216dd5 (0x44dff14 0x3000002 0x94 0x0)
0x225e3f78 : 0x295156 (0x3c9f768 0x0 0x0 0x0)
0x225e3fc8 : 0x2a148d (0x3c9f764 0x0 0x10 0x7212644)
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.AppleIntelCPUPowerManagement(105.13.0)@0x1c9ad000->0x1c9cafff
BSD process name corresponding to current thread: notifyd
Mac OS version:
10H574
Kernel version:
Darwin Kernel Version 10.5.0: Fri Nov 5 23:20:39 PDT 2010; root:xnu-1504.9.17~1/RELEASE_I386
System model name: iMac7,1 (Mac-F4238CC8)
System uptime in nanoseconds: 192682025668
unloaded kexts:
com.apple.driver.AirPortBrcm43xx 423.91.27 (addr 0x22c1b000, size 0x1900544) - last unloaded 165488578251
loaded kexts:
com.apple.kext.ATIFramebuffer 6.2.4 - last loaded 99002809940
com.apple.DontSteal_Mac_OSX 7.0.0
com.apple.driver.AppleLPC 1.4.12
com.apple.driver.AppleBacklight 170.0.34
com.apple.driver.ACPISMCPlatformPlugin 4.5.0d5
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AppleIRController 303.8
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.iokit.SCSITaskUserClient 2.6.5
com.apple.driver.AirPortBrcm43224 426.36.1
com.apple.driver.AppleFWOHCI 4.7.1
com.apple.driver.AppleEFINVRAM 1.4.0
com.apple.driver.AppleUSBHub 4.1.7
com.apple.driver.AppleUSBEHCI 4.1.7
com.apple.iokit.IOAHCIBlockStorage 1.6.3
com.apple.iokit.AppleYukon2 3.2.1b1
com.apple.driver.AppleAHCIPort 2.1.5
com.apple.driver.AppleIntelPIIXATA 2.5.1
com.apple.driver.AppleUSBUHCI 4.1.5
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleACPIButtons 1.3.5
com.apple.driver.AppleSMBIOS 1.6
com.apple.driver.AppleACPIEC 1.3.5
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 105.13.0
com.apple.security.sandbox 1
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.11
com.apple.driver.AppleIntelCPUPowerManagement 105.13.0
com.apple.iokit.IONDRVSupport 2.2
com.apple.kext.ATI2400Controller 6.2.4
com.apple.kext.ATISupport 6.2.4
com.apple.iokit.IOGraphicsFamily 2.2
com.apple.driver.IOPlatformPluginFamily 4.5.0d5
com.apple.driver.AppleSMC 3.1.0d3
com.apple.driver.CSRUSBBluetoothHCIController 2.3.8f7
com.apple.driver.AppleUSBBluetoothHCIController 2.3.8f7
com.apple.iokit.IOBluetoothFamily 2.3.8f7
com.apple.iokit.IOUSBHIDDriver 4.1.5
com.apple.driver.AppleUSBMergeNub 4.1.5
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.5
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.iokit.IO80211Family 312
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IOUSBUserClient 4.1.5
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOATAPIProtocolTransport 2.5.1
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.5
com.apple.iokit.IONetworkingFamily 1.10
com.apple.iokit.IOAHCIFamily 2.0.4
com.apple.iokit.IOATAFamily 2.5.1
com.apple.iokit.IOUSBFamily 4.1.7
com.apple.driver.AppleEFIRuntime 1.4.0
com.apple.iokit.IOHIDFamily 1.6.5
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.TMSafetyNet 6
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 289
com.apple.iokit.IOStorageFamily 1.6.2
com.apple.driver.AppleACPIPlatform 1.3.5
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0

Are you trying to boot off a 10.6.5 updated system, or a 10.6.5 installer DVD from another Mac? According to;
http://en.wikipedia.org/wiki/MacOS_X10.6
The build and Darwin version belong exclusively to 10.6.5.
Your Mac can only boot off 10.6 and 10.6.3 retail to install 10.6, as well as systems upgraded from those 10.6 installations on your specific model and vintage iMac. But it can't boot off another Mac's installer. The 10.6 installer DVD must look like *
and not say Upgrade, Dropin, or OEM.
- * Links to my pages may give me compensation.
Message was edited by: a brody

Unable to create a new cluster on our domain

Hi there,
I am having difficulties creating a new server 2012 R2 failover cluster in our domain. We have a working 2008 R2 cluster that has been running fine for years now.
I have tried on different hardward with single nodes and multiple nodes when making the cluster. I can see the new cluster account is created in AD and I have triple checked all permissions required to create the cluster. The resulting errors
are:
Adding special permissions to the computer object failed. Trying to add 'Full-Access' permissions for security principal S-1-5-21-2379181152-2103701998-3253613930-1309 to computer object CN=VM-CLUSTER-1,OU=Servers,DC=HHS,DC=local failed. Verify that the
user running create cluster has permissions to update the computer object in Active Directory Domain Services. The parameter is incorrect.
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...
There was an error cleaning up the cluster nodes. Use Clear-ClusterNode to manually clean up the nodes.
An error occurred while creating the cluster.
The parameter is incorrect
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
Any suggestions on what could be causing this? My only current route of investigation is a currently missing domain controller account in AD as I assume this must be AD related.

Failover Cluster Validation Report
Node:
Node-4.HHS.local
Validated
Started
04/03/2014 09:05:31
Completed
04/03/2014 09:05:53
The Validate a Configuration Wizard must be run after any change is made to the configuration of the cluster or hardware. For more information, see
http://go.microsoft.com/fwlink/p/?LinkId=280145.
Results by Category
Name
Result Summary
Description
Hyper-V Configuration
<result></result>
<description>Success</description>
Inventory
<result></result>
<description>Success</description>
Network
<result></result>
<description>Warning</description>
Storage
<result></result>
<description>Warning</description>
System Configuration
<result></result>
<description>Warning</description>
Hyper-V Configuration
Name
Result
Description
<id>List Information About Servers Running Hyper-V</id>
<result></result>
<description>Success</description>
<id>Validate Compatibility of Virtual Fibre Channel SANs for Hyper-V</id>
<result></result>
<description>Success</description>
<id>Validate Hyper-V Memory Resource Pool Compatibility</id>
<result></result>
<description>Success</description>
<id>Validate Hyper-V Network Resource Pool And Virtual Switch Compatibility</id>
<result></result>
<description>Success</description>
<id>Validate Hyper-V Processor Resource Pool Compatibility</id>
<result></result>
<description>Success</description>
<id>Validate Hyper-V Role Installed</id>
<result></result>
<description>Success</description>
<id>Validate Hyper-V Storage Resource Pool Compatibility</id>
<result></result>
<description>Success</description>
<id>Validate Matching Processor Manufacturers</id>
<result></result>
<description>Success</description>
Inventory
Name
Result
Description
<id>List BIOS Information</id>
<result></result>
<description>Success</description>
<id>List Environment Variables</id>
<result></result>
<description>Success</description>
<id>List Fibre Channel Host Bus Adapters</id>
<result></result>
<description>Success</description>
<id>List iSCSI Host Bus Adapters</id>
<result></result>
<description>Success</description>
<id>List Memory Information</id>
<result></result>
<description>Success</description>
<id>List Operating System Information</id>
<result></result>
<description>Success</description>
<id>List Plug and Play Devices</id>
<result></result>
<description>Success</description>
<id>List Running Processes</id>
<result></result>
<description>Success</description>
<id>List SAS Host Bus Adapters</id>
<result></result>
<description>Success</description>
<id>List Services Information</id>
<result></result>
<description>Success</description>
<id>List Software Updates</id>
<result></result>
<description>Success</description>
<id>List System Drivers</id>
<result></result>
<description>Success</description>
<id>List System Information</id>
<result></result>
<description>Success</description>
<id>List Unsigned Drivers</id>
<result></result>
<description>Success</description>
Network
Name
Result
Description
<id>List Network Binding Order</id>
<result></result>
<description>Success</description>
<id>Validate Cluster Network Configuration</id>
<result></result>
<description>Success</description>
<id>Validate IP Configuration</id>
<result></result>
<description>Success</description>
<id>Validate Network Communication</id>
<result></result>
<description>Not Applicable</description>
<id>Validate Windows Firewall Configuration</id>
<result></result>
<description>Success</description>
Storage
Name
Result
Description
<id>List Disks</id>
<result></result>
<description>Success</description>
<id>List Disks To Be Validated</id>
<result></result>
<description>Not Applicable</description>
<id>Validate CSV Network Bindings</id>
<result></result>
<description>Not Applicable</description>
<id>Validate CSV Settings</id>
<result></result>
<description>Not Applicable</description>
<id>Validate Disk Access Latency</id>
<result></result>
<description>Not Applicable</description>
<id>Validate Disk Arbitration</id>
<result></result>
<description>Not Applicable</description>
<id>Validate Disk Failover</id>
<result></result>
<description>Not Applicable</description>
<id>Validate File System</id>
<result></result>
<description>Not Applicable</description>
<id>Validate Microsoft MPIO-based disks</id>
<result></result>
<description>Not Applicable</description>
<id>Validate Multiple Arbitration</id>
<result></result>
<description>Not Applicable</description>
<id>Validate SCSI device Vital Product Data (VPD)</id>
<result></result>
<description>Not Applicable</description>
<id>Validate SCSI-3 Persistent Reservation</id>
<result></result>
<description>Not Applicable</description>
<id>Validate Simultaneous Failover</id>
<result></result>
<description>Not Applicable</description>
<id>Validate Storage Spaces Persistent Reservation</id>
<result></result>
<description>Not Applicable</description>
System Configuration
Name
Result
Description
<id>Validate Active Directory Configuration</id>
<result></result>
<description>Success</description>
<id>Validate All Drivers Signed</id>
<result></result>
<description>Success</description>
<id>Validate Memory Dump Settings</id>
<result></result>
<description>Success</description>
<id>Validate Operating System Edition</id>
<result></result>
<description>Success</description>
<id>Validate Operating System Installation Option</id>
<result></result>
<description>Success</description>
<id>Validate Operating System Version</id>
<result></result>
<description>Success</description>
<id>Validate Required Services</id>
<result></result>
<description>Success</description>
<id>Validate Same Processor Architecture</id>
<result></result>
<description>Not Applicable</description>
<id>Validate Service Pack Levels</id>
<result></result>
<description>Not Applicable</description>
<id>Validate Software Update Levels</id>
<result></result>
<description>Not Applicable</description>
Overall Result
Testing has completed successfully and the configuration is suitable for clustering.

[solved] Booting a "Multiboot" OS only works with high amounts of mem

edit: ok, I hate when it happens, but I've just found the solution: raising the memory reserved for the virtual machine. It's funny, however, that such simple kernel won't boot with less than 128MB of RAM.
I'm not sure if this is the right place to post this question, but as it's at least indirectly related to programming, I'll post it here.
Recently I've read Tenenbaum's book about Minix and now I'm feeling like hacking a simple OS if only for saying "I can do it". The problem is I got stuck right at the first step: booting. I wasn't willing to implement a bootloader so I decided to use Grub and implement a Multiboot compatible kernel.
Running 'info multiboot' you can see a example showing how to implement a "multiboot" kernel. I used exactly the same code and compiled it with:
gcc -nostartfiles -nodefaultlibs -o kernel boot.S kernel.c
The code compiles with two warnings about redefinitions of printf, but it gives no errors. The 'kernel' file is less than 3KB big and running 'objdump -d kernel' seems to be fine.
Satisfied with it, I've tried to create an ISO image so I could test it in a virtual machine (VirtualBox). I followed the instructions from Grub manual of how to install it in a CD (create a iso/boot/grub/ folder, put stage2_eltorito there, etc). I also created a menu.lst like this:
default 0
timeout 30
fallback 1
title Test
root (cd)
kernel /boot/kernel
and created the ISO image with: 'mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot -boot-load-size 4 -boot-info-table -o grub.iso iso' .
I've tried to run it in a virtual machine and it boots, but when I press enter to run 'Test', which should run the kernel from the 'multiboot' example, grub gives me an error:
Booting 'Test'
root (cd)
Filesystem type is iso9660, using whole disk.
kernel /boot/kernel
[Multiboot-elf, <0x8048000:0x803:0x0>
Error 28: Selected item cannot fit into memory.
Press any key to continue...
And then it fallsback to the menu. (The menu shows [639k lower / 64448k upper memory])
Last edited by andre.ramaciotti (2009-10-12 19:54:04)

The linker is compiling your binary to the default location of 0x8000000. This is fine for Linux to load as an application (even with less than 128MB memory, Linux can use the MMU on the CPU to map anything to 0x8000000). However with ring0 code you are dealing with real physical memory locations. You would need either a linker script (which you can look up, also see: http://wiki.osdev.org/Linker_Scripts) or to specify the options on the command line with
ld -Ttext 0x100000 etc.
0x100000 is at 1MB, so that leaves BIOS memory unaffected. For memory management past that you should read a memory map, which is beyond the scope of this.
Edit: Fix formatting issues.
Last edited by sdkmvx (2009-10-12 19:41:52)

Oracle Linux 6.0 64 bit instalation problem

Hi,
I downloaded Oracle Linux 6.0 64 bit from Oracle site. I unpacked it and burned it on dvd, but it can't boot so I can't install it. I could't do it even with virtual machine. I also put disk detection latency to 15 sec so I could give Linux enough time to boot, but it did't help. So any sugestion? :) I have core i7 2600 and Gigabyte UD4 P67 B3, bit I don't think it is a problem.
Thx
Edited by: MarcusO on 2011.03.30 00:15

This directory contains image files used during the Oracle Linux 6
installation process.
The boot.iso file that is sometimes found in the images directory has
been removed for space reasons. It is available as a separate download
from ULN. boot.iso is an ISO 9660 image of a bootable CD-ROM. It is useful
in cases where the CD-ROM installation method is not desired, but the
CD-ROM's boot speed would be an advantage.
To use this image file, burn the file onto CD-R (or CD-RW) media as you
normally would.
From Images folder, installation DVD.
Can anyone tell me what to do

ORA-01157: cannot identify/lock data file 13 - see DBWR trace file

Hi all,
I've a Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.
I'm using ASM.
Yesterday I added new disks and then I changed the +/etc/udev/rules.d/98-oracle.rules+ file.
Now it looks like this (the bolded are the new ones):
# Oracle Configuration Registry
KERNEL=="emcpowerd1", OWNER="root", GROUP="oinstall", MODE="640", NAME="ocr"
# Voting Disks
KERNEL=="emcpowerr1", OWNER="oracle", GROUP="oinstall", MODE="640", NAME="voting"
# Spfile ASM+
KERNEL=="emcpowers1", OWNER="oracle", GROUP="dba", MODE="660", NAME="spfileASM"
# ASM Devices
KERNEL=="emcpowerj1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm0" #onlineredo asm disk
KERNEL=="emcpowern1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm1" #data asm disk
KERNEL=="emcpowerh1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm2" #data asm disk
KERNEL=="emcpowerq1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm3" #data asm disk
KERNEL=="emcpowere1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm4" #data asm disk
KERNEL=="emcpowerg1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm5" #data asm disk
KERNEL=="emcpowerl1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm6" #data asm disk
KERNEL=="emcpowero1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm7" #data asm disk
KERNEL=="emcpowerf1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm8" #data asm disk
KERNEL=="emcpowerm1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm9" #data asm disk
KERNEL=="emcpoweri1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm10" #data asm disk
KERNEL=="emcpowerp1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm11" #data asm disk
KERNEL=="emcpowerk1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm12" #data asm disk
KERNEL=="emcpowert", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm210" #data asm disk SATA
KERNEL=="emcpowerc", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm211" #data asm disk SATA
KERNEL=="emcpowerb", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm212" #data asm disk SATA
KERNEL=="emcpowera", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm213" #data asm disk SATA
It's the same on both RAC nodes.
The operating system, a RedHat 5.4, see the new devices (both nodes):
ls -ltr /dev/asm*
brw-rw---- 1 oracle dba 120, 16 May 18 10:03 /dev/asm212
brw-rw---- 1 oracle dba 120, 304 May 18 10:03 /dev/asm210
brw-rw---- 1 oracle dba 120, 32 May 18 10:03 /dev/asm211
brw-rw---- 1 oracle dba 120, 0 May 18 10:03 /dev/asm213
brw-rw---- 1 oracle dba 120, 209 May 18 10:05 /dev/asm1
brw-rw---- 1 oracle dba 120, 81 May 18 13:40 /dev/asm8
brw-rw---- 1 oracle dba 120, 97 May 18 13:40 /dev/asm5
brw-rw---- 1 oracle dba 120, 193 May 18 13:40 /dev/asm9
brw-rw---- 1 oracle dba 120, 161 May 18 13:40 /dev/asm12
brw-rw---- 1 oracle dba 120, 241 May 18 13:40 /dev/asm11
brw-rw---- 1 oracle dba 120, 177 May 18 13:40 /dev/asm6
brw-rw---- 1 oracle dba 120, 225 May 18 13:40 /dev/asm7
brw-rw---- 1 oracle dba 120, 65 May 18 13:40 /dev/asm4
brw-rw---- 1 oracle dba 120, 129 May 18 13:40 /dev/asm10
brw-rw---- 1 oracle dba 120, 257 May 18 13:40 /dev/asm3
brw-rw---- 1 oracle dba 120, 113 May 18 13:40 /dev/asm2
brw-rw---- 1 oracle dba 120, 145 May 18 13:40 /dev/asm0
Both ASM instance see new devices:
From ASM1
SQL*Plus: Release 11.1.0.6.0 - Production on Tue May 18 13:43:10 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM1
SQL> select path from v$asm_disk;
PATH
/dev/asm212
/dev/asm211
/dev/asm213
/dev/asm210
/dev/asm1
/dev/asm4
/dev/asm5
/dev/asm0
/dev/asm12
/dev/asm9
/dev/asm2
/dev/asm10
/dev/asm7
/dev/asm11
/dev/asm3
/dev/asm8
/dev/asm6
17 rows selected.
SQL>
From ASM2
SQL*Plus: Release 11.1.0.6.0 - Production on Tue May 18 13:42:39 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM2
SQL> select path from v$asm_disk;
PATH
/dev/asm213
/dev/asm211
/dev/asm210
/dev/asm212
/dev/asm8
/dev/asm7
/dev/asm6
/dev/asm11
/dev/asm4
/dev/asm12
/dev/asm5
/dev/asm9
/dev/asm1
/dev/asm3
/dev/asm10
/dev/asm2
/dev/asm0
17 rows selected.
SQL>
Then I created a disk group:
CREATE DISKGROUP STORE EXTERNAL REDUNDANCY DISK '/dev/asm210';
Then I created a new tablespace:
CREATE TABLESPACE store DATAFILE '+STORE';
I did all this operations from NODE1.
What is happening now is that everytime I try to read something from new diskgroup FROM NODE2 I get the ORA-01157:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707
No problem to read from NODE1.
The simple query on dba_data_file work from NODE1 and fails from NODE2 with the ORA-01157.
I found this on the alert log:
<msg time='2010-05-18T10:06:41.084+00:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
module='' pid='11014'>
<txt>Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11014.trc:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707'
</txt>
</msg>
And this from the trace:
Trace file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11014.trc
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
ORACLE_HOME = /u01/app/oracle/product/11.1.0/db1
System name: Linux
Node name: node02
Release: 2.6.18-128.7.1.el5
Version: #1 SMP Wed Aug 19 04:00:49 EDT 2009
Machine: x86_64
Instance name: EVODB2
Redo thread mounted by this instance: 2
Oracle process number: 19
Unix process pid: 11014, image: oracle@node02 (SMON)
*** 2010-05-18 10:06:41.084
*** SESSION ID:(151.1) 2010-05-18 10:06:41.084
*** CLIENT ID:() 2010-05-18 10:06:41.084
*** SERVICE NAME:(SYS$BACKGROUND) 2010-05-18 10:06:41.084
*** MODULE NAME:() 2010-05-18 10:06:41.084
*** ACTION NAME:() 2010-05-18 10:06:41.084
DDE rules only execution for: ORA 1110
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
----- DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- (Action duration in csec: 0) -----
----- END DDE Actions Dump -----
*** 2010-05-18 10:06:41.084
SMON: following errors trapped and ignored:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707'
Any suggestion about how to solve the problem?
Thanks in advance!
Samuel

I didn't understand what do you mean with thread...
But I think you found the problem
Initialization files of both ASM instance are: SPFILE='/dev/spfileASM'
that SPFILE is (common for both):
+ASM2.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
+ASM2.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA'
+ASM1.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA','STORE'#Manual Mount
*.asm_diskstring='/dev/asm*'
*.cluster_database=true
*.diagnostic_dest='/u01/app/oracle'
+ASM1.instance_number=1
+ASM2.instance_number=2
*.instance_type='asm'
*.large_pool_size=12M
+ASM1.local_listener='LISTENER_ASM'
+AC
Then I executed another query:
From ASM1
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM1
SQL> select name, state from v$asm_diskgroup;
NAME STATE
ARCHIVELOG MOUNTED
DATA MOUNTED
ONLINELOG MOUNTED
STORE MOUNTED
SQL>
From ASM2
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM2
SQL> select name, state from v$asm_diskgroup;
NAME STATE
ARCHIVELOG MOUNTED
DATA MOUNTED
ONLINELOG MOUNTED
STORE DISMOUNTED
SQL>
Than the question is:
how can I mount the disk group STORE also on ASM2?
I think the problems is into the spfile lines:
+ASM2.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA'
+ASM1.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA','STORE'
How can I change the +ASM2.asm_diskgroups value?
Thanks

SCOM 2012 Service Level Dashboard

I have been tasked with creating a Service level dashboard for SCOM 2012. After reading up on various blogs and sites around methods and BI / reporting tools I am no closer to knowing what would be the best solution, and would appreciate some guidance.
I want to create SLO groups for applications - Exchange, AD, SQL, SCCM etc. and have a high level heat map with measures like CPU util, Disk space %, latency etc. updated every minute and displayed in each block (preferably using corners of a single block),
and if possible to add a bootstrap style icon into each block.
I would like drill down functionality on each group that then breaks down into another heatmap (per server).
And then to drill down further which displays a SLD type dashboard on that instance.
I am comfortable with creating the final level SLD using widgets, would it be possible to use Visio for the heatmaps ?
I have looked into using Power View, would conditional formatting be a better option ?
Id like to publish the dashboard into Sharepoint.
Would appreciate your feedback. Once i know which solution to look into, it would become much easier to focus my attention.

Hi,
I would like to suggest you refer to the articles below:
Creating a Service Level Dashboard
http://technet.microsoft.com/en-us/library/hh212692.aspx
Monitoring Service Level Objectives by Using Operations Manager
http://technet.microsoft.com/en-us/library/hh212753.aspx
For more information on the Visio 2010, Sharepoint 2010 and Savision LiveMaps
solutions, see the excellent blog series by SCOM MVP Marnix Wolf from the link
below:
http://thoughtsonopsmgr.blogspot.com/2010/09/scom-and-dashboards.html
Regards,
Yan Li
Regards, Yan Li

Changing my HDD and warranty information...

Hello everyone, i would like some information.
I would like to change my hard drive because i don't trust toshiba drives and i had a hard crash while i was trying to boot camp... My questions is more warranty related i suppose...
So what i want is to buy a WD Scorpio 7200 rpm and change it for my self because i don't have any apple store in my country and the resellers are not trustworthy... And i was wondering if i will loose my warranty if doing that...
I attached the kernel panic document attached and it would be really helpful to know what these number are codes are related to...
Regards
Interval Since Last Panic Report: 1749865 sec
Panics Since Last Report: 1
Anonymous UUID: 9E2EB171-33D4-4FD8-970D-7B8B56B7C7A7
Wed Sep 29 21:15:34 2010
panic(cpu 0 caller 0x41a79a): "hfsswapHFSPlusBTInternalNode: catalog key #11263 offset too big (0x0000)\n"@/SourceCache/xnu/xnu-1504.7.4/bsd/hfs/hfs_endian.c:500
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x5bd3bb38 : 0x21b455 (0x5cf328 0x5bd3bb6c 0x2238b1 0x0)
0x5bd3bb88 : 0x41a79a (0x5b90d8 0x2bff 0x0 0x6)
0x5bd3bc28 : 0x40f791 (0x5bd3bc48 0x871ae10 0x1 0x1)
0x5bd3bc68 : 0x2c966d (0x57b4fda0 0x8717004 0x865a4bc 0x10505d9)
0x5bd3bcb8 : 0x1053bba (0x57b4fda0 0x0 0x0 0x2000)
0x5bd3bce8 : 0x104ab97 (0x8f83214 0x0 0x2000 0x0)
0x5bd3bd58 : 0x1053bba (0x86cf400 0x8f83200 0x0 0x2000)
0x5bd3bd88 : 0x14a204d (0x5bd3bdc4 0x0 0x2000 0x0)
0x5bd3bde8 : 0x14a4210 (0x86cf800 0x86858c8 0x64 0x0)
0x5bd3be08 : 0xf5367e (0x86de700 0x86bfb00 0x0 0x29d54e)
0x5bd3be38 : 0xf54270 (0x86ca480 0x86bfb00 0x2e6bc84a 0x86a0400)
0x5bd3be58 : 0xf5bece (0x86bfb00 0x86bfb00 0x0 0x2a1591)
0x5bd3be98 : 0xf5c028 (0x86a0400 0x86bfb00 0x0 0x0)
0x5bd3bed8 : 0xf5daa6 (0x86a0400 0x2000 0x5bd3bef8 0x85963d4)
0x5bd3bf38 : 0xf5a076 (0x86a0400 0x0 0x8d513d8 0x5bd3bf94)
0x5bd3bf58 : 0x54787e (0x86c3940 0x86c3adc 0x5bd3bf88 0x227161)
0x5bd3bf88 : 0x547cd8 (0x86c3ac0 0x86c3ac0 0x8551dcc5 0x7fff)
0x5bd3bfc8 : 0x29e6cc (0x86c3ac0 0x0 0x10 0x91ebde4)
Kernel Extensions in backtrace (with dependencies):
com.apple.iokit.IOAHCIBlockStorage(1.6.2)@0x149f000->0x14b1fff
dependency: com.apple.iokit.IOAHCIFamily(2.0.4)@0xf51000
dependency: com.apple.iokit.IOStorageFamily(1.6.1)@0x1042000
com.apple.driver.AppleAHCIPort(2.1.2)@0xf57000->0xf6afff
dependency: com.apple.iokit.IOAHCIFamily(2.0.4)@0xf51000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x926000
com.apple.iokit.IOAHCIFamily(2.0.4)@0xf51000->0xf56fff
com.apple.iokit.IOStorageFamily(1.6.1)@0x1042000->0x1059fff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10F569
Kernel version:
Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386
System model name: MacBookPro6,1 (Mac-F22589C8)
System uptime in nanoseconds: 6546309188433
unloaded kexts:
com.apple.driver.AppleFileSystemDriver 2.0 (addr 0x105a000, size 0x12288) - last unloaded 152848533712
loaded kexts:
com.paceap.kext.pacesupport.snowleopard 5.7.2
com.digidesign.iokit.DigiDal 8.0.4f2
com.apple.driver.AppleHWSensor 1.9.3d0
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AGPM 100.12.12
com.apple.driver.AppleMikeyHIDDriver 1.2.0
com.apple.driver.AppleHDA 1.8.7f1
com.apple.driver.AppleMikeyDriver 1.8.7f1
com.apple.driver.AppleUpstreamUserClient 3.3.2
com.apple.driver.AudioAUUC 1.4
com.apple.driver.AppleIntelHDGraphics 6.1.8
com.apple.driver.AppleIntelHDGraphicsFB 6.1.8
com.apple.driver.SMCMotionSensor 3.0.0d4
com.apple.kext.AppleSMCLMU 1.5.0d3
com.apple.DontSteal_Mac_OSX 7.0.0
com.apple.driver.AudioIPCDriver 1.1.2
com.apple.driver.AppleGraphicsControl 2.8.63
com.apple.GeForce 6.1.8
com.apple.driver.ACPISMCPlatformPlugin 4.1.2b1
com.apple.driver.AppleLPC 1.4.12
com.apple.driver.AppleUSBTCButtons 1.8.1b1
com.apple.driver.AppleIRController 303.8
com.apple.driver.AppleUSBTCKeyboard 1.8.1b1
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.iokit.SCSITaskUserClient 2.6.5
com.apple.iokit.IOAHCIBlockStorage 1.6.2
com.apple.driver.AppleUSBHub 4.0.0
com.apple.driver.AppleFWOHCI 4.7.1
com.apple.driver.AirPortBrcm43224 425.16.2
com.apple.iokit.AppleBCM5701Ethernet 2.3.8b2
com.apple.driver.AppleEFINVRAM 1.3.0
com.apple.driver.AppleSmartBatteryManager 160.0.0
com.apple.driver.AppleUSBEHCI 4.0.2
com.apple.driver.AppleUSBUHCI 4.0.2
com.apple.driver.AppleAHCIPort 2.1.2
com.apple.driver.AppleACPIButtons 1.3.2
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleSMBIOS 1.6
com.apple.driver.AppleACPIEC 1.3.2
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 105.10.0
com.apple.security.sandbox 0
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.11
com.apple.driver.AppleIntelCPUPowerManagement 105.10.0
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.5 - last loaded 5969237577466
com.apple.iokit.IOUSBMassStorageClass 2.6.1
com.apple.driver.DspFuncLib 1.8.7f1
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction
HERE IS THE LOG AFTER THE DISK VERYFY...
Verifying volume “Macintosh HD”
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Incorrect block count for file 0.indexDirectory
(It should be 1718 instead of 859)
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Macintosh HD was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.

Kernel Extensions in backtrace (with dependencies):
com.apple.iokit.IOAHCIBlockStorage(1.6.2)@0x149f000->0x14b1fff
dependency: com.apple.iokit.IOAHCIFamily(2.0.4)@0xf51000
dependency: com.apple.iokit.IOStorageFamily(1.6.1)@0x1042000
com.apple.driver.AppleAHCIPort(2.1.2)@0xf57000->0xf6afff
dependency: com.apple.iokit.IOAHCIFamily(2.0.4)@0xf51000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x926000
com.apple.iokit.IOAHCIFamily(2.0.4)@0xf51000->0xf56fff
com.apple.iokit.IOStorageFamily(1.6.1)@0x1042000->0x1059fff
BSD process name corresponding to current thread: kernel_task
This is usually the important part of the message. I'm however, not convinced with this error message that the issue will be resolved with a hard drive replacement. Not to mention, the Western Digital drive has the same percentage of failure chance as the Toshiba drive (and the Hitachi drive... and the Seagate drive... etc.)
From my experience with a kernel_task as the BSD process related to the panic it's usually a hardware related failure. However, an easy way to identify this would be a clean install of the OS on the existing (or new HD). If the machine continues to panic, we've already eliminated software as the problem which would indicate a hardware-related issue.

Size Limits to Essbase

Hi,
I am working on a Planning application and as most of you would now, it is based on a BSO Essbase cube.
I wanted to know, if there are any limitations to the size of the dimensions? And if yes, then what is the limit on the number of members?
For your reference, I have two dimensions that have roughly 10,000 to 15,000 members.
At the moment, it takes time to deploy the application but otherwise, everything seems to work. I want to know if there is any limit to expansion so I can better prepare for that scenario. Thanks.
Regards,
Shehzad

Please,
check the limits here DBAG .
Before you hit these limits, I assume that your hardware will no longer be able to run calculations (as DISK IO latency on per block operations increases linear).
I always prefer designs that would only have the amount of detail, that is usable for analyzing major effects. Business people are happy when it takes the database to calculate all dependencies after changing a value in a few seconds.
In 11.1.1.3 dense restructures are still single thread operations that issue IOs for each block (IOs > 10K). This is a llot of stress for our IO subsystems - thus restructures run at 2 MB/s. Therefore large databases consume too much time during maintenance operations.
I managed to bring a 200GB database down to just 12 GB by:
- removing things that were unimportant to the business
- use dynamic calculation where possible (even for currencies)
- split the database into three
Don't get me wrong - if it's the business demand to have 100.000 members, thats fine - I just never found a REAL reason why this adds to a business process.
Sascha.

SpeedGrade Interface & Performance Questions

New SpeedGrade user.... had a great experience grading a commerical spec this weekend on the CC version. Would like to start using it during client attend, but need to understand a few things first:
1) Is there a way to keep the Look color controls from dimming? I would like to them to stay on, or bright, all the time.
2) Can you set the parade scopes to function normally where the waveforms move, but the scope outline itself stays fixed?
3) Does anyone have any ideas for making tracking faster? Right now a 5-6 second clip takes what seems like a few minutes to track.
4) I have an SSD boot drive. Other than media storage, does SpeedGrade use any cache locations that benefit from fast drive I/O?
5) Are SpeedGrade corrections actually realtime in the the way that Premiere or Resolve are, or is it caching heavily in the background to enable playback of corrections?
6) I am getting about 10fps on render out using ProRes444 and 3-4 layers of corrections on a 2.66 GHz, 12-Core Mac Pro with 32GB of ram, a K5000, and very fast RAID array. My disk performance (latency?) hovers around 7-10ms, and CPU is around 300-400ms. The other two are always at 0ms. Is there anything I can invest in that would help get render outs up to at least 24fps?

I have tried both Cuda and OpenCL and both have issues crashing when exporting (or failed export). Software works fine, but takes a long time to export and playback is unusably sluggish.
Source material is Canon 5d2 and canon 5d3 .h264 All-I and IPB compression schemes. 23.97fps. I have tried with no external display, and with external. Internal storage (flash) and external. I have the faster of the macbook retina's with 16GB ram.
It's literally stopped my production, as exports are flaky and I can't really edit without slowly rendering. I have tried re-installing the software, and trashign preferences, and repaired disk permissions. My drive is less than half full.
Here are specs:
Premiere pro 6.0.2 (latest update)
OSX 10.8.2 (latest update)
2.5GHz i7 quad core
16GB ram
500GB apple flash drive
Thunderbolt Lacie Raid

ASM_DISKSTRING is empty and discover discs

Hi,
SO: RHEL6
GI: 11.2.0.3
User owner: grid
The parameter ASM_DISKSTRING is null string however discovers disks.
SQL> select name, path from v$asm_disk;
NAME                           PATH
                               /dev/vg_hdisk_ora/lv_hd10
                               /dev/vg_hdisk_ora/lv_hd15
                               /dev/vg_hdisk_ora/lv_hd3
                               /dev/vg_hdisk_ora/lv_hd6
                               /dev/vg_hdisk_ora/lv_hd4
                               /dev/vg_hdisk_ora/lv_hd7
                               /dev/vg_hdisk_ora/lv_hd5
                               /dev/vg_hdisk_ora/lv_hd2
                               /dev/vg_hdisk_ora/lv_hd8
                               /dev/vg_hdisk_ora/lv_hd9
                               /dev/vg_hdisk_ora/lv_hd20
                               /dev/vg_hdisk_ora/lv_hd18
                               /dev/vg_hdisk_ora/lv_hd17
                               /dev/vg_hdisk_ora/lv_hd19
                               /dev/vg_hdisk_ora/lv_hd16
                               /dev/vg_hdisk_ora/lv_hd14
                               /dev/vg_hdisk_ora/lv_hd11
                               /dev/vg_hdisk_ora/lv_hd13
                               /dev/vg_hdisk_ora/lv_hd12
                               /dev/vg_hdisk_ora/lv_hd1
20 rows selected.
SQL> show parameters string
NAME                                 TYPE        VALUE
asm_diskstring                       stringAfter setting asm_diskstring to "/dev/asm*", list 40 disks (kernel-assigned device file names & UDEV name)
DISK_NUMBER PATH
          0 /dev/asm-disk10
         39 /dev/vg_hdisk_ora/lv_hd15
          2 /dev/asm-disk3
          3 /dev/asm-disk6
          4 /dev/asm-disk4
          5 /dev/asm-disk7
          6 /dev/asm-disk5
          7 /dev/asm-disk2
          8 /dev/asm-disk8
          9 /dev/asm-disk9
         10 /dev/asm-disk20
         11 /dev/asm-disk18
         12 /dev/asm-disk17
         13 /dev/asm-disk19
         14 /dev/asm-disk16
         15 /dev/asm-disk14
         16 /dev/asm-disk11
         17 /dev/asm-disk13
         18 /dev/asm-disk12
         19 /dev/asm-disk15
         20 /dev/vg_hdisk_ora/lv_hd10
         21 /dev/vg_hdisk_ora/lv_hd1
         22 /dev/vg_hdisk_ora/lv_hd3
         23 /dev/vg_hdisk_ora/lv_hd6
         24 /dev/vg_hdisk_ora/lv_hd4
         25 /dev/vg_hdisk_ora/lv_hd7
         26 /dev/vg_hdisk_ora/lv_hd5
         27 /dev/vg_hdisk_ora/lv_hd2
         28 /dev/vg_hdisk_ora/lv_hd8
         29 /dev/vg_hdisk_ora/lv_hd9
         30 /dev/vg_hdisk_ora/lv_hd20
         31 /dev/vg_hdisk_ora/lv_hd18
         32 /dev/vg_hdisk_ora/lv_hd17
         33 /dev/vg_hdisk_ora/lv_hd19
         34 /dev/vg_hdisk_ora/lv_hd16
         35 /dev/vg_hdisk_ora/lv_hd14
         36 /dev/vg_hdisk_ora/lv_hd11
         37 /dev/vg_hdisk_ora/lv_hd13
         38 /dev/vg_hdisk_ora/lv_hd12
          1 /dev/asm-disk1
40 rows selected.1. Why not list only the names of devices UDEV?
2. Is this normal when creating UDEV rules to ASM?
regards
Amin

Two thoughts.
1. Read the FAQ and learn how to post to these forums.
2. Read the Oracle docs where it states:
"The null string; Automatic Storage Management discovery finds all disks in an operating system-specific
location to which the Automatic Storage Management instance has read/write access."

Oracle VM Guest Performance as HVM

All,
I was hoping to get clarification on this:
I happen to have a server with a processor that supports virtual machine in hardware (AMD-V). I have installed a couple of 64-bit OEL5u4 VMs off of the install iso (not from eDelivery templates, but from eDelivery iso). My guess is that these guests think they are using the hardware directly, which, as I undertand gets to be finally handled by qemu-dm in Dom0. Is this an efficient way of doing things with these OEL versions, or should I consider altering the guests so that they can communicate with Dom0 in a more efficient manner? The Oracle web site offers rpms for the guests, but seem to be targetted at OEL5 Update 1. Maybe these improvements are built in OELu4?
FWIW, I ran "hdparm -tT /dev/sda" on the host, and "hdparm -tT /dev/hda" in the guest, and the buffered read performance is worse in the VM by a factor of 5. The way I configured it, hda in the guest maps to a Logical Volume block device on the host, so I was hoping to get much better performance.
Any input welcome.

FWIW, I pursued this by reading the Oracle Server manual again, as well as what I could find from RHEL5. Again, this is trying to configure a guest with paravirtual drivers when the guest is run in full hardware virtualization, in order to retain as much disk performance as possible.
The short of it is that if the vm.vfg file makes use of "xvda" instead of "hda", then OEL5.4 uses the disk in a much more efficient manner (meaning it does a hypercall from DomU to Dom0, so Dum0 stops using the slower emulation in Dom0).
In my case, I chose to map the DomU hard disk to a Logical Volume in Dom0:
disk = [
'phy:/dev/DomUDisk2/LVOracleApp,xvda,w',
In this case, running "hdparm -tT :/dev/DomUDisk2/LVOracleApp" in Dom0 yields to near identical results to running "hdparm -tT /dec/xvda" in DomU. I used to have a loss of a factor 5 with emulation.
If anybody has to retrace my steps and try to replicate this, there are guides out there that mention installing missing paravirtual driver modules in the guest by downloading some rpm. Starting at OEL5.4, they are already there (/lib/modules/2.6.18-164.el5/kernel/drivers/xenpv_hvm/), so no extra rpms are required.
There is one caveat: Booting from xvda using the paravirtual drivers is somewhat less than automatic. Contrary to what you can read, grub does not seem to have a problem locating the kernel and initial ram disk. So, after grub does its thing and gives control to the kernel, the init script in the ram disk tries and locate the root file system. It then scans and finds the hard disk as hda (emulation), eventually mounts it, and runs init off of the disk. This new init has the paravirtual drivers from the hard disk, and finds the SAME DISK as xvda. This cannot be good, although it works and does not seem to thrash the file system as one would think. In order to prevent this from happening, there are a couple of changes to do in the grub configuration file /boot/grub/grub.cfg). The idea is to prevent the kernel from scanning for IDE disks:
kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet hda=noprobe ide0=noprobe
Now, once this is done, we have prevented the kernel from finding the root file system, and this VM is unbootable! The problem is that the initial ram drive does not have the paravirtual drivers built-in, so xvda, with the root file system, cannot be found. Fortunately, adding the paravirtual drivers to the initial ram drive is undramatic:
mkinitrd -f newinitrd 2.6.18-164.el5 --omit-scsi-modules with=xen-vbd with=xen-vnif preload xen-vbd preload xen-vnif*
The newinitrd file can then be copied to /boot with the right name for grub.
I thought I would pass this along as I found that there were great benefits to running the DomUs this way, performance-wise. At this point, I am not sure how these configurations would survive an upgrade of the kernel. I would think that an update to the initrd config file is in order. Thoughts welcome.

Disk Kernell Latency

Similar Messages

Maybe you are looking for