发布于

Fix for Unable to Create Symlinks in Shared Folders Between VirtualBox Linux VM and Windows Host

Software Setup:

  • VirtualBox VM: Ubuntu 22
  • Host: Windows 10

When attempting to create symbolic links in a shared folder within an Ubuntu 22 VirtualBox VM, you may encounter several errors:

1.Error during npm install esbuild:

    Error: EPERM: operation not permitted, symlink '../esbuild/bin/esbuild' -> '/var/www/reverb.test/node_modules/.bin/esbuild'

    2.Error when creating symlinks in PHP:

    symlink(): Operation not permitted

    3.Error when running the ln command:

    ln: failed to create symbolic link 'xxx.so.0': Read-only file system

    4.Error when running the cp command:

    cannot create symbolic link `xxxx': Read-only file system

    5.Another error during cp:

    cannot create symbolic link `xxxx': Protocol error

    These issues occur because VirtualBox restricts the creation of symbolic links in shared folders for security reasons. To allow symbolic link creation, you’ll need to enable the option VBoxInternal2/SharedFoldersEnableSymlinksCreate/<share_folder_name>. For Vagrant users, this option is automatically configured when running vagrant up. For VirtualBox users, you can manually enable this setting using the VBoxManage.exe tool, which is located in the same directory as the VirtualBox GUI on Windows.

    Step-by-Step Guide:

    1.Close VirtualBox.

    2.Open a command prompt with administrator privileges and navigate to the VirtualBox installation directory (e.g., cd C:\Programs\Oracle\VirtualBox). Then, execute the following command:

    VBoxManage setextradata YOURVMNAME VBoxInternal2/SharedFoldersEnableSymlinksCreate/YOURSHAREFOLDERNAME 1

    1) Replace YOURVMNAME with the name of your Ubuntu VM.

    2) Replace YOURSHAREFOLDERNAME with the name of the shared folder, which corresponds to the “Shared Folder Name” you set in VirtualBox, not the actual folder path or its name.

    Example:

    VBoxManage setextradata Ubuntu22 VBoxInternal2/SharedFoldersEnableSymlinksCreate/share 1

    3 Run VirtualBox as an administrator to apply the changes.

    References:

    发布于

    Why Multiple Elasticsearch Nodes Fail to Form a Cluster: master_not_discovered_exception or NotMasterException and How to Fix It

    If you’ve encountered a situation where multiple Elasticsearch nodes fail to automatically form a cluster and the logs show the error: “master_not_discovered_exception”, you are not alone.

    The Problem

    The root cause is often related to system administrators cloning virtual machines to create multiple Elasticsearch servers. When this happens, every Elasticsearch node ends up with the same node ID, and as a result, the cluster cannot successfully elect a master node.

    Verifying the Issue

    You can verify this issue by listing all the node IDs with the following command:

    GET /_cat/nodes?v&h=id,ip,name&full_id=true

    However, since the Elasticsearch cluster hasn’t formed, you need to query each node individually, like this:

    curl 192.168.110.111:9200/_cat/nodes?v&h=id,ip,name&full_id=true
curl 192.168.110.112:9200/_cat/nodes?v&h=id,ip,name&full_id=true

    The Solution

    Elasticsearch requires each node to have a unique node ID. To fix this issue, you need to delete the index data on each node. If Elasticsearch was installed using the RPM package, the index data is usually stored in /var/lib/elasticsearch by default. After deleting the data, restart Elasticsearch, and it will generate a new, unique node ID for each node.

    Reference

    For further details, check the full article here: https://www.656463.com/wenda/jdbhjrjqNotMasterExceptionqgddxc_359.

    发布于

    Fix for “An SSH Installation Couldn’t Be Found” Error When Connecting to a Remote Server in VS Code

    Operating System: Windows 10

    When using the Remote-SSH extension in VS Code for remote development, you might encounter the error message “An SSH installation couldn’t be found” during the first connection attempt to a remote server. This error indicates that the VS Code Remote-SSH extension cannot find ssh.exe in your Windows system.

    By default, VS Code looks for the ssh command in the system’s PATH environment variable. If it’s not found, this error occurs.

    One solution is to install the Git package on your Windows system, which includes ssh.exe. Then, you can specify the exact path to ssh.exe in the settings of the VS Code Remote-SSH extension by configuring the remote.SSH.path option. Here’s how:

    1. Install the Git package, which includes ssh.exe.
    2. In VS Code, press F1 -> type Remote-SSH: Settings and hit Enter. This will open the Remote-SSH configuration file.
    3. Locate the remote.SSH.path option and set its value to the absolute path of ssh.exe on your Windows system. For example:
    C:\Programs\Git\usr\bin\ssh.exe

    Alternatively, you can install the OpenSSH package, which also includes ssh.exe, and use that instead of the Git-provided version.

    发布于

    Windows 10 or Windows 11 Only Shows One Hard Drive After Reinstallation? Here’s the Fix

    If you have two hard drives in your system but only see one in “This PC” after reinstalling Windows 10 or 11, follow these steps to resolve the issue:

    1. Right-click on This PC and select Manage.
    2. Go to Device Manager under System Tools and check Disk drives. If both drives are listed, it means the second drive is recognized and there is no issue with the hardware.
    3. Now, open Storage > Disk Management.
    4. Right-click on the second hard drive and select Change Drive Letter and Paths. Assign a drive letter to the second drive.

    After doing this, the second drive should appear in This PC in File Explorer.

    发布于

    How to Restore Files Deleted by Windows Defender on Windows 10 and Windows 11?

    For Windows 10:
    1.Open Windows Security Center
    2.Go to Virus & threat protection
    3.Navigate to Threat history
    4.Check the Detected threats
    5.Select Restore

    For Windows 11:
    1.Open Windows Security Center
    2.Go to Virus & threat protection
    3.Navigate to Protection history
    4.Check the Quarantined threats
    5.Select Restore

    Important Note
    Restoring quarantined files requires administrative privileges on your Windows system.

    发布于

    Windows10和Windows11如何还原被Windows Defender删除的文件？

    对于Windows10：

    打开Windows安全中心->病毒和威胁防护->威胁历史记录->检查出的威胁->还原

    对于Windows11：

    打开Windows安全中心->病毒和威胁防护->保护历史记录->已隔离威胁->还原

    注意事项

    在还原被隔离的文件时，需要你有Windows系统的管理员权限。

    发布于

    How to Fix Screen Flickering Issue After Windows 11 Update

    Today, after updating my Windows 11 system and rebooting, I encountered a screen flickering problem.

    I checked both my Nvidia and Intel graphics drivers, and they were up to date. So where was the issue?

    I suspected that the problem arose because my system had been upgraded from Windows 10 to Windows 11. Some hidden settings or configurations from the older Intel graphics drivers on Windows 10 might have been incompatible with the newer drivers on Windows 11.

    To resolve the issue, I used Display Driver Uninstaller (DDU) to completely remove the Intel graphics driver. Afterward, I reinstalled the latest version of the Intel graphics driver, and the screen flickering problem was fixed!

    Note: When installing the latest Intel graphics driver, make sure to run the installer as an administrator.

    Download the latest Intel graphics driver here: https://www.intel.com/content/www/us/en/download/19344/intel-graphics-windows-dch-drivers.html

    Download the latest DDU here: https://www.wagnardsoft.com/display-driver-uninstaller-ddu-

    Reference
    https://bbs.pcbeta.com/viewthread-1944975-1-1.html