Hi everyone.  (newbie alert)
I have a PBS 3.3.2 server on bare metal. There are two datastores used for backup of a PVE server.
I had a couple of drives and decided to stripe two 8TB drives when I started.
I wasn't able to create the stripe using the gui, so I did it via the command line with
	
		
This worked fine until I did an update of PBS in around November and the first backup failed as it couldn't "open chunk store".
After reading the forums, I found that the disks were OK just not showing up in the "zpool list" or "zpool status".
I followed directions from other posts and found the disks using
	
		
 and added it back using 
	
	
	
		
The datastore was available and has worked for a few months.
I thought I fixed the problem but when I ran the next update yesterday and rebooted, I have exactly the same problem. I used the same steps to add back the disk. The second datastore on the pbs was created using the GUI and doesn't have this problem. I suspect that in doing the manual datastore creation I missed something or made a mistake but I don't know where to start to figure it out.
Could you provide some suggestions on what I have to look for to fix this properly so each reboot I don't have to manually add back the datastore?
Thanks in advance.
				
			I have a PBS 3.3.2 server on bare metal. There are two datastores used for backup of a PVE server.
I had a couple of drives and decided to stripe two 8TB drives when I started.
I wasn't able to create the stripe using the gui, so I did it via the command line with
		Code:
	
	zpool create -f -o ashift=12 backup sdc sdd
	This worked fine until I did an update of PBS in around November and the first backup failed as it couldn't "open chunk store".
After reading the forums, I found that the disks were OK just not showing up in the "zpool list" or "zpool status".
I followed directions from other posts and found the disks using
		Code:
	
	ls -lah /dev/disk/by-id/
	
		Code:
	
	zpool import -a -d /dev/disk/by-id/actual_disk_ID
	The datastore was available and has worked for a few months.
I thought I fixed the problem but when I ran the next update yesterday and rebooted, I have exactly the same problem. I used the same steps to add back the disk. The second datastore on the pbs was created using the GUI and doesn't have this problem. I suspect that in doing the manual datastore creation I missed something or made a mistake but I don't know where to start to figure it out.
Could you provide some suggestions on what I have to look for to fix this properly so each reboot I don't have to manually add back the datastore?
Thanks in advance.
			
				Last edited: