SunCluster rebooting due to faulty quorum device

Hi,
I have a 2 node SunCluster on 2 E2900's running Solairs 10 11/06.
Ive got a problem with the Cluster quorum which I hope someone can assist with�.
Basically, the 2 node cluster has 1 quorum device called d17s2 configured from an EMC SAN and we are using Powerpath, this is a 16GB partition on a separate LUN (previously used for a zone). I added the quorum using clsetup and used the global device d17
The �*scstat �q*� output shows:-
Quorum device added by clsetup�
-- Quorum Summary �
Quorum votes possible:     3
Quorum votes needed:     2
Quorum votes present:     2
-- Quorum votes by node �
          Node Name          Present          Possible     Status
Node votes:     server1          1          1     Online
Node votes:     server2          1          1     Online
-- Quorum Votes by Device --
          Device Name          Present          Possible     Status
Device Votes:     /dev/did/rdsk/d17s2     1          1     Online
When I reboot server1, server2 panics with the following message:-
Panic [cpu1]/thread=300065be060: CMM: Cluster lost operational quorum aborting.
And goes back to the ok prompt..
When both servers reboot the following message appears:-
WARNING: clq_scsi3: Ioctl to register node�s key returned success but read check found that key is not present on quorum device /dev/did/rdsk/d17s2
WARNING: CMM: Registering reservation key on quorum device /dev/did/rdsk/d17s2 failed with error 2
And then they both start up in cluster mode and start the 3 oracle resource groups as they should. I can failover the RG�s and it works ok but as I say when I reboot one of the servers the other one panics as if it can�t see quorum�
Ive googled, am on Sunsolve as I write and it seems to point to a bad quorum device but this is a shared EMC LUN presented and as you can see, im using the global device which I think is correct�
Is there anything I need to ask Storage to do with regard to the LUN presentation..??.. if not how do I fix the faulty quorum device..??.. ive also tried the quorum device on a shared data disk but this give me the same issue..
Thanks in advance..
Steve...

Hi,
there are 2 problems here:
a) you can configure the QD, and it shows as online, but is not counted as being online. You only have 2 out of 3 votes although everything looks ok. That is a bug. If I could reproduce it I would file a bug. But I do not have access to an EMC system.
b) you cannot succesfully configure a QD on an EMC using PP.
There is a document available from EMC that tells you how to configure the storage. The only thing that I found browsing through it, is the PER bit
"Sun Cluster 3.x uses SCSI-3 PGR (persistent group reservation) for
storage devices that are accessible through more than two paths.
Symmetrix systems support this functionality using the PER setting
on the SymmWin Edit Volumes dialog. This flag must be set for all
devices that will be presented to the Sun Cluster nodes."
This is from "EMC host connectivity with Sun SOlaris".
It would be interesting to see what error messages are logged when you first configure the QD.
Then try again with the PER setting. Maybe that is the problem.
The fact that the "other" node panic's with loss of operational quorum is only a logical consequence of what is happening with the QD.
Hartmut

Similar Messages

"clq: (C192716) I/O error." message when trying to add a quorum device

A little bit of history: Recently our storage folks migrated us from CLARiiON LUNs to VNX LUNs on all the shared disks. At the time, the cluster booted fine. However, since all the DID device IDs changed, we no longer have a valid quorum device:
<pre>bash-3.00$ sudo clq list
d11
host2
host1
bash-3.00$ sudo cldev show d11
cldev: (C727402) Could not locate instance "11".
bash-3.00$</pre>
When I try to add another quorum device I get the error shown in the title:
<pre>bash-3.00$ sudo clq add d41
clq: (C192716) I/O error.
bash-3.00$ sudo cldev show d41
=== DID Device Instances ===
DID Device Name: /dev/did/rdsk/d41
Full Device Path: host2:/dev/rdsk/c4t5006016B46E0574Ed0
Full Device Path: host2:/dev/rdsk/c6t5006016946E0574Ed0
Full Device Path: host2:/dev/rdsk/c4t5006016246E0574Ed0
Full Device Path: host2:/dev/rdsk/c6t5006016046E0574Ed0
Full Device Path: host2:/dev/rdsk/c8t5006016346E0574Ed0
Full Device Path: host2:/dev/rdsk/c2t5006016146E0574Ed0
Full Device Path: host2:/dev/rdsk/c8t5006016A46E0574Ed0
Full Device Path: host2:/dev/rdsk/c2t5006016846E0574Ed0
Full Device Path: host1:/dev/rdsk/c2t5006016846E0574Ed0
Full Device Path: host1:/dev/rdsk/c8t5006016A46E0574Ed0
Full Device Path: host1:/dev/rdsk/c2t5006016146E0574Ed0
Full Device Path: host1:/dev/rdsk/c8t5006016346E0574Ed0
Full Device Path: host1:/dev/rdsk/c4t5006016246E0574Ed0
Full Device Path: host1:/dev/rdsk/c6t5006016046E0574Ed0
Full Device Path: host1:/dev/rdsk/c6t5006016946E0574Ed0
Full Device Path: host1:/dev/rdsk/c4t5006016B46E0574Ed0
Replication: none
default_fencing: global
bash-3.00$</pre>
Another issue we are having is that all the shared disks are showing "failed" for their status:
<pre>bash-3.00$ sudo cldev status d41
=== Cluster DID Devices ===
Device Instance Node Status
/dev/did/rdsk/d41 host1 Fail
host2 Fail
bash-3.00$</pre>
The old CLARiiON devices had array failover mode of 1 and the new devices have array failover mode of 4. Anyone know if that is an issue? I have MPxIO disabled in the fp.conf file.
Any assistance would be greatly appreciated.

