Search results

Worked like a charm, thank you. So far anyone else who stumbles on this thread, step 4 should be something like this. 4. zpool attach rpool sda3 nvme1n1p3

Currently my `rpool` consists of 1x SATA SSD, and 2x NVMe SSDs. I'd like to remove the SATA disk but neither of the NVMe disks are bootable, either when changing settings in the BIOS of my ASRock X470D4U, or when manually selecting the NVMe disks from the F11 boot menu. Neither of the NVMe...

I forgot to mention or make explicit my reasoning. The idea is that if anything goes wrong with the upgrade, then I can always swap the BOOT pool out for the disk that was removed from the BOOT pool's vdev, in 3 and 6.

Hi all, I'm just prepping to update my Proxmox server to the latest version, mainly in response to the bug found in ZFS. My backups are a little bit old and for reasons that I won't go into, my options are either to not update Proxmox until I can make a backup (which may be as long as in the...

It's the root disk. FYI, the old subvols that I want to restore are on "nvme-pool", and my new container subvols are in "rpool/data". I have just tried the following procedure- I used syncoid to send | recv subvol-101-disk-0 from "nvme-pool" to "rpool/data". I renamed the...

I am aware of that but thank you for mentioning it. If the "sent" was within a string I had formatted as inline code, then it was a (now fixed) typo. I think at this point, I need to clarify that there are two main issues, so to speak. First of all, I may or may not have destroyed my old...

That's weird. So you can't see https://forum.proxmox.com/threads/ive-really-screwed-up-bad-please-help.91408/#post-399582 ? I can see it whilst I'm logged in but not when I open a new private browser window. If anyone could enlighten me as to why it was deleted, I'd be grateful. Anyway...

Thank you for your response. Before you posted, I had started editing my previous comment with info regarding use of the -R flag. Please see the edit at the bottom of my previous comment for more details.

I just don't understand what's going on... I've booted my FreeNAS / TrueNAS install and imported the nvme-pool. I've then taken a recursive snapshot of the nvme-pool via the TrueNAS GUI, and then send | recv'd via the shell to a newly create pool (pool980). When I navigate pool980, the dataset...

There's good new and bad news.... The good news is, is that I've got a second NVMe disk and I'm ready to sort out a mirrored boot disk. The bad news is that in the process of send | recv a snapshot of nvme-pool to my rpool disk, I think I've found the reasons why my data disappeared on my...

I would love to be able to snapshot Containers that have bind mounts without having the edit the .conf each time!

For what it's worth, I've attached the old install disk to my PC and imported the pool as altrpool. I then ran sudo zfs list -r altrpool. NAME USED AVAIL REFER MOUNTPOINT altrpool 30.7G 198G 104K /altrpool altrpool/ROOT...

That's what I've done, both with an Ubuntu live CD and from a fresh install of Proxmox (on a different disk) but the snapshots are all small (see the second post of this thread) and the boot behaviour remains the same.

1. I hear ya... that's why the really important stuff on TANK is almost entirely backed up to another ZFS pool on a TrueNAS server, which has been off for a couple of weeks (so I should have 99.9% of the data elsewhere). But this is definitely a lesson learned, I had been planning to replicate...

When I rollback, the boot behaviour is the same as it was before I rolled back anything. The boot stalls and I get run-init: can't execute '/sbin/init': No such file or directory which causes a kernel panic. I think I'm just gonna fresh install. It'll get me back up and running quicker.

After doing something very stupid that looks like it may have destroyed my install, it looks like I might have to do a fresh install and create my containers from scratch. I still have the ZFS dataset subvols for the containers from my old, borked Proxmox install (as they were stored on a...

One last comment before I turn in. I'm at the point now where I'm starting to feel that perhaps I should take this as a blessing in disguise. (fingers crossed) I don't think I've lost anything really important... aside from the time I put into setting up my orignal install (smartd, crontab...

I'm starting to think that I've completely borked my install... I had a spare SSD laying around, so I did a fresh install of Proxmox onto "Fresh-SSD", and then tried importing my pools. Thankfully though, it appears my data on `TANK` and `nvme-pool` is intact. So I still have the important...

I have three ZFS pools on my server "TANK" - a 6x10TB RAIDz2 for my data "nvme-pool" - a single 500GB NVMe disk used for fast storage for LXC and VMs. Then there's the disk which Proxmox is installed to but I'm not 100% sure whether I should be calling it rpool or bpool, or something else, so...

Thanks for the reply, Wolfgang (and for making me realise I never posted the reply you in a previous thread!... I just hope I saved the draft somewhere).