Case : 
In this case I am currently facing my usb is in read-only mode permanently.

this used command to have done :

sudo bash Ventoy2Disk.sh -i /dev/sdb

output :

**********************************************
      Ventoy: 1.1.10  x86_64
      longpanda admin@ventoy.net
      https://www.ventoy.net
**********************************************

Disk : /dev/sdb
Model: Generic Mass storage (scsi)
Size : 59 GiB
Style: MBR


Attention:
You will install Ventoy to /dev/sdb.
All the data on the disk /dev/sdb will be lost!!!

Continue? (y/n) y

All the data on the disk /dev/sdb will be lost!!!
Double-check. Continue? (y/n) y
dd: failed to open '/dev/sdb': Read-only file system
Write data to /dev/sdb failed, please check whether it's in use.

• run lsblk

• run dmesg to check log kernel

• run hdparm

• run dd to verify

First thing first, I encounter this issue when updating my arch linux pc and I did in my terminal to updating arch keyring and solve.

Solve

sudo pacman -Sy archlinux-keyring

How to enable tun module in arch linux? To verify you are able to hit these commands below.

lsmod | grep tun
ls -l /dev/net/tun

it will show you tun if show nothing, it means your module is disable. To check whether tun module is available in your system, hit this command.

modinfo tun

the output will be like this.

# modinfo tun
filename:       /lib/modules/6.12.65-1-lts/kernel/drivers/net/tun.ko.zst
alias:          devname:net/tun
alias:          char-major-10-200
license:        GPL
author:         (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
description:    Universal TUN/TAP device driver
srcversion:     4121824D1D36298ECBF61FA
depends:        
intree:         Y
name:           tun
retpoline:      Y
vermagic:       6.12.65-1-lts SMP preempt mod_unload 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        20:4C:6E:6F:12:6C:EF:6C:CC:0E:57:71:96:C4:15:17:72:69:F8:4C
sig_hashalgo:   sha512
signature:      30:65:02:30:7F:18:10:96:7B:32:23:D0:FB:D7:64:54:7C:19:CE:CE:
		DA:13:7E:3A:DE:E0:A0:F8:52:F0:CC:BA:48:C5:E4:26:91:FF:8A:A5:
		24:F8:84:AB:C1:48:9B:30:7A:67:E2:29:02:31:00:C2:75:C2:47:19:
		F5:BB:C7:66:E5:42:99:DA:FF:06:20:C3:66:54:44:F1:41:41:5D:B3:
		6E:B0:61:39:BC:49:A6:E6:4E:7D:84:31:D7:70:E2:67:51:41:BE:42:
		55:2E:28

if all of those step pop out an output meaning your system is ready to rock in!

Description​

Saat melakukan instalasi Ubuntu Server 25.10 menggunakan QEMU/KVM di host Arch Linux, Virtual Machine (VM) berhasil mendapatkan alamat IP melalui DHCP dari bridge virbr0, namun gagal mengakses internet (error Network Unreachable atau IGN pada tahap pemilihan mirror).

setelah trouble shouting ternyata kebijakan firewall secara default memblokir semua lalu lintas yang mencoba "menyeberang"/FORWARD antar interface. Karena VM berada di virbr0 dan ingin keluar melalui WiFi/Ethernet, paket datanya langsung dibuang (DROP) oleh rule tersebut.

this is full script to create virtbr0, I am using bash.

# pastikan modul tun sudah aktif
sudo modprobe tun
# akan otomatis membuat bridge 'virtbr0'
sudo virsh net-start default

#sudo virsh net-autostart default
ip a show virbr0

Di script ini pertama-tama akan mengaktifkan modul tun di system linux aku lalu membuat bridge virtbr0 atau virtual bridge.

sudo iptables --list

# sudo iptables --list 
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy DROP)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
DOCKER-USER  all  --  anywhere             anywhere            
DOCKER-FORWARD  all  --  anywhere             anywhere            

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain DOCKER (4 references)
target     prot opt source               destination         
DROP       all  --  anywhere             anywhere            
DROP       all  --  anywhere             anywhere            
DROP       all  --  anywhere             anywhere            
DROP       all  --  anywhere             anywhere            

Chain DOCKER-BRIDGE (1 references)
target     prot opt source               destination         
DOCKER     all  --  anywhere             anywhere            
DOCKER     all  --  anywhere             anywhere            
DOCKER     all  --  anywhere             anywhere            
DOCKER     all  --  anywhere             anywhere            

Chain DOCKER-CT (1 references)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED

Chain DOCKER-FORWARD (1 references)
target     prot opt source               destination         
DOCKER-CT  all  --  anywhere             anywhere            
DOCKER-INTERNAL  all  --  anywhere             anywhere            
DOCKER-BRIDGE  all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            

Chain DOCKER-INTERNAL (1 references)
target     prot opt source               destination         

Chain DOCKER-USER (1 references)
target     prot opt source               destination         

# Izinkan paket data lewat di bridge virtual
sudo iptables -I FORWARD -o virbr0 -j ACCEPT
sudo iptables -I FORWARD -i virbr0 -j ACCEPT

# cativate IP Forwarding 
sudo sysctl -w net.ipv4.ip_forward=1

Untuk cara alternatifnya yaitu di permanenkan.

yaitu dengan cara

Permanenkan IP Forwarding​

Buat file baru.

sudo nano /etc/sysctl.d/30-ipforward.conf

isi dengan net.ipv4.ip_forward=1 untuk ngeforward IP dari virtbr0.

Gunakan lsblk untuk melihat daftar device dan filesystem:

lsblk -f

NAME        FSTYPE FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1
├─sda2      ntfs         DATA     A61087D71087ACBD
└─sda3      btrfs                 25902326-073a-4842-9c65-ad8d62222771  254.1G    15% /
sdb
nvme0n1
├─nvme0n1p1 ntfs         Recovery 1ED80811D807E63D
├─nvme0n1p2 vfat   FAT32          5A08-EE40                              58.7M    39% /boot/efi
├─nvme0n1p3
└─nvme0n1p4 ntfs         OS       5A360D4B360D2A19

Format Disk​

In linux, ensure the package is available.

sudo pacman -S dosfstools

Example format to EXT32:

sudo mkfs.vfat -F 32 /dev/sdb1

Mount (pasang filesystem)​

Buat folder mountpoint:

sudo mkdir -p /mnt/usb

Mount:

sudo mount /dev/sdb1 /mnt/usb

Cek hasil:

ls /mnt/usb
df -h | grep sdb

Umount (lepas filesystem)​

sudo umount /dev/sdb1

# or

sudo umount -l /mnt/usb   # lazy umount
sudo umount -f /mnt/usb   # force umount (hati-hati)

sudo umount -l /mnt/usb   # lazy umount
sudo umount -f /mnt/usb   # force umount (hati-hati)

Advanced Mount Options​

Mount dengan opsi:

sudo mount -t vfat -o uid=1000,gid=1000,umask=022 /dev/sdb1 /mnt/usb

Opsi penting:

• ro → read-only
• rw → read-write
• noexec → cegah eksekusi file biner
• nosuid → abaikan SUID/SGID
• nodev → abaikan device file

Mount berdasarkan UUID / LABEL:

sudo mount UUID=5A08-EE40 /mnt/usb
sudo mount LABEL=DATA /mnt/usb

Bind mount (pasang folder ke folder lain):

sudo mount --bind /home/user/Downloads /mnt/usb

Mount ISO/IMG:

sudo mount -o loop archlinux.iso /mnt/iso

Hapus Filesystem (Wipe)​

Hilangkan signature filesystem:

sudo wipefs -a /dev/sdb

Overwrite awal disk (100MB pertama):

sudo dd if=/dev/zero of=/dev/sdb bs=1M count=100

Hapus partisi:

sudo fdisk /dev/sdb
# Tekan d untuk delete, w untuk simpan

yay -S sunshine wf-recorder slurp grim wl-clipboard

# enable service
systemctl --user start sunshine # if you need to start on boot just using `systemctl --user enable sunshine`

# If it doesn't start just hit
sunshine            # <= this is a command

You will see line bellow Afterward, coppy the link and paste to your browser.

If you encounter any issu just hit the documentation.

Install postgresql in your arch using

sudo pacman -S postgresql php-pgsql apache

# activate postgresql and apache systemd services
sudo systemctl enable {postgresql,httpd}
sudo systemctl start {postgresql,httpd}

# verify
sudo systemctl status {postgresql,httpd}

It will look like this

Create User & Database in postgresql​

Create User​

sudo -iu postgres

After login to posgresql database, then create user

# create new user
createuser --bypassrls -s -l -d laravel

Create Database​

createdb -O laravel laravel_db

Set .env in Laravel​

DB_CONNECTION=pgsql
DB_HOST=127.0.0.1
DB_PORT=5432                # port postgresql
DB_DATABASE=laravel_db      # database
DB_USERNAME=laravel         # user
DB_PASSWORD=

then php artisan migrate:fresh. Done!

sudo pacman -Rns pulseaudio

sudo pacman -S pipewire wireplumber pipewire-pulse pipewire-alsa

Enable it​

Run with no sudo because dbus run in tty.

systemctl --user enable --now pipewire pipewire-pulse wireplumber

Verify service​

systemctl --user status pipewire

Hi dawg, how are you?

recenly, I could not connect to the internet when I pluged in my LAN into my laptop. Btw, I use Arch Linux in this case.

I realized once I hit a command ip a | ip address show eth0.