Here's an update: Had the storage group change the failover mode on the VNX LUNs to mode 1 and everything was happy. All the disk are in the Ok status and I was able to replace the quorum device. Not sure if the C192718 error was due to the status of the disk or the array failover mode...

Error Message: Reboot and Select proper Boot device.

My HP desktop computer (model p6654y) will not boot directly into Windows.
I can ALWAYS make it boot into Windows by first pressing the F10 key to enter the BIOS. If I then exit the BIOS (without even making any changes), the computer will boot into Windows.
If I don't first enter the BIOS, the computer will USUALLY take me to a black screen that says:
"Reboot and Select proper Boot device. Or Insert Boot Media in selected Boot device and press a key."
At this point it won't boot any further.
Also, the last message the BIOS displays (before the error) is:
"00 USB mass storage devices found and configured".
After that, all of the lines of text on the screen move up one level and then the screen goes black and soon after I get the Proper Boot Device error.
I do not have anything plugged into USB ports except an ordinary mouse and ordinary keyboard (both of which I changed - in case they were faulty).
My BIOS is set to boot from the Hard Drive first.
I reset my CMOS.
I do not have a CD in the CD drive.
It used to be that this would ALWAYS happen if I (1) Turned off the Computer, (2) Unplugged it for 60 seconds, (3) Plugged it back in, and (4) Turned it on. Now (after trying various things), it only SOMETIMES happens when I do this.
Any ideas?

Hello @GardenGuy1,
I have read your post on how your desktop computer is having a difficult time booting into Windows, and I would be happy to assist you in this matter!
To further diagnose this issue, I recommend testing the health of your system's hard drive by following the steps in this document on Testing for Hardware Failures (Windows 7). If the hard drive is found to be in good working order, I also suggest restoring your BIOS back to factory settings. This can be done by following this document on Recovering the BIOS.
Please re-post with the results of your troubleshooting, and I look forward to your reply!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

Panic when I try to install Quorum device

Hi,
I am trying to install Sun cluster 3.0 with Clariion.
I can see the same disk in both nodes of the cluster. Even with scdidadm -L, everything looks fine.
But when I try to install the quorum device, I get a panic in one or both servers.
I have check the major and minor number of the devices, but I not sure how is this, and if this is the problem.
Does anybody know about this.?
thanks
Ruben.

This is a difficult question to answer without details
about the messages prior to the panic. The nodes
may be panicing due to the "failfast" panic mechanism
for data protection. If this is the case, then the problem
could be that the Clariion is not properly implementing
the SCSI-2 or SCSI-3 reservation. Please consult your
Clariion support service for information on the use of
the Clariion with Sun Cluster.
-- richard

My daily MBP 15 kernal crash/reboot- due to coreaudiod?

Every day after MBP awakes from sleep mode.... I have to reboot due to a kernal crash.... All patches have been applied... that I know of. I think it has something to do with the NVIDIA GeForce GT 330M card. Seen various posts on this but nothing has worked so far.
Anyone see anything out of place?
Anonymous UUID:
BF53C943-B3D6-498F-9EAD-4CEEDC517BCD
Thu Mar 15 09:01:07 2012
panic(cpu 0 caller 0xffffff80002c266d): Kernel trap at 0xffffff7f8077b9ea, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x0000000108222ab0, CR3: 0x0000000049e4e010, CR4: 0x00000000000206e0
RAX: 0x4451b84c00000000, RBX: 0xffffff802b61d610, RCX: 0x4451b84c00000000, RDX: 0xffffff801586e7c0
RSP: 0xffffff80f265bae0, RBP: 0xffffff80f265baf0, RSI: 0xffffff802b61d610, RDI: 0xffffff801586e7c0
R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0xffffff8015c54c00, R11: 0xffffff800086ef30
R12: 0xffffff8014d9e4a8, R13: 0xffffff8015c54c00, R14: 0xffffff801586b200, R15: 0xffffff8015c54c00
RFL: 0x0000000000010207, RIP: 0xffffff7f8077b9ea, CS: 0x0000000000000008, SS: 0x0000000000000010
CR2: 0x0000000108222ab0, Error code: 0x0000000000000000, Faulting CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff80f265b7a0 : 0xffffff8000220702
0xffffff80f265b820 : 0xffffff80002c266d
0xffffff80f265b9c0 : 0xffffff80002d7a1d
0xffffff80f265b9e0 : 0xffffff7f8077b9ea
0xffffff80f265baf0 : 0xffffff7f8077849c
0xffffff80f265bb10 : 0xffffff7f80779664
0xffffff80f265bb40 : 0xffffff800063a191
0xffffff80f265bba0 : 0xffffff7f807774d6
0xffffff80f265bbe0 : 0xffffff8000637f5b
0xffffff80f265bc20 : 0xffffff7f8077744a
0xffffff80f265bc40 : 0xffffff800065341b
0xffffff80f265bd80 : 0xffffff80002a3b78
0xffffff80f265be80 : 0xffffff8000223006
0xffffff80f265beb0 : 0xffffff8000214829
0xffffff80f265bf10 : 0xffffff800021bb58
0xffffff80f265bf70 : 0xffffff80002aeb80
0xffffff80f265bfb0 : 0xffffff80002d8383
Kernel Extensions in backtrace:
com.apple.iokit.IOAudioFamily(1.8.6f6)[345E325F-3E96-3FEB-8C50-E446305F4ED8]@0xf fffff7f8076f000->0xffffff7f80798fff
dependency: com.apple.kext.OSvKernDSPLib(1.3)[CF50CA5A-4AF6-3E28-B84B-9619535445E7]@0xfffff f7f80769000
BSD process name corresponding to current thread: coreaudiod
Mac OS version:
11D50
Kernel version:
Darwin Kernel Version 11.3.0: Thu Jan 12 18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64
Kernel UUID: 7B6546C7-70E8-3ED8-A6C3-C927E4D3D0D6
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 70732380821375
last loaded kext at 70657253391828: com.apple.iokit.IOAVBFamily
1.0.0d22 (addr 0xffffff7f807dc000, size 36864)
last unloaded kext at 34821678544131: com.apple.iokit.IOAVBFamily
1.0.0d22 (addr 0xffffff7f807dc000, size 36864)
loaded kexts:
com.parallels.filesystems.prlufs
2010.12.28
com.parallels.kext.prl_vnic
7.0 15054.722853
com.parallels.kext.prl_netbridge
7.0 15054.722853
com.parallels.kext.prl_hid_hook
7.0 15054.722853
com.parallels.kext.prl_hypervisor
7.0 15054.722853
com.parallels.kext.prl_usb_connect
7.0 15054.722853
com.vmware.kext.vmnet
3.0.0
com.vmware.kext.vmioplug
3.0.0
com.vmware.kext.vmci
3.0.0
com.vmware.kext.vmx86
3.0.0
com.Cycling74.driver.Soundflower
1.5.1
com.jft.driver.PdaNetDrv
1.0.64
com.apple.filesystems.smbfs
1.7.0
com.apple.driver.AppleHWSensor
1.9.4d0
com.apple.filesystems.autofs
3.0
com.apple.driver.AudioAUUC
1.59
com.apple.iokit.IOUserEthernet
1.0.0d1
com.apple.driver.AppleMikeyHIDDriver
122
com.apple.driver.AppleHDA
2.1.7f9
com.apple.driver.AGPM
100.12.42
com.apple.driver.AppleMikeyDriver
2.1.7f9
com.apple.driver.AppleUpstreamUserClient
3.5.9
com.apple.driver.AppleMCCSControl
1.0.26
com.apple.driver.AppleIntelHDGraphics
7.1.8
com.apple.driver.AppleIntelHDGraphicsFB
7.1.8
com.apple.driver.SMCMotionSensor
3.0.1d2
com.apple.driver.AppleSMCLMU
2.0.1d2
com.apple.Dont_Steal_Mac_OS_X
7.0.0
com.apple.driver.AudioIPCDriver
1.2.2
com.apple.driver.AppleLPC
1.5.3
com.apple.driver.AppleMuxControl
3.0.16
com.apple.GeForce
7.1.8
com.apple.driver.ACPI_SMC_PlatformPlugin
4.7.5d4
com.apple.driver.AppleUSBTCButtons
225.2
com.apple.driver.AppleUSBTCKeyboard
225.2
com.apple.driver.AppleUSBCardReader
3.0.1
com.apple.driver.AppleIRController
312
com.apple.iokit.SCSITaskUserClient
3.0.3
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless
1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib
1.0.0d1
com.apple.BootCache
33
com.apple.iokit.IOAHCIBlockStorage
2.0.1
com.apple.driver.AppleUSBHub
4.5.0
com.apple.driver.AppleSmartBatteryManager
161.0.0
com.apple.driver.AppleFWOHCI
4.8.9
com.apple.driver.AirPort.Brcm4331
513.20.19
com.apple.iokit.AppleBCM5701Ethernet
3.0.8b2
com.apple.driver.AppleEFINVRAM
1.5.0
com.apple.driver.AppleAHCIPort
2.2.0
com.apple.driver.AppleUSBEHCI
4.5.8
com.apple.driver.AppleACPIButtons
1.4
com.apple.driver.AppleRTC
1.4
com.apple.driver.AppleHPET
1.6
com.apple.driver.AppleSMBIOS
1.7
com.apple.driver.AppleACPIEC
1.4
com.apple.driver.AppleAPIC
1.5
com.apple.driver.AppleIntelCPUPowerManagementClient
167.3.0
com.apple.nke.applicationfirewall
3.2.30
com.apple.security.quarantine
1.1
com.apple.driver.AppleIntelCPUPowerManagement
167.3.0
com.apple.iokit.IOAVBFamily
1.0.0d22
com.apple.kext.triggers
1.0
com.apple.iokit.IOSurface
80.0
com.apple.iokit.IOBluetoothSerialManager
4.0.3f12
com.apple.iokit.IOSerialFamily
10.0.5
com.apple.driver.DspFuncLib
2.1.7f9
com.apple.driver.AppleSMBusController
1.0.10d0
com.apple.iokit.IOFireWireIP
2.2.4
com.apple.driver.AppleHDAController
2.1.7f9
com.apple.iokit.IOHDAFamily
2.1.7f9
com.apple.iokit.IOAudioFamily
1.8.6fc6
com.apple.kext.OSvKernDSPLib
1.3
com.apple.driver.ApplePolicyControl
3.0.16
com.apple.driver.AppleSMBusPCI
1.0.10d0
com.apple.driver.AppleGraphicsControl
3.0.16
com.apple.driver.AppleBacklightExpert
1.0.3
com.apple.nvidia.nv50hal
7.1.8
com.apple.NVDAResman
7.1.8
com.apple.iokit.IONDRVSupport
2.3.2
com.apple.iokit.IOGraphicsFamily
2.3.2
com.apple.driver.AppleSMC
3.1.1d8
com.apple.driver.IOPlatformPluginFamily
4.7.5d4
com.apple.driver.BroadcomUSBBluetoothHCIController
4.0.3f12
com.apple.driver.AppleUSBBluetoothHCIController
4.0.3f12
com.apple.iokit.IOBluetoothFamily
4.0.3f12
com.apple.driver.AppleUSBMultitouch
227.1
com.apple.iokit.IOSCSIBlockCommandsDevice
3.0.3
com.apple.iokit.IOUSBMassStorageClass
3.0.1
com.apple.iokit.IOUSBHIDDriver
4.4.5
com.apple.driver.AppleUSBMergeNub
4.5.3
com.apple.driver.AppleUSBComposite
4.5.8
com.apple.iokit.IOSCSIMultimediaCommandsDevice
3.0.3
com.apple.iokit.IOBDStorageFamily
1.6
com.apple.iokit.IODVDStorageFamily
1.7
com.apple.iokit.IOCDStorageFamily
1.7
com.apple.driver.CoreStorage
182.10
com.apple.driver.XsanFilter
403
com.apple.iokit.IOAHCISerialATAPI
2.0.1
com.apple.iokit.IOSCSIArchitectureModelFamily
3.0.3
com.apple.iokit.IOUSBUserClient
4.5.8
com.apple.iokit.IOFireWireFamily
4.4.5
com.apple.iokit.IO80211Family
412.2
com.apple.iokit.IOEthernetAVBController
1.0.0d5
com.apple.iokit.IONetworkingFamily
2.0
com.apple.iokit.IOAHCIFamily
2.0.7
com.apple.driver.AppleEFIRuntime
1.5.0
com.apple.iokit.IOHIDFamily
1.7.1
com.apple.iokit.IOUSBFamily
4.5.8
com.apple.iokit.IOSMBusFamily
1.1
com.apple.security.sandbox
177.3
com.apple.kext.AppleMatch
1.0.0d1
com.apple.security.TMSafetyNet
7
com.apple.driver.DiskImages
331
com.apple.iokit.IOStorageFamily
1.7
com.apple.driver.AppleKeyStore
28.18
com.apple.driver.AppleACPIPlatform
1.4
com.apple.iokit.IOPCIFamily
2.6.8
com.apple.iokit.IOACPIFamily
1.4
Unable to gather system configuration information.Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i7, 2.66 GHz, 8 GB, SMC 1.58f16
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53533531323634485A2D3147314131
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53533531323634485A2D3147314131
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.100.98.75.19)
Bluetooth: Version 4.0.3f12, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet Adaptor (en2), Ethernet, en2
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS725050A9A362, 500.11 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa130000 / 5
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0xfa120000 / 4
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0xfa113000 / 8
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 4
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0xfd110000 / 3

