• RELEVANCY SCORE 4.46

    DB:4.46:Probe-Scsi-All Returns Incomplete Path f7





    I have a Blade 2500 I want to install Solaris 10 on.
    I don't think the blade is giving me the entire path
    to a device. What I have is an external DVD-ROM drive
    that is connected to the onboard SCSI bus. I can see
    the device with a probe-scsi-all, but probe-scsi-all
    only returns /pci@1e,600000/pci@3/scsi@2,1 which I think is
    an imcomplete path. I've tried
    /pci@1e,600000/pci@3/scsi@2,1/sd@3,0 and that doesn't work.
    I've tried other combinations as well.

    Any ideas?

    DB:4.46:Probe-Scsi-All Returns Incomplete Path f7

    I got the problem solved. What worked was appending disk@3,0:f to the end of the devalias path, so you would have this:

    /pci@1e,600000/pci@3/scsi@2,1/disk@3,0:f

  • RELEVANCY SCORE 2.81

    DB:2.81:Re: Bad Day!! 1s





    Look around in the OBP: compare the output of "probe-scsi-all" with your devalias for "disk"...

    The path you're using for the alias "disk" should be shown in the probe output. If it isn't, then something about your setup has definately changed.

    DB:2.81:Re: Bad Day!! 1s

    I am no sun. However i work with a sun partner. Because i love this name, that's why i included it in my nick.

  • RELEVANCY SCORE 2.67

    DB:2.67:Probe-Scsi-All Can Detect 3511 Storage But Not Format 7m





    Hi,
    I have an E2900 server connected with a Sun StorEdge 3511 by a dual FC card.I can detect the 3511 drives from probe-scsi-all but not from format.I am using solaris 9 O/S.
    Any help or suggestions would be of great help.
    regards
    Moin

    DB:2.67:Probe-Scsi-All Can Detect 3511 Storage But Not Format 7m

    c6 fc connected unconfigured unknownSo I'd try a 'cfgadm -c configure c6' and see if the disk(s) appear in cfgadm -l output, then do a 'devfsadm' to bring it into format.

    --
    Darren

  • RELEVANCY SCORE 2.66

    DB:2.66:Scsi Probe 4times..Why? xx


    Hi,
    My .conf looks like this.....

    name = "mydriver" class="scsi"
    target=0 lun=0
    ---
    ---
    --
    target=15 lun=0
    /*added my stuff here*/
    blocks_per_bit=16
    bm_shift=10
    ....etc

    why add_drv or drv_config is calling my probe routine 4times for 15 targets? totally, it is calling my probe routine 60 times.

    can any one help me in this ?

    thanks
    kiran

    DB:2.66:Scsi Probe 4times..Why? xx

    Hi,
    My .conf looks like this.....

    name = "mydriver" class="scsi"
    target=0 lun=0
    ---
    ---
    --
    target=15 lun=0
    /*added my stuff here*/
    blocks_per_bit=16
    bm_shift=10
    ....etc

    why add_drv or drv_config is calling my probe routine 4times for 15 targets? totally, it is calling my probe routine 60 times.

    can any one help me in this ?

    thanks
    kiran

  • RELEVANCY SCORE 2.65

    DB:2.65:Storedge 3310 Read Error zx


    I've just installed 5 new Sun 146GB 10K drives in my SE3310, attached to a Sun 280R. The install and LUN setup went fine, format went fine, but I'm getting this error on the console and in /var/adm with some frequency:

    Sep 10 08:59:12 onestop scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4/sd@0,1 (sd74):
    Sep 10 08:59:12 onestop incomplete read- retrying
    Sep 10 09:11:28 onestop scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4/sd@0,0 (sd36):
    Sep 10 09:11:28 onestop incomplete read- retrying

    Firmware version is 3.250.

    What's this telling me?

    Thanks,
    Harry

    DB:2.65:Storedge 3310 Read Error zx

    I've just installed 5 new Sun 146GB 10K drives in my SE3310, attached to a Sun 280R. The install and LUN setup went fine, format went fine, but I'm getting this error on the console and in /var/adm with some frequency:

    Sep 10 08:59:12 onestop scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4/sd@0,1 (sd74):
    Sep 10 08:59:12 onestop incomplete read- retrying
    Sep 10 09:11:28 onestop scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@1/scsi@4/sd@0,0 (sd36):
    Sep 10 09:11:28 onestop incomplete read- retrying

    Firmware version is 3.250.

    What's this telling me?

    Thanks,
    Harry

  • RELEVANCY SCORE 2.60

    DB:2.60:Ace: How Do I Check What Status Code Does Url Returns s1



    Hi,

    I'm doing health check using probes where I'm checking urls.

    how do I check which status code does URL return so that I can put that code in "expect status" of the probe (so probe succeeds).

    when to use "request method get", "request method head" and " header Host header-value"

    DB:2.60:Ace: How Do I Check What Status Code Does Url Returns s1


    Hi Gavin,

    If it is an HTTP web server, you can try this from the ACE itself:

    10.198.16.92 is my server.

    ACE-4710A/Admin# telnet 10.198.16.92 80

    Trying 10.198.16.92...

    Connected to 10.198.16.92.

    Escape character is '^]'.

    GET / http ----------------------------------- I typed this

    HTTP/1.1 200 OK ------------------------ here is the http code response

    Date: Mon, 05 Sep 2011 15:06:00 GMT

    Server: Apache/2.2.8 (Win32)

    Last-Modified: Wed, 23 Dec 2009 00:47:10 GMT

    ETag: "1c00000001e576-f8-47b5aa9a0fc89"

    Accept-Ranges: bytes

    Content-Length: 248

    Connection: close

    Content-Type: text/html

    NSS SITE

       http://10.198.16.92/links.html"

       http://10.198.16.92/search.html"

    Connection closed by foreign host.

    ACE-4710A/Admin#

    Regarding your other questions:

    when to use "request method get", "request method head" and " header Host header-value" methods?

    HTTP GET request method to direct the server to get the page.

    HTTP HEAD request method to direct the server to get only the header for the page.

    And the host header values is used in case you want the ACE to use an specific host on the probe itself, by default the ACE is going to use the server IP as the host on the probe connections, there are some server/app the does not like this, and they reject the probe because of this.

    In order to avoid this we can modify the host header, so the ACE will use a different host value instead of the server IP address.

    Hope this help.

    Rodrigo

  • RELEVANCY SCORE 2.53

    DB:2.53:Question About Scsi Devices cj


    Hi,

    On a HP-ux system i can do an ioscan.
    On a sun system i've to bring down the system to the OK prompt and type probe-scsi
    Also on solaris with legato networker i can use /etc/LGTOuscsi/inquire

    But if i don't have legato networker on my system and i'm not allowed to shut down the system how can i get this information from my sun solaris system?

    Jan Holtrop

  • RELEVANCY SCORE 2.53

    DB:2.53:Sun Storedge 2u Sdlt 600 Tape Drive Install Issue 7x


    After installing the tape drive and doing a scsi probe I get the following errors:

    ERROR: LSI1030 MPT FIRMWARE, FAULT CODE:
    8112: PCI BUS FAULT

    ERROR: LSI 1030 COULD NOT SET INITIATOR ID.
    CANT OPEN SCSI HOST ADAPTER.

    What would cause this? hardware is brand new also.

    DB:2.53:Sun Storedge 2u Sdlt 600 Tape Drive Install Issue 7x

    After installing the tape drive and doing a scsi probe I get the following errors:

    ERROR: LSI1030 MPT FIRMWARE, FAULT CODE:
    8112: PCI BUS FAULT

    ERROR: LSI 1030 COULD NOT SET INITIATOR ID.
    CANT OPEN SCSI HOST ADAPTER.

    What would cause this? hardware is brand new also.

  • RELEVANCY SCORE 2.53

    DB:2.53:Problems With Vnx And Ndmp-Devices 3f



    Hi,

    We have a setup with 1 datamover connected to a HP D2D VTL.

    After a reboot of the VTL, the VTL is not visible by the datamover anymore.

    I have rebooted the mover with the following commands:

    server_cpu server_2 -reboot -monitor now

    This "probe"-command shows nothing

    server_devconfig server_2 -probe -scsi -nondisks

    As does the

    server_devconfig server_2 -list -scsi -nondisks

    All HBAs both on the mover and vtl is online on the SAN-switches.

    I have tried to zone the VTL with my backupserver - the VTL comes up immediately. How can I troubleshoot this problems?

    best regards

    avik

  • RELEVANCY SCORE 2.53

    DB:2.53:Little Stops In The Mail Server 83


    Hi,

    I've noted that, one of my mail server stops for 10 minutes aproximadetly and then return as normal . I dont know why. If I see logs, I see all as normal. It happen in every hour, 10 minutes aprox.

    I attach a graph of the CPU and Network and you will see the stops of the server.

    http://dathvader.galenics.net/stop.png

    I reboot the machine serveral times but nothing happen.

    Where is the problem?

    If I execute dmesg command, I can see the following:

    +or SCSI Domain = 2+
    +Discovery condition = 0x00000000+
    +Jettisoning kernel linker.+
    +Resetting IOCatalogue.+
    +Matching service count = 0+
    +Matching service count = 0+
    +Matching service count = 0+
    +Matching service count = 0+
    +Matching service count = 0+
    +Matching service count = 0+
    +Matching service count = 1+
    +Xserve2,1: stalling for module+
    +Xserve2,1: stalling for module+
    +Xserve2,1: stalling for module+
    +ACPISMC_PlatformPlugin::getCPUPSSData - WARNING: _PSS table invalid; ACPI is probably incomplete+
    +ACPISMC_PlatformPlugin::getCPUPSSData - WARNING: _PSS table invalid; ACPI is probably incomplete+
    +ACPISMC_PlatformPlugin::getCPUPSSData - WARNING: _PSS table invalid; ACPI is probably incomplete+
    +ACPISMC_PlatformPlugin::getCPUPSSData - WARNING: _PSS table invalid; ACPI is probably incomplete+
    +ACPISMC_PlatformPlugin::getCPUPSSData - WARNING: _PSS table invalid; ACPI is probably incomplete+
    +ACPISMC_PlatformPlugin::getCPUPSSData - WARNING: _PSS table invalid; ACPI is probably incomplete+
    +ACPISMC_PlatformPlugin::getCPUPSSData - WARNING: _PSS table invalid; ACPI is probably incomplete+
    +ACPISMC_PlatformPlugin::getCPUPSSData - WARNING: _PSS table invalid; ACPI is probably incomplete+
    +Previous Shutdown Cause: 5+
    +Apple16X50ACPI1: Identified Serial Port on ACPI Device=UAR1+
    +Apple16X50ACPI::start FOUND DB9 Property for AAPL,connector+
    +Apple16X50UARTSync: Detected 16550AF/C/CF FIFO=16 MaxBaud=115200+
    +Matching service count = 1+
    AppleTyMCEDriver::probe(Xserve2,1)
    +AppleTyMCEDriver::probe fails+
    +AppleIntel8254XEthernet: Ethernet address 00:1e:52:f3:72:c0+
    +AppleIntel8254XEthernet: Ethernet address 00:1e:52:f3:72:c1+
    +Ethernet [Intel8254x]: Link up on en0, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [792d,af08,0de1,0e00,cde1,3800]+
    +Ethernet [Intel8254x]: Link up on en1, 1-Gigabit, Full-duplex, No flow-control, Debug [792d,ac48,0de1,0e00,c1e1,7800]+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +ALF ALERT: sockwallcntlupdaterules ctl_enqueuedata rts err 55+
    +serialnumberd 434 FSWRITEDATA SBF /dev/dtracehelper 13 (seatbelt)+
    +serialnumberd 434 FSREADDATA SBF /dev/autofs_nowait 13 (seatbelt)+
    +serialnumberd 434 FSREADDATA SBF /usr/sbin 13 (seatbelt)+
    +ALF: ifnetget_address_listfamily error 12+
    +Limiting closed port RST response from 276 to 250 packets per second+
    +Limiting closed port RST response from 293 to 250 packets per second+
    +Limiting closed port RST response from 263 to 250 packets per second+
    +Limiting closed port RST response from 277 to 250 packets per second+
    +Limiting closed port RST response from 262 to 250 packets per second+
    +Limiting closed port RST response from 273 to 250 packets per second+

    Any Clue?

    Thanks for all.

    DB:2.53:Little Stops In The Mail Server 83

    hi,

    you are the machine, pterobyte.

    Like u said, the reason of the slowdown was because the amount of junk Mail in /var/virusmails.

    We had recently a spam attack and we have many junk emails in that directory, aproximadetly 80000 mails.

    Again, thanks for ur clues and help.

    Bye!!!

  • RELEVANCY SCORE 2.51

    DB:2.51:Probe Http In Ios Slb 9s



    Hi,

    I have the following problem. The configuration of the probe is:

    ip slb probe test http

    request method GET url /test/test1/default.css

    port 80

    But the SLB provides probe only for directory /test/ not for whole path (URL). :-( It is seen from the sniffer:

    GET /test/ HTTP/1.1

    Is this a bug in the IOS or the URL is only for root directory?

    DB:2.51:Probe Http In Ios Slb 9s


    hi,

    can u see any message in web server log file?

    I tried the same config and I got correct url path in http request:

    -- ip slb config --

    ip slb probe TEST http

    request url /keepalive/sub/keepalive.txt

    interval 10

    -- apache log --

    192.168.211.1 192.168.211.12 - - [25/Jul/2007:16:55:05 +0200] "GET /keepalive/sub/keepalive.txt HTTP/1.0" 200 7

    -- ios version --

    12.2(18)SXF7

    --

    martin

  • RELEVANCY SCORE 2.51

    DB:2.51:Cannot Boot Solaris 8(Sparc) Flar pj


    We have a Solaris 8 Flash Archive (.flar file) that when we recover and boot it, it mounts the root slice, but can't mount the other slices, and when I do a "format" it say's "No disks found!". At the OBP, when I do a "show-disks" or "probe-scsi" or "probe-scsi-all" I can see the two disks. When I boot from a Solaris 10 boot CD, I can see the disks.

    What's going on? Is the "/etc/path_to_inst" and the "/dev/rdsk" and "/dev/dsk" files and dirs corrupted?

    DB:2.51:Cannot Boot Solaris 8(Sparc) Flar pj

    Hi.

    It's look like flar archive don't contetns all required drivers for used platform.

    This flar was prepared on this system or on another ?

    What system ?

  • RELEVANCY SCORE 2.51

    DB:2.51:Problem Access Local Storage Seagate Scsi Disks k9



    I have installed ESXi 4.0 (build 164009) on a Supermicro AS-1040C-8B server in my QA environment.

    I have installed 3 local SCSI U320 disks (SCSI ID0: Seagate ST3300007LC (ESXI is installed here), SCSI ID1: Seagate ST3300655LC, SCSI ID2: Seagate ST3300655LC). HostRAID on the onboard Adaptec AIC-7902 controller is disable. At boot all 3 disk are recognised correctly by the Adaptec SCSI configuration utility. They were all formated individually with the Adaptec SCSI configuration utility.

    With ESXi installed only one of the Seagate ST33000655LC is recognised. The path to the second ST3300655LC disk returns status dead (See attached images). If I boot ESXi with only one of the ST3300655LC install it recognise the disk fine (works for either of these disks in SCSI slot 1 or 2. Just only sees one when both are installed together).

    Any ideas what is going on?

    On vSphere Client gt; Configuration gt; Storage Adapters page the controller device is listed as AIC-8902 U320 OEM even though the motherboard chipset is AIC-7902. Could this be a problem?

    Also the device name returned for the ST3300655LC is naa.500000000000000 which seems strange. I would expect more of a random number.

    Any pointers to why I am having problems with the using 2 Seagate ST3300655LC disks together within the 1 server?

    DB:2.51:Problem Access Local Storage Seagate Scsi Disks k9


    Looking at the the drivers it appears that they both 7902 and 8902 take the same driver so it may not make a difference. I would do some more firmware checking. From my dealings in the past Supermicro was not all that responsive but if pushed they did have other versions available. The lack of support beyond the day you bought it was what drove me to only buying 1st tier servers.

  • RELEVANCY SCORE 2.51

    DB:2.51:Path.Getinvalidfilenamechars Incomplete ma


    Is it intently that Path.GetInvalidFileNameChars returns a non-complete list of characters invalid for filenames on Windows systems? I've just discovered that * (asterisk) is not a valid character, yet it is not listed by Path.GetInvalidFileNameChars and trying to create a file with an asterisk in the filename will result in an ArgumentException, trace: at System.IO.Path.CheckInvalidPathChars(String path) at System.IO.Path.GetFileName(String path) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options) at System.IO.File.Create(String path) I'm confused since CheckInvalidPathChars seems to know what chars are invalid yet GetInvalidFileNameChars does not?

    DB:2.51:Path.Getinvalidfilenamechars Incomplete ma

    By the way... Path.GetInvalidFileNameChars should return an asterisk as one of the characters.  It's GetInvalidPathChars() that does not.David Morton - http://blog.davemorton.net/ - @davidmmorton

  • RELEVANCY SCORE 2.50

    DB:2.50:Sparc Station 10 External Scsi Problems f8


    Hi folks,
    i have installed Solaris 8 (10/01) on a Sparc Station 10.
    All worked fine, except, that only 2 drives from the external SCSI-Array (4 drives ) are recognized by the system.
    The format-command hangs for more than 5 Minutes after starting it and then displays ALL drives, but 2 of the
    ext. are shown as unknown drivetype.
    In the diag probe-scsi-all, all drives are showed correctly.
    The SCSI configuration: 3 SCSI Controllers .
    2 internal HD's (1.0 GB) and (i hope for the future) 4
    external. CDROM is attach one the external connector
    from the internal drivecontroller.

    Any ideas... ?

    Thx in adavance.

    Peter
    peter.menges@ems-ag.de

    DB:2.50:Sparc Station 10 External Scsi Problems f8

    I have forgot one info: I have tested all drives using an
    E450 System. All looks fine.
    So, it looks not like a hardware problem.

    Peter

  • RELEVANCY SCORE 2.50

    DB:2.50:Installing A Scsi Controller Card k8


    We are trying to install a Symbios Logic dual channel SCSI card to a Sun Ultra 10 client workstation. We can not get the system to recognize the card. At first, we performed a "probe-scsi-all" and "boot -r". When that didn't work, we decided to reload the Sun Solaris 2.6 operating software. This too, did not work. Please respond with the step(s) we are obviously missing.
    Thanks,
    V. Gier

    DB:2.50:Installing A Scsi Controller Card k8

    When you ran probe-scsi-all, was the scsi controller seen? If the controller was not seen at that point, there is nothing you can do in Solaris to make the card be seen.

    Is the card from Sun? Do you see a sun part number on it? It would be on a small sticker that also has a barcode on it.

  • RELEVANCY SCORE 2.49

    DB:2.49:Ace Probe j3



    Hi,

    i've requirement to declare probe as sucess of url returns 200 OK or 302 or string value. any of this status would declare probe as sucess.

    probe http status1

    request method head url /um/load

    expect status 200 200

    expect status 302 302

    expect regex string value

    open 1

    would this be enough to meet my requirement? please advise.

    DB:2.49:Ace Probe j3


    Hi,

    This will not work.

    From the manual section on configuring probes.

    "An HTTP probe establishes a TCP connection and issues an HTTP request to the server for an expected string and status code. The ACE can compare the received response with configured codes, looking for a configured string in the received HTTP page, or verifying hash for the HTTP page. If any of these checks fail, the server is marked as failed.

    For example, if you configure an expected string and status code and the ACE finds them both in the server response, the server is marked as passed. However, if the ACE does not receive either the server response string or the expected status code, it marks the server as failed."

    You can configure multiple status ranges, but you can't mix them with the regex.  If you wanted to do this then you would need to write a custom tcl script. Your probe will succeed only if  (return status is 200 or 302) AND the regex is matched.

    HTH

    Cathy

  • RELEVANCY SCORE 2.46

    DB:2.46:Problems With Storeedge 3310 s9


    I am at my wit's end with this problem.

    Our company just completed an upgrade in that we added an extra 3310 to 2 database servers. They are both v480s with StorEdge 3310s connected to a SCSI-3 controller (the one with the qus). The operating system is Solaris 8.

    Here's the problem: We added an extra 3310 to each dbase server, with each 3310 unit taking its own controller port. When we did a boot -r, one server came up fine and saw the new disks, while the other one did not see it. Not only that, but it did not see the old disk array either.

    We checked the sd.conf, added some new targets and LUNs and rebooted. We managed to see the new disk array, but still no old disk array. We uninstalled and reinstalled the qus driver, with both 32 and 64-bit drivers. No luck.

    We created a brand-new sd.conf with possibly the longest set of LUNs and targets ever. Nothing.

    probe-scsi-all sees the drives with no problem.

    We noticed one message during bootup:
    Command not Completed: Potential data path failure: resp-resp_reason = 0x1d: pkt-pkt_state = 0x7: pkt-pkt_reason = 0x3: tgt = 0

    That looks like the qus driver is having problems with even passing a command. We changed the cables and even swapped out the backplanes on the 3310s. No luck.

    We even went as far as upgrading the operating system to Solaris 9. No luck. Installed 9_Recommended. No luck.

    cfgadm -al does not see the drives.

    I don't think the hardware is bad, since probe-scsi-all at the OpenBoot prompt sees the drives.

    Any help at all would be appreciated. I have hammered at this for nearly 14 hours now.

    DB:2.46:Problems With Storeedge 3310 s9

    oooo this is a little late coming in(a month?). Sorry about that, but the result should have been to update the qus driver patch, replace the SCSI adapter, replace the 3310 IO board( you said the midplane, which I find odd since its a packet transfer problem, and there is a scsi chip on that IO board, I'll wager...)

    hopefully a call with sun service was performed.

  • RELEVANCY SCORE 2.46

    DB:2.46:Can You Probe For Scsi Devices While Kernel Is Up And Running? 99



    I have a tape drive attached, and for some reason LUN 1 of vmhba1 was not recognized.(There SHOULD be vmhba1:5:0:0 and then vmhba1:5:1:0. Is there anyway to probe for new devices, etc or is this at the BIOS level that the scan would first need to be initialized.?

    Message was edited by:

    mattssi

  • RELEVANCY SCORE 2.46

    DB:2.46:Serious Issue With Ibm Ds4400 And Multiple San Connected Boxes jf



    Hi everyone,

    We are have having issues with our IBM san and 2-3 ESX 2.5.3 connected boxes.

    Things will be running fine for several days then HP Insight manager notifies us of a a device change on all the HBA's located in the ESX boxes.

    If we log into the esx host, SAN related commands are impossible to use. Huge timeouts exist when running commands like 'vmkmultipath -q' or 'vdf' or browsing the /vmfs volume which is located on the SAN.

    We are running dual HBA QLogic 2343s. The only way to recover from this error is to disconnect 1 HBA temporarily, allow for a failover to occur then reconnect the HBA and things are ok.

    vmkmultipath before disconnection of 1 hba

    Disk vmhba1:0:2 (307,196 MB) has 2 paths. Policy is mru.

    vmhba1:0:2 on (preferred, active)

    vmhba2:0:2 on ()

    vmkmultipath after disconnection of 1 hba

    Disk vmhba1:0:2 (307,196 MB) has 2 paths. Policy is mru.

    vmhba1:0:2 on (preferred)

    vmhba2:0:2 on (active)

    We have tried setting our prefered/active path to path 2 but after a few days it will have the issue again and we are required to unplug again, thus the process starts again.

    When the issue is happening /var/log/vmkernel goes nuts on all machines. Some logs are as follows:

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:25.676 cpu0)Helper: 485: 3: status=1 func=0x41396c since=35878818141360

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:25.676 cpu0)Helper: 485: 6: status=2 func=0x4144fc since=35013600422361

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:25.676 cpu0)ALERT: Helper: 995: making request(0x4144fc) async.

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:25.676 cpu0)VMNIX: VMFS: 446: timed out

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.115 cpu0)WARNING: SCSI: 5912: READ of handleID 0x7e6

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.116 cpu0)SCSI: 8879: vmhba1:0:2:1 status = 0/3 0x0 0x0 0x0

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.116 cpu0)SCSI: 8955: vmhba1:0:2:1 Retry (abort after timeout)

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.116 cpu0)WARNING: SCSI: 2555: vmhba1:0:2:1 Abort cmd due to timeout, s/n=62812, attempt 1

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.116 cpu0)LinSCSI: 3361: Aborting cmds. with originSN 62812 from vmhba1:0:2

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.116 cpu0)WARNING: SCSI: 2565: vmhba1:0:2:1 Abort cmd on timeout succeeded, s/n=62812, attempt 1

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.116 cpu0)WARNING: SCSI: 5663: vmhba1:0:2:1 status = 0/2 0x0 0x0 0x0

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.116 cpu0)SCSI: 8879: vmhba1:0:2:1 status = 0/2 0x0 0x0 0x0

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.116 cpu0)SCSI: 8905: vmhba1:0:2:1 Retry (busy)

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.171 cpu0)WARNING: SCSI: 6042: returns 0xbad0004 for vmhba1:0:2

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.171 cpu0)WARNING: FS2: 1690: error 0xbad0004

    Sep 1 14:15:56 cbret070 vmkernel: 0:02:46:26.171 cpu0)WARNING: FS2: 1766: error flushing file descriptor 0.15

    Sep 1 14:16:36 cbret070 vmkernel: 0:02:47:06.173 cpu0)WARNING: SCSI: 5912: READ of handleID 0x7e6

    Sep 1 14:16:36 cbret070 vmkernel: 0:02:47:06.173 cpu0)SCSI: 8879: vmhba1:0:2:1 status = 0/3 0x0 0x0 0x0

    Sep 1 14:16:36 cbret070 vmkernel: 0:02:47:06.173 cpu0)SCSI: 8955: vmhba1:0:2:1 Retry (abort after timeout)

    Sep 1 14:16:36 cbret070 vmkernel: 0:02:47:06.173 cpu0)WARNING: SCSI: 2555: vmhba1:0:2:1 Abort cmd due to timeout, s/n=62912, attempt 1

    Sep 1 14:16:36 cbret070 vmkernel: 0:02:47:06.173 cpu0)LinSCSI: 3361: Aborting cmds. with originSN 62912 from vmhba1:0:2

    Sep 1 14:16:36 cbret070 vmkernel: 0:02:47:06.173 cpu0)WARNING: SCSI: 2565: vmhba1:0:2:1 Abort cmd on timeout succeeded, s/n=62912, attempt 1

    Sep 1 14:16:36 cbret070 vmkernel: 0:02:47:06.173 cpu0)WARNING: SCSI: 5663: vmhba1:0:2:1 status = 0/2 0x0 0x0 0x0

    Sep 1 14:16:36 cbret070 vmkernel: 0:02:47:06.173 cpu0)SCSI: 8879: vmhba1:0:2:1 status = 0/2 0x0 0x0 0x0

    Sep 1 14:16:36 cbret070 vmkernel: 0:02:47:06.173 cpu0)SCSI: 8905: vmhba1:0:2:1 Retry (busy)

    and these

    Sep 1 16:43:59 CBREP071 vmkernel: 4:06:29:18.699 cpu1)WARNING: SCSI: 5663: vmhba1:0:2:1 status = 24/0 0x0 0x0 0x0

    Sep 1 16:44:10 CBREP071 vmkernel: 4:06:29:29.839 cpu1)WARNING: SCSI: 5663: vmhba1:0:2:1 status = 24/0 0x0 0x0 0x0

    Sep 1 16:44:11 CBREP071 vmkernel: 4:06:29:30.343 cpu1)WARNING: SCSI: 5663: vmhba1:0:2:1 status = 24/0 0x0 0x0 0x0

    Sep 1 16:44:35 CBREP071 vmkernel: 4:06:29:54.383 cpu2)WARNING: SCSI: 5663: vmhba1:0:2:1 status = 24/0 0x0 0x0 0x0

    I admit our firmware is outdated on both HBA card and our SAN components, these are being addressed in the next couple of weeks.

    We have support calls with both IBM and Vmware and cannot get either parties to give us a solution.

    Any help is appreciated,

    Thanks

    DB:2.46:Serious Issue With Ibm Ds4400 And Multiple San Connected Boxes jf


    This issue has been resolved by updating firmware on all san components as well as recarving the SAN disks to have more spindles per Array.

  • RELEVANCY SCORE 2.46

    DB:2.46:Difficulty With San Boot Of Solaris 10 (On V245) From Hp Eva 4000 - pa


    Hi

    This is my first post. I'm trying to get my head around what's preventing me booting a V245 solaris 10 from a LUN presented from an HP EVA 4000.
    The machine boots up ok from a local disk. So, i've done the LUN masking (presentation) on the EVA and the Brocade zoning - solaris can see the disk.
    I've formated it close to the current internal root disk, and had used ufsdump/ufsrestore and installboot to copy the contents of / onto the new LUN , which i had mounted as /mnt.

    My problem is i just can't seem to get at the new disk at the ok prompt - i'm never quite sure that i'm booting from the correct disk.
    I believe all the compatibility with o/s qlc card drivers and the EVA are in order.

    The qlc HBA is as follows:
    Sun SG-XPCI2FC-QF2/x6768A 1077 2312 1077 10A and have suitable patch 119139-33

    Here's some output:

    root@bwdnbtsl02# uname -a
    SunOS bwdnbtsl02 5.10 Generic_137111-01 sun4u sparc SUNW,Sun-Fire-V245
    root@bwdnbtsl02#

    root@bwdnbtsl02# luxadm probe
    No Network Array enclosures found in /dev/es

    Found Fibre Channel device(s):
    Node WWN:50001fe15009df00 Device Type:Disk device
    Logical Path:/dev/rdsk/c4t600508B4001066A60000C00002B50000d0s2
    root@bwdnbtsl02#

    Now down at ok prompt, probe-scsi-all can see the EVA (HSV) LUNS
    (Here's a sample of the output)

    ok probe-scsi-all
    /pci@1f,700000/pci@0/SUNW,qlc@2,1
    ************************* Fabric Attached Devices ************************
    Adapter portId - 640100
    Device PortId 640000 DeviceId 1 WWPN 210000e08b8a3e4f

    Device PortId dc0000 DeviceId 2 WWPN 50001fe15009df09
    Lun 0 HP HSV200 6220

    Lun 1 DISK HP HSV200 6220

    Device PortId d20000 DeviceId 3 WWPN 50001fe150092f19
    Lun 0 HP HSV200 6220

    /pci@1f,700000/pci@0/SUNW,qlc@2
    ************************* Fabric Attached Devices ************************
    Adapter portId - 630100
    Device PortId 630000 DeviceId 1 WWPN 210100e08baa3e4f

    Device PortId 780000 DeviceId 2 WWPN 50001fe15009df08
    Lun 0 HP HSV200 6220

    Lun 1 DISK HP HSV200 6220

    Device PortId 6e0000 DeviceId 3 WWPN 50001fe150092f18
    Lun 0 HP HSV200 6220

    So, i attempt to boot with the following:

    ok boot /pci@1f,700000/pci@0/SUNW,qlc@2/fp@0,0/disk@w50001fe15009df08,0:a
    Boot device: /pci@1f,700000/pci@0/SUNW,qlc@2/fp@0,0/disk@w50001fe15009df08,0:a File and args:
    Can't read disk label.
    Can't open disk label package

    Can't open boot device

    {1} ok

    If anyone can put me straight here i'd be most grateful.

    thanks john

    DB:2.46:Difficulty With San Boot Of Solaris 10 (On V245) From Hp Eva 4000 - pa

    Hello John,

    no, you didn't include your e-mail address. I just adviced not to respond by e-mail.

    If someone includes an e-mail address in a post, it's impossible to remove this addresss after someone has responded to this post.
    Only the moderators can block this post and include the original post without the e-mail address.

    Michael

  • RELEVANCY SCORE 2.46

    DB:2.46:Dual Path Disks df



    Is there a way to create disks with two scsi controllers assigned to it in order to create dual path disks?

    DB:2.46:Dual Path Disks df


    Ok then it is not possible.

    The iSCSI issue is a completely different issue than this topic, but for my software, and for some reason unknown to me, it cannot work with disks presented via iscsi but can with vmdk disks. I had asked this before but did not get any answers. I fail to find any docs that shows how to setup iscsi for use in vmware server.

    This is VMWare Server 1.0.4 on top of Linux OS such as CentOS 4.

  • RELEVANCY SCORE 2.46

    DB:2.46:V210 Adn A1000 m9


    Hi there;

    V210 - Ultra 160 Scsi multimode (SE/LVD)
    A1000 - Ultra Scsi - Differential

    Can these be used together? I've connected an A1000 to the back of a V210 and
    probe-scsi-all doesn't see it. Not a good sign.

    Bob

    DB:2.46:V210 Adn A1000 m9

    Ultra 160 is LVD(Low voltage).

    You can not mix LVD with HVD but you can connect single ended device to it.

  • RELEVANCY SCORE 2.45

    DB:2.45:Problem With Driver Install: "Driver Successfully Added To System But Failed To Attach" d7


    When install SCSI card Ultra320 driver on Solaris 9 Sparc station, get following error:
    devfsadm: driver failed to attach: itmpt
    Warning: Driver (itmpt) successfully added to system but failed to attach
    devfsadm: driver failed to attach: itip
    Warning: Driver (itip) successfully added to system but failed to attach

    IBut when run ok prompt command, get results:

    1) ok probe-scsi-all
    /pci#64;le, 600000/LSILogic, scsi#64;5
    MPT Version 1.02, Firmware Version 1.03.37.00
    Initiator ID is 7
    Taget 0
    Unit 0 Removable Device type 8 EXABYTE VXA 1x10 1U A10B
    Target 1
    Unit 0 Removable Tape EXABYTE VXA-2 2109
    2) ok show-devs
    ......
    /pci#64;1e,600000/LSILogic,scsi#64;5 /disk
    /pci#64;1e,600000/LSILogic,scsi#64;5/tape
    ......

    Thanks in advance for your advice.

    Jennifer

  • RELEVANCY SCORE 2.45

    DB:2.45:E2900 Scsi Error xc


    Hello,

    On an E2900 server, the probe-scsi-all is returning the following error:

    "ERROR: LSI1030: unknown error returned by IOC: scsi-status = 00, ioc-status = 0044"

    Any suggestions are appreciated!

    Thanks

    DB:2.45:E2900 Scsi Error xc

    Hello,

    On an E2900 server, the probe-scsi-all is returning the following error:

    "ERROR: LSI1030: unknown error returned by IOC: scsi-status = 00, ioc-status = 0044"

    Any suggestions are appreciated!

    Thanks

  • RELEVANCY SCORE 2.44

    DB:2.44:Sun V240 Dvd Not Showing In Probe-Scsi xc


    hi
    sun v240 shows err message
    cannt open boot device

    DB:2.44:Sun V240 Dvd Not Showing In Probe-Scsi xc

    @Shaiphali80,
    Same response as in your other post of the same question.
    http://forum.java.sun.com/thread.jspa?threadID=5258879

    Perfect example why cross-posting gets the responses littered all over the place.
    As time goes forward those responses get separated and no longer make any sense.

    ---
    Edit:
    Be sure to give SUNGOD1 the Duke Stars.
    They responded correctly.

  • RELEVANCY SCORE 2.44

    DB:2.44:Random Reboots - X440 - 2.5.3-24171 ---San Issue? 1f



    I have been working the dreaded "random reboot" issue for several months now and while I thought the issue was hardware related based on the errors on the x440's ASM Logs:

    18 X SERVPROC 06/14/06 01:13:31 Resetting system due to an unrecoverable error

    19 X SERVPROC 06/14/06 01:13:30 Adapter in PCI slot 1 or 2 signaled error.

    and had replaced NIC cards (IBM Dual 10/100 Server Adaptor Cards) as well as the PCIX board, the stupid thing is still randomly rebooting.

    The odd thing is, the same time (at least for the last reboot anyway), the SAN administrator had recieved an alert that the LUNs were no longer on their preferred path, and subsequently, manually failed the LUNs back.

    The machine is an IBM x440 with the latest BIOS and Firmware patches; its connected to an IBM FastT SAN; the OS is 2.5.3-24171.

    Here is a section of the VMKernerl log:

    Jun 15 09:45:30 nsvmnodea vmkernel: 1:08:42:26.826 cpu0)VMNIX: WARNING: VmkDev: 888: failed dsk=vmhba0:0:16:0 status=0xbad000a.

    Jun 15 09:45:30 nsvmnodea vmkernel: 1:08:42:26.837 cpu0)WARNING: SCSI: 2963: Manual switchover to path vmhba1:0:17 begins.

    Jun 15 09:45:31 nsvmnodea vmkernel: 1:08:42:26.838 cpu0)WARNING: SCSI: 2515: Could not switchover to vmhba1:0:17. Check Unit Ready Command returned an error instead of NOT READY for standby controller .

    Jun 15 09:45:31 nsvmnodea vmkernel: 1:08:42:26.838 cpu0)WARNING: SCSI: 2999: Manual switchover to vmhba1:0:17 completed unsuccessfully.

    Jun 15 09:45:31 nsvmnodea vmkernel: 1:08:42:26.839 cpu1)WARNING: SCSI: 5663: vmhba1:0:17:0 status = 2/0 0x5 0x25 0x0

    Jun 15 09:45:31 nsvmnodea vmkernel: 1:08:42:26.839 cpu0)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 09:45:31 nsvmnodea vmkernel: 1:08:42:26.839 cpu0)WARNING: SCSI: 6716: Failed for vmhba0:0:17 status = 195887114

    Jun 15 09:45:31 nsvmnodea vmkernel: 1:08:42:26.839 cpu0)VMNIX: WARNING: Mod: 1381: status 0xbad000a world 0xffffffff vmhba0:0:17:0 for vmware-ccagent

    Jun 15 09:45:31 nsvmnodea vmkernel: 1:08:42:26.839 cpu0)VMNIX: WARNING: VmkDev: 888: failed dsk=vmhba0:0:17:0 status=0xbad000a.

    Jun 15 09:45:31 nsvmnodea vmkernel: 1:08:42:26.840 cpu0)WARNING: SCSI: 2963: Manual switchover to path vmhba1:0:17 begins.

    Jun 15 09:45:32 nsvmnodea vmkernel: 1:08:42:26.841 cpu0)WARNING: SCSI: 2515: Could not switchover to vmhba1:0:17. Check Unit Ready Command returned an error instead of NOT READY for standby controller .

    Jun 15 09:45:32 nsvmnodea vmkernel: 1:08:42:26.841 cpu0)WARNING: SCSI: 2999: Manual switchover to vmhba1:0:17 completed unsuccessfully.

    Jun 15 09:45:32 nsvmnodea vmkernel: 1:08:42:26.842 cpu1)WARNING: SCSI: 5663: vmhba1:0:17:0 status = 2/0 0x5 0x25 0x0

    Jun 15 09:45:32 nsvmnodea vmkernel: 1:08:42:26.842 cpu0)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 09:45:32 nsvmnodea vmkernel: 1:08:42:26.842 cpu0)WARNING: SCSI: 6716: Failed for vmhba0:0:17 status = 195887114

    Jun 15 09:45:32 nsvmnodea vmkernel: 1:08:42:26.842 cpu0)VMNIX: WARNING: Mod: 1381: status 0xbad000a world 0xffffffff vmhba0:0:17:0 for vmware-ccagent

    Jun 15 09:45:32 nsvmnodea vmkernel: 1:08:42:26.842 cpu0)VMNIX: WARNING: VmkDev: 888: failed dsk=vmhba0:0:17:0 status=0xbad000a.

    Jun 15 09:45:32 nsvmnodea vmkernel: 1:08:42:26.842 cpu1)WARNING: SCSI: 5663: vmhba0:0:18:0 status = 2/0 0x5 0x25 0x0

    Jun 15 09:45:33 nsvmnodea vmkernel: 1:08:42:26.842 cpu0)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 09:45:33 nsvmnodea vmkernel: 1:08:42:26.842 cpu0)WARNING: SCSI: 6716: Failed for vmhba0:0:18 status = 195887114

    Jun 15 09:45:33 nsvmnodea vmkernel: 1:08:42:26.842 cpu0)VMNIX: WARNING: Mod: 1381: status 0xbad000a world 0xffffffff vmhba0:0:18:0 for vmware-ccagent

    Jun 15 09:45:33 nsvmnodea vmkernel: 1:08:42:26.842 cpu0)VMNIX: WARNING: VmkDev: 888: failed dsk=vmhba0:0:18:0 status=0xbad000a.

    Jun 15 09:45:33 nsvmnodea vmkernel: 1:08:42:26.843 cpu1)WARNING: SCSI: 5663: vmhba0:0:18:0 status = 2/0 0x5 0x25 0x0

    Jun 15 09:45:33 nsvmnodea vmkernel: 1:08:42:26.843 cpu0)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 09:45:33 nsvmnodea vmkernel: 1:08:42:26.843 cpu0)WARNING: SCSI: 6716: Failed for vmhba0:0:18 status = 195887114

    Jun 15 09:45:33 nsvmnodea vmkernel: 1:08:42:26.845 cpu0)VMNIX: WARNING: Mod: 1381: status 0xbad000a world 0xffffffff vmhba0:0:18:0 for vmware-ccagent

    Jun 15 09:45:33 nsvmnodea vmkernel: 1:08:42:26.845 cpu0)VMNIX: WARNING: VmkDev: 888: failed dsk=vmhba0:0:18:0 status=0xbad000a.

    Jun 15 09:49:12 nsvmnodea vmkernel: 1:08:46:09.176 cpu1)WARNING: SCSI: 5663: vmhba1:0:25:1 status = 24/0 0x0 0x0 0x0

    Jun 15 09:49:12 nsvmnodea vmkernel: 1:08:46:09.324 cpu1)WARNING: SCSI: 5663: vmhba1:0:19:1 status = 24/0 0x0 0x0 0x0

    Jun 15 09:49:12 nsvmnodea vmkernel: 1:08:46:09.418 cpu1)WARNING: SCSI: 5663: vmhba1:0:19:1 status = 24/0 0x0 0x0 0x0

    Jun 15 09:49:12 nsvmnodea last message repeated 4 times

    Jun 15 10:37:01 nsvmnodea vmkernel: 1:09:33:58.115 cpu3)WARNING: SCSI: 5663: vmhba1:0:16:0 status = 0/2 0x0 0x0 0x0

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.395 cpu1)WARNING: SCSI: 5663: vmhba1:0:16:0 status = 2/0 0x5 0x25 0x0

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.395 cpu7)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.395 cpu7)WARNING: SCSI: 6716: Failed for vmhba1:0:16 status = 195887114

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.396 cpu1)WARNING: SCSI: 5663: vmhba1:0:17:0 status = 2/0 0x5 0x25 0x0

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.396 cpu7)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.396 cpu7)WARNING: SCSI: 6716: Failed for vmhba1:0:17 status = 195887114

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.397 cpu1)WARNING: SCSI: 5663: vmhba1:0:18:0 status = 2/0 0x5 0x25 0x0

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.397 cpu7)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.397 cpu7)WARNING: SCSI: 6716: Failed for vmhba1:0:18 status = 195887114

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.969 cpu1)WARNING: SCSI: 5663: vmhba1:0:18:0 status = 2/0 0x5 0x25 0x0

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.969 cpu1)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.969 cpu1)WARNING: SCSI: 6716: Failed for vmhba1:0:18 status = 195887114

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.970 cpu1)WARNING: SCSI: 5663: vmhba1:0:17:0 status = 2/0 0x5 0x25 0x0

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.970 cpu1)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.970 cpu1)WARNING: SCSI: 6716: Failed for vmhba1:0:17 status = 195887114

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.971 cpu1)WARNING: SCSI: 5663: vmhba1:0:16:0 status = 2/0 0x5 0x25 0x0

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.971 cpu1)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 10:37:04 nsvmnodea vmkernel: 1:09:34:01.971 cpu1)WARNING: SCSI: 6716: Failed for vmhba1:0:16 status = 195887114

    Jun 15 10:38:23 nsvmnodea vmkernel: 1:09:35:20.773 cpu0)VMNIX: WARNING: Mod: 376: Minor version mismatch vmnix (0x1c0001), vmware-ccagent (0x1c0000)

    Jun 15 10:40:32 nsvmnodea vmkernel: 1:09:37:29.453 cpu1)WARNING: SCSI: 5663: vmhba1:0:18:0 status = 2/0 0x5 0x25 0x0

    Jun 15 10:40:32 nsvmnodea vmkernel: 1:09:37:29.453 cpu5)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 10:40:32 nsvmnodea vmkernel: 1:09:37:29.453 cpu5)WARNING: SCSI: 6716: Failed for vmhba1:0:18 status = 195887114

    Jun 15 10:40:32 nsvmnodea vmkernel: 1:09:37:29.454 cpu1)WARNING: SCSI: 5663: vmhba1:0:17:0 status = 2/0 0x5 0x25 0x0

    Jun 15 10:40:32 nsvmnodea vmkernel: 1:09:37:29.454 cpu5)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 10:40:32 nsvmnodea vmkernel: 1:09:37:29.454 cpu5)WARNING: SCSI: 6716: Failed for vmhba1:0:17 status = 195887114

    Jun 15 10:40:32 nsvmnodea vmkernel: 1:09:37:29.454 cpu1)WARNING: SCSI: 5663: vmhba1:0:16:0 status = 2/0 0x5 0x25 0x0

    Jun 15 10:40:32 nsvmnodea vmkernel: 1:09:37:29.454 cpu5)WARNING: SCSI: 8760: returns error: "I/O error". Code: 0xbad000a.

    Jun 15 10:40:32 nsvmnodea vmkernel: 1:09:37:29.454 cpu5)WARNING: SCSI: 6716: Failed for vmhba1:0:16 status = 195887114

    Jun 15 10:40:32 nsvmnodea vmkernel: 1:09:37:29.955 cpu1)WARNING: SCSI: 5663: vmhba0:0:1:0 status = 2/0 0x5 0x94 0x1

    Jun 15 10:40:33 nsvmnodea vmkernel: 1:09:37:29.961 cpu7)WARNING: SCSI: 2963: Manual switchover to path vmhba0:0:1 begins.

    Jun 15 10:40:34 nsvmnodea vmkernel: 1:09:37:32.022 cpu7)WARNING: SCSI: 2992: Manual switchover to vmhba0:0:1 completed successfully.

    Jun 15 10:50:01 nsvmnodea vmkernel: 1:09:46:58.342 cpu0)WARNING: SCSI: 2963: Manual switchover to path vmhba1:0:1 begins.

    Jun 15 10:50:01 nsvmnodea vmkernel: 1:09:46:58.344 cpu4)WARNING: SCSI: 2511: Did not switchover to vmhba1:0:1. Check Unit Ready Command returned READY instead of NOT READY for standby controller .

    Jun 15 10:50:01 nsvmnodea vmkernel: 1:09:46:58.344 cpu4)WARNING: SCSI: 2992: Manual switchover to vmhba1:0:1 completed successfully.

    Jun 15 10:50:16 nsvmnodea vmkernel: 1:09:47:13.893 cpu1)WARNING: SCSI: 5663: vmhba0:0:26:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:17 nsvmnodea vmkernel: 1:09:47:14.295 cpu1)WARNING: SCSI: 5663: vmhba0:0:26:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:17 nsvmnodea vmkernel: 1:09:47:14.296 cpu1)WARNING: SCSI: 5663: vmhba0:0:26:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:17 nsvmnodea vmkernel: 1:09:47:14.393 cpu1)WARNING: SCSI: 5663: vmhba0:0:26:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:17 nsvmnodea vmkernel: 1:09:47:14.860 cpu1)WARNING: SCSI: 5663: vmhba0:0:26:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:18 nsvmnodea vmkernel: 1:09:47:16.024 cpu7)WARNING: SCSI: 2963: Manual switchover to path vmhba1:0:26 begins.

    Jun 15 10:50:19 nsvmnodea vmkernel: 1:09:47:16.085 cpu3)WARNING: SCSI: 2511: Did not switchover to vmhba1:0:26. Check Unit Ready Command returned READY instead of NOT READY for standby controller .

    Jun 15 10:50:19 nsvmnodea vmkernel: 1:09:47:16.085 cpu3)WARNING: SCSI: 2992: Manual switchover to vmhba1:0:26 completed successfully.

    Jun 15 10:50:19 nsvmnodea vmkernel: 1:09:47:16.193 cpu1)WARNING: SCSI: 5663: vmhba0:0:26:1 status = 2/0 0x5 0x94 0x1

    Jun 15 10:50:20 nsvmnodea vmkernel: 1:09:47:17.293 cpu1)WARNING: SCSI: 5663: vmhba0:0:24:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:23 nsvmnodea vmkernel: 1:09:47:20.293 cpu1)WARNING: SCSI: 5663: vmhba0:0:24:1 status = 2/0 0x5 0x94 0x1

    Jun 15 10:50:23 nsvmnodea vmkernel: 1:09:47:20.301 cpu3)WARNING: SCSI: 2963: Manual switchover to path vmhba1:0:24 begins.

    Jun 15 10:50:23 nsvmnodea vmkernel: 1:09:47:20.302 cpu1)WARNING: SCSI: 2511: Did not switchover to vmhba1:0:24. Check Unit Ready Command returned READY instead of NOT READY for standby controller .

    Jun 15 10:50:23 nsvmnodea vmkernel: 1:09:47:20.302 cpu1)WARNING: SCSI: 2992: Manual switchover to vmhba1:0:24 completed successfully.

    Jun 15 10:50:31 nsvmnodea vmkernel: 1:09:47:28.824 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:32 nsvmnodea vmkernel: 1:09:47:29.225 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:32 nsvmnodea vmkernel: 1:09:47:29.291 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:32 nsvmnodea vmkernel: 1:09:47:29.291 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:32 nsvmnodea vmkernel: 1:09:47:29.292 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:32 nsvmnodea vmkernel: 1:09:47:29.324 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:32 nsvmnodea vmkernel: 1:09:47:29.376 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:32 nsvmnodea last message repeated 2 times

    Jun 15 10:50:32 nsvmnodea vmkernel: 1:09:47:29.524 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:32 nsvmnodea vmkernel: 1:09:47:29.807 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:33 nsvmnodea vmkernel: 1:09:47:30.224 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:33 nsvmnodea vmkernel: 1:09:47:30.307 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:33 nsvmnodea vmkernel: 1:09:47:30.359 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:33 nsvmnodea vmkernel: 1:09:47:30.359 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:33 nsvmnodea vmkernel: 1:09:47:30.360 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:33 nsvmnodea vmkernel: 1:09:47:30.525 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:34 nsvmnodea vmkernel: 1:09:47:31.215 cpu1)WARNING: SCSI: 2963: Manual switchover to path vmhba1:0:22 begins.

    Jun 15 10:50:34 nsvmnodea vmkernel: 1:09:47:31.216 cpu1)WARNING: SCSI: 2511: Did not switchover to vmhba1:0:22. Check Unit Ready Command returned READY instead of NOT READY for standby controller .

    Jun 15 10:50:34 nsvmnodea vmkernel: 1:09:47:31.216 cpu1)WARNING: SCSI: 2992: Manual switchover to vmhba1:0:22 completed successfully.

    Jun 15 10:50:34 nsvmnodea vmkernel: 1:09:47:31.364 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x5 0x94 0x1

    Jun 15 10:50:34 nsvmnodea vmkernel: 1:09:47:31.375 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x5 0x94 0x1

    Jun 15 10:50:34 nsvmnodea vmkernel: 1:09:47:31.474 cpu1)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 2/0 0x5 0x94 0x1

    Jun 15 10:50:34 nsvmnodea vmkernel: 1:09:47:32.057 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:35 nsvmnodea vmkernel: 1:09:47:32.090 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:35 nsvmnodea vmkernel: 1:09:47:32.290 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:35 nsvmnodea vmkernel: 1:09:47:32.290 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:35 nsvmnodea vmkernel: 1:09:47:32.291 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:35 nsvmnodea vmkernel: 1:09:47:32.292 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:35 nsvmnodea vmkernel: 1:09:47:32.440 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:35 nsvmnodea vmkernel: 1:09:47:32.558 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:35 nsvmnodea vmkernel: 1:09:47:32.558 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:35 nsvmnodea vmkernel: 1:09:47:32.591 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:36 nsvmnodea vmkernel: 1:09:47:33.073 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:36 nsvmnodea vmkernel: 1:09:47:33.406 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:36 nsvmnodea vmkernel: 1:09:47:33.441 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:36 nsvmnodea vmkernel: 1:09:47:33.524 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:36 nsvmnodea vmkernel: 1:09:47:33.524 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:36 nsvmnodea vmkernel: 1:09:47:33.576 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 10:50:37 nsvmnodea vmkernel: 1:09:47:34.073 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x5 0x94 0x1

    Jun 15 10:50:37 nsvmnodea vmkernel: 1:09:47:34.195 cpu7)WARNING: SCSI: 2963: Manual switchover to path vmhba1:0:20 begins.

    Jun 15 10:50:44 nsvmnodea vmkernel: 1:09:47:41.142 cpu0)WARNING: SCSI: 5663: vmhba1:0:22:1 status = 0/2 0x0 0x0 0x0

    Jun 15 10:50:46 nsvmnodea vmkernel: 1:09:47:43.636 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:50:46 nsvmnodea vmkernel: 1:09:47:43.636 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:50:46 nsvmnodea vmkernel: 1:09:47:43.637 cpu4)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/2 0x0 0x0 0x0

    Jun 15 10:50:46 nsvmnodea vmkernel: 1:09:47:43.638 cpu4)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/2 0x0 0x0 0x0

    Jun 15 10:50:46 nsvmnodea vmkernel: 1:09:47:43.926 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:50:46 nsvmnodea vmkernel: 1:09:47:43.926 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:50:47 nsvmnodea vmkernel: 1:09:47:43.928 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/2 0x0 0x0 0x0

    Jun 15 10:51:01 nsvmnodea vmkernel: 1:09:47:58.912 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:51:01 nsvmnodea vmkernel: 1:09:47:58.912 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:51:01 nsvmnodea vmkernel: 1:09:47:58.913 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:51:01 nsvmnodea vmkernel: 1:09:47:58.913 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:51:16 nsvmnodea vmkernel: 1:09:48:13.934 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:51:16 nsvmnodea last message repeated 7 times

    Jun 15 10:51:17 nsvmnodea vmkernel: 1:09:48:13.935 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:51:17 nsvmnodea vmkernel: 1:09:48:13.935 cpu0)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 0/8 0x0 0x0 0x0

    Jun 15 10:51:17 nsvmnodea vmkernel: 1:09:48:14.195 cpu7)WARNING: SCSI: 5912: READ of handleID 0x7ce

    Jun 15 10:51:17 nsvmnodea vmkernel: 1:09:48:14.196 cpu7)WARNING: SCSI: 2555: vmhba1:0:20:1 Abort cmd due to timeout, s/n=3938426, attempt 1

    Jun 15 10:51:17 nsvmnodea vmkernel: 1:09:48:14.196 cpu7)WARNING: SCSI: 2565: vmhba1:0:20:1 Abort cmd on timeout succeeded, s/n=3938426, attempt 1

    Jun 15 10:51:17 nsvmnodea vmkernel: 1:09:48:14.252 cpu0)WARNING: SCSI: 2511: Did not switchover to vmhba1:0:20. Check Unit Ready Command returned READY instead of NOT READY for standby controller .

    Jun 15 10:51:17 nsvmnodea vmkernel: 1:09:48:14.252 cpu0)WARNING: SCSI: 2992: Manual switchover to vmhba1:0:20 completed successfully.

    Jun 15 11:45:35 nsvmnodea vmkernel: 1:10:42:32.651 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:35 nsvmnodea vmkernel: 1:10:42:32.850 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:35 nsvmnodea vmkernel: 1:10:42:32.900 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:36 nsvmnodea vmkernel: 1:10:42:33.150 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:36 nsvmnodea vmkernel: 1:10:42:33.407 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:36 nsvmnodea vmkernel: 1:10:42:33.537 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:36 nsvmnodea vmkernel: 1:10:42:33.550 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:36 nsvmnodea last message repeated 2 times

    Jun 15 11:45:36 nsvmnodea vmkernel: 1:10:42:33.551 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:36 nsvmnodea vmkernel: 1:10:42:33.619 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:36 nsvmnodea vmkernel: 1:10:42:33.900 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:36 nsvmnodea vmkernel: 1:10:42:33.900 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:37 nsvmnodea vmkernel: 1:10:42:34.190 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:37 nsvmnodea vmkernel: 1:10:42:34.200 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:37 nsvmnodea vmkernel: 1:10:42:34.383 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x5 0x94 0x1

    Jun 15 11:45:37 nsvmnodea vmkernel: 1:10:42:34.385 cpu0)WARNING: SCSI: 2963: Manual switchover to path vmhba0:0:20 begins.

    Jun 15 11:45:37 nsvmnodea vmkernel: 1:10:42:34.386 cpu0)WARNING: SCSI: 2511: Did not switchover to vmhba0:0:20. Check Unit Ready Command returned READY instead of NOT READY for standby controller .

    Jun 15 11:45:37 nsvmnodea vmkernel: 1:10:42:34.386 cpu0)WARNING: SCSI: 2992: Manual switchover to vmhba0:0:20 completed successfully.

    Jun 15 11:45:37 nsvmnodea vmkernel: 1:10:42:34.500 cpu1)WARNING: SCSI: 5663: vmhba1:0:20:1 status = 2/0 0x5 0x94 0x1

    Jun 15 11:45:37 nsvmnodea vmkernel: 1:10:42:34.623 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 2/0 0x6 0x29 0x0

    Jun 15 11:45:39 nsvmnodea vmkernel: 1:10:42:36.553 cpu1)WARNING: SCSI: 5663: vmhba1:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:39 nsvmnodea vmkernel: 1:10:42:36.554 cpu1)WARNING: SCSI: 5663: vmhba1:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:39 nsvmnodea vmkernel: 1:10:42:36.555 cpu1)WARNING: SCSI: 5663: vmhba1:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:39 nsvmnodea vmkernel: 1:10:42:36.683 cpu1)WARNING: SCSI: 5663: vmhba1:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:39 nsvmnodea vmkernel: 1:10:42:36.683 cpu1)WARNING: SCSI: 5663: vmhba1:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:40 nsvmnodea vmkernel: 1:10:42:37.184 cpu1)WARNING: SCSI: 5663: vmhba1:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:40 nsvmnodea vmkernel: 1:10:42:37.716 cpu1)WARNING: SCSI: 5663: vmhba1:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:40 nsvmnodea vmkernel: 1:10:42:37.721 cpu1)WARNING: SCSI: 5663: vmhba1:0:22:1 status = 2/0 0x6 0x8b 0x2

    Jun 15 11:45:41 nsvmnodea vmkernel: 1:10:42:38.712 cpu0)WARNING: SCSI: 2963: Manual switchover to path vmhba0:0:22 begins.

    Jun 15 11:45:41 nsvmnodea vmkernel: 1:10:42:38.715 cpu0)WARNING: SCSI: 2511: Did not switchover to vmhba0:0:22. Check Unit Ready Command returned READY instead of NOT READY for standby controller .

    Jun 15 11:45:41 nsvmnodea vmkernel: 1:10:42:38.715 cpu0)WARNING: SCSI: 2992: Manual switchover to vmhba0:0:22 completed successfully.

    Jun 15 11:45:41 nsvmnodea vmkernel: 1:10:42:39.032 cpu1)WARNING: SCSI: 5663: vmhba1:0:22:1 status = 2/0 0x5 0x94 0x1

    Jun 15 11:45:47 nsvmnodea vmkernel: 1:10:42:44.982 cpu1)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 0/2 0x0 0x0 0x0

    Jun 15 11:45:47 nsvmnodea vmkernel: 1:10:42:44.983 cpu2)WARNING: SCSI: 5663: vmhba0:0:20:1 status = 0/2 0x0 0x0 0x0

    Jun 15 11:45:51 nsvmnodea vmkernel: 1:10:42:48.233 cpu2)WARNING: SCSI: 5663: vmhba0:0:22:1 status = 0/2 0x0 0x0 0x0

    Jun 15 11:45:58 nsvmnodea vmkernel: 1:10:42:55.116 cpu0)WARNING: SCSI: 2963: Manual switchover to path vmhba0:0:26 begins.

    Jun 15 11:45:58 nsvmnodea vmkernel: 1:10:42:55.123 cpu0)WARNING: SCSI: 2511: Did not switchover to vmhba0:0:26. Check Unit Ready Command returned READY instead of NOT READY for standby controller .

    Jun 15 11:45:58 nsvmnodea vmkernel: 1:10:42:55.123 cpu0)WARNING: SCSI: 2992: Manual switchover to vmhba0:0:26 completed successfully.

    Jun 15 11:49:21 nsvmnodea vmkernel: 1:10:46:18.553 cpu0)VMNIX: WARNING: Mod: 376: Minor version mismatch vmnix (0x1c0001), vmware-ccagent (0x1c0000)

    Jun 15 11:49:30 nsvmnodea vmkernel: 1:10:46:26.603 cpu1)WARNING: SCSI: 5663: vmhba1:0:24:0 status = 2/0 0x6 0x29 0x0

    Jun 15 11:49:30 nsvmnodea vmkernel: 1:10:46:27.091 cpu1)WARNING: SCSI: 5663: vmhba1:0:24:0 status = 2/0 0x5 0x94 0x1

    Jun 15 11:49:30 nsvmnodea vmkernel: 1:10:46:27.094 cpu0)WARNING: SCSI: 2963: Manual switchover to path vmhba0:0:24 begins.

    Jun 15 11:49:30 nsvmnodea vmkernel: 1:10:46:27.095 cpu0)WARNING: SCSI: 2511: Did not switchover to vmhba0:0:24. Check Unit Ready Command returned READY instead of NOT READY for standby controller .

    Jun 15 11:49:30 nsvmnodea vmkernel: 1:10:46:27.095 cpu0)WARNING: SCSI: 2992: Manual switchover to vmhba0:0:24 completed successfully.

    Jun 15 13:31:44 nsvmnodea vmkernel: 1:12:28:41.992 cpu0)VMNIX: WARNING: Mod: 376: Minor version mismatch vmnix (0x1c0001), vmware-ccagent (0x1c0000)

    As you can see there is a ton of SCSI warnings and Manual Switchover entries as well. (You'll see a few warnings about vmhba0:0:16, 17 and 18 - these were LUNs that were zoned out last night and before I executed a SAN rescan so I expected to see some of those).

    My first though is that I had some LUN thrashing going on but according to the SAN admin all the settings are correct (the host type is set to LNXCL so AVT is disabled) and the failover policy is set to MRU.

    So I'm kinda lost here....anyone have any suggestions?

    Peter

    DB:2.44:Random Reboots - X440 - 2.5.3-24171 ---San Issue? 1f


    Is the SAN an IBM San? If so, if you are having preferred path problems the problem is in the DSXXXX disk susbsystem controller. I am going to keep looking at your output, but get back to me on the type of backend you have on your san.

  • RELEVANCY SCORE 2.44

    DB:2.44:U60 Can't Start s8


    Hi everybody,

    I have a problem with my u60. It hung when it booting. In promt, I typed probe-scsi, it shows 2 HD, in obtest everything is ok. When I typed boot disk, it hungs forever. PLEASE HELP!!!

    DB:2.44:U60 Can't Start s8

    Hi everybody,

    I have a problem with my u60. It hung when it booting. In promt, I typed probe-scsi, it shows 2 HD, in obtest everything is ok. When I typed boot disk, it hungs forever. PLEASE HELP!!!

  • RELEVANCY SCORE 2.44

    DB:2.44:Replacing Disk c8


    We had a disk go bad, we replaced it, and rebooted with boot -r. Fortunately, the disk that died had no real important data (we do have backups). But, when trying to run format to partition the new disk, I get the following error:
    "Searching for disks...Arithmetic Exception (core dumped)"

    Unfortunately, I never ran probe-scsi-all from the ok prompt. This server is production server, so I can't run probe-scsi-all from the ok prompt until some odd hour of the night. Is there a way to probe the scsi bus without doing a STOP-A?
    Any ideas on what might be causing the "Arithmetic Exception"??

    The drive was enclosed in a 4 bay array. The other drives all mounted without any issues.

    We are running Solaris 2.4 on a Sparc20. (Please do not recommend upgrading! I'm working on that!!)

    Thanks in advance!

    DB:2.44:Replacing Disk c8

    You can do an "equivalent" to probe-scsi once the Operating system is up and running by using the following:
    iostat -En

  • RELEVANCY SCORE 2.43

    DB:2.43:Trouble Getting An E220r To Recognize A Storedge D2 z7


    Hi,
    I have a StorEdge D2 filled with 12 36 gig drives, attched to the onboard external SCSI port on the back of an E220R.
    However, I cant get the system to recognize the drive tray. If I do a probe-scsi-all from the ok prompt, I get this:

    /pci@1f,4000/scsi@3,1
    Fatal SCSI error at script address 10 Unexpected disconnect

    that error repeats itself 30 times, the probe-scsi-all probes the next scsi device and finds the internal scsi hard drive and cdrom drive.

    I tried doing a reset-all, and got the same results.

    any ideas what might be causing this?

    DB:2.43:Trouble Getting An E220r To Recognize A Storedge D2 z7

    The D2 supports LVD SCSI. The onboard E220R is single-ended SCSI. While LVD is supposed to
    be backwards-compatible with single-ended, you may find cases where this doesn't work well.
    In particular, single-ended is very picky about cable lengths. I think you will find that Sun only
    supports the D2 for certain LVD cards.

    -- richard

  • RELEVANCY SCORE 2.42

    DB:2.42:How To Split Data Into Two Rows 13


    I have a query that returns a table similar to:State        Status          CountCA          Complete     10CA          Incomplete   200NC          Complete     20NC          Incomplete   205SC           Incomplete   50What sort of query will allow me to reformat the table into:State      Complete     IncompleteCA         10               200NC         20               205SC          NULL         50

    DB:2.42:How To Split Data Into Two Rows 13

    Try this:create table stateinfo(state char(2), status char(20), count int) GOinsert into stateinfo(state, status, count) values('CA','Complete',     10)insert into stateinfo(state, status, count) values('CA','Incomplete',   200)insert into stateinfo(state, status, count) values('NC','Complete',     20)insert into stateinfo(state, status, count) values('NC','Incomplete',   205)insert into stateinfo(state, status, count) values('SC','Incomplete',   50)select state, complete= sum(case when status='Complete' then count end), incomplete= sum(case when status='InComplete' then count end) from stateinfogroup by state

  • RELEVANCY SCORE 2.42

    DB:2.42:Sun V240 Dvd Not Showing In Probe-Scsi aj


    hi
    error message is
    cannt open boot device
    when i write boot cdrom

    DB:2.42:Sun V240 Dvd Not Showing In Probe-Scsi aj

    The optical drives in V210/V240 systems are IDE drives.
    You won't see them via probe-scsi.
    You will need to do a probe-ide to see them.

    As for your boot error, try replacing the media with known bootable commercially created disks.
    If that doesn't work, then replace the optical drive.

  • RELEVANCY SCORE 2.42

    DB:2.42:E250 + Ultrascsi External 9gb Disk 7j


    Group,

    Have an E250 that I'm trying to connect an external UltraSCSI External 9GB disk to.

    Scsi-probe-all sees the device but upon boot, there is no visibility of the drive. No mount.

    iostat -En does not find the drive.

    Running Solaris 2.8. Metatool only shows one controller "c0" with my existing and available drives, although I do have the SCSI card.

    Target drive id = 5. Any reccomendation would be greatly appreciated.

    Thanks,

    DB:2.42:E250 + Ultrascsi External 9gb Disk 7j

    boot -r was it. Since I followed the scsi-probe-all with a reset-all, I negelected the boot -r the first time around.

    Thanks,

  • RELEVANCY SCORE 2.40

    DB:2.40:Virtual Scsi Ids Don't Match With Windows Scsi Ids 7m



    Hello friends, We have a question about VM's SCSI ids:

    If I run a WMI query against a virtual machine, to get the SCSI ID of its virtual disks, returns me:

    Two more SCSI controllers if the virtual machine is running on a ESX 4.1.One more SCSI controller if the virtual machine is running on a ESX 3.5.

    An example. If I will run this VBS script on a VM under an ESX 4.1, we can see that SCSI IDs in Windows match with SCSI id in VM's "Edit Settings":

    Valor = 2
    Set objWMIService = GetObject("winmgmts:" "{impersonationLevel=impersonate}!\\.\root\cimv2")
    Set colDiskDrives = objWMIService.ExecQuery ("Select * from Win32_DiskDrive")
    For each objDiskDrive in colDiskDrives
    wscript.echo "El disc Windows " objDiskDrive.DeviceID " correspon a nivell d'VMWare al SCSI(" objDiskDrive.SCSIPort - Valor "." objDiskDrive.SCSITargetId ")"
    Next

    DB:2.40:Virtual Scsi Ids Don't Match With Windows Scsi Ids 7m


    Hello friends, We have a question about VM's SCSI ids:

    If I run a WMI query against a virtual machine, to get the SCSI ID of its virtual disks, returns me:

    Two more SCSI controllers if the virtual machine is running on a ESX 4.1.One more SCSI controller if the virtual machine is running on a ESX 3.5.

    An example. If I will run this VBS script on a VM under an ESX 4.1, we can see that SCSI IDs in Windows match with SCSI id in VM's "Edit Settings":

    Valor = 2
    Set objWMIService = GetObject("winmgmts:" "{impersonationLevel=impersonate}!\\.\root\cimv2")
    Set colDiskDrives = objWMIService.ExecQuery ("Select * from Win32_DiskDrive")
    For each objDiskDrive in colDiskDrives
    wscript.echo "El disc Windows " objDiskDrive.DeviceID " correspon a nivell d'VMWare al SCSI(" objDiskDrive.SCSIPort - Valor "." objDiskDrive.SCSITargetId ")"
    Next

  • RELEVANCY SCORE 2.40

    DB:2.40:Pe 2450 With Perc 3/Si - Scsi A External Termination Voltage Probe j1


  • RELEVANCY SCORE 2.40

    DB:2.40:Re: Probe-Scsi Message Error ad


    I am receiving the same errrors when I executed probe-scsi-all. This is the first time I have dealt with this deivice, and the LSI. I created a mirror for my root drive and was researching.

    Did you get any response? I want to check firmware upgrades.

    Thanks

    DB:2.40:Re: Probe-Scsi Message Error ad

    And that is exactly what is happening, but the manual also says you should be able to do "boot disk2" and it should boot. I'm wondering if I have to break the mirror to boot the second drive because it indicated the drive had to be unmounted to create the mirror. With the source disk still functioning, maybe it doesn't mount it.

    Thanks for your suggestions.

  • RELEVANCY SCORE 2.40

    DB:2.40:Sme Error - Incomplete Path Or Invalid Location km



    Anyone seen this - we're getting this after running verification on a recent backup:

    Error dialog box:

    ###

    SnapManager for Exchange

    Failed to get Exchange information for Server - SERVERNAME

    Error Code: 0xC0040206

    [SnapDrive Error]: Incomplete path or invalid location.

    ###

    Exchange server is up, filer is up, SnapDrive service is running fine etc.

    Please help!

    DB:2.40:Sme Error - Incomplete Path Or Invalid Location km


    Mark, putting in the filer name + IP didn't make a difference unfortunately.

    SnapDrive version is 4.0.0.1273, FAS270, ONTAP 7.2

    I'm able to browese to http://filername/na_admin and create a test lun successfully.

  • RELEVANCY SCORE 2.40

    DB:2.40:Lto3-Hpsc To Dual Scsi Card km


    I have installed SL500 with 5 SCSI Tape drive LTO3-HPSC connected to SunFire V490 with 3 PCI-X - Dual Ultra-320 SCSI Cards LSI , but I can't see the cards on OBP
    when I issue probe-scsi-all result is /pci@8,70000/scsi@2 , I've installed the recommended driver and patches but I can't see the tape drives under /dev/rmt here is what is on the /var/adm/messages ::

    Oct 3 11:23:06 dbserver scsi: lus1 at mpt1: target 0 lun 0
    Oct 3 11:23:06 dbserver genunix: lus1 is /pci@8,700000/scsi@2,1/lus@0,0
    Oct 3 11:23:06 dbserver lus: no match for pci1000,30 found in lus.conf:
    Oct 3 11:23:06 dbserver lus: ntargets - 8 - based on bus width

    even when I issue #cfgadm it appears to be connected configured but the state is unknown ?

    any idea about this?

    DB:2.40:Lto3-Hpsc To Dual Scsi Card km

    I have installed SL500 with 5 SCSI Tape drive LTO3-HPSC connected to SunFire V490 with 3 PCI-X - Dual Ultra-320 SCSI Cards LSI , but I can't see the cards on OBP
    when I issue probe-scsi-all result is /pci@8,70000/scsi@2 , I've installed the recommended driver and patches but I can't see the tape drives under /dev/rmt here is what is on the /var/adm/messages ::

    Oct 3 11:23:06 dbserver scsi: lus1 at mpt1: target 0 lun 0
    Oct 3 11:23:06 dbserver genunix: lus1 is /pci@8,700000/scsi@2,1/lus@0,0
    Oct 3 11:23:06 dbserver lus: no match for pci1000,30 found in lus.conf:
    Oct 3 11:23:06 dbserver lus: ntargets - 8 - based on bus width

    even when I issue #cfgadm it appears to be connected configured but the state is unknown ?

    any idea about this?

  • RELEVANCY SCORE 2.39

    DB:2.39:Connecting Rsm 214 To Sun E4500 Via Scsi Interface 7j


    I installed X1065A on my Sun E4500 server, which support HVD SCSI and connect RSM 219 to it. However, the server can not find any disk. Probe-scsi only show CD-Rom. Fowlling document of RSM219, it need HVD SCSI Adapter. Any suggestion for that?

    Thanks.

  • RELEVANCY SCORE 2.39

    DB:2.39:Solaris 11and Vmware Esxi 3x


    It seems that Solaris 11 doesn't run under VMWare ESXi. Even when installing from the iso, there are mpt errors.

    Nov 11 01:30:44 solaris scsi: [ID 107833 kern.notice] scsi_state = 0, transfer count = 0, scsi_status = 0
    Nov 11 01:30:44 solaris scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,1976@10/sd@1,0 (sd2):
    Nov 11 01:30:44 solaris incomplete write- retrying
    Nov 11 01:30:44 solaris scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,1976@10 (mpt0):
    Nov 11 01:30:44 solaris unknown ioc_status = 4
    Nov 11 01:30:44 solaris scsi: [ID 107833 kern.notice] scsi_state = 0, transfer count = 0, scsi_status = 0
    Nov 11 01:30:44 solaris scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,1976@10/sd@1,0 (sd2):
    Nov 11 01:30:44 solaris incomplete write- retrying

    Has anyone else tried to run it on ESXi?

    DB:2.39:Solaris 11and Vmware Esxi 3x

    No scsi error on ESX v3.5 but at startup I had a message:

    NOTICE: MPO disabled because memory is interleaved

    Maybe the problem is between the mpo driver and the VMware virtual hardware.

    --
    Giancarlo

  • RELEVANCY SCORE 2.39

    DB:2.39:Sparcstorage Array (Ssa), How To Add It ? ax


    Hi Gurus,

    I have a SparcStorage Array on a E4500 server with SunOS 5.6

    Any ideas on what I need to do in order to be recognized by the server?

    I cann't see it while running probe-scsi-all, no reboot -- -r, no disks, drvconfig, etc.

    The arrays are powered on,

    Regards

    DB:2.39:Sparcstorage Array (Ssa), How To Add It ? ax

    lycan;

    not sure if you got this straightened out but I figured I would add to this.
    As torreysun said you need the older soc not soc+.

    Since you have a E4500 your i/o brd is most likely a 501-4883 which is soc+ and uses gbics 370-2303 which does not support the old SSA unit.

    What you need is a soc host adaptor 501-2069 with soc module 370-1426 which can be added to the sbus slot on the 501-4883 i/o brd.

    You will not be able to see the unit low level with probe-fcal-all or probe-scsi-all (I tried the probe-scsi-all command on an SS1000 with a SSA attached just to confirm). I do not have an E4500 to try the probe-scsi-all command with the SSA attached but am pretty sure you will not see it with that either. Probe-fcal-all was used on the E3500 units that had internal fibre drives.

    Older systems Probe-scsi-all was originally only used to see scsi drives. On the newer units like the 280R, V880 which use internal fibre drives the probe-scsi-all command will show the fibre drives.

    Thanks

    CA

  • RELEVANCY SCORE 2.39

    DB:2.39:Custom Endpoint / Http Probe / Get Request And Recieve String d3


    I am needing a bit more strength in the azure endpoint configuration, for an application healthcheck. Getting a 200 header response isn't enough. I need to have the endpoint probe run a GET request on a specified path, and ensure it returns a
    specific string SUCCESS. Using the standard probe request it may return a 200, but the application on the web server may not be displaying the proper content and continue to serve requests.

    Is there a way to create a custom azure endpoint to retrieve a specific string from a GET request to the web server?

    DB:2.39:Custom Endpoint / Http Probe / Get Request And Recieve String d3

    Dear Customer,

    I therefore would like to provide the following information for your reference:

    Configuring Connection Strings
    http://msdn.microsoft.com/en-us/library/windowsazure/ee758697.aspx

    I hope this helps. If you have any questions or concerns, please do not hesitate to let me know.

  • RELEVANCY SCORE 2.38

    DB:2.38:About Realmode Driver Befdebug Utility 83


    Hi Dear All,
    Does anyone know that befdebug could probe SCSI PCI Host adapter?
    Should I do "NODE_START" in xxxx_legacy_probe
    routine for my pci scsi adapter?

    Best Regards
    Erich Chen

    DB:2.38:About Realmode Driver Befdebug Utility 83

    Hi Dear All,
    I have done all solaris driver include kernel mode and real mode.
    I just share my experience for all that need it.
    The befdebug utility can not probe PCI device.
    The probe function is only for legacy device.
    But You can do legacy probe function for your PCI adapter.
    Read PCI resorce irq port vendor id device id and set_res.
    If you do it ,you could use befdebug probe function to save your
    "device node data" file.

    %befdebug probe
    %(run your realmodedriver.exe)
    %befdebug save node.dat

    now,you could get node.dat for your PCI Host Adapter.

    If you would not ,You should create your node.dat file for your PCI Host adapter.
    Because,befdebug need it.
    You can get node.dat sample from solaris realmode paper.
    It is text file that include your adapter's pci current resource.

    % befdebug -d install node.dat
    % (run your realmodedriver.exe)

  • RELEVANCY SCORE 2.37

    DB:2.37:Hba Error 1j



    Anyone know what this means? Is the card dead?

    WARNING: SCSI: 5921: returns 0xbad0040 for vmhba1:0:25

    Thanks!

    DB:2.37:Hba Error 1j


    Guys,

    Sorry for the delay... just saw your post. If you can, please include the ESX version and patch level when providing errors. Unfortunately, we often need to review different source code to decipher different versions of ESX

    0x0bad0040[/b]

    \----

    ESX VERSION VMK_ERROR_CODE DESCRIPTIVE STRING DECIMAL HEX

    \----

    2.5.x VMK_NO_CONNECT "No connection" 195887168 0x0bad0040

    2.1.x VMK_BAD_ACPI "Error parsing ACPI Table" 195887168 0x0bad0040

    /code

    Based on the scenario, I would guess that you are running 2.5.x and the error is therefore reporting "no connection"[/b] to the target LUN/path.

    I would probably start by:

    \- Have the SAN team take the LUN away from your WWN's (obtained via wwpn.pl)

    \- Rescan via url=http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1352KB1352[/url]

    \- Clear any Persistent Bindings (if they exist) via url=http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1302KB1302[/url]

    \- Reboot the ESX host

    \- Have the SAN team present the LUN again

    \- Rescan.

    Of course, you should ensure that all of your diskmaxlun, diskmasklun, etc. are in order and haven't changed. There are many ways to approach this, I have just presented a few. Hopefully the solution won't end up being that the SP needs to be rebooted

    Please keep us posted.

  • RELEVANCY SCORE 2.37

    DB:2.37:Backup Not Starting fx


    I have NW 7,21 Client in which probe (Savegrp -p) succeeds but backing up to tape never starts. It is showing all save sets as incomplete in group details. Client initiated backup also not working for this server. What could be the problem?

    DB:2.37:Backup Not Starting fx

    Problem resolved...a hung exe at client end was the problem..and this is killed by rebooting server.

  • RELEVANCY SCORE 2.37

    DB:2.37:Luxadm Will Not Find My Storedge A5200 Enclosure But Can See The Drives sk


    For the life of me I cannot get our T2000 to recognize the StorEdge A5200 enclosure.
    The command 'luxadm probe' will find the drives, however not the enclosure.

    I can take this same enclosure and connect it to an e4500 and it is discovered correctly so I doubt that it is a hardware failure.

    [root@ora3.test /var/adm]$ luxadm probe
    No Network Array enclosures found in /dev/es

    Found Fibre Channel device(s):
    Node WWN:2000002037c29d7b Device Type:Disk device
    Logical Path:/dev/rdsk/c2t32d0s2

    ... and so on for all of the drives ...

    I tried an 'luxadm insert', however this was also unsuccessful.

    I did notice some errors (CRC) in the /var/adm/messages file;

    Feb 19 11:14:17 ora3.test.experts-exchange.com qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
    Feb 19 11:14:27 ora3.test.experts-exchange.com scsi: [ID 243001 kern.warning] WARNING: /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0 (fcp2):
    Feb 19 11:14:27 ora3.test.experts-exchange.com INQUIRY-83 to D_ID=0x9e lun=0x0 failed: State:Local Reject, Reason:CRC Error. Giving up
    Feb 19 11:14:42 ora3.test.experts-exchange.com scsi: [ID 243001 kern.warning] WARNING: /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0 (fcp2):
    Feb 19 11:14:42 ora3.test.experts-exchange.com INQUIRY-83 to D_ID=0x75 lun=0x0 failed: State:Local Reject, Reason:CRC Error. Giving up
    Feb 19 11:14:47 ora3.test.experts-exchange.com scsi: [ID 799468 kern.info] ssd44 at fp2: name w2200002037de6e1d,0, bus address ab
    Feb 19 11:14:47 ora3.test.experts-exchange.com genunix: [ID 936769 kern.info] ssd44 is /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/ssd@w2200002037de6e1d,0
    Feb 19 11:14:47 ora3.test.experts-exchange.com genunix: [ID 408114 kern.info] /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/ssd@w2200002037de6e1d,0 (ssd44) online

    I am guessing that these were the requests to get the enclosure info.

    We are running Solaris 10 with up to date patches;
    [root@ora3.test /var/adm]$ uname -a
    SunOS ora3.test.com 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Fire-T200

    Again, thank you for your time!

    DB:2.37:Luxadm Will Not Find My Storedge A5200 Enclosure But Can See The Drives sk

    After talking to Sun support, I was guided to install patch 125184-10 which solved my problem.

    Thanks to all!

  • RELEVANCY SCORE 2.37

    DB:2.37:T1000 Dual Drive Assembly 3c


    Hi

    I am trying to install a dual drive assembly on a T1000. I have the assembly installed but cannot seem to identify the additional drive when I power up.
    I have updated the firmware to the most current version. When I use probe-scsi-all from the OBP it only returns the original drive regardless if the drive is located in drive slot 0 or 1. I have not formatted the unseen drive yet but I thought probe-scsi-all would display it at the OBP. Should I be booting from the good drive and then formatting the unseen drive? Will this then make the drive visible?

    {0} ok probe-scsi-all
    /pci@7c0/pci@0/pci@8/scsi@2

    MPT Version 1.05, Firmware Version 1.06.00.00

    Target 0 Volume 2
    Unit 0 Disk LSILOGICLogical Volume 3000 143112591 Blocks, 73 GB

    /pci@780/pci@0/scsi@8,1

    /pci@780/pci@0/scsi@8

    {0} ok devalias disk
    disk /pci@7c0/pci@0/pci@8/scsi@2/disk@0,0
    {0} ok sc showhost
    Sun-Fire-T1000 System Firmware 6.6.5 2008/07/29 15:28

    Host flash versions:
    OBP 4.28.9 2008/06/30 21:24
    Hypervisor 1.6.4 2008/06/06 04:57
    POST 4.28.9 2008/06/30 21:56
    sc

    DB:2.37:T1000 Dual Drive Assembly 3c

    Hi Michael

    I used the Installing the Single or Dual-Drive Assembly in the Sun Fire T1000 guide. I have double checked the J5002 J5003 connectors and both are connected to the motherboard in the correct slots.

    I have two hard drives 1 a Fujitsu 1 Sanio, I can reverse the placement of the drives and each time I do probe-scsi-all the Fujitsu drive seems to be recognised but the Sanio does not (see below for output). I have even tried replacing the Sanio with another Fujitsu drive just encase the drive is faulty but I get the same results.

    I will try and do a network install and use the raidctrl to see what it brings up.

    Thanks,
    Alisdair

    Fujitsu Drive 0 Sanio Drive 1

    {0} ok probe-scsi-all
    /pci@7c0/pci@0/pci@8/scsi@2

    MPT Version 1.05, Firmware Version 1.06.00.00

    Target 0 Volume 2
    Unit 0 Disk LSILOGICLogical Volume 3000 143112591 Blocks, 73 GB

    /pci@780/pci@0/scsi@8,1

    /pci@780/pci@0/scsi@8
    {0} ok devalias disk
    disk /pci@7c0/pci@0/pci@8/scsi@2/disk@0,0

    Sanio Drive 0 Fujitsu Drive 1
    {0} ok probe-scsi-all
    /pci@7c0/pci@0/pci@8/scsi@2

    MPT Version 1.05, Firmware Version 1.06.00.00

    Target 1 Volume 0
    Unit 0 Disk LSILOGICLogical Volume 3000 143112591 Blocks, 73 GB

    /pci@780/pci@0/scsi@8,1

    /pci@780/pci@0/scsi@8

    {0} ok devalias disk
    disk /pci@7c0/pci@0/pci@8/scsi@2/disk@0,0

    Empty Drive 0 Fujitsu Drive 1
    {0} ok probe-scsi-all
    /pci@7c0/pci@0/pci@8/scsi@2

    MPT Version 1.05, Firmware Version 1.06.00.00

    Target 1 Volume 0
    Unit 0 Disk LSILOGICLogical Volume 3000 143112591 Blocks, 73 GB

    /pci@780/pci@0/scsi@8,1

    /pci@780/pci@0/scsi@8

    {0} ok devalias disk
    disk /pci@7c0/pci@0/pci@8/scsi@2/disk@0,0

  • RELEVANCY SCORE 2.36

    DB:2.36:Cambiar Path De Owa En Exchange 2007 ja


    Hola amigos, me gustaria saber como cambiar el path de conexion a owa (p.ej https://mail.dominio.com/owa). Probe cambiando el path en la consola de Exchange Server pero no he podido. Actualmente redirecciono https://mail.dominio.com hacia https://mail.dominio.com/owa pero necesito cambiar el path owaSaludos!

    DB:2.36:Cambiar Path De Owa En Exchange 2007 ja

    Hola, me puedes dar el enlace donde le responder? lo necesito. GraciasPeter Chirinos | Microsoft Office Specialist, Software Developer, Microsoft Certified Professional, MAP , Microsoft Small Business Specialist| @peter_chirinos

  • RELEVANCY SCORE 2.36

    DB:2.36:Attempting To Use Http Probe js



    We're currently using the TCP probe for a load balanced app, however will need to change it to HTTP. The back-end servers are Window based and are running IIS. There's an app team, another team that supports IIS and another team that support the servers. Once we've configured the HTTP probe on the ACE, including the request method and the url, which of the above team would we need to reach out to coordinate the url path and the expected status code from the server?

     

    Thanks.

     

    _ Greg...  

    DB:2.36:Attempting To Use Http Probe js


    Hi Greg,

    I think it should be the application team who manages that application should be the one responsible but then they are also known as server team:) Anyways good luck and let me know if you have any questions.

     

    Regards,

    Kanwal

    Note: Please mark answers if they are helpful.

  • RELEVANCY SCORE 2.36

    DB:2.36:Replacing The Cdrom With A Dvd (Tos Sd-M1401-S) 3x


    I am thinking of replacing the cdrom with a dvd (TOS SD-M1401-S) on an Ultra 60 with Solaris 9. Are there going to be any "special" steps other than making sure the scsi id is set to 6 on the dvd? I mean, are there steps like probe-scsi, order of filesystem preference config, etc. things that are important to do?

    DB:2.36:Replacing The Cdrom With A Dvd (Tos Sd-M1401-S) 3x

    I am thinking of replacing the cdrom with a dvd (TOS SD-M1401-S) on an Ultra 60 with Solaris 9. Are there going to be any "special" steps other than making sure the scsi id is set to 6 on the dvd? I mean, are there steps like probe-scsi, order of filesystem preference config, etc. things that are important to do?

  • RELEVANCY SCORE 2.36

    DB:2.36:Probe-Scsi-All Not Showing Storedge dc


    Need help on storedge 3310......
    As I discussed an issue on 3310 .......

    I tried probe-scsi-all to check the storage device........but its not showing it.............

    any idea??

    DB:2.36:Probe-Scsi-All Not Showing Storedge dc

    Ok.
    But it was working fine before the upgrade....also the luns are mapped ...
    when I tries to remap with sccli, it says ...already mapped.........

    just stucked..........

  • RELEVANCY SCORE 2.36

    DB:2.36:Different Size For Same A Structure In 32 And 64-Bit Application On X86_64 cx


    My driver returns that the ioctl isn't recognized when the ioctl is called from 32-bit application, but not from 64-bit application on 64-bit x86_x64 system. I found there is a different value of cmd argument in same an ioctl. And the root cause is that the size is difference for same a structure in 32 and 64-bit application after I digged more. I know the structure define isn't good for the alignment, but the problem doesn't happen on 64-bit Sparc system.

    #define IOC_DEVICE_PATHS IOR('S',21,devicepath_t)

    typedef struct {
    int instance; /* Instance Number of this path */
    int tgt; /* SCSI target for this path */
    int lun; /* SCSI LUN for this path */
    uint64_t wwnn; /* WWNN for this fc path */
    uint64_t wwpn; /* WWPN for this fc path */
    int path_type; /* primary 0 or alt 1, 2, 3, ..., 15 */
    /* none 0xFF */
    int enable; /* path enable 1, disable 0 */
    char devpath[125]; /* devices path of this path */
    char dev_ser[33]; /* Device serial number */
    char ucode_level[32]; /* Device microcode level */
    } device_path_t;

    In 32-bit application, the size of the structure is 0xE4 (228) with 8 bytes padding.
    device_path_t 228 instance 4 tgt 4 lun 4 wwnn 8 wwpn 8 path_type 4 enable 4 devpath 125 dev_ser 33 ucode_level 32
    cmd 40E45315 size of device_path_t E4

    In 64-bit application, the size is 0xE8 (232) with 12 bytes padding.
    device_path_t 232 instance 4 tgt 4 lun 4 wwnn 8 wwpn 8 path_type 4 enable 4 devpath 125 dev_ser 33 ucode_level 32
    cmd 40E85315 size of device_path_t E8

    Is it a compiling issue? How to fix it without the change for the structure?

    Thanks for your help.

    DB:2.36:Different Size For Same A Structure In 32 And 64-Bit Application On X86_64 cx

    Try reading documentation for '#pragma pack'. (In the C manual)
    The padding between the odd-sized character field sis probably different.
    I think you can use #pragma pack to affect how much padding the compiler
    puts between things. In order to really understand what's going
    on you'll want to know exactly where the compiler has placed
    the padding bytes in both the 32-bit and 64-bit compiles.

    --chris

  • RELEVANCY SCORE 2.36

    DB:2.36:How Detect External Scsi Storage Without Reboot? f9


    Need help.
    Does someone can let me know the way to detect external scsi drive connected to sun server without rebooting server, and running "probe-scsi-all" command from OK prompt.

  • RELEVANCY SCORE 2.36

    DB:2.36:Why Would A Failed Drive Scare The Rest Of The Drives Off The Scsi Bus? 7a


    I have a VMWare 4-based system running Solaris 10 5/09 s10x_u7wos_08 as a VM configured with PCI passthrough to give it control over an LSI 22320SE SCSI HBA. This is connected to an external Areca SATA to SCSI RAID array in JBOD mode. The drives are 750 GB Seagate Barracudas, ST3750640AS and are part of a raidz2 in ZFS.

    The Areca controller reports a single drive has failed and Solaris notices it simultaneously. So far, so good.

    But immediately after that, the other drives on this array start running frightened as if whatever the first drive got is contagious. Two others even go offline temporarily. What could cause this to happen?

    Of course, the pool goes offline. However, on reboot, the pool comes up with just that first failed drive in a "cannot open" state.

    Aug 4 16:34:51 therealvault fmd: [ID 441519 daemon.error] SUNW-MSG-ID: ZFS-8000-GH, TYPE: Fault, VER: 1, SEVERITY: Major
    Aug 4 16:34:51 therealvault EVENT-TIME: Tue Aug 4 16:34:51 EDT 2009
    Aug 4 16:34:51 therealvault PLATFORM: VMware Virtual Platform, CSN: VMware-42 0d 39 ad 2b 8f 11 e0-5a 2f 74 a0 ad 7a f4 86, HOSTNAME: therealvault
    Aug 4 16:34:51 therealvault SOURCE: zfs-diagnosis, REV: 1.0
    Aug 4 16:34:51 therealvault EVENT-ID: c8bc8758-7a63-ecd3-b550-e3181e9c64be
    Aug 4 16:34:51 therealvault DESC: The number of checksum errors associated with a ZFS device
    Aug 4 16:34:51 therealvault exceeded acceptable levels. Refer to http://sun.com/msg/ZFS-8000-GH for more information.
    Aug 4 16:34:51 therealvault AUTO-RESPONSE: The device has been marked as degraded. An attempt
    Aug 4 16:34:51 therealvault will be made to activate a hot spare if available.
    Aug 4 16:34:51 therealvault IMPACT: Fault tolerance of the pool may be compromised.
    Aug 4 16:34:51 therealvault REC-ACTION: Run 'zpool status -x' and replace the bad device.
    Aug 4 16:36:05 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0 (mpt2):
    Aug 4 16:36:05 therealvault Disconnected command timeout for Target 1
    Aug 4 16:36:05 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,0 (sd35):
    Aug 4 16:36:05 therealvault SCSI transport failed: reason 'reset': retrying command
    Aug 4 16:36:08 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,0 (sd35):
    Aug 4 16:36:08 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:10 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,0 (sd35):

    Now the others are getting nervous:
    Aug 4 16:36:20 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,4 (sd31):
    Aug 4 16:36:20 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:21 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,5 (sd32):
    Aug 4 16:36:21 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:21 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,2 (sd37):
    Aug 4 16:36:21 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:21 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,3 (sd38):
    Aug 4 16:36:21 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:21 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,0 (sd27):
    Aug 4 16:36:21 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:22 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,1 (sd28):
    Aug 4 16:36:22 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:22 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,6 (sd33):
    Aug 4 16:36:22 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:22 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,7 (sd34):
    Aug 4 16:36:22 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:22 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,4 (sd39):
    Aug 4 16:36:22 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:23 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,5 (sd40):
    Aug 4 16:36:23 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:23 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,2 (sd29):
    Aug 4 16:36:23 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:23 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,3 (sd30):
    Aug 4 16:36:23 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:23 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,6 (sd41):
    Aug 4 16:36:23 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:24 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,7 (sd42):
    Aug 4 16:36:24 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:24 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,2 (sd29):

    And these two were frightened to "death" at least until I rebooted:
    Aug 4 16:37:35 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,1 (sd28):
    Aug 4 16:37:35 therealvault drive offline
    Aug 4 16:37:35 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,0 (sd27):
    Aug 4 16:37:35 therealvault drive offline

    Now the log is winding down with errors here:
    Aug 4 16:48:59 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,5 (sd32):
    Aug 4 16:48:59 therealvault SYNCHRONIZE CACHE command failed (5)
    Aug 4 16:48:59 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,4 (sd31):
    Aug 4 16:48:59 therealvault disk not responding to selection
    Aug 4 16:48:59 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,4 (sd31):
    Aug 4 16:48:59 therealvault SYNCHRONIZE CACHE command failed (5)
    Aug 4 16:48:59 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,3 (sd30):
    Aug 4 16:48:59 therealvault disk not responding to selection

    DB:2.36:Why Would A Failed Drive Scare The Rest Of The Drives Off The Scsi Bus? 7a

    I have a VMWare 4-based system running Solaris 10 5/09 s10x_u7wos_08 as a VM configured with PCI passthrough to give it control over an LSI 22320SE SCSI HBA. This is connected to an external Areca SATA to SCSI RAID array in JBOD mode. The drives are 750 GB Seagate Barracudas, ST3750640AS and are part of a raidz2 in ZFS.

    The Areca controller reports a single drive has failed and Solaris notices it simultaneously. So far, so good.

    But immediately after that, the other drives on this array start running frightened as if whatever the first drive got is contagious. Two others even go offline temporarily. What could cause this to happen?

    Of course, the pool goes offline. However, on reboot, the pool comes up with just that first failed drive in a "cannot open" state.

    Aug 4 16:34:51 therealvault fmd: [ID 441519 daemon.error] SUNW-MSG-ID: ZFS-8000-GH, TYPE: Fault, VER: 1, SEVERITY: Major
    Aug 4 16:34:51 therealvault EVENT-TIME: Tue Aug 4 16:34:51 EDT 2009
    Aug 4 16:34:51 therealvault PLATFORM: VMware Virtual Platform, CSN: VMware-42 0d 39 ad 2b 8f 11 e0-5a 2f 74 a0 ad 7a f4 86, HOSTNAME: therealvault
    Aug 4 16:34:51 therealvault SOURCE: zfs-diagnosis, REV: 1.0
    Aug 4 16:34:51 therealvault EVENT-ID: c8bc8758-7a63-ecd3-b550-e3181e9c64be
    Aug 4 16:34:51 therealvault DESC: The number of checksum errors associated with a ZFS device
    Aug 4 16:34:51 therealvault exceeded acceptable levels. Refer to http://sun.com/msg/ZFS-8000-GH for more information.
    Aug 4 16:34:51 therealvault AUTO-RESPONSE: The device has been marked as degraded. An attempt
    Aug 4 16:34:51 therealvault will be made to activate a hot spare if available.
    Aug 4 16:34:51 therealvault IMPACT: Fault tolerance of the pool may be compromised.
    Aug 4 16:34:51 therealvault REC-ACTION: Run 'zpool status -x' and replace the bad device.
    Aug 4 16:36:05 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0 (mpt2):
    Aug 4 16:36:05 therealvault Disconnected command timeout for Target 1
    Aug 4 16:36:05 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,0 (sd35):
    Aug 4 16:36:05 therealvault SCSI transport failed: reason 'reset': retrying command
    Aug 4 16:36:08 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,0 (sd35):
    Aug 4 16:36:08 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:10 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,0 (sd35):

    Now the others are getting nervous:
    Aug 4 16:36:20 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,4 (sd31):
    Aug 4 16:36:20 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:21 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,5 (sd32):
    Aug 4 16:36:21 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:21 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,2 (sd37):
    Aug 4 16:36:21 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:21 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,3 (sd38):
    Aug 4 16:36:21 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:21 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,0 (sd27):
    Aug 4 16:36:21 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:22 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,1 (sd28):
    Aug 4 16:36:22 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:22 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,6 (sd33):
    Aug 4 16:36:22 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:22 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,7 (sd34):
    Aug 4 16:36:22 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:22 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,4 (sd39):
    Aug 4 16:36:22 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:23 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,5 (sd40):
    Aug 4 16:36:23 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:23 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,2 (sd29):
    Aug 4 16:36:23 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:23 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,3 (sd30):
    Aug 4 16:36:23 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:23 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,6 (sd41):
    Aug 4 16:36:23 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:24 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@1,7 (sd42):
    Aug 4 16:36:24 therealvault SCSI transport failed: reason 'incomplete': retrying command
    Aug 4 16:36:24 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,2 (sd29):

    And these two were frightened to "death" at least until I rebooted:
    Aug 4 16:37:35 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,1 (sd28):
    Aug 4 16:37:35 therealvault drive offline
    Aug 4 16:37:35 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,0 (sd27):
    Aug 4 16:37:35 therealvault drive offline

    Now the log is winding down with errors here:
    Aug 4 16:48:59 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,5 (sd32):
    Aug 4 16:48:59 therealvault SYNCHRONIZE CACHE command failed (5)
    Aug 4 16:48:59 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,4 (sd31):
    Aug 4 16:48:59 therealvault disk not responding to selection
    Aug 4 16:48:59 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,4 (sd31):
    Aug 4 16:48:59 therealvault SYNCHRONIZE CACHE command failed (5)
    Aug 4 16:48:59 therealvault scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci15ad,7a0@17,1/pci1000,10b0@0/sd@0,3 (sd30):
    Aug 4 16:48:59 therealvault disk not responding to selection

  • RELEVANCY SCORE 2.36

    DB:2.36:Automounting Fails For Some Dvds zm



    Hello,

    Im trying to get automounter (HAL with thunar-volman) working correctly, but I am hitting a problem:

    All CDs - work OK (mount automatically)DVDs recorded from .ISO images - work OK (mount automatically)DVDs that Ive burned with data - wont mount automatically, have to go to terminal and manually say mount /dev/sr0 /media/cdrom.

    Running hald as non-daemon and verbose gives me:
    I insert DVD
    [13943]: 22:46:56.004 [i] addon-storage.c:355: Checking whether device /dev/sr0 is locked on HAL
    [13943]: 22:46:56.005 [i] addon-storage.c:363: ... device /dev/sr0 is not locked on HAL
    CD spins and the drive LED is blinking
    [13943]: 22:46:56.004 [i] addon-storage.c:355: Checking whether device /dev/sr0 is locked on HAL
    [13943]: 22:46:56.005 [i] addon-storage.c:363: ... device /dev/sr0 is not locked on HAL
    22:47:12.020 [i] osspec.c:241: SEQNUM=1495, ACTION=change, SUBSYSTEM=scsi, DEVPATH=/sys/devices/pci0000:00/0000:00:02.5/host1/target1:0:0/1:0:0:0, DEVNAME=, IFINDEX=0
    22:47:12.020 [i] hotplug.c:114: /sys/devices/pci0000:00/0000:00:02.5/host1/target1:0:0/1:0:0:0 is a device (store)
    22:47:12.020 [i] device.c:4522: refresh_dev: subsys=scsi
    [13943]: 22:47:12.024 [D] addon-storage.c:542: Media insertion detected on /dev/sr0
    22:47:12.024 [D] hald_dbus.c:1652: udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_H44N, key=storage.removable.media_available
    22:47:12.025 [i] hald_dbus.c:3052: entering, local_interface=1
    22:47:12.025 [D] hald_dbus.c:3061: udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_H44N
    22:47:12.025 [i] blockdev.c:1666: blockdev_rescan_device: udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_H44N
    Run started hald-probe-storage (10000) (0)
    ! full path is /usr/lib/hal/hald-probe-storage, program_dir is /usr/lib/hal
    woohoo
    [13949]: 22:47:12.028 [D] probe-storage.c:155: Doing probe-storage for /dev/sr0 (bus scsi) (drive_type cdrom) (udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_H44N) (--only-check-for-fs==1)
    [13949]: 22:47:12.028 [D] probe-storage.c:163: Doing open (/dev/sr0, O_RDONLY | O_NONBLOCK)
    [13949]: 22:47:12.032 [D] probe-storage.c:169: Returned from open(2)
    [13949]: 22:47:12.040 [D] probe-storage.c:310: Checking for optical disc on /dev/sr0
    [13949]: 22:47:12.041 [D] probe-storage.c:318: Doing open (/dev/sr0, O_RDONLY | O_NONBLOCK | O_EXCL)
    [13949]: 22:47:12.042 [D] probe-storage.c:348: PROBE HAS EXCLUSIVE LOCK ON CDROM
    [13949]: 22:47:12.045 [D] probe-storage.c:390: media size = 3086548992
    [13949]: 22:47:12.046 [D] probe-storage.c:398: PROBE CLOSED LOCK ON CDROM
    22:47:12.047 [i] hald_dbus.c:1342: storage.cdrom.read_speed - 22160
    22:47:12.047 [i] hald_dbus.c:1342: storage.cdrom.write_speed - 24930
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 24930
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 24929
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 22160
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 22159
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 11080
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 11079
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 5540
    22:47:12.047 [i] hald_dbus.c:1366: storage.removable.media_available - True
    22:47:12.047 [i] hald_dbus.c:1350: storage.removable.media_size - 3086548992
    pid 13949: rc=2 signaled=0: /usr/lib/hal/hald-probe-storage
    22:47:12.049 [i] blockdev.c:1622: hald-probe-storage --only-check-for-media returned 2 (exit_type=0)
    22:47:12.049 [i] blockdev.c:1638: Media insertion detected with file system on main block device; synthesizing hotplug add
    22:47:12.049 [i] osspec.c:966: hal_util_find_known_parent: /sys/block/sr0/fakevolume-/sys/block/sr0
    22:47:12.049 [i] blockdev.c:874: block_add: sysfs_path=/sys/block/sr0/fakevolume dev=/dev/sr0 is_part=0, parent=0x09e8ca40
    22:47:12.049 [i] blockdev.c:882: Handling /dev/sr0 as fakevolume - sysfs_path_real=(null)
    Run started hald-probe-volume (10000) (0)
    ! full path is /usr/lib/hal/hald-probe-volume, program_dir is /usr/lib/hal
    [13950]: 22:47:12.053 [D] probe-volume.c:377: Doing probe-volume for /dev/sr0

    [13950]: 22:47:12.065 [D] probe-volume.c:388: volume.block_size = 2048
    [13950]: 22:47:12.065 [D] probe-volume.c:392: volume.size = 3086548992
    [13950]: 22:47:12.072 [D] probe-volume.c:436: Disc in /dev/sr0 has data
    [13950]: 22:47:13.913 [D] probe-volume.c:469: get_disc_type returned 0x11
    22:47:22.055 [i] blockdev.c:387: entering; exit_type=1, return_code=0
    [13950]: 22:47:22.296 [E] probe-volume.c:301: Timed out probing /dev/sr0 - broken device driver?
    pid 13950: rc=1 signaled=0: /usr/lib/hal/hald-probe-volume
    [13943]: 22:47:28.004 [i] addon-storage.c:355: Checking whether device /dev/sr0 is locked on HAL
    [13943]: 22:47:28.005 [i] addon-storage.c:363: ... device /dev/sr0 is not locked on HAL

    DB:2.36:Automounting Fails For Some Dvds zm


    Hello,

    Im trying to get automounter (HAL with thunar-volman) working correctly, but I am hitting a problem:

    All CDs - work OK (mount automatically)DVDs recorded from .ISO images - work OK (mount automatically)DVDs that Ive burned with data - wont mount automatically, have to go to terminal and manually say mount /dev/sr0 /media/cdrom.

    Running hald as non-daemon and verbose gives me:
    I insert DVD
    [13943]: 22:46:56.004 [i] addon-storage.c:355: Checking whether device /dev/sr0 is locked on HAL
    [13943]: 22:46:56.005 [i] addon-storage.c:363: ... device /dev/sr0 is not locked on HAL
    CD spins and the drive LED is blinking
    [13943]: 22:46:56.004 [i] addon-storage.c:355: Checking whether device /dev/sr0 is locked on HAL
    [13943]: 22:46:56.005 [i] addon-storage.c:363: ... device /dev/sr0 is not locked on HAL
    22:47:12.020 [i] osspec.c:241: SEQNUM=1495, ACTION=change, SUBSYSTEM=scsi, DEVPATH=/sys/devices/pci0000:00/0000:00:02.5/host1/target1:0:0/1:0:0:0, DEVNAME=, IFINDEX=0
    22:47:12.020 [i] hotplug.c:114: /sys/devices/pci0000:00/0000:00:02.5/host1/target1:0:0/1:0:0:0 is a device (store)
    22:47:12.020 [i] device.c:4522: refresh_dev: subsys=scsi
    [13943]: 22:47:12.024 [D] addon-storage.c:542: Media insertion detected on /dev/sr0
    22:47:12.024 [D] hald_dbus.c:1652: udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_H44N, key=storage.removable.media_available
    22:47:12.025 [i] hald_dbus.c:3052: entering, local_interface=1
    22:47:12.025 [D] hald_dbus.c:3061: udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_H44N
    22:47:12.025 [i] blockdev.c:1666: blockdev_rescan_device: udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_H44N
    Run started hald-probe-storage (10000) (0)
    ! full path is /usr/lib/hal/hald-probe-storage, program_dir is /usr/lib/hal
    woohoo
    [13949]: 22:47:12.028 [D] probe-storage.c:155: Doing probe-storage for /dev/sr0 (bus scsi) (drive_type cdrom) (udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_H44N) (--only-check-for-fs==1)
    [13949]: 22:47:12.028 [D] probe-storage.c:163: Doing open (/dev/sr0, O_RDONLY | O_NONBLOCK)
    [13949]: 22:47:12.032 [D] probe-storage.c:169: Returned from open(2)
    [13949]: 22:47:12.040 [D] probe-storage.c:310: Checking for optical disc on /dev/sr0
    [13949]: 22:47:12.041 [D] probe-storage.c:318: Doing open (/dev/sr0, O_RDONLY | O_NONBLOCK | O_EXCL)
    [13949]: 22:47:12.042 [D] probe-storage.c:348: PROBE HAS EXCLUSIVE LOCK ON CDROM
    [13949]: 22:47:12.045 [D] probe-storage.c:390: media size = 3086548992
    [13949]: 22:47:12.046 [D] probe-storage.c:398: PROBE CLOSED LOCK ON CDROM
    22:47:12.047 [i] hald_dbus.c:1342: storage.cdrom.read_speed - 22160
    22:47:12.047 [i] hald_dbus.c:1342: storage.cdrom.write_speed - 24930
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 24930
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 24929
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 22160
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 22159
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 11080
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 11079
    22:47:12.047 [i] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds - 5540
    22:47:12.047 [i] hald_dbus.c:1366: storage.removable.media_available - True
    22:47:12.047 [i] hald_dbus.c:1350: storage.removable.media_size - 3086548992
    pid 13949: rc=2 signaled=0: /usr/lib/hal/hald-probe-storage
    22:47:12.049 [i] blockdev.c:1622: hald-probe-storage --only-check-for-media returned 2 (exit_type=0)
    22:47:12.049 [i] blockdev.c:1638: Media insertion detected with file system on main block device; synthesizing hotplug add
    22:47:12.049 [i] osspec.c:966: hal_util_find_known_parent: /sys/block/sr0/fakevolume-/sys/block/sr0
    22:47:12.049 [i] blockdev.c:874: block_add: sysfs_path=/sys/block/sr0/fakevolume dev=/dev/sr0 is_part=0, parent=0x09e8ca40
    22:47:12.049 [i] blockdev.c:882: Handling /dev/sr0 as fakevolume - sysfs_path_real=(null)
    Run started hald-probe-volume (10000) (0)
    ! full path is /usr/lib/hal/hald-probe-volume, program_dir is /usr/lib/hal
    [13950]: 22:47:12.053 [D] probe-volume.c:377: Doing probe-volume for /dev/sr0

    [13950]: 22:47:12.065 [D] probe-volume.c:388: volume.block_size = 2048
    [13950]: 22:47:12.065 [D] probe-volume.c:392: volume.size = 3086548992
    [13950]: 22:47:12.072 [D] probe-volume.c:436: Disc in /dev/sr0 has data
    [13950]: 22:47:13.913 [D] probe-volume.c:469: get_disc_type returned 0x11
    22:47:22.055 [i] blockdev.c:387: entering; exit_type=1, return_code=0
    [13950]: 22:47:22.296 [E] probe-volume.c:301: Timed out probing /dev/sr0 - broken device driver?
    pid 13950: rc=1 signaled=0: /usr/lib/hal/hald-probe-volume
    [13943]: 22:47:28.004 [i] addon-storage.c:355: Checking whether device /dev/sr0 is locked on HAL
    [13943]: 22:47:28.005 [i] addon-storage.c:363: ... device /dev/sr0 is not locked on HAL

  • RELEVANCY SCORE 2.36

    DB:2.36:Message About Incorrect Client k8


    Hi everybody. I have a message when trying to backup a client. The backup is successful but appears the message:Successful Save Sets --- * sun8d7siba1:Probe savegrp: suppressed 11 lines of output. * sun8d7siba1:Probe 7198:savefs: path /informix/QAS by default belongs to client sun8d7siba1 and NOT client sun8d7siba1! * sun8d7siba1:Probe 7200:savefs: Default client index for scheduled save will be that of sun8d7siba1. * sun8d7siba1:Probe 7198:savefs: path /var/mqm by default belongs to client sun8d7siba1 and NOT client sun8d7siba1! * sun8d7siba1:Probe 7200:savefs: Default client index for scheduled save will be that of sun8d7siba1. * sun8d7siba1:Probe 7198:savefs: path /export/home by default belongs to client sun8d7siba1 and NOT client sun8d7siba1! * sun8d7siba1:Probe 7200:savefs: Default client index for scheduled save will be that of sun8d7siba1. * sun8d7siba1:Probe 7198:savefs: path /EAGENT by default belongs to client sun8d7siba1 and NOT client sun8d7siba1! * sun8d7siba1:Probe 7200:savefs: Default client index for scheduled save will be that of sun8d7siba1. * sun8d7siba1:Probe savefs sun8d7siba1: succeeded. As you see, it seems to be a cluster issue, but the client is a single node. And the strange is that the message makes reference to the same client (sun8d7siba1).Have you any idea of what is going on?Thank you in advance

    DB:2.36:Message About Incorrect Client k8

    I got this first time on 7.4.5 on HPUX (before I was running 7.4.4.5 without problems). I've been given the patch so if you find yourself affected open the case... (in my case with standalone clients I could ignore it, but it also cause failures with cluster clients so....).

  • RELEVANCY SCORE 2.35

    DB:2.35:Sun Fire 280r - Fast Data Access Mmu Miss Error Message 1s


    We recently removed the RSC card from one of our Sun Fire 280R servers (to replace a faulty one on a more important server.)
    Since then it won't boot automatcially, instead it drops to the boot prompt.
    When we type boot it fails with the error Fast Data Access MMU Miss.
    Trying a test-all it hangs.
    probe-scsi and probe-scsi-all work fine.
    Is there any way to disable the RSC card?
    What could be casunig these errors?

    We don't require the RSC card as we intend to install Linux (RedHat) on this server.

    Many thanks

    DB:2.35:Sun Fire 280r - Fast Data Access Mmu Miss Error Message 1s

    John, the 280R supports X2136A and earlier version, these cards can run Red Hat Linux. Solaris 10 supports many GNU applications and can be configured with many commercial applications supported with Red Hat Linux. Linux on SPARC is limited and cumbersome compared to Solaris! On our old Hardware support forum companies could not solicit business by posting offers, perhaps this should be discouraged here too. The US market can be very good for used hardware, there are always good deals to be had, however be careful with warranty promises!

  • RELEVANCY SCORE 2.35

    DB:2.35:V440 Scsi Issues As Relates To Lsi1030 Controller cm


    Hello all,

    I am running into issues with the SCSI bus on a V440. I am running Solaris 10 on the server. I am trying to attache a StorageTek L20 tape library to the onboard Ultra 320 SVD SCSI port on the back of the V440. When I do a probe-scsi-all I get the following errors:

    ERROR: LSI1030 timeout waiting for interrupt.
    ERROR: LSI1030 Could not set initiator ID
    Can't open SCSI adapter

    ERROR: LSI1030 MPT Firmware, fault code 8112 PCI BUS Fault.

    I have done the reset-all and issued the probe-scsi-all before boot, so that is not an issues. The LSI1030 firmware is the latest release.

    Any ideas on how to attack this one?

    DB:2.35:V440 Scsi Issues As Relates To Lsi1030 Controller cm

    For those that may read this thread a year or two or three from now.

    They were able to receive additional assistance from other forums, as well.
    http://www.tek-tips.com/viewthread.cfm?qid=1375944
    http://www.linuxquestions.org/questions/showthread.php?t=558412

  • RELEVANCY SCORE 2.35

    DB:2.35:Updating The Cluster Hiararchy Physical Paths Tree After Replacing The Scsi 77


    Dear Gents,

    I have 2 Clustered Nodes whic are connected to a 3310 SCSI Array thriugh a single SCSI cable path for each.

    I am planning ot replace one SCSI Card from one node with a different SCSI Card which use the QUS driver instead of the MPT old Driver.

    i need a complete procedure in how to do so from the begining. including shutting down the nodes. then power which one first and how to update the cluster for the new SCSI paths. etc

    Solaris 10 is installed in both of the nodes.

    Best Regards

    DB:2.35:Updating The Cluster Hiararchy Physical Paths Tree After Replacing The Scsi 77

    If at all possible I would test this in a lab environment first.

    Granted it is tricky to exactly replicate server, storage, etc.

    Flop services over to the non-SCSI replacement node
    Shutdown SCSI replacement node
    Replace the SCSI card
    Boot node into cluster
    cldev repair

    The only complication I can think of is if you had the cluster quorum on the storage array and the OS on the repaired node was not able to find the quorum due to the HBA changing.

    If you are using a quorum server this should not be an issue (and maybe it isn't, just thinking out loud).

    The only other thing I could think of is if there are any configuration settings such as SCSI ID between the old HBA and the 3310 that you would need to match.

    For example, old-HBA was SCSI ID 3 and you need the new-HBA to match.

    Some of the older Sun arrays did a split configuration deal to work with cluster. I'm not sure if the 3310 is setup this way so you may want to check that bit out as well.

    I would be interested to see if anyone else has something to add in here as I haven't run into this exact scenario before...usually changing disks rather than controllers.

    Edited by: nate_keegan on Oct 21, 2009 2:49 PM

  • RELEVANCY SCORE 2.35

    DB:2.35:Scsi Aha 2940uw-Of Card Drivers For Solaris V8 On Sparc m1


    I'm trying to upgrade my Ultra-5 system from 2.6 to 2.8 (solaris8) and the OS is unable to recogize the Adaptec AHA 2940UW-OF (Open Firmware) SCSI card.

    I've upgraded the system bios to most recent version. The Open Boot "probe-scsi" command does recognize the card and all the devices on the SCSI bus.

    I looked at Adaptec's website, no updated drivers are listed, and they are not able to comment further. I haven't been able to find anything on the drivers on Sun's site as well.

    Help!

    DB:2.35:Scsi Aha 2940uw-Of Card Drivers For Solaris V8 On Sparc m1

    Hi

    sorry can't offer help. In fact this is a me too response
    I am about to take delivery of an Ultra5 and I have a standard
    Adaptec PC 2940UW. Is there any way I could use this with the
    Ultra 5? . Is the Open Firmware a flashable replacement
    for the standard PC BIOS ? (Probably not because I can't find
    any reference to it on Adaptec's web site.

    If this is not possible what SCSI card choices do I have. (I would
    like to be able to attach old narrow devices and wide devices

  • RELEVANCY SCORE 2.35

    DB:2.35:Vs/2005 Debugger Loads Incomplete Path.... 9x


    For some reason, my VS/2005 has stopped debugging apps, instead, when I try to run them, I get a message that says somedll.dll is not found - it's always a DLL that is on the path (the .EXE will run from a command prompt).
    I wrote a small program that does a getenv(PATH); and what it returns is only 577 bytes, and my actual path is around 1900.  I've tried changing some paths in the Tools|Options|C++ Directorys|Executable, but that doesn't seem to matter.
    My VS is version 8.0.50727.42 (RTM.050727-4200).
    Help!  This is driving me crazy!!!!!!!!!!!!!!!!
     
    Thanks!
     
    - David Little
    - COADE, Inc.
    - Houston, Texas

    DB:2.35:Vs/2005 Debugger Loads Incomplete Path.... 9x

    Visual Studio gets its path from explorer.  So whatever path is around 1900 is not getting passed to VS (use ProcessExplorer to find out what path VS has).  The path in CMD.EXE is quite different from the explorer path.  You can add to it via Advanced in System properties (on the computer properties page).
     
    I don't recommend leaving dll loads to the path, use explicit locations and explicit binding, or have things in a single directory where they are accessible.  But that's just my opinion,
     
    John

  • RELEVANCY SCORE 2.35

    DB:2.35:Adaptec 2906 Scsi Card Not Support My Scanner j3


    In my G4 is a Adaptec 2906 installed. If I connect my scanner (Linoscan 1800), I can not choose him in the scanprogramm. SCSI-Probe shows the scanner with the right ID. What can I do? If I need another SCSI-Card, what is the right choose?

    DB:2.35:Adaptec 2906 Scsi Card Not Support My Scanner j3

    In my G4 is a Adaptec 2906 installed. If I connect my scanner (Linoscan 1800), I can not choose him in the scanprogramm. SCSI-Probe shows the scanner with the right ID. What can I do? If I need another SCSI-Card, what is the right choose?

  • RELEVANCY SCORE 2.35

    DB:2.35:Re: Enterprise 250 Scsi Issues? Urgently Need Help mj


    Thanks mate,

    Unfortunately this has not helped, i get the same errors and the probe-scsi-all gives exactly the same output.

    When i do boot cdrom or boot cdrom -sv i get the same error as what i had posted originally.

    Any other ideas?

    DB:2.35:Re: Enterprise 250 Scsi Issues? Urgently Need Help mj

    Hello Jason,

    there is something malfunctioning behind the backplane (data cable or terminator at the end). Please recheck if there is a bent pin, loose connection or a broken wire.

    Can you please confirm:

    1. probe-scsi-all with a single disk in bay 0, data cable attached to the internal tape drive and cd-rom but power from the 2 devices removed.

    2. probe-scsi-all with a single disk in bay 0, data cable attached to the internal tape drive and cd-rom with power to the 2 devices applied.

    3. probe-scsi-all without any disk, data cable attached to the internal tape drive and cd-rom with power to the 2 devices applied.

    Despite that probe-scsi[b]-all is only required to probe all SCSI controllers, it doesn't cause harm.

    I have tried another SCSI CD-ROM, one from a sparc station 10 that i know works. I get the same error,

    Did you remove the CD-ROM drive from the external enclosure (the SS10 supports no internal CD-ROM) or did you attach the enclosure to the external connector on the back of the E250 ?

    If you issue probe-scsi-all with a internal hard disks and the tape drive/CD-ROM data cable (but no power cable) attached, is the external CD-ROM drive detected ?

    If you try to boot from the external cd-rom, keep in mind that the device path is different ( /pci@1f, 4000/scsi@3, 1/sd@6,0 instead of //pci@1f,4000/scsi@3/sd@6,0).

    I would really suggest that you get in touch with the company that sold you the system.

    Michael

  • RELEVANCY SCORE 2.35

    DB:2.35:Detect The Target And Lun Ids For Fibre Devices 99


    For the SCSI device, we can issue probe-scsi-all at OK prompt to determine the target and lun ids. How about the fibre devices? If the device is connected to the machine with SAN or a switch, are there any commands can tell the target and lun ids for the devices?

    DB:2.35:Detect The Target And Lun Ids For Fibre Devices 99

    You should check your HBA manual.
    Almost every card in the market (well, at least Qlogic, Emulex and JNI) has
    Fcode to let you check the FC network. Consult the documentation to see
    the specific commands for your HBA

    For the SCSI device, we can issue probe-scsi-all at OK
    prompt to determine the target and lun ids. How about
    the fibre devices? If the device is connected to the
    machine with SAN or a switch, are there any commands
    can tell the target and lun ids for the devices?

  • RELEVANCY SCORE 2.34

    DB:2.34:Deprovisioned Storage Lun, Not Getting Removed From Os aj


    A storage lun was deprovisioned on the SAN environment. But, the device details are not getting cleared from the OS. It keeps throwing error messages that the lun has gone offline. Executed 'devfsadm -c disk -C -v' did not help.

    How do I remove this? Please find the details/command output relating to the issue.

    root@chnvsnrtmt001 # echo | format
    Searching for disks...done

    AVAILABLE DISK SELECTIONS:
    0. c1t0d0 SUN146G cyl 14087 alt 2 hd 24 sec 848
    /pci@1f,700000/scsi@2/sd@0,0
    1. c1t2d0 SUN146G cyl 14087 alt 2 hd 24 sec 848
    /pci@1f,700000/scsi@2/sd@2,0
    2. c1t3d0 SUN146G cyl 14087 alt 2 hd 24 sec 848
    /pci@1f,700000/scsi@2/sd@3,0
    3. c5t60A98000486E61334E3452477435754Dd0 NETAPP-LUN-7310 cyl 6535 alt 2 hd 16 sec 6016
    /scsi_vhci/ssd@g60a98000486e61334e3452477435754d
    4. c5t60A9800043346C395A4A43456578514Cd0 NETAPP-LUN-0.2 cyl 6535 alt 2 hd 16 sec 12032
    /scsi_vhci/ssd@g60a9800043346c395a4a43456578514c
    5. c5t60A9800043346C395A5A434735675050d0 drive not available
    /scsi_vhci/ssd@g60a9800043346c395a5a434735675050
    Specify disk (enter its number): Specify disk (enter its number):
    root@chnvsnrtmt001 # luxadm probe
    No Network Array enclosures found in /dev/es

    Found Fibre Channel device(s):
    Node WWN:500a098086780fee Device Type:Disk device
    Logical Path:/dev/rdsk/c5t60A98000486E61334E3452477435754Dd0s2
    Node WWN:500a098086780fee Device Type:Disk device
    Logical Path:/dev/rdsk/c5t60A9800043346C395A4A43456578514Cd0s2
    Node WWN:500a098086780fee Device Type:Disk device
    Logical Path:/dev/rdsk/c5t60A9800043346C395A5A434735675050d0s2
    root@chnvsnrtmt001 # luxadm display /dev/rdsk/c5t60A9800043346C395A5A434735675050d0s2
    Error: SCSI failure. - /dev/rdsk/c5t60A9800043346C395A5A434735675050d0s2.

    root@chnvsnrtmt001 # tail /var/adm/messages
    Feb 17 15:22:29 chnvsnrtmt001 offline
    Feb 17 15:24:22 chnvsnrtmt001 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a9800043346c395a5a434735675050 (ssd16):
    Feb 17 15:24:22 chnvsnrtmt001 offline
    Feb 17 15:26:37 chnvsnrtmt001 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a9800043346c395a5a434735675050 (ssd16):
    Feb 17 15:26:37 chnvsnrtmt001 offline
    Feb 17 15:47:16 chnvsnrtmt001 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a9800043346c395a5a434735675050 (ssd16):
    Feb 17 15:47:16 chnvsnrtmt001 offline
    Feb 17 16:00:00 chnvsnrtmt001 ntpdate[8705]: [ID 774510 daemon.notice] step time server 10.72.216.25 offset -0.177232 sec
    Feb 17 16:04:40 chnvsnrtmt001 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a9800043346c395a5a434735675050 (ssd16):
    Feb 17 16:04:40 chnvsnrtmt001 offline
    root@chnvsnrtmt001 # uname -a
    SunOS chnvsnrtmt001 5.9 Generic_122300-07 sun4u sparc SUNW,Sun-Fire-V440
    root@chnvsnrtmt001 #

    DB:2.34:Deprovisioned Storage Lun, Not Getting Removed From Os aj

    A storage lun was deprovisioned on the SAN environment. But, the device details are not getting cleared from the OS. It keeps throwing error messages that the lun has gone offline. Executed 'devfsadm -c disk -C -v' did not help.

    How do I remove this? Please find the details/command output relating to the issue.

    root@chnvsnrtmt001 # echo | format
    Searching for disks...done

    AVAILABLE DISK SELECTIONS:
    0. c1t0d0 SUN146G cyl 14087 alt 2 hd 24 sec 848
    /pci@1f,700000/scsi@2/sd@0,0
    1. c1t2d0 SUN146G cyl 14087 alt 2 hd 24 sec 848
    /pci@1f,700000/scsi@2/sd@2,0
    2. c1t3d0 SUN146G cyl 14087 alt 2 hd 24 sec 848
    /pci@1f,700000/scsi@2/sd@3,0
    3. c5t60A98000486E61334E3452477435754Dd0 NETAPP-LUN-7310 cyl 6535 alt 2 hd 16 sec 6016
    /scsi_vhci/ssd@g60a98000486e61334e3452477435754d
    4. c5t60A9800043346C395A4A43456578514Cd0 NETAPP-LUN-0.2 cyl 6535 alt 2 hd 16 sec 12032
    /scsi_vhci/ssd@g60a9800043346c395a4a43456578514c
    5. c5t60A9800043346C395A5A434735675050d0 drive not available
    /scsi_vhci/ssd@g60a9800043346c395a5a434735675050
    Specify disk (enter its number): Specify disk (enter its number):
    root@chnvsnrtmt001 # luxadm probe
    No Network Array enclosures found in /dev/es

    Found Fibre Channel device(s):
    Node WWN:500a098086780fee Device Type:Disk device
    Logical Path:/dev/rdsk/c5t60A98000486E61334E3452477435754Dd0s2
    Node WWN:500a098086780fee Device Type:Disk device
    Logical Path:/dev/rdsk/c5t60A9800043346C395A4A43456578514Cd0s2
    Node WWN:500a098086780fee Device Type:Disk device
    Logical Path:/dev/rdsk/c5t60A9800043346C395A5A434735675050d0s2
    root@chnvsnrtmt001 # luxadm display /dev/rdsk/c5t60A9800043346C395A5A434735675050d0s2
    Error: SCSI failure. - /dev/rdsk/c5t60A9800043346C395A5A434735675050d0s2.

    root@chnvsnrtmt001 # tail /var/adm/messages
    Feb 17 15:22:29 chnvsnrtmt001 offline
    Feb 17 15:24:22 chnvsnrtmt001 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a9800043346c395a5a434735675050 (ssd16):
    Feb 17 15:24:22 chnvsnrtmt001 offline
    Feb 17 15:26:37 chnvsnrtmt001 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a9800043346c395a5a434735675050 (ssd16):
    Feb 17 15:26:37 chnvsnrtmt001 offline
    Feb 17 15:47:16 chnvsnrtmt001 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a9800043346c395a5a434735675050 (ssd16):
    Feb 17 15:47:16 chnvsnrtmt001 offline
    Feb 17 16:00:00 chnvsnrtmt001 ntpdate[8705]: [ID 774510 daemon.notice] step time server 10.72.216.25 offset -0.177232 sec
    Feb 17 16:04:40 chnvsnrtmt001 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a9800043346c395a5a434735675050 (ssd16):
    Feb 17 16:04:40 chnvsnrtmt001 offline
    root@chnvsnrtmt001 # uname -a
    SunOS chnvsnrtmt001 5.9 Generic_122300-07 sun4u sparc SUNW,Sun-Fire-V440
    root@chnvsnrtmt001 #

  • RELEVANCY SCORE 2.34

    DB:2.34:Aic-7899 Scsi Ddg-D Scsi 015 027 Error? d3


    PowerEdge 1400SC server cannot boot up, run the diagnostic on AIC-7899 SCSI returns with error message : DOS Medium Error (3-1101), Read retries exhausted. DDG-D SCSI 015 027. what will be the problem? is the the hardware failure? thanks.

    DB:2.34:Aic-7899 Scsi Ddg-D Scsi 015 027 Error? d3

    PowerEdge 1400SC server cannot boot up, run the diagnostic on AIC-7899 SCSI returns with error message : DOS Medium Error (3-1101), Read retries exhausted. DDG-D SCSI 015 027. what will be the problem? is the the hardware failure? thanks.

  • RELEVANCY SCORE 2.34

    DB:2.34:Dual Scsi Pci Adaptor Not Recognised By Solaris 9 3a


    I have Solaris 9 O/S installed on an enterprise 220, I also have a dual scsi adaptor installed with a Storedge D1000 connected to it, however when I do a touch /reconfigure with init 0 or boot -r or a probe-scsi-all the O/S only sees the 2 internal disks. How do i get the system to recognise the scsi card and the attached D1000 ??? IM going banannas here please help!!

    DB:2.34:Dual Scsi Pci Adaptor Not Recognised By Solaris 9 3a

    Unlikely to be the jumper cable if it wasn't connected at the time as you imply.

    If you haven't already, please try with nothing plugged into the SCSI ports on the adapter. If it still plays up, it suggests a faulty adapter - perhaps not seated properly, or knackered.

  • RELEVANCY SCORE 2.34

    DB:2.34:Scrolling Bootprom 79


    trying to look at probe-scsi-all output in bootprom
    but it scrolls by too fast, fills up screen and rolls
    over to next screen....

    is there a way to pause the scrolling
    or something similar to the more command ?

    help!

    thanks,

    shaun

    DB:2.34:Scrolling Bootprom 79

    Did you try using Control-S to pause the output?

  • RELEVANCY SCORE 2.34

    DB:2.34:Migrating To San Powerpath Boot Device On Aix 5.3 - Howto? 9k


    Hello all,I am trying to migrate the rootvg from a locally attached scsi disk to a powerpathed SAN device on AIX 5.3. Do you guys have any suggestions what to do in which order?The point of departure:hdisk0 (local scsi disk) - rootvghdisk3 (san disk on 1st path)hdisk4 (san disk on 2nd path)hdiskpower0 (hdisk3 + hdisk4)What I did so far was this:extendvg rootvg hdiskpower0migratepv hdisk0 hdiskpower0reducevg rootvg hdisk0chpv -c hdisk0bootlist -m normal hdisk3 hdisk4pprootdev fixThe "pprootdev fix" command returns an error:0301-154 bosboot: missing proto file: /usr/lib/boot/network/chrp.hdiskpower.protopprootdev: PowerPath boot is not currently enabled.So, did I do something wrong or did I miss something?

    DB:2.34:Migrating To San Powerpath Boot Device On Aix 5.3 - Howto? 9k

    Thanks for the quick replies. With help of those documentations I was able to manage the migration.

  • RELEVANCY SCORE 2.34

    DB:2.34:How To List Scsi Device From Command Prompt? s3


    hi everybody,

    I am using a (uname -a)
    SunOS SUNIX1 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10

    I trying to create links in /dev for the sst driver.

    I am trying to list the following info about all the scsi devices
    (1) controller
    (2) target
    (3) lun.
    (4) Vendor name
    (5) Model name

    In a shell script.

    As we get from prom command probe-scsi-all

    I tried iostat -E it does not list DVD-RAM drives and it also does not give me the controller no.

    Thank you. in advance for your help/suggestion.

    sajansathi

    DB:2.34:How To List Scsi Device From Command Prompt? s3

    shridhara,

    scsiinfo does list all the devices and the scsi host adapters.
    I found it at ftp://ftp.cdf.toronto.edu/pub/scsiinfo.

    Thank you so much for the tip.

    sajansathi

  • RELEVANCY SCORE 2.34

    DB:2.34:Sun Blade 100 And Symbios 22801 af


    I have installed a Sy,bios 22801 scsi card and a Seagate 72GB SCSI harddisk into a Sun Blade 100.
    in OBP, I type probe-scsi-all, it can recognize it the scsi harddisk out.
    But when I try to boot the harddisk it it seems it can't find the device.
    I define the harddisk as sddisk in the following path
    /pci@1f,0/pci@5/scsi@0/disk@0,0:a, then it can boot and find the hostname. but it will try to find /pci@1f,0/pci@5/scsi@0/sd@0,0:a, then it will be failed.
    I want to ask can Sun Blade 100 be booted from scsi ?
    If can, what I should do ? The OBP version on my Sun Blade 100 is 4.17.1

    DB:2.34:Sun Blade 100 And Symbios 22801 af

    HI..

    Looking into some information, I found this note:

    **********************************

    If you can boot from the CD-ROM, but still cannot mount it manually in multi-user mode, check the /kernel/drv/sd.conf file to make sure that it contains four atapi entries for the CD-ROM device:

    name="sd" class="scsi" class_prop="atapi"
    target=0 lun=0;
    name="sd" class="scsi" class_prop="atapi"
    target=1 lun=0;
    name="sd" class="scsi" class_prop="atapi"
    target=2 lun=0;
    name="sd" class="scsi" class_prop="atapi"
    target=3 lun=0;

    ***********************************************

    Is it possible that the scsi drive has to be on a target ID different fom 0-3?

    The /kernel/drv/sd.conf file lists as follows:

    $ more /kernel/drv/sd.conf
    #
    # Copyright (c) 1992, by Sun Microsystems, Inc.
    #
    #ident "@(#)sd.conf 1.9 98/01/11 SMI"

    name="sd" class="scsi" class_prop="atapi"
    target=0 lun=0;

    name="sd" class="scsi" class_prop="atapi"
    target=1 lun=0;

    name="sd" class="scsi" class_prop="atapi"
    target=2 lun=0;

    name="sd" class="scsi" class_prop="atapi"
    target=3 lun=0;

    name="sd" class="scsi"
    target=4 lun=0;

    name="sd" class="scsi"
    target=5 lun=0;

    name="sd" class="scsi"
    target=6 lun=0;

    name="sd" class="scsi"
    target=8 lun=0;

    name="sd" class="scsi"
    target=9 lun=0;

    name="sd" class="scsi"
    target=10 lun=0;

    name="sd" class="scsi"
    target=11 lun=0;

    name="sd" class="scsi"
    target=12 lun=0;

    name="sd" class="scsi"
    target=13 lun=0;

    name="sd" class="scsi"
    target=14 lun=0;

    name="sd" class="scsi"
    target=15 lun=0;
    $

    What does this part mean??
    "class_prop="atapi" on the first 4 target statements?

  • RELEVANCY SCORE 2.34

    DB:2.34:One Of Two List Boxes Working Other Returns Null. d7



    To whom it may concern,

    I'm working with a earlier program not created by myself and have an odd behavior from a list box. There are two list boxes with on operating correctly and the other shows a null in data. When you look at the front panel you'll see two list boxes on the right side. The one labeled "File for L1 Test" is working the one "File for L2 Test" isn't. Even though the path come in the file names in the L2 box don't make it into the program and when you probe the test line you get a "" for the probe. Any idea of why one works and the other doesn't?

    Gary Tyrna







    Solved!
    Go to Solution.

    DB:2.34:One Of Two List Boxes Working Other Returns Null. d7


    Matthew,

    Thank you for your suggestion. This was the trouble and I know have this working. It may have been the older version that created this program and when I brought this up in LabVIEW 2010 mite have caused the corruption problem.

    Thanks Again,

    Gary Tyrna

  • RELEVANCY SCORE 2.33

    DB:2.33:Cambiar Path Owa En Exchange Server 2007 a1


    Hola amigos, me gustaria saber como cambiar el path de conexion a owa (p.ej https://mail.dominio.com/owa). Probe cambiando el path en la consola de Exchange Server pero no he podido. Actualmente redirecciono https://mail.dominio.com hacia https://mail.dominio.com/owa pero necesito cambiar el path owaSaludos!

    DB:2.33:Cambiar Path Owa En Exchange Server 2007 a1

    Hola, pudiste realizar el cambio del path ???Peter Chirinos | Microsoft Office Specialist, Software Developer, Microsoft Certified Professional, MAP , Microsoft Small Business Specialist| @peter_chirinos

  • RELEVANCY SCORE 2.33

    DB:2.33:Ultra 60 Scsi Question cz


    We have an Ultra 60 running Solaris 8 but we need a LVD capable card. I've gotten my hands on an Adaptec 29160N but it doesn't show up in the "probe-scsi-all" output.

    I guess I'm asking if its compatable at all and if it is what do I have to do to make it work?

    Thanks for any help
    Chris

    DB:2.33:Ultra 60 Scsi Question cz

    If the peripheral must be connected to a LVD card, then the
    375-3057 (X6758a) adapter is qualified for that systemboard.

    Here's the link in the SSH for the E220R system's SCSI cards:
    http://sunsolve.sun.com/handbook_pub/Systems/E220R/components.html#SCSI

    The U-60, the E220R, and the Netra 112x systems all use the same systemboard.

    Adaptec products and Sun SPARC systems just don't function well, together.
    Adaptec doesn't feel there's enough market out there, to include compatibility in their HBA's.

  • RELEVANCY SCORE 2.33

    DB:2.33:Solaris 10, Isalogic Scsi Interface And Arcvault Tape Library xf


    I put an ISALogic SCSI interface card into a SunBlade 2000, installed
    Solaris 10_u4 on it and attached an ARCVault tape library. The system
    see the tape but fails to see the library and the robot. The robot and the
    tape are on the same scsi bus.

    I followed the instructions on how to do a scsi passthrough and did a probe-scsi-all
    at the ok prompt of the system.
    The probe on the ISAlogic interface card sent the system into a bus error.

    Any idea how I could make the robot visible on the same bus?

    Lydia

  • RELEVANCY SCORE 2.33

    DB:2.33:Zfs Pool Frequently Going Offline pz


    I am setting up some servers with ZFS raids and and finding that all of them are suffering from I/O errors that cause the pool to go offline (and when that happens everything freezes and I have to power cycle... then everything boots up fine).

    T1000, V245, and V240 systems all exhibit the same behavior.

    Root is mirrored ZFS.
    The raid is configure as one big LUN (3 to 8 TB depending on system) and that lun is the entire pool. In other words, there is no ZFS redundancy. My thinking was I would let the raid handle that.

    Based on some searches I decided to try setting

    set sd:sd_max_throttle=20

    in /etc/system and rebooting, but that made no difference.

    My sense is that the troubles start when there is a lot of activity. I ran these for many days with light activity and no problems. Once I started migrating the data over from the old systems did the problems start. Here is a typical error log:

    Jun 6 16:13:15 newserver scsi: WARNING: /pci@1f,700000/pci@0,2/scsi@1,1 (mpt3):
    Jun 6 16:13:15 newserver Connected command timeout for Target 0.
    Jun 6 16:13:15 newserver scsi: WARNING: /pci@1f,700000/pci@0,2/scsi@1,1 (mpt3):
    Jun 6 16:13:15 newserver Target 0 reducing sync. transfer rate
    Jun 6 16:13:16 newserver scsi: WARNING: /pci@1f,700000/pci@0,2/scsi@1,1/sd@0,0 (sd2):
    Jun 6 16:13:16 newserver SCSI transport failed: reason 'reset': retrying command
    Jun 6 16:13:19 newserver scsi: WARNING: /pci@1f,700000/pci@0,2/scsi@1,1/sd@0,0 (sd2):
    Jun 6 16:13:19 newserver Error for Command: read(10) Error Level: Retryable
    Jun 6 16:13:19 newserver scsi: Requested Block: 182765312 Error Block: 182765312
    Jun 6 16:13:19 newserver scsi: Vendor: IFT Serial Number: 086A557D-00
    Jun 6 16:13:19 newserver scsi: Sense Key: Unit Attention
    Jun 6 16:13:19 newserver scsi: ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Jun 6 16:13:19 newserver scsi: WARNING: /pci@1f,700000/pci@0,2/scsi@1,1/sd@0,0 (sd2):
    Jun 6 16:13:19 newserver incomplete read- retrying
    Jun 6 16:13:20 newserver scsi: WARNING: /pci@1f,700000/pci@0,2/scsi@1,1/sd@0,0 (sd2):
    Jun 6 16:13:20 newserver incomplete write- retrying
    Jun 6 16:13:20 newserver scsi: WARNING: /pci@1f,700000/pci@0,2/scsi@1,1/sd@0,0 (sd2):
    Jun 6 16:13:20 newserver incomplete write- retrying
    Jun 6 16:13:20 newserver scsi: WARNING: /pci@1f,700000/pci@0,2/scsi@1,1/sd@0,0 (sd2):
    Jun 6 16:13:20 newserver incomplete write- retrying
    ... ~80 similar lines deleted ...
    Jun 6 16:13:21 newserver scsi: WARNING: /pci@1f,700000/pci@0,2/scsi@1,1/sd@0,0 (sd2):
    Jun 6 16:13:21 newserver incomplete read- retrying
    Jun 6 16:13:21 newserver scsi: WARNING: /pci@1f,700000/pci@0,2/scsi@1,1/sd@0,0 (sd2):
    Jun 6 16:13:21 newserver incomplete read- giving up

    At this point everything is hung and I am forced to power cycle.

    I'm very confused on how to proceed with this.... since this is happening on all three systems I an reluctant to blame the hardware.

    I would be very grateful to any suggestions on how to get out from under this!

    Thanks,

    David C

    DB:2.33:Zfs Pool Frequently Going Offline pz

    Hi, and thanks for the reply.

    I am running: SunOS newserver 5.10 Generic_139555-08 sun4u sparc SUNW,Sun-Fire-V245, which I believe to be the most current download, fully patched.

    I'll take a look at the timeout as you suggest.

    David

  • RELEVANCY SCORE 2.33

    DB:2.33:Legacymp Limit Exceeded km



    I am seeing these warnings in the messages log (for multiple paths).

    Also exeriencing 'missing' luns and SCSI targets.

    Are the below errors anything to do with this?

    WARNING: SCSI: 1355: LegacyMP Plugin could not claim path: vmhbaX:X:X. Limit exceeded
    WARNING: ScsiPath: 3236: Plugin 'legacyMP' had an error (Limit exceeded) while claiming path 'vmhbaX:X:X'.Skipping the path.

    DB:2.33:Legacymp Limit Exceeded km


    I am seeing these warnings in the messages log (for multiple paths).

    Also exeriencing 'missing' luns and SCSI targets.

    Are the below errors anything to do with this?

    WARNING: SCSI: 1355: LegacyMP Plugin could not claim path: vmhbaX:X:X. Limit exceeded
    WARNING: ScsiPath: 3236: Plugin 'legacyMP' had an error (Limit exceeded) while claiming path 'vmhbaX:X:X'.Skipping the path.

  • RELEVANCY SCORE 2.32

    DB:2.32:Storedge 3310 And Format j1


    hi,

    i have the following problem:

    a storedge 3310 with raid controller. i have partitioned the volume ( which consists of 6 raid 1 logical drives) into 4 partions and assigned luns to these partitions.

    probe-scsi-all shows the following:

    /pci@1e,600000/pci@2/scsi@4
    Target 0
    Unit 0 Disk SUN StorEdge 3310 0325
    Unit 1 Disk SUN StorEdge 3310 0325
    Unit 2 Disk SUN StorEdge 3310 0325
    Unit 3 Disk SUN StorEdge 3310 0325

    format shows only the first one:

    0. c0t0d0
    /pci@1c,600000/scsi@2/sd@0,0
    1. c0t1d0
    /pci@1c,600000/scsi@2/sd@1,0
    2. c2t0d0
    /pci@1e,600000/pci@2/scsi@4/sd@0,0

    where are the other three partitions?

    DB:2.32:Storedge 3310 And Format j1

    http://forum.sun.com/thread.jspa?threadID=23700tstart=0

  • RELEVANCY SCORE 2.32

    DB:2.32:Bus Fault 3s


    BUGID 4112751
    This is my problem but there is no fix.. After checking a prtdiag | grep OBP I am all current but yet have the problem.

    I am connecting a A1000 with 12 /36Gb disks to a fast wide scsi..'

    after doing that and at the OK prompt I do a probe-scsi-all -f and I get locked out of system and get msgs bus fault

    any help

    DB:2.32:Bus Fault 3s


    1. enter the OBP with STOP+a or power off / on and then init 0 to get to ok prompt
    2. ok setenv auto-boot? false
    3. ok reset or reset-all
    4. system reboots to ok prompt
    5. ok probe-scsi-all
    6. when done enter put your original settings back so the system will automatically boot the operating system in case of a power failure.
    7. ok setenv auto-boot? true
    8. ok reset or reset-all
    9. systems boots normally from system disk.

    Bottom line. If you get a warning do not continue with probe-scsi and similar commands without setting auto-boot? false. The probe- commands like to be run after POST completes and system stops at the ok prompt.

  • RELEVANCY SCORE 2.32

    DB:2.32:Just Installed 2540, What To Do Next? pd


    Hi, I have a Sun Fire V440 that I needed more storage for, so we purchased a 2540 array, and a HBA from Sun to go in the 440. The 440 is running Solaris 10 08/07. The HBA has two ports and one is connected to Controller A in the 2540 and the other to Controller B. In the 2540, I have one host, called email. I have two initiators, email-a and email-b, associated with the two WWNs. I have a volume that is mapped to the two initiators. Now I am trying to figure out where to go from here on the host.

    I think I need to do a stmsboot -e but I want to make sure that I don't mess up the existing mounts (the machine has some internall drives). Will the stmsboot command affect only fiber devices and leave everything else alone? Here are the outputs of some commands:

    luxadm probe
    No Network Array enclosures found in /dev/es

    Found Fibre Channel device(s):
    Node WWN:200a00a0b839c3e1 Device Type:Disk device
    Logical Path:/dev/rdsk/c5t2d0s2
    Logical Path:/dev/rdsk/c6t0d0s2

    Will there be only one path after I do the stmsboot -e command?

    cfgadm -al -o show_FCP_dev
    Ap_Id Type Receptacle Occupant Condition
    c5 fc-private connected configured unknown
    c5::200b00a0b839c3e2,0 disk connected configured unknown
    c5::200b00a0b839c3e2,31 disk connected configured unknown
    c6 fc-private connected configured unknown
    c6::200a00a0b839c3e2,0 disk connected configured unknown
    c6::200a00a0b839c3e2,31 disk connected configured unknown

    The LUN that I defined on the 2540 was 0, where does the 31 come from?

    mpathadm list initiator-port
    Initiator Port: iqn.1986-03.com.sun:01:0003badd169f.47c92095,4000002a00ff

    The docs show two lines of output for this command, will it show up after the stmsboot?

    format
    Searching for disks...done

    c5t2d0: configured with capacity of 2035.71GB
    c6t0d0: configured with capacity of 2035.71GB

    AVAILABLE DISK SELECTIONS:
    0. c1t0d0 SUN146G cyl 14087 alt 2 hd 24 sec 848
    /pci@1f,700000/scsi@2/sd@0,0
    1. c1t1d0 SUN146G cyl 14087 alt 2 hd 24 sec 848
    /pci@1f,700000/scsi@2/sd@1,0
    2. c1t2d0 SUN146G cyl 14087 alt 2 hd 24 sec 848
    /pci@1f,700000/scsi@2/sd@2,0
    3. c1t3d0 SUN146G cyl 14087 alt 2 hd 24 sec 848
    /pci@1f,700000/scsi@2/sd@3,0
    4. c5t2d0 SUN-LCSM100_F-0617-1.99TB
    /pci@1c,600000/SUNW,qlc@1/fp@0,0/ssd@w200b00a0b839c3e2,0
    5. c6t0d0 SUN-LCSM100_F-0617-1.99TB
    /pci@1c,600000/SUNW,qlc@1,1/fp@0,0/ssd@w200a00a0b839c3e2,0

    Will disks 4 and 5 be consolidated after the stmsboot?

    Thanks for any advice

    Jim McCullars
    University of Alabama in Huntsville

    DB:2.32:Just Installed 2540, What To Do Next? pd

    mccullarsj wrote:
    The LUN 31s were as a result of something called Access in the 2430, that is used for in-band communications.The LUN 31 is the UTM LUN. This is the LUN required for in-band management as you indicated. If you do not use in-band management, you can use CAM to unmap this LUN 31.
    This UTM LUN isn't specific to the 2540 only, it is working the same for the 6130, 6140, 6540, 2510, 2530, 2540, FLX380, etc...

  • RELEVANCY SCORE 2.32

    DB:2.32:Re: Sun Enterprise 4500 Server Wont Boot af


    Harold will take care of you with that system. Stay with his advice.

    Your output from the probe of the SCSI bus has given you the device path to your disk.

    The E4500 never had any "internal" disk drives. Even disk boards are external drives, connected by cables that were external to the chassis. Disks always required you a custom device alias in OBP.
    Try going through the system documentation at Docs.Sun.Com for hints of an absolute path to the disk device.

    From your description of how you have everything connected, I think you
    have it attached to what would normally only be used for a tape drive
    in the machine's removable media bay? If that is correct, it may
    explain why Solaris never found the disk. Your Linux installation
    may also have placed an Ext3 filesystem layout on the drive which is
    foreign to Solaris. You would have to boot to CDROM, open a command prompt window, run format with the -e command switch, then re-label the drive for UFS usage. (search the various Solaris OS forums for `ext3`)

    ---
    Also,
    [The OBP 3.x Command Reference Manual 806-1377|http://docs.sun.com/app/docs/doc/806-1377-10?q=openboot+command+reference]

    DB:2.32:Re: Sun Enterprise 4500 Server Wont Boot af

    Haha thanks haroldb, I did spent liek 10 minutes messing with that last night, until I saw the label on the inside of the cover haha. But anyway the e4500 is up and running just fine :) I actually had one of the drives in the 711 die, and re installed debian on the internal drive, and it now boots off the internal hard drive just fine. I'm guessing It wasn't working before because of a misspelling of "fase" instead of "fas" and the unit/target numbers have to be entered opposite too how the sun docs said they had to be haha (even though I did try different orderings). But everything works :)

    So it is possible to boot these things off "internal" hard drives. Thank you so much haroldb, and rukbat, you guys are awesome.

  • RELEVANCY SCORE 2.32

    DB:2.32:How To Test Helloworld Sample Using A Broadcast Probe Generating Events jm


    Hello,

    The eclipse IDE provide some template to test CEP application.
    I'm interested to test the HelloWorld without using an adapter. The decription of the sample is the following:
    +"Similar to the Hello World sample application. Instead of using an adapter to inject test data, a broadcast probe generates events. Instead of using an event bean to display event output, a watch probe displays events output from the processor. "+

    A sample.probekit is provided but i don't know how to trigger it.

    probes host-application="aa" comm-port="8902"
    watch-probe id="watchProbe"
    downstream-stagehelloworldOutputChannel/downstream-stage
    /watch-probe

    broadcast-probe id="broadcastProbe"
    csv-file path="sample-probe-data.csv"/
    upstream-stagehelloworldInputChannel/upstream-stage
    delay1000/delay
    /broadcast-probe

    /probes

    Thanks for your help.
    chenda

    DB:2.32:How To Test Helloworld Sample Using A Broadcast Probe Generating Events jm

    Hello,

    The eclipse IDE provide some template to test CEP application.
    I'm interested to test the HelloWorld without using an adapter. The decription of the sample is the following:
    +"Similar to the Hello World sample application. Instead of using an adapter to inject test data, a broadcast probe generates events. Instead of using an event bean to display event output, a watch probe displays events output from the processor. "+

    A sample.probekit is provided but i don't know how to trigger it.

    probes host-application="aa" comm-port="8902"
    watch-probe id="watchProbe"
    downstream-stagehelloworldOutputChannel/downstream-stage
    /watch-probe

    broadcast-probe id="broadcastProbe"
    csv-file path="sample-probe-data.csv"/
    upstream-stagehelloworldInputChannel/upstream-stage
    delay1000/delay
    /broadcast-probe

    /probes

    Thanks for your help.
    chenda

  • RELEVANCY SCORE 2.32

    DB:2.32:How To List Scsi Device From Command Prompt? 1s


    hi everybody,

    I am using a (uname -a)
    SunOS SUNIX1 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10

    I trying to create links in /dev for the sst driver.

    I am trying to list the following info about all the scsi devices
    (1) controller
    (2) target
    (3) lun.

    In a shell script.

    As we get from prom command probe-scsi-all

    I tried iostat -E it does not list DVD-RAM drives and it also does not give me the controller no.

    Thank you. in advance for your help/suggestion.

    sajansathi

    DB:2.32:How To List Scsi Device From Command Prompt? 1s

    devfsadm(1m) maintains the /dev tree. If the device is found
    and a driver can be associated, then devfsadm may build a
    /dev entry for it. That is a good place to start looking as it
    may get rather complicated from there, depending on what
    you are needing.
    -- richard

  • RELEVANCY SCORE 2.32

    DB:2.32:Corrpt Label; Wrong Magic Number s7


    I got a Sun unit "Ultra Enterprise 2" to be installed with Solaris 10. What I have just done were:

    1. Successful boot of the machine
    OK
    2. Probe all scsi devices
    OK probe-scsi-all
    3. All scsi devices were probed.

    MAG3091L ===== inserted in D1000 storage
    ST39103LC ===== inserted in D1000 storage
    DDRS39130 ===== inserted in D1000 storage
    -------------------------------------------------------------------------------
    ST39102LC ===== Local Drive
    Toshiba xxxx ===== Removable Read Device

    4. Start to install from CD rom
    OK boot cdrom - nowin

    then during the probing a Warning prompted:

    WARNING: /sbus1f, 0/QLGC, isp@0,10000 /sd@a,0 (sd24)
    Corrpt Label; wrong magic number

    What should be the fix for this, I am certain that this has something to do with the D1000 storedge but am not sure how to deal with this. I hope somebody would help.

    Many thanks
    Petalio

  • RELEVANCY SCORE 2.32

    DB:2.32:Ultra 60 Won't Boot 81


    When booting this Ultra 60, it gets to the 'Initializing memory' message and it doesn't go any further. I can see the disk when I get to the 'ok' prompt and do a 'probe-scsi-all'. What kind of problem does this point to?

    DB:2.32:Ultra 60 Won't Boot 81

    This server has been around for several years. It has Solaris 8 installed on it.

  • RELEVANCY SCORE 2.32

    DB:2.32:Registry Probe Configuration am


    I'm trying to create a registry probe for a service. The key has an ampersand in it:
    HKLM\Software\Wow6432Node\GFI Fax Voice\FaxMaker\Path
    When I add and save it the text changes to:
    HKLM\Software\Wow6432Node\GFI Fax amp; Voice\Faxmaker\Path

    How can I escape the ampersand character?

    DB:2.32:Registry Probe Configuration am

    Hi
    Can you try updatingMpxmlin notepad with path of xml and test it.
    Regardssridhar v

  • RELEVANCY SCORE 2.32

    DB:2.32:Not Booting From Dvd Solaris 10 ap


    Hi,

    I am trying to install Solaris 10 on Sun 420R Sparc. I am trying to install it with DVD. But when I try to install it by using the command boot cdrom. I get the following error.

    {0} ok boot cdrom - nowin
    Boot device: /pci@1f,4000/scsi@3/disk@6,0:f File and args: - nowin
    Bad magic number in disk label
    Can't open disk label package

    Can't open boot device

    I have checked the DVD. I ran probe-scsi-all and it looks good.

    {0} ok devalias cdrom
    cdrom /pci@1f,4000/scsi@3/disk@6,0:f
    {0} ok show-devs
    /SUNW,UltraSPARC-II@3,0
    /SUNW,UltraSPARC-II@2,0
    /SUNW,UltraSPARC-II@1,0
    /SUNW,UltraSPARC-II@0,0
    /counter-timer@1f,1c00
    /pci@1f,2000
    /pci@1f,4000
    /virtual-memory
    /memory@0,0
    /aliases
    /options
    /openprom
    /chosen
    /packages
    /pci@1f,2000/scsi@1,1
    /pci@1f,2000/scsi@1
    /pci@1f,2000/scsi@1,1/tape
    /pci@1f,2000/scsi@1,1/disk
    /pci@1f,2000/scsi@1/tape
    /pci@1f,2000/scsi@1/disk
    /pci@1f,4000/scsi@4,1
    /pci@1f,4000/scsi@4
    /pci@1f,4000/scsi@3,1
    /pci@1f,4000/scsi@3
    /pci@1f,4000/network@1,1
    /pci@1f,4000/ebus@1
    /pci@1f,4000/scsi@4,1/tape
    /pci@1f,4000/scsi@4,1/disk
    /pci@1f,4000/scsi@4/tape
    /pci@1f,4000/scsi@4/disk
    /pci@1f,4000/scsi@3,1/tape
    /pci@1f,4000/scsi@3,1/disk
    /pci@1f,4000/scsi@3/tape
    /pci@1f,4000/scsi@3/disk
    /pci@1f,4000/ebus@1/flashprom@10,0
    /pci@1f,4000/ebus@1/eeprom@14,0
    /pci@1f,4000/ebus@1/fdthree@14,3023f0
    /pci@1f,4000/ebus@1/ecpp@14,3043bc
    /pci@1f,4000/ebus@1/su@14,3062f8
    /pci@1f,4000/ebus@1/su@14,3083f8
    /pci@1f,4000/ebus@1/se@14,400000
    /pci@1f,4000/ebus@1/sc@14,500000
    /pci@1f,4000/ebus@1/SUNW,pll@14,504000
    /pci@1f,4000/ebus@1/power@14,724000
    /pci@1f,4000/ebus@1/auxio@14,726000
    /openprom/client-services
    /packages/sun-keyboard
    /packages/SUNW,builtin-drivers
    /packages/disk-label
    /packages/obp-tftp
    /packages/deblocker
    /packages/terminal-emulator
    {0} ok probe-scsi
    Target 0
    Unit 0 Disk SEAGATE ST318305LSUN18G 0340
    Target 1
    Unit 0 Disk SEAGATE ST318305LSUN18G 0340
    Target 6
    Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011007
    {0} ok

    Can anyone help me with this?

    Thanks

    DB:2.32:Not Booting From Dvd Solaris 10 ap

    The 420R first shipped in November 1999.
    Initially, they all had CDROM drives and not DVD readers.

    You might also get that same error
    if you are inserting a DVD disk into a CD drive.

    Next, the 390-0025 DVD drives had problems booting
    from any DVD media with more than (I vaguely recall)
    something such as 3GB of data on it.
    They could read from them,
    just not boot from them.
    That was a peculiarity of the drive.
    Recent releases of Solaris 10 fill those DVD disks.

    Try your installation with CD media instead of DVD's.

  • RELEVANCY SCORE 2.32

    DB:2.32:Discovery Probe fs



    Hello,

    I have couple of question.

    1. I have a written a probe to read the files from the folder using powershell(windows system). But now I need to read the content of the file in the folder I am getting this error Cannot find path because it does not exist. even though file exist. I am using Get-Content command.

    2. Is it possible to pass output of one probe to another probe.

    Thanks

    Satinder

    DB:2.32:Discovery Probe fs


    It is! Especially when you are calling one probe from the result of a sensor being processed.. Example is our HMC probes that are posted here in the community. In one probe we set the variable servername

    if (line.length == 0)

    continue;

    var parts = line.split(/,/);

    var serverName = parts[0];

    Then call that variable in the next probe to be triggered...

    // Send out the probe to explore the power server's LPAR

    this.triggerProbe(serverName, "HMC - Power Server LPAR");

  • RELEVANCY SCORE 2.32

    DB:2.32:Cant See Disks In E3500 c9


    Hi ,

    I have E3500 which cant see disks in OpenBoot .
    probe-scsi show my just cdrom and no one of 8 internal disks.

    Regards ,
    Eran

    DB:2.32:Cant See Disks In E3500 c9

    i cant even boot my machine.

    See my probe-scsi-all output :

    {a} ok probe-scsi-all
    /sbus@7,0/SUNW,fas@3,8800000

    /sbus@3,0/fcaw@0,0
    Target 4 ( AL_PA e1 )
    Unit 0 Disk SEAGATE ST318203FSUN18G 034A99477323
    Target 5 ( AL_PA e0 )
    Unit 0 Disk SEAGATE ST318203FSUN18G 034A99477648
    Target 7 ( AL_PA da )
    Unit 0 Disk SEAGATE ST318203FSUN18G 034A99446390

    /sbus@3,0/SUNW,fas@3,8800000
    Target 6
    Unit 0 Removable Read Only device TOSHIBA CD-ROM XM-3801TA020701/20/97

    /sbus@2,0/fcaw@2,0
    Target 0 ( AL_PA ef )
    Unit 0 Disk SEAGATE ST318203FSUN18G 034A99477635
    Target 1 ( AL_PA e8 )
    Unit 0 Disk SEAGATE ST318304FSUN18G 08260131L0DJ
    Target 2 ( AL_PA e4 )
    Unit 0 Disk SEAGATE ST39102FCSUN9.0G072899330409

    {a} ok

  • RELEVANCY SCORE 2.32

    DB:2.32:Why Do Workflow Join Activities Contain An Incomplete Path? kf



    I was wondering when a workflow Join activity's Incomplete path would ever be taken? (This activity has two output paths: Complete and Incomplete)

    I have a Join that joins up the paths of 2 parallel tasks that occur after a corresponding Branch activity. Regardless of what closed state I set the 2 tasks to (Closed Complete or Closed Incomplete) the Join always continues down its Complete path. Never do I see when the 'Incomplete' path would be taken. In what scenarios is the Incomplete path utilized?

    DB:2.32:Why Do Workflow Join Activities Contain An Incomplete Path? kf


    Correct. The Join activity will take the Incomplete path when all incoming transitions that can complete, have completed. Join is smart enough to figure out when there are some incoming transitions that can never complete, like in Christopher's example.

  • RELEVANCY SCORE 2.32

    DB:2.32:D1000 Missing Drives 73


    I have a D1000 with 12 x SUN18GB drives. 'probe-scsi-all' at the OBP prompt shows all 12 of my disks. But in Solaris, /dev/dsk (also 'format') only shows 8 of the disks. The machines is a V880 running Solaris 8. Any ideas? Thanks.

    DB:2.32:D1000 Missing Drives 73

    Have you run 'devfsadm -v' to check that the system has correctly identified them?

    --A.

  • RELEVANCY SCORE 2.32

    DB:2.32:Problem With Firewire: Device Does Not Support Any More Concurrent Logins j3


    Hi,

    I am having real problem is getting shared access to a firewire drive. At any give time only one of the nodes are able to access the drive. Constantly seeing the following message:

    ieee1394: sbp2: Device does not support any more concurrent logins
    sbp2: probe of 0050770e4000057d-0 failed with error -16
    ieee1394: sbp2: Maximum concurrent logins supported: 1

    So far changed 3 different Firewire PCI cards from different manufacturer thinking that it has something to do with the chipset. Finally was able to get the OHCI compliant PCI card...but still continue to see the problem. Have been trying it for long long time...would appreciate any help or pointers to help to get this going.

    Additional Information:

    On Node One:
    ==========
    # lspci |grep 1394
    03:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
    # dmesg |grep sbp2
    sbp2: $Rev: 1265 $ Ben Collins bcollins@debian.org
    ieee1394: sbp2: Maximum concurrent logins supported: 1
    ieee1394: sbp2: Number of active logins: 1
    ieee1394: sbp2: Device does not support any more concurrent logins
    sbp2: probe of 0050770e4000057d-0 failed with error -16
    dmesg |grep -i scsi
    SCSI subsystem initialized
    scsi0 : ata_piix
    scsi1 : ata_piix
    Type: Direct-Access ANSI SCSI revision: 05
    SCSI device sda: 312500000 512-byte hdwr sectors (160000 MB)
    SCSI device sda: drive cache: write back
    Attached scsi disk sda at scsi0, channel 0, id 1, lun 0
    scsi2 : SCSI emulation for IEEE-1394 SBP-2 Devices

    On Node Two:
    ==========
    # lspci |grep 1394
    03:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
    # dmesg |grep sbp2
    sbp2: $Rev: 1265 $ Ben Collins bcollins@debian.org
    ieee1394: sbp2: Maximum concurrent logins supported: 1
    ieee1394: sbp2: Number of active logins: 1
    ieee1394: sbp2: Device does not support any more concurrent logins
    sbp2: probe of 0050770e4000057d-0 failed with error -16
    ieee1394: sbp2: Maximum concurrent logins supported: 1
    ieee1394: sbp2: Number of active logins: 0
    ieee1394: sbp2: Logged into SBP-2 device
    # dmesg |grep -i scsi
    scsi3 : SCSI emulation for IEEE-1394 SBP-2 Devices
    scsi4 : SCSI emulation for IEEE-1394 SBP-2 Devices
    Type: Direct-Access ANSI SCSI revision: 06
    SCSI device sdc: 320173056 512-byte hdwr sectors (163929 MB)
    SCSI device sdc: drive cache: write through
    Attached scsi disk sdc at scsi4, channel 0, id 0, lun 0
    ==================================================

    Appreciate your help and time.

    Regards
    CP

    DB:2.32:Problem With Firewire: Device Does Not Support Any More Concurrent Logins j3

    Hi,

    I am having real problem is getting shared access to a firewire drive. At any give time only one of the nodes are able to access the drive. Constantly seeing the following message:

    ieee1394: sbp2: Device does not support any more concurrent logins
    sbp2: probe of 0050770e4000057d-0 failed with error -16
    ieee1394: sbp2: Maximum concurrent logins supported: 1

    So far changed 3 different Firewire PCI cards from different manufacturer thinking that it has something to do with the chipset. Finally was able to get the OHCI compliant PCI card...but still continue to see the problem. Have been trying it for long long time...would appreciate any help or pointers to help to get this going.

    Additional Information:

    On Node One:
    ==========
    # lspci |grep 1394
    03:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
    # dmesg |grep sbp2
    sbp2: $Rev: 1265 $ Ben Collins bcollins@debian.org
    ieee1394: sbp2: Maximum concurrent logins supported: 1
    ieee1394: sbp2: Number of active logins: 1
    ieee1394: sbp2: Device does not support any more concurrent logins
    sbp2: probe of 0050770e4000057d-0 failed with error -16
    dmesg |grep -i scsi
    SCSI subsystem initialized
    scsi0 : ata_piix
    scsi1 : ata_piix
    Type: Direct-Access ANSI SCSI revision: 05
    SCSI device sda: 312500000 512-byte hdwr sectors (160000 MB)
    SCSI device sda: drive cache: write back
    Attached scsi disk sda at scsi0, channel 0, id 1, lun 0
    scsi2 : SCSI emulation for IEEE-1394 SBP-2 Devices

    On Node Two:
    ==========
    # lspci |grep 1394
    03:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
    # dmesg |grep sbp2
    sbp2: $Rev: 1265 $ Ben Collins bcollins@debian.org
    ieee1394: sbp2: Maximum concurrent logins supported: 1
    ieee1394: sbp2: Number of active logins: 1
    ieee1394: sbp2: Device does not support any more concurrent logins
    sbp2: probe of 0050770e4000057d-0 failed with error -16
    ieee1394: sbp2: Maximum concurrent logins supported: 1
    ieee1394: sbp2: Number of active logins: 0
    ieee1394: sbp2: Logged into SBP-2 device
    # dmesg |grep -i scsi
    scsi3 : SCSI emulation for IEEE-1394 SBP-2 Devices
    scsi4 : SCSI emulation for IEEE-1394 SBP-2 Devices
    Type: Direct-Access ANSI SCSI revision: 06
    SCSI device sdc: 320173056 512-byte hdwr sectors (163929 MB)
    SCSI device sdc: drive cache: write through
    Attached scsi disk sdc at scsi4, channel 0, id 0, lun 0
    ==================================================

    Appreciate your help and time.

    Regards
    CP

  • RELEVANCY SCORE 2.31

    DB:2.31:Unable To Attach Powervault 220s Storage zf



    I have had this Powervault attached to this ESX server for over a year and now after a BIOS upgrade on the server (Dell Poweredge 1850) and a firmware upgrade on the controller (Perc3/dc) the VMkernel will not attach the drive. I have a Perc4 (local storage) and a Perc3 on the Powervault. This is the error in the console log:

    May 28 15:18:51 vmwesx2 kernel: PCI_IDE: unknown IDE controller on PCI bus 00 device f9, VID=8086, DID=24db

    May 28 15:18:51 vmwesx2 kernel: PCI: Device 00:1f.1 not available because of resource collisions

    May 28 15:18:51 vmwesx2 kernel: PCI_IDE: chipset revision 2

    May 28 15:18:51 vmwesx2 kernel: PCI_IDE: not 100%% native mode: will probe irqs later

    May 28 15:18:51 vmwesx2 kernel: ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio

    May 28 15:18:51 vmwesx2 kernel: ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio

    May 28 15:18:51 vmwesx2 kernel: hda: SAMSUNG CD-ROM SN-124, ATAPI CD/DVD-ROM drive

    May 28 15:18:51 vmwesx2 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14

    May 28 15:18:51 vmwesx2 kernel: hda: ATAPI 24X CD-ROM drive, 128kB Cache

    May 28 15:18:51 vmwesx2 kernel: Uniform CD-ROM driver Revision: 3.12

    May 28 15:18:51 vmwesx2 kernel: Floppy drive(s): fd0 is 1.44M

    May 28 15:18:51 vmwesx2 kernel: FDC 0 is a National Semiconductor PC87306

    May 28 15:18:51 vmwesx2 kernel: SCSI subsystem driver Revision: 1.00

    May 28 15:18:51 vmwesx2 kernel: request_module\[scsi_hostadapter]: Root fs not mounted

    May 28 15:18:51 vmwesx2 kernel: request_module\[scsi_hostadapter]: Root fs not mounted

    May 28 15:18:51 vmwesx2 kernel: NET4: Linux TCP/IP 1.0 for NET4.0

    May 28 15:18:51 vmwesx2 kernel: IP Protocols: ICMP, UDP, TCP, IGMP

    May 28 15:18:51 vmwesx2 kernel: IP: routing cache hash table of 2048 buckets, 16Kbytes

    May 28 15:18:51 vmwesx2 kernel: TCP: Hash tables configured (established 32768 bind 32768)

    May 28 15:18:51 vmwesx2 kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

    May 28 15:18:51 vmwesx2 kernel: RAMDISK: Compressed image found at block 0

    May 28 15:18:51 vmwesx2 kernel: Freeing initrd memory: 289k freed

    May 28 15:18:51 vmwesx2 kernel: VFS: Mounted root (ext2 filesystem).

    May 28 15:18:51 vmwesx2 kernel: megaraid: v2.10.7 (Release Date: Sat Jun 5 02:32:59 EDT 2004)

    May 28 15:18:51 vmwesx2 kernel: megaraid: found 0x1028:0x0013:bus 2:slot 14:func 0

    May 28 15:18:51 vmwesx2 kernel: scsi0:Found MegaRAID controller at 0xd200b000, IRQ:27

    May 28 15:18:51 vmwesx2 kernel: megaraid: \[522A:H430] detected 1 logical drives.

    May 28 15:18:51 vmwesx2 kernel: megaraid: supports extended CDBs.

    May 28 15:18:51 vmwesx2 kernel: megaraid: channel[0] is raid.

    May 28 15:18:51 vmwesx2 kernel: megaraid: found 0x101e:0x1960:bus 5:slot 0:func 0

    May 28 15:18:51 vmwesx2 kernel: scsi1:Found MegaRAID controller at 0xd200d000, IRQ:24

    May 28 15:18:51 vmwesx2 kernel: megaraid: \[199A:3.35] detected 1 logical drives.

    May 28 15:18:51 vmwesx2 kernel: megaraid: supports extended CDBs.

    May 28 15:18:51 vmwesx2 kernel: megaraid: channel[0] is raid.

    May 28 15:18:51 vmwesx2 kernel: megaraid: channel[1] is raid.

    May 28 15:18:51 vmwesx2 kernel: scsi0 : LSI Logic MegaRAID 522A 254 commands 16 targs 4 chans 7 luns

    May 28 15:18:51 vmwesx2 kernel: scsi1 : LSI Logic MegaRAID 199A 254 commands 16 targs 5 chans 7 luns

    May 28 15:18:51 vmwesx2 kernel: scsi0: scanning scsi channel 0 for logical drives.

    May 28 15:18:51 vmwesx2 kernel: Vendor: MegaRAID Model: LD 0 RAID1 34G Rev: 522A

    May 28 15:18:51 vmwesx2 kernel: Type: Direct-Access ANSI SCSI revision: 02

    May 28 15:18:51 vmwesx2 kernel: scsi0: scanning scsi channel 1 for logical drives.

    May 28 15:18:51 vmwesx2 kernel: scsi0: scanning scsi channel 2 for logical drives.

    May 28 15:18:51 vmwesx2 kernel: scsi0: scanning scsi channel 3 for logical drives.

    May 28 15:18:51 vmwesx2 kernel: scsi0: scanning scsi channel 4 \[P0] for physical devices.

    May 28 15:18:51 vmwesx2 kernel: Vendor: PE/PV Model: 1x2 SCSI BP Rev: 1.0

    May 28 15:18:51 vmwesx2 kernel: Type: Processor ANSI SCSI revision: 02

    May 28 15:18:51 vmwesx2 kernel: scsi1: scanning scsi channel 0 for logical drives.

    May 28 15:18:51 vmwesx2 kernel: Vendor: MegaRAID Model: LD 0 RAID5 839G Rev: 199A

    May 28 15:18:51 vmwesx2 kernel: Type: Direct-Access ANSI SCSI revision: 02

    May 28 15:18:51 vmwesx2 kernel: scsi1: scanning scsi channel 1 for logical drives.

    May 28 15:18:51 vmwesx2 kernel: scsi1: scanning scsi channel 2 for logical drives.

    May 28 15:18:51 vmwesx2 kernel: scsi1: scanning scsi channel 3 for logical drives.

    May 28 15:18:51 vmwesx2 kernel: scsi1: scanning scsi channel 4 \[P0] for physical devices.

    May 28 15:18:51 vmwesx2 kernel: scsi1: scanning scsi channel 5 \[P1] for physical devices.

    May 28 15:18:51 vmwesx2 kernel: Vendor: DELL Model: PV22XS Rev: E.17

    May 28 15:18:51 vmwesx2 kernel: Type: Processor ANSI SCSI revision: 03

    May 28 15:18:51 vmwesx2 kernel: VMWARE SCSI Id: Supported VPD pages for sda : 0x0 0x80 0x83

    May 28 15:18:51 vmwesx2 kernel: VMWARE SCSI Id: Device id info for sda:

    May 28 15:18:51 vmwesx2 kernel: VMWARE SCSI Id: Id for sda 0x27 0x30 0x78 0x30 0x30 0x27 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x4c 0x44 0x20 0x30 0x20 0x52

    May 28 15:18:51 vmwesx2 kernel: VMWARE: Unique Device attached as scsi disk sda at scsi0, channel 0, id 0, lun 0

    May 28 15:18:51 vmwesx2 kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0

    May 28 15:18:51 vmwesx2 kernel: VMWARE SCSI Id: Supported VPD pages for sdb : 0x0 0x80 0x83

    May 28 15:18:51 vmwesx2 kernel: VMWARE SCSI Id: Device id info for sdb:

    May 28 15:18:51 vmwesx2 kernel: VMWARE SCSI Id: Id for sdb 0x27 0x30 0x78 0x30 0x30 0x27 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x4c 0x44 0x20 0x30 0x20 0x52

    May 28 15:18:51 vmwesx2 kernel: VMWARE: Duplicate found for scsi disk at scsi1, channel 0, id 0, lun 0

    May 28 15:18:51 vmwesx2 kernel: VMWARE: Device that would have been attached as scsi disk sdb at scsi1, channel 0, id 0, lun 0

    May 28 15:18:51 vmwesx2 kernel: Has not been attached because it is a duplicate path or on a passive path[/b]

    May 28 15:18:51 vmwesx2 kernel: scsi_register_host starting finish

    May 28 15:18:51 vmwesx2 kernel: SCSI device sda: 71024640 512-byte hdwr sectors (34680 MB)

    May 28 15:18:51 vmwesx2 kernel: Partition check:

    May 28 15:18:51 vmwesx2 kernel: sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8

    May 28 15:18:51 vmwesx2 kernel: scsi_register_host done with finish

    May 28 15:18:51 vmwesx2 kernel: kjournald starting. Commit interval 5 seconds

    May 28 15:18:51 vmwesx2 kernel: EXT3-fs: mounted filesystem with ordered data mode.

    As you can see the system sees the 839G drive on scsi1 (vmhba1:0:0) but it won't attach it because of whatever this "duplicate" error is.

    Like I said earlier, this device has been attached to this server for over a year and it's been fine.

    Anybody seen anything like this or know what this error means? I know it's not a "supported" storage system so VMWare couldn't help me.

    Thnaks group.

    Shawn

    DB:2.31:Unable To Attach Powervault 220s Storage zf


    Thanks for the suggestions. I've swapped out the perc3 for a perc4 with the updated firmware on it and I have the powervault back. Interesting thing is it shows up as vmhba2. So. now I have a perc4/se (vmhba0) and a perc4/dc (vmhba2).

  • RELEVANCY SCORE 2.31

    DB:2.31:Ultra 60 Obp xk


    Hi

    I have problem with my Ultra 60.
    when i do:
    probe-scsi-all
    /pci@1f,4000/scsi@3,1

    /pci@1f,4000/scsi@3

    it hangs. set-defaults doesn't hep. Have you got any ideas what to do?

    Paul.

    DB:2.31:Ultra 60 Obp xk

    Perhaps it is time to push the workstation through a DIAG POST.
    You will need to be connected to it on TTYa, from another system,
    as all information will go out that console connection and not out through any graphics card.
    The keyboard is likely disabled during the procedure, at least until it completes POST and enters OBP.

    If you need it, the OBP 3.x Command Reference Manual is available at:
    http://docs.sun.com/app/docs/doc/806-1377-10?q=openboot+command+reference

    Re-install everything back into the chassis,and then ...
    You would leave auto-boot? at `false`,
    you change the diag-device variable to `disk`,
    you change the diag-level variable to `max`,
    and you change the diag-switch? variable to `true`.

    When you next power it on, the system will be pushed through an extensive POST.
    Low level components will be examined very closely.
    That includes cpu(s), DIMMs, controller chipsets, data busses, and more.

    Again, all the results will stream out the TTYa console.
    Capture it as a text file to the system you've connected to that port,
    and you may find the culprit.

  • RELEVANCY SCORE 2.31

    DB:2.31:Desparate Help With D1000 k3


    I have an Enterprise 220R with Solaris 9 O/S, and a SunStorEdge D1000(8x 18Gb disks). I understand that the onboard SCSI SE is incompatible with the SCSI on the D1000, however I have a PCI dual SCSI card which is Differential installed on the 220R. Using a sun 530-2453 cable I have connected the 220R to the 1st Interface on the D1000, and then linked the other SCSI interfaces using a HPDB68M to HPDB68M cable, finally teminating it at the last interface with a terminator. It all seems to be connected correctly but the 220R refuses to recognise the D1000. I have used the devfsadm -c disks command to see if the system recognises it but with no joy. Ive looked over the docoumentation again and again but seem to be getting no where.
    Basically my configuration is:
    Enterprise220R -- StorEdge 1st SCSI interface -- HPDB68M cable(2nd SCSI interface) -- HPDb68M(3rd SCSI interface) -- SCSI Terminator.

    I also went to the OK prompt and typed in probe-scsi-all and only received an output which recognises the 2 onboard scsi disks:
    /pci@1f, 4000/scsi@2,1
    /pci@1f, 4000/scsi@2
    Fatal SCSI error at address 10 unexpected disconnect
    /pci@1f, 4000/scsi@3,1
    /pic@1f, 4000/scsi@3

    How do I get solaris to recognise the D1000?? Does it have something to do with the /dev or /devices ??
    Please help im going banannas here!!

    DB:2.31:Desparate Help With D1000 k3

    I have an Enterprise 220R with Solaris 9 O/S, and a SunStorEdge D1000(8x 18Gb disks). I understand that the onboard SCSI SE is incompatible with the SCSI on the D1000, however I have a PCI dual SCSI card which is Differential installed on the 220R. Using a sun 530-2453 cable I have connected the 220R to the 1st Interface on the D1000, and then linked the other SCSI interfaces using a HPDB68M to HPDB68M cable, finally teminating it at the last interface with a terminator. It all seems to be connected correctly but the 220R refuses to recognise the D1000. I have used the devfsadm -c disks command to see if the system recognises it but with no joy. Ive looked over the docoumentation again and again but seem to be getting no where.
    Basically my configuration is:
    Enterprise220R -- StorEdge 1st SCSI interface -- HPDB68M cable(2nd SCSI interface) -- HPDb68M(3rd SCSI interface) -- SCSI Terminator.

    I also went to the OK prompt and typed in probe-scsi-all and only received an output which recognises the 2 onboard scsi disks:
    /pci@1f, 4000/scsi@2,1
    /pci@1f, 4000/scsi@2
    Fatal SCSI error at address 10 unexpected disconnect
    /pci@1f, 4000/scsi@3,1
    /pic@1f, 4000/scsi@3

    How do I get solaris to recognise the D1000?? Does it have something to do with the /dev or /devices ??
    Please help im going banannas here!!

  • RELEVANCY SCORE 2.31

    DB:2.31:Ace To Load Balance Proxy Servers sc



    Hi,

    i have a set of 4 proxy servers that are already load balanced. But they are using a incorrectly configured health probe on the ace. I need to know a good configuration for a heath probe that will send a http request over port 80 , wait for response, and read it?  I searched the forum and the cisco pages but could not find a proper answer.        

    the current probe is as follows:

    probe http HTTPGET

      description Tests that www.gmail.com returns 302 redirect

      interval 10

      request method get url http://www.gmail.com

      expect status 302 302

    -Gordon


    DB:2.31:Ace To Load Balance Proxy Servers sc


    Hi Gordon,

    probe http P_HTTP_TEST

      interval 5

      passdetect interval 3

      passdetect count 3

      request method get url /test

      expect status 200 200

      expect regex testdata   ---- This is the data you want to parse in order to make the probe successful.

    If the regex match fails then the probe will be declare it as failed.

    regards,

    Ajay Kumar

  • RELEVANCY SCORE 2.31

    DB:2.31:Esx 2.5.3 San Contention Issue (Scsi Reserve Timeout) - Please Help! x9



    Hello All!

    We are having an issue with VMware and SAN which I understand to be called a "SCSI Reserve Conflict". The basic setup is this:

    We have 15 ESX host Servers (IBM x366) each server can see 3 LUNs which we call VMFS1, VMFS2, and VMFS3.

    Each server has 4 paths to each LUN and we are using preferred path.

    What we are seeing is that the Virtual Machine Guest will often perform slowly or "freeze" for no apparent reason.

    On the "linux command line level" if I go to /vmfs/VMFS2 I will often get a:

    ls: .: Resource temporarily unavailable

    The log /var/log/vmkwarning is filled with:

    Feb 6 11:23:40 pdc-al-vm01 vmkernel: 46:10:29:58.796 cpu2)WARNING: SCSI: 5663: vmhba1:0:1:0 status = 24/0 0x0 0x0 0x0

    Feb 6 11:23:40 pdc-al-vm01 vmkernel: 46:10:29:58.796 cpu5)WARNING: SCSI: 6042: returns 0xbad0023 for vmhba1:0:1

    Feb 6 11:23:40 pdc-al-vm01 vmkernel: 46:10:29:59.395 cpu3)WARNING: SCSI: 5663: vmhba1:0:1:0 status = 24/0 0x0 0x0 0x0

    Feb 6 11:23:40 pdc-al-vm01 vmkernel: 46:10:29:59.395 cpu2)WARNING: SCSI: 6042: returns 0xbad0023 for vmhba1:0:1

    Feb 6 11:23:41 pdc-al-vm01 vmkernel: 46:10:29:59.914 cpu3)WARNING: SCSI: 5663: vmhba1:0:1:0 status = 24/0 0x0 0x0 0x0

    Feb 6 11:23:41 pdc-al-vm01 vmkernel: 46:10:29:59.914 cpu0)WARNING: SCSI: 6042: returns 0xbad0023 for vmhba1:0:1

    Feb 6 11:23:41 pdc-al-vm01 vmkernel: 46:10:30:00.438 cpu3)WARNING: SCSI: 5663: vmhba1:0:1:0 status = 24/0 0x0 0x0 0x0

    Feb 6 11:23:41 pdc-al-vm01 vmkernel: 46:10:30:00.438 cpu2)WARNING: SCSI: 6042: returns 0xbad0023 for vmhba1:0:1

    Feb 6 11:23:42 pdc-al-vm01 vmkernel: 46:10:30:01.013 cpu3)WARNING: SCSI: 5663: vmhba1:0:1:0 status = 24/0 0x0 0x0 0x0

    Feb 6 11:23:42 pdc-al-vm01 vmkernel: 46:10:30:01.013 cpu0)WARNING: SCSI: 6042: returns 0xbad0023 for vmhba1:0:1

    We have third party support through IBM and when I called them about this they told me basically that when a particular ESX Host Server is accessing the LUN that it will "lock" the LUN and it isn't available for reading/writing by any other host server. However, they didn't offer any suggestions as to how to fix this.

    Is there anyone out there who can help me understand what is going on and how to fix this and improve the performance of my virtual environment?

    BTW, I'm using a Hitachi Tagmastore USP 600 with Qlogic HBAs.

    Any insight would be greatly appreciated!

    thanks!

    -Christopher

    DB:2.31:Esx 2.5.3 San Contention Issue (Scsi Reserve Timeout) - Please Help! x9


    Thanks for this, I'm going to take your advice and split the environment into 8 LUNs. I can't do this all at once though...I have to break them up one volume at a time over a few months.

    Your advice was very helpful though, it was plain to see what was going on after I considered your reply.

    Thanks again!

  • RELEVANCY SCORE 2.31

    DB:2.31:How To Install Scsi+Network Card On Ultra5 8c


    run "probe-scsi" on Openboot,host cannt find external scsi unit .
    need driver?,
    my scsi+network card fcc id is GWVFRESH,
    main chip is stp2003(sun) 21152(DEC) isp1040(qlogic)

    DB:2.31:How To Install Scsi+Network Card On Ultra5 8c

    you need to run;
    ok probe-scsi-all
    or
    ok show-devs

    once confirmed, boot -r to configure in. is the obp version ok to handle this card??

  • RELEVANCY SCORE 2.31

    DB:2.31:Networker Not See Autochanger, Only Tape Drive s8



    I have Solaris 10 OS, Networker Server 7.5 SP1 and SL24 Tape library.

    When trying to configure autochanger it couldn't be seen from Networker server.

    Please find below inquire command:

    root@backup# inquirescsidev@0.1.0:HP Ultrium 4-SCSI H58W|Tape, /dev/rmt/0cbn S/N: HU19336GDA ATNN=HP Ultrium 4-SCSI HU19336GDA WWNN=50014380032A62B1 WWPN=50014380032A62B2 WW2N=50014380032A62B1 PORT=00000001

    But the server see both devices tape and changer

    Here is the output:

    root@backup# luxadm probe

    Found Fibre Channel device(s): Node WWN:50014380032a62b1 Device Type:Medium changer device Logical Path:/devices/scsi_vhci/medium-changer@g50014380032a62b0 Node WWN:50014380032a62b1 Device Type:Tape device Logical Path:/dev/rmt/0n

    root@backup# cfgadm -al -o show_SCSI_LUN

    Ap_Id Type Receptacle Occupant Conditionc2 fc-fabric connected configured unknownc2::50014380032a62b2,0 tape connected configured unknownc2::50014380032a62b2,1 med-changer connected configured unknownc3 fc-fabric connected unconfigured unknown

    I don't know where could be the problem?

    Any idea?

    I already updated OS with latest patches, and firmware of tape library and drive.

    Thanks a lot for your help.

    DB:2.31:Networker Not See Autochanger, Only Tape Drive s8


    Well, jbconfig also doesn't configure the library.

    Hopefully I found the problem:

    On Sun Servers x Series and on Solaris 10 OS by default is enabled multipathing althought there's only one path via SAN to the library.

    When I disabled it it was possible to see not only tape drive but also autochanger.

  • RELEVANCY SCORE 2.31

    DB:2.31:Booting A Blade 1500 Frm A Scsi Disk 1s


    I have installed Solaris 8 on a scsi disk attached to a Blade 1500.

    But I can't find a way to boot it. What would be the device name of the scsi disk?

    probe-scsi-all does not find the scsi disk (nor the scsi card it seems).

    Edited by: RobertB720 on Feb 9, 2008 9:56 AM

    DB:2.31:Booting A Blade 1500 Frm A Scsi Disk 1s

    Hi,

    I got confirmation that my card cannot be used to boot a scsi drive, so I'll get a replacement.

    Thank you for your help!

  • RELEVANCY SCORE 2.31

    DB:2.31:Problem Recognizing L25 Tape Library (Probe-Scsi-All Shows Disks?) sj


    Hello,

    I am having a problem recognizing an L25 library. Details of my hardware -

    I have tried using two different Netra T1 200 systems, with latest OBP (1.0.17), with a PCI dual differential scsi card (375-0006/X6541A). I have verified that the card is supported in the netra, and L25 is supported on this card. I have swapped cables, terminators and scsi cards. I am able to use the LTO drive, when I have it connected on its own scsi bus, or if its second to the library controller in the scsi chain.

    I can not see or use the library autoloader, though, from either OBP or the OS. From the OBP the library appears to be DISKS, and hangs after lun 7. On one of the scsi cards, the probe-scsi shows the "disks" then hangs until I send a break, on the other I get an MMU miss error:
    ok probe-scsi-all
    /pci@1f,0/pci@1/scsi@5,1
    Target 0
    Unit 0 Disk
    Unit 1 Disk
    Unit 2 Disk
    Unit 3 Disk
    Unit 4 Disk
    Unit 5 Disk
    Unit 6 Disk
    Unit 7 Disk

    Fast Instruction Access MMU MissI am thinking I may have a hardware issue with the library, or could I still be having a scsi issue of some kind? Any help would be appreciated! Thanks in advance,

    Erin

    DB:2.31:Problem Recognizing L25 Tape Library (Probe-Scsi-All Shows Disks?) sj

    Hello,

    Thanks for you suggestions on this problem. I finally found the issue, so I wanted to post it for anyone else out there having similar problems -

    It turns out that Solaris does not natively/by default create device files for the L25 library changer. Apparently most of the commercial backup applications (Solstice Backup, Netbackup, Legato) will identify the attached autochanger, and create whatever file(s) they need. I am currently using bacula, however, so I don't have any other utilities at my disposal, I was expecting my device files to be created by the OS.

    To make the device files, I had to use the SGEN driver (see Sun doc id 72861 - http://sunsolve.sun.com/search/document.do?assetkey=1-9-72861-1) . It was easy enough to do (vi /kernel/drv/sgen.conf ; modload /kernel/drv/sgen ; devfsadm), and I then had a working /dev/scs/changer/c*t*d* file for me to interact with the library. I don't know why I had such problems seeing it from the OBP, but I can use the device now, no probs!

    Thanks again,

    Erin