this suspiicius this shown like this

afterward, I briefly verify whether my eth0 is detected then I command ethtool eth0. at 'Link detected: yes'. It's FINE so how the fuck is going on. FU

Check if NetworkManager is controlling and Fuckkkkk! yes. I found it disconnect "I SAID DAMN SURE". it solves using nmcli device status.

8

How I do tackel?​

sudo nmcli device set eth0 manage yes
sudo nmcli device connect eth0

and kaboom!

I have gotten an issue while attemting to build a Docker image with the following command:

docker build -t izfaha/express:v1 .

And I encountered this error:

Cannot connect to the Docker daemon at unix:///home/ray/.docker/desktop/docker.sock. Is the docker daemon running?

How do I tackle?​

Root cause is:

First, Docker CLI was configured to use Docker Desktop, even though I was running native Docker in linux.

Second, the configuration file at ~/.docker/config.json contain:

{
  "auths": {},
  "credsStore": "desktop",
  "currentContext": "desktop-linux"
}

This caused Docker to:

• Attempt to connect to a nonexistent socket: /home/ray/.docker/desktop/docker.sock

• Call missing credentials helper: docker-credential-desktop

Solution​

Ensure Docker Daemon is Running​

sudo systemctl start docker
sudo systemctl enable docker

Switch Context to the Default Linux One​

docker context use default
docker context ls               # to verify docker context set to default

Remove Faulty Docker Desktop Configuration​

rm -rf ~/.docker

Recently, I was trying build docker image but it become an issue. Pop in my terminal up a messege.

The main issue is I used wrong docker path in docker context. In my case, I remain using docker desktop path.

After I change it using docker context default, suddenly it works.

And I verify docker context ls

Utilizing this command scp username@ip-server:/path/ke/file.txt /lokasi/di/local.

scp user@192.168.1.12:/home/user/file.txt ~/Download

Upload from Local to Server​

Ini untuk upload file dari local ke server. scp ~/lokasi/file/di/local user@ip-server:/path/ke/lokasi.

scp ~/Documents/file.txt user@192.168.1.12:/home/user/Downloads

scp -P 2223 user@192.168.1.12:/home/user/Project/file.txt ~/Downloads

scp -r ~/Downloads/directory-main user@192.168.1.12:/home/user/Projects/

scp -i ~/.ssh/id_rsh/ssh-key.pem ~/Documents/file.txt user@192.168.1.12:/home/user/Projects

scp -C bigfile.zip user@192.168.1.20:/home/user/Documents

scp -r -P 2345 -i ~/.ssh/id_rsa ~/Projects user@192.168.6.123:/home/user/Downloads

First up, we have to look up into our interface we are using. To verify write down this command.

ip link

it will be different in other distro. In my case, it shown up using wlp2s0. Setting up the IP to static is piece of cake, Just bash it out.

nmcli connection modify "COE-WIFI" ipv4.addresses 192.168.77.235/24
nmcli connection modify "COE-WIFI" ipv4.gateway 192.168.77.254
nmcli connection modify "COE-WIFI" ipv4.dns "1.1.1.1 8.8.8.8 8.8.4.4"
nmcli connection modify "COE-WIFI" ipv4.method manual

nmcli connection up "Wired connection 1"

Then check your ip using ip a. And boom! you pull it off dawg!

Issues​

1. Can not connect internet when LAN is pluged in.

   • You need to remove your connection using this command.

   nmcli connection delete "Wired connection 1"
   

   Then verify, whether your connection to browse or google, and check your IP ip a. If you need to auto connect when pluging your LAN in, just use this command.

   nmcli connection modify "Wired connection 1" connection.autoconnect yes
   

   • Cara hapus IP dari eth0

   sudo ip addr del 192.168.77.151/24 dev eth0
   

When I remove a file inside '/blog', I get this error

ERROR in ./.docusaurus/registry.js 1:11337-11448

Module not found: Error: Can't resolve '@site/blog/2021-08-26-welcome/index.md?truncated=true' in '/home/ray/Documents/documentation/.docusaurus'

ERROR in ./.docusaurus/registry.js 1:11505-11581

Module not found: Error: Can't resolve '@site/blog/2021-08-26-welcome/index.md?truncated=true' in '/home/ray/Documents/documentation/.docusaurus'

ERROR in ./.docusaurus/registry.js 1:12427-12532

Module not found: Error: Can't resolve '@site/blog/2021-08-26-welcome/index.md' in '/home/ray/Documents/documentation/.docusaurus'

ERROR in ./.docusaurus/registry.js 1:12574-12635

Module not found: Error: Can't resolve '@site/blog/2021-08-26-welcome/index.md' in '/home/ray/Documents/documentation/.docusaurus'

and it is caused by '.docusaurus' file cache.

rm -rf .docusaurus build

npm run start