Thanks Linc! :-) We are on to the same solution. In fact, your other advice got me on this path.
Trying to remove all of the following stuff, will have to do it manually.. though I cannot find them anywhere in the Finder... may have to go 'Terminal' on these babies.
com.vmware.kext.vmx86(3.0.0)
com.vmware.kext.vmci(3.0.0)
com.vmware.kext.vmioplug(3.0.0)
com.vmware.kext.vmnet(3.0.0)
com.vmware.launchd.vmware
com.plexapp.mediaserver
com.Cycling74.driver.Soundflower (Not sure where this even came from)
and the PDANet stuff as well
Stay tuned.

Remote system reboots due to error when exporting config.

I have a PXI-8196 controller operating on a network in a PXI-1052 chassis. I am trying to export the config and the remote system reboots due to system error.

Your Computer looks to be a Late 2010 iMac, if so is the RAM spec as shown below?
Maximum Memory
16 GB
Memory Slots
4 - 204-pin PC3-10600 (1333 MHz) DDR3 SO-DIMM

RT target reboots due to system error

The RT target reboots and displays the following error after the normal setup info:
Reboot due to system error.
Redirecting output to log file.
I don't know where this "log file" is saved and I don't know why the rt engine restarts.
I have 3 PCI 6143 boards and I'm reading at 250 ksamples/sec. I'm storing the data to an RT FIFO (waveform dbl array type) and using TCP to send this to the host computer where I want to display in a graph. The vi on the target computer runs fine without any connection to the host computer. When the vi on the host computer starts up, however, problems start to happen.
The host computer gets the data from the target very slowly. It takes about 5 seconds for TCP Read to read the byte size. The byte size is about 600kb. After the byte size is read the rt engine mysteriously restarts and displays the message above. My system works fine if I change all the waveform dbl array types to DBL Array. The reason I want a waveform type is because the host computer is not getting enough data with the DBL Array. For example, instead of getting a steady, straight line in the graph, I get a line jumping from 0 to the value it's supposed to be over and over.
I'm using vis similar to the vis created by the RT Communication wizard for both the target and host communication.

