Recent Posts

Pages: [1] 2 3 ... 10
1
Laptops / Re: [Fixed] Inspiron 7000 not starting when pressing "power on"
« Last post by Lirras on September 21, 2017, 08:46:54 AM »
Thanks Admin, this got my Inspiron working again.
2
Servers / Reset Error Codes
« Last post by lopezrx on August 05, 2017, 05:02:12 PM »
08/05/2017

I had a bad Power Supply on my dual power supply Dell 2950 Server Tower Config.  I changed it out easily enough, but the digital display on the front panel still shows error condition(s).  How can I clear it?

Rick McCoy
3
Linux Base / How to disable SSH on XenServer
« Last post by Guru9 on August 11, 2016, 09:10:43 AM »
    [list=decimal]
    • Open the Console View for the Host



    [list=decimal]
    • Select "Remote Service Configuration"


    [list=decimal]
    • Select "Enable/Disable Remote Shell"




    [list=decimal]
    • Enter root Credentials and press <Enter>


    [list=decimal]
    • Highlight Enable and press <Enter>


    [list=decimal]
    • SSH has now been enabled



    Note: Disable SSH after use due to security vulnerability.
    4
    VMware - ESX / VMware Tools - GuestRpcSendTimedOut: message to toolbox timed out.
    « Last post by Guru9 on August 11, 2016, 05:23:01 AM »
      Attempts to take a quiesced snapshot in a Windows Server 2003 Guest OS might fail with an error similar to the following:

        2016-04-16T03:05:22.371Z| vmx| I120: GuestRpcSendTimedOut: message to toolbox timed out.
        2016-04-16T03:05:22.371Z| vmx| I120: Msg_Post: Warning
        2016-04-16T03:05:22.371Z| vmx| I120:
    [msg.snapshot.quiesce.rpc_timeout] A timeout occurred while communicating with VMware Tools in the virtual machine.
      2016-04-16T03:05:22.371Z| vmx| I120: ----------------------------------------
      2016-04-16T03:05:22.374Z| vmx| I120: ToolsBackup: changing quiesce state: IDLE -> DONE
      2016-04-16T03:05:22.374Z| vmx| I120: SnapshotVMXTakeSnapshotComplete: Done with snapshot 'afea': 0
      2016-04-16T03:05:22.374Z| vmx| I120: SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Failed to quiesce the virtual machine (40).
      2016-04-16T03:05:33.304Z| vmx| I120: GuestRpcSendTimedOut: message to toolbox timed out.
      2016-04-16T03:05:40.550Z| vmx| I120: Tools: Tools heartbeat timeout.
      2016-04-16T03:05:43.300Z| vmx| I120: GuestRpcSendTimedOut: message to toolbox-dnd timed out.
      2016-04-16T03:05:48.306Z| vmx| I120: GuestRpcSendTimedOut: message to toolbox timed out.

    Solution

    To workaround this issue, perform the following
    [list=decimal]
    • Uninstall VMware Tools 10.0.9. 
    • Replace it with VMware Tools 10.0.8. 
    5
    Symptoms
    • Storage migration of a virtual machine fails.

    • You see this error in the /var/log/vpxa.log on the ESXi host:

    Code: [Select]
    A fatal internal error occurred. See the virtual machine's log for more details. Failed to copy one or more disks.
    [/size][/font][/li][li]You see this error in the /vmfs/volumes/datastore/vm_name/vmware.log on the ESXi host:

    Code: [Select]
    YYYY-MM-DD TIME.752Z| vmx| W110: SVMotion: scsi0:0: Failed to copy disk: I/O error
    YYYY-MM-DD TIME.752Z| Worker#1| W110: SVMotionMirroredModeThreadDiskCopy: Found internal error when woken up on diskCopySemaphore. Aborting storage vmotion.
      [/size][/font][/li]
    • You see this error in var/log/vmkernel.log

    Code: [Select]
    [list][li][font=Courier New][size=10pt]YYYY-MM-DD TIME.641Z cpu4:33440)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x28 (0x412e40448bc0, 7812129) to dev "naa.6006016095d0280076bfa8267680df11" on path "vmhba2:C0:T1:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x11 0x0. Act:NONE[/size][/font]
    [font=Courier New][size=10pt]YYYY-MM-DD TIME.641Z cpu4:33440)ScsiDeviceIO: 2337: Cmd(0x412e40448bc0) 0x28, CmdSN 0x5671fa from world 7812129 to dev "naa.6006016095d0280076bfa8267680df11" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x11 0x0.[/size][/font]
    [/li][/list]
    Purpose

    SVMotion tasks are failing due to an I/O error.


    Cause

    This issue is caused because the ESXi host is unable to read the data from the Datastore where the VM is running during storage vMotion.

    Sense Data: 0x3 0x11 0x0 indicate that disk naa.6006016095d0280076bfa8267680df11 has gone bad and returning medium error. This indicates a hardware failure. It is possible that disk is showing OK from array, but some of blocks/sectors on the disk has gone bad, so when Read/Write IO happens on the disk it fails the IO.

    This is caused due to an error in LUN and vmfs is not involved here.The Sense code 0x3 means Medium error and  0x11/0x0 is Additional sense code indicate "Unrecovered Read error". This is due to flaw in the medium or an error in the recorded data


    6
    Windows / "0x80070057" when saving files
    « Last post by Guru9 on August 08, 2016, 05:43:54 AM »
      Symptoms
      When you back up files by using Windows Backup on a computer that is running Windows 7, the backup fails and you receive the following error message:An internal error has occurred: The parameter is incorrect: (0x80070057)

      Resolution
      To resolve this problem, use one of the following methods:

      Method 1:

      Change the decimal symbol settingThis problem can occur if the decimal symbol is not set to  '.' (dot).
      This is common in languages and locales other than English (United States), such as German (Germany).

      To change the decimal symbol setting, follow these steps:[list=decimal]
      • Open  Control Panel, click Clock, Language, and Region,  and then click Region and Language.
      • Click the Formats tab, and then click Additional settings.
      • In the Decimal symbol field, type . (dot), and then click OK two times.
      • Restart the computer.
      Note Some third-party software may cause changes to the runtime locale of the computer  and override the setting in Control Panel.


      Method 2:

      Add a registry key valueWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

      [list=decimal]
      • Click Start,   type Regedit.exe  in the Search programs and files box, and then press ENTER.
      •   Locate and then click the following registry subkey:  HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\System
      •   On the Edit menu, point to New, and then click DWORD Value.
      •   Type CopyFileBufferedSynchronousIo, and then press ENTER.   
      • Right-click CopyFileBufferedSynchronousIo, and then click Modify.   
      • In the Value data box, type 1, and then click OK.
      •   Exit Registry Editor.
      7
      Windows / How to change the RDP listening port for Remote Desktop in Windows?
      « Last post by Guru9 on August 08, 2016, 05:42:31 AM »
        [list=decimal]
        • Start Registry Editor.
        • Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber
        • On the Edit menu, click Modify, and then click Decimal.
        • Type the new port number, and then click OK.
        • Quit Registry Editor.
        • Restart the computer.
        Note When you try to connect to this computer by using the Remote Desktop connection, you must type the new port. Maybe you have to set the firewall to allow the new port number before you connect to this computer by using the Remote Desktop connection.
        8
        Windows / Enable the Windows Key on a keyboard
        « Last post by Guru9 on August 08, 2016, 05:41:07 AM »
            If the Windows key is not working you can enable it via the Regedit

        To enable the Windows key, follow these steps: [list=decimal]
        • Click Start, click Run, type regedt32, and then click OK.
        • On the Windows menu, click HKEY_LOCAL_ MACHINE on Local Machine.
        • Double-click the System\CurrentControlSet\Control folder, and then click the Keyboard Layout folder.
        • Right-click the Scancode Map registry entry, and then click Delete. Click Yes.
        • Close Registry Editor and restart the computer
        To disable the Windows key, follow these steps: [list=decimal]
        • Click Start, click Run, type regedt32, and then click OK.
        • On the Windows menu, click HKEY_LOCAL_ MACHINE on Local Machine.
        • Double-click the System\CurrentControlSet\Control folder, and then click the Keyboard Layout folder.
        • On the Edit menu, click Add Value, type in Scancode Map, click REG_BINARY as the Data Type, and then click OK.
        • Type 00000000000000000300000000005BE000005CE000000000 in the Data field, and then click OK.
        • Close Registry Editor and restart the computer.
        9
        Code: [Select]
        Open Folder

        \\uncpath is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

        Logon Failure: The target account name is incorrect.
          [/li]

        Resolution


        To resolve this issue on a file server that is running the SMB version 1 protocol, add the DisableStrictNameChecking value to the registry:

        Code: [Select]
        Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
        DWORD name: DisableStrictNameChecking
        DWORD value: 1

        Important Do not use DNS CNAMEs in the future for file servers. If you want to still give "alternate names" to servers, you can do so with the following command:

        Code: [Select]
        NETDOM COMPUTERNAME /ADD
        Note This command automatically registers SPNs for the alternate names.

         We do not recommend that you resolve this issue for a file server that is not Windows-based by typing the following commands in an elevated Command Prompt window on a Windows-based computer. Be aware that you would have to be logged on with Domain Administrator credentials and then press Enter at the command prompt to register the SPN for the CNAME of the non-Windows-based File Server storage device:
        SETSPN -a host/alias_name targetserver
        SETSPN -a host/alias_name.contoso.com targetserver
        10
        Q: What does the Cluster Health - Disk format version test do?

        This test verifies the disk format version of all Virtual SAN disks currently in use, and ensures that all Virtual SAN disks use the highest disk format version that the host supports.

        Q: What does it mean when it is in an error state?

        If this check returns a warning, it means that the disk format version of one or more Virtual SAN disks are compatible, but out of date. The following software configurations are allowed, but they do not support the latest Virtual SAN features.

        • Hosts are running Virtual SAN 6.1, and in-use Virtual SAN disks have disk format v1.0 (this configuration does not support Virtual SAN sparse and optimized snapshots).
        • Hosts are running Virtual SAN 6.2, and in-use disks have disk format v1.0 or v2.0 (this configuration does not support deduplication and compression, or RAID 5/6 fault tolerance).
        To get full support of the latest Virtual SAN features, on-disk upgrade is recommended.

        If this check returns an error, it means the disk format version of one or more Virtual SAN disks have a disk format version that is out of data and is not compatible with other Virtual SAN disks. The error case is disk format  v2.0 mixed with disk format v3.0, and it is very dangerous because it can break Virtual SAN data. This configuration must be fixed immediately.

        Q: How does one troubleshoot and fix the error state?


        If the result of this check is a warning, it is recommended that you upgrade the on-disk format. If the result is an error, the following message is displayed:

        Code: [Select]
        v2.0 disk cannot work with v3.0 disk, on-disk format upgrade is required.For both cases, a Virtual SAN on-disk format upgrade is required to fix the issue. Click the On-disk Format Upgrade button on the vSphere Web Client (Manage > Settings > Virtual SAN > General).
        Pages: [1] 2 3 ... 10