After kernel upgrade, ZFS couldn’t start, but some process create some file in the mount point. So after that ZFS can’t start the process ever again. Here’s how to fix.
1. disable service zfs.target and restart.
user@ubuntu:~$ sudo systemctl disable zfs.target
2. after reboot delete or move data in mount point to another location.
1. Download and update using dpkg -i <splunk package>.
user@Lnx:~$ sudo dpkg -i splunk-7.3.2-c60db69f8e32-linux-2.6-amd64.deb
[sudo] password for <user>:
(Reading database ... 235721 files and directories currently installed.)
Preparing to unpack splunk-7.3.2-c60db69f8e32-linux-2.6-amd64.deb ...
This looks like an upgrade of an existing Splunk Server. Attempting to stop the installed Splunk Server...
Stopping splunkd...
Shutting down. Please wait, as this may take a few minutes.
..
Stopping splunk helpers...
Done.
Unpacking splunk (7.3.2) over (7.3.1) ...
Setting up splunk (7.3.2) ...
complete
user@Lnx:~$
2. Update and start service.
user@Lnx:~$ cd /opt/splunk/bin/
user@Lnx:/opt/splunk/bin$ sudo ./splunk enable boot-start
Do you agree with this license? [y/n]: y
Perform migration and upgrade without previewing configuration changes? [y/n] y
Here is how to add harddisk into proxmox storage pool.
1. After we connect new hard disk to our host. Verify attached harddisk in proxmox.
2. Format each harddisk. We will add sdb – sdf to our new storage pool.
root@proxmox:/# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 512M 0 part
└─sda3 8:3 0 238G 0 part
├─pve-swap 253:0 0 8G 0 lvm [SWAP]
├─pve-root 253:1 0 59.3G 0 lvm /
├─pve-data_tmeta 253:2 0 1.6G 0 lvm
│ └─pve-data 253:4 0 151.6G 0 lvm
└─pve-data_tdata 253:3 0 151.6G 0 lvm
└─pve-data 253:4 0 151.6G 0 lvm
sdb 8:16 0 1.8T 0 disk
sdc 8:32 0 1.8T 0 disk
sdd 8:48 0 1.8T 0 disk
sde 8:64 0 1.8T 0 disk
sdf 8:80 0 1.8T 0 disk
root@proxmox:/#
Format each disk from sdb – sdf
root@proxmox:/# /sbin/fdisk /dev/sdb
Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): g
Created a new GPT disklabel (GUID: CF141939-59BA-2C40-AC12-75A379E67B22).
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
root@proxmox:/#
This problem occurred because we are free user without proxmox enterprise subscription and this prevent us from update or install new package. Here’s how to fix it.
1. Comment out proxmox enterprise source.
root@proxmox:/# vim /etc/apt/sources.list.d/pve-enterprise.list
2. Add new proxmox source. Delete old one and put in new source.
root@proxmox:/# vim /etc/apt/sources.list
deb http://ftp.debian.org/debian buster main contrib
deb http://ftp.debian.org/debian buster-updates main contrib
# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve buster pve-no-subscription
# security updates
deb http://security.debian.org buster/updates main contrib