hi Kristi,
thanks for responding.
I'm using Labview 7.1 Real-time on a dell gpx 270 on a LAN (gigabit connection) using static IPs. I'm currently doing continuous analog acquisition on multiple channels (24 total). I have a normal priority loop managing the TCP connection, a time-critical loop within that acquiring data. On the host computer (another dell) I have all normal priority vis. I have 1 VI that contains 2 vis in it- a vi that handles the GUI and a vi that handles the TCP.
I gave up on using waveforms so i'm getting the y-component out of the 1D-waveform that i get from the daqmx vi and putting that into a 1D dbl array and storing it in an rt-fifo. By the upload, hopefully, you can see what i'm talking about. Without using waveforms the rt target does not reboot, but i still get jitter. The host computer (with the gui) seems to be reading an empty fifo more times than it has data. When I put a 100ms wait in the TCP loop on the host computer, I get the data slower, but no jitter. I don't know anything about timing so I'm guessing that's my major problem. Am I supposed to put waits inside of various loops?? I varied my time-critical loop wait time from 1ms to 3ms to see if anything would change, but no changes.
On a side note I will be acquiring data from a total of 13 6143 PCI boards from 5 different PCs when this is all done.
Attachments:
simplesystem.JPG ‏15 KB

Reboot due to system error / Register dump from exception handler

hi,
I have a problem with Labview RT when using Reboot function.
The RT target (desktop) reboot but there is a message : Reboot due to system error. And if I reboot once again, the target become in safe mode.
Now, If I look at the log I obtain the following message see more in the log attached!
*** REGISTER DUMP FROM EXCEPTION HANDLER (code 0x80000003) ***
I don't understand why there is this message.
Anybody has an explaination?
Attachments:
Nouveau Document texte2.txt ‏6 KB

julesjay a écrit:
ok I didn't know that. I will wait for tomorrow.
NI france is not very efficient about labview Real time problems.
There is one or two experts and there aren't easily reachable.
So a lot of question I send stay with no answer.....
That why I hope someone will be able to help me.
Hi Julesjay,
After i have see your log file and the problem, i think NI FRANCE are working on your request for all problems you have in your application.
And i don't understand what you say that, because we have make test, we have send us informations for make different tests, and we are still working on your problem.
I know the problem are not resolved, but we are working for resolve it quickly.
I suggested you to contact the AE that are your service request for have more information.
Best regards,
Christophe S.
FSE East of France І Certified LabVIEW Associate Developer І National Instruments France

Unable to set quorum device

Hi all!
I'm installing SC 3.1 on two sun fire v240 nodes with storedge 3511
When running the 'scsetup' and choosing a quorum device (d4 - see list below), I get error:
scconf -a -q globaldev=d4
scconf: Failed to add quorum device (d4) - global device is not found
DID info:
scdidadm -L
1 v240node2.test.lynx:/dev/rdsk/c0t0d0 /dev/did/rdsk/d1
2 v240node2.test.lynx:/dev/rdsk/c1t0d0 /dev/did/rdsk/d2
3 v240node2.test.lynx:/dev/rdsk/c1t1d0 /dev/did/rdsk/d3
4 v240node2.test.lynx:/dev/rdsk/c3t44d0 /dev/did/rdsk/d4
5 v240node1.test.lynx:/dev/rdsk/c0t0d0 /dev/did/rdsk/d5
6 v240node1.test.lynx:/dev/rdsk/c0t1d0 /dev/did/rdsk/d6
7 v240node1.test.lynx:/dev/rdsk/c2t40d0 /dev/did/rdsk/d7
what is interesting that scdidadm shows different did names (d4,d7) for same shared se 3511 disk. Guess it should bethe same.
Any help on this?

Thanx a lot. I checked this and it turned out that chanels were maped with different partitions of logical drive. Was only my inattention :)

P67a-GD65 (b3) boot problem (reboot and select proper boot device)

Hello All,
I have the following problem;
When I start my computer sometimes it starts normal or I get the following warning;
Reboot and select proper boot device.
If this happens, its stays for a few seconds on A2 at the lower right corner , then MSI mainboard screen, and then the above warning.
When i use the reset button, it starts normal or same problem.Sometimes i need to restart it like 5-7 times to get it started normal.
My system info:
Mainboard: MSI P67A-GD65 (MS-7681)
Chipset: Intel Sandy Bridge
Processor: Intel Core i7 2600K @ 3400MHz
Physical Memory: 4096MB (2 x 2048 DDR3-SDRAM)
Video Card: AMD Radeon HD 6900 Series
Hard Disk: Seagate ST31000528AS ATA Device (1000GB)
Hard Disk: Seagate ST3200822AS ATA Device (200GB)
Hard Disk: Seagate ST3200822AS ATA Device (200GB)
DVD-Rom Drive: XMTQ FGPIR0DURGHI
DVD-Rom Drive: Toshiba Samsung SH-S223C CDDVDW
Monitor Type: LG L1915S - 19 inches
Monitor Type: ACER X233H - 23 inches
Network Card: Microsoft Virtual WiFi Miniport Adapter
Network Card: Wireless-N 300 USB Adapter WNA3100
Operating System: Windows 7 Ultimate Professional, Media Center 6.01.7600 (64 bit)
DirectX: Version 11.00
Windows Performance Index: 5.9 on 7.9
Mainboard bios: 1.9
Hopefully someone can help me.
Thanks,
Tammo

Zalman ZM660-XT
AC Input Range Voltage 100VAC ~ 240VAC ±10% DC Output
Frequency 50Hz~60Hz Output V. Output Load Rating Combined
Power
AC Input Current
(Rated) 115VAC 9.5A Imin Imax Ipeak
230VAC 4A +3.3V 0.8A 30A 35A 155W 660W
PFC Type Active PFC +5V 0.5A 30A 35A
Power Factor 99% Maximum
+12V1 0.5A 20A 22A 636W
Inrush Current Limit
(@ Cold start at 25°C) 115VAC 80A +12V2 0.5A 20A 22A
230VAC 60A +12V3 0.5A 20A 22A
Efficiency 88% Maximum @230VAC, Typical load +12V4 0.5A 20A 22A
DC Output
Voltage
Regulations Output V. Regulation Range At Full
Load -12V 0.0A 0.8A 22.1W
+3.3VDC ±5% +3.14V~+3.47V +5VSB 0.1A 2.5A 3.5A
+5VDC ±5% +4.75V~+5.25V Protection Features
+12V1DC ±5% +11.4V~+12.6V Over Voltage Protection(OVP)
+12V2DC ±5% +11.4V~+12.6V Over Current Protection(OCP)
+12V3DC ±5% +11.4V~+12.6V Short Circuit Protection(SCP)
+12V4DC ±5% +11.4V~+12.6V Over Temperature Protection(OTP)
-12VDC ±10% -10.8V~-13.0V Under Voltage Protection(UVP)
+5VSB ±5% +4.75V~+5.25V Ambient Temperature
DC Output
Ripple
& Noise Output V. Specification At Full
Load Operation 0°C ~ +40°C
+3.3VDC 50mV Storage -20°C ~ +80°C
+5VDC 50mV Ambient Humidity
+12V1&2DC 120mV Operation 5%RH ~ 95%RH
+12V3&4DC 120mV Storage 5%RH ~ 95%RH
-12VDC 120mV Dimensions
+5VSB 50mV 180(L) x 150(W) x 86(H) mm

My MacBook won't start up properly, and I suspect it may be the result of a power surge due to faulty wiring in my apartment. Is this the kind of thing that can typically be repaired, and if so, at what price?

My MacBook won't start properly. It seems to run, but the screen won't light. I suspect the cause is a power surge due to faulty wiring in my apartment. Is this the kind of thing that can typically be repaired, and if so, at what price?

you need to bring it somewhere so it can be determined exactly what is wrong with it and then an estimate can be provided.

I/O error when adding quorum device

Hi all, i'm in the process of building a two-node 3.2 Sun cluster using two HP DL380 servers. I seem to have managed to get the sun cluster 3.2 s/w installed on both nodes but i'm having problems adding a quorum device.
Using either scsetup or clquorum, i get the following error:
# /usr/cluster/bin/clquorum add d4
clquorum: (C192716) I/O error.
Does anyone know what this means?
Thanks in advance,
Stewart
******** Here are my devices ***********
# /usr/cluster/bin/cldevice list -v
DID Device Full Device Path
d1 nfst1:/dev/rdsk/c1t0d0
d2 nfst1:/dev/rdsk/c3t0d0
d3 nfst1:/dev/rdsk/c2t5006016A106023E0d4
d3 nfst1:/dev/rdsk/c2t50060162106023E0d4
d3 nfst2:/dev/rdsk/c2t50060160106023E0d4
d3 nfst2:/dev/rdsk/c2t50060168106023E0d4
d4 nfst1:/dev/rdsk/c2t5006016A106023E0d3
d4 nfst1:/dev/rdsk/c2t50060162106023E0d3
d4 nfst2:/dev/rdsk/c2t50060160106023E0d3
d4 nfst2:/dev/rdsk/c2t50060168106023E0d3
d5 nfst1:/dev/rdsk/c2t5006016A106023E0d2
d5 nfst1:/dev/rdsk/c2t50060162106023E0d2
d5 nfst2:/dev/rdsk/c2t50060160106023E0d2
d5 nfst2:/dev/rdsk/c2t50060168106023E0d2
d6 nfst1:/dev/rdsk/c2t5006016A106023E0d1
d6 nfst1:/dev/rdsk/c2t50060162106023E0d1
d6 nfst2:/dev/rdsk/c2t50060160106023E0d1
d6 nfst2:/dev/rdsk/c2t50060168106023E0d1
d7 nfst1:/dev/rdsk/c2t5006016A106023E0d0
d7 nfst1:/dev/rdsk/c2t50060162106023E0d0
d7 nfst2:/dev/rdsk/c2t50060160106023E0d0
d7 nfst2:/dev/rdsk/c2t50060168106023E0d0
d8 nfst1:/dev/rdsk/c2t5006016A1060235Dd3
d8 nfst1:/dev/rdsk/c2t500601621060235Dd3
d8 nfst2:/dev/rdsk/c2t500601681060235Dd3
d8 nfst2:/dev/rdsk/c2t500601601060235Dd3
d9 nfst1:/dev/rdsk/c2t5006016A1060235Dd2
d9 nfst1:/dev/rdsk/c2t500601621060235Dd2
d9 nfst2:/dev/rdsk/c2t500601681060235Dd2
d9 nfst2:/dev/rdsk/c2t500601601060235Dd2
d10 nfst1:/dev/rdsk/c2t5006016A1060235Dd1
d10 nfst1:/dev/rdsk/c2t500601621060235Dd1
d10 nfst2:/dev/rdsk/c2t500601681060235Dd1
d10 nfst2:/dev/rdsk/c2t500601601060235Dd1
d11 nfst1:/dev/rdsk/c2t5006016A1060235Dd0
d11 nfst1:/dev/rdsk/c2t500601621060235Dd0
d11 nfst2:/dev/rdsk/c2t500601681060235Dd0
d11 nfst2:/dev/rdsk/c2t500601601060235Dd0
d12 nfst1:/dev/rdsk/c2t5006016830220BA0d0
d12 nfst1:/dev/rdsk/c2t5006016130220BA0d0
d12 nfst2:/dev/rdsk/c2t5006016930220BA0d0
d12 nfst2:/dev/rdsk/c2t5006016030220BA0d0
d13 nfst2:/dev/rdsk/c1t0d0
d14 nfst2:/dev/rdsk/c3t0d0
Cluster DID Devices ===
Device Instance Node Status
/dev/did/rdsk/d10 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d11 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d12 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d14 nfst2 Ok
/dev/did/rdsk/d2 nfst1 Ok
/dev/did/rdsk/d3 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d4 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d5 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d6 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d7 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d8 nfst1 Ok
nfst2 Ok
/dev/did/rdsk/d9 nfst1 Ok
nfst2 Ok

Hi All,
I have a very similar problem, maybe someone has seen it ?
I'm trying to finish installation of Sun Solaris 3.2 on two Sun-Fire-V240s (HBAs are QLogic QLA2342) over SPARC Solaris 10.
When I get to the stage of adding a quorum disk to Sun Cluster 3.2:
# scconf -a -q globaldev=d24
the following error is received:
scconf: Failed to add quorum device (d24) - unable to scrub the device.
I ran the commands:
# scdidadm -r
# scdidadm -i
# scdidadm -L
Where the d24 is as follows:
# scdidadm -L
24 SRV-00-003:/dev/rdsk/c5t128d41 /dev/did/rdsk/d24
24 SRV-00-049:/dev/rdsk/c5t128d41 /dev/did/rdsk/d24
# ls -ls /dev/did/rdsk/d24
2 lrwxrwxrwx 2 root root 42 Apr 7 13:40 /dev/did/rdsk/d24 -> ../../../devices/pseudo/did@24:24,24s7,raw
Format describes the disk as:
Current Disk = c5t128d40
<StoreAge-rbarak_vol40_clu-#12 cyl 98 alt 2 hd 4 sec 512>
/pseudo/vhba@0/vsd@80,28
I Googled the net, and beside references to disks bigger than 1 GB, I couldn't find any relevant suggestions.
Anyone has any experience with this "unable to scrub the device" error ?
Thanks,
Ron.

Satellite C660: message: reboots and select proper boot device

Hello,
I dropped the laptop today literally a few inches from the floor, it slipped from my hands as I was placing it on the floor. It fell flat.
I am now seeing the message "reboot and select proper boot device"
I have tried a few different options that I have read, and I can see the HDD in the F2 BIOS thing...or whatever it is called. So it is being recognised, but I can't seem to get around the message. Any suggestions?
Thanks in advance.
PS I will need clear instructions, I'm not stupid, but I need things explaining. I do understand some bits and pieces.
Thanks

Hi
Thanks for your reply. I already looked at BIOS and saw the hard drive make/model etc listed, but it wouldn't boot from it.
I took it to a local shop today and they had run diagnostics on the hard drive and say that no data can even be recovered.
Devastated. I was really hoping it would be ok at least for data recovery because the laptop was still recognising it.
Does anyone know if this is definitely going to be the case?
Are the shop being truthful?
Thanks

[Solved]Unbootable fresh intall - reboot and select proper boot device

Hello, this is not my first Arch Linux installation, but it is my first time posting to the forums. I just completed my second attempt at installing Arch on a brand-new Toshiba Satellite C55. After the installation completes and I reboot, instead of Grub I get a blank screen with this message:
Reboot and select proper Boot device
or Insert Boot Media in selected Boot device and press a key
I thought maybe I made a mistake, so I started over and completed a second installation, only to get the same message. I am not sure how to proceed. I tried booting from a xubuntu live usb I had lying around, and it doesn't recognize that either, although it does recognize my Arch live usb.
Any ideas?
Last edited by zevski (2015-04-29 03:05:31)

UPDATE: I erased the entire disk with
sgdisk -Z
and reinstalled again, this time creating only a boot partition and a root partition for the rest . Installed gummiboot instead of GRUB. This time it worked, so I know that at least I did not brick my machine.
I don't know if erasing the disk did the trick (since this machine had previously had Windows 8 on it, and may have had something "leftover"), or if I had made a mistake during the partition or when mounting the partitions (I noticed an error in my fstab the third time around, so I started over ,again, and the fourth time it worked).
Just thought I would post this in case any other newbies run into the same issue.

MSI B75MA-P45 "Reboot and Select proper Boot device"

Hey guys, I just had this PC delivered to me yesterday, pre-built after my specs. Been using their company for a decade and never had an issue (that said, they might very well have screwed up this time, but I would love some feedback).
So, when I plug in the PC and boot it it get stuck at "Reboot and Select proper Boot device" (and in the bottom right it blink between A2/B4 before it gets to the reboot prompt).
What I have done to try to fix this:
1) Go into BIOS and swap around the boot order. No luck with that, and I cannot find the SSD HD on the list either.
2) Confirmed it was set on AHCI mode.
3) Booted with the MSI Motherboard CD to get to Winki. In the Winki file manager I do see the SSD HD with Windows installed! But the BIOS cannot find it.
The specs:
Board: MSI B75MA-P45
Bios: E7798IMS V1.5
VGA: ASUS Geforce GTX660Ti
PSU: Corsair CX 500
Intel Core i7-3770
Corsair Cooling Hydro H55
RAM: Corsair XMS3 Vengeance CL9
Samsung SSD 840 Series 120 GB
Seagate Barracuda 2TB
Win 8
So I'm left a bit dumbstruck here. It seems quite clear the BIOS cannot find the SSD for some reason, but I'm not sure how to sort this?
I mean: I do see Windows in the Winki file manager, so the HD is clearly there and readable. But on the other hand it cannot find it in the BIOS so I can't choose it as a boot drive.
Any suggestions on what might cause this and how I could solve it?
Thank you.

Wow, that was easier than I thought.. after hours of browsing internet, trying all kinds of BIOS settings, eventually I just opened the case and plugged out the SATA cables and plugged them back in. Boom, it works. Didn't expect it to be that easy since the Winki still could see the HD.
Seems BIOS is more sensitive than the Winki. But there you go, problem solved.

SunCluster rebooting due to faulty quorum device

Similar Messages

Maybe you are looking for