ZFS Encrypted ZFS error

S

simon

Hi guys,
This is my first post and I'll do my best to not only make sense but provide as much information as I can.
I have a virtual machine that runs FreeBSD on VMware (it might be or might not be important)
I resized the disk today right after I'd deleted the backup since I didn't have much space left on the backup disk to retain two backups - that was the second and biggest mistake I made.
The first was not exporting the pool right after I made the changes and before I rebooted it.
The error I'm getting reads:

6705


I have tried using gpart to create/recreate the boot partition and reinstall bootcode but the same message keeps coming up.
I have a feeling it is all about giving it the right parameters and it'll be back - what those are and how to to go about it are why I'm asking for your help.
This is the output from gpart show/list using a live CD:

6707

6708

6709


1563218592423.png
1563218666451.png
1563218773574.png
 

Attachments

  • 1563218573199.png
    1563218573199.png
    101.6 KB · Views: 136
The disk was geli encrypted so I'm almost certain it'll be necessary to use geli at some point in this recovery.
Your assistance/pointers will be most welcome.
PS: it is my disk and I have the password/passphrase - I just made a mistake while expanding the available storage.
 
The tricky part will be to find out the exact same block where the original freebsd-zfs partition started from. It doesn't matter where it ends but it needs to begin at the exact same spot. Then you can try geli(8) first: geli attach /dev/da0p3. If that works the partition itself should be accessible. If you can't unlock it then you're likely not in the right spot.
 
SirDice said:
The tricky part will be to find out the exact same block where the original freebsd-zfs partition started from. It doesn't matter where it ends but it needs to begin at the exact same spot. Then you can try geli(8) first: geli attach /dev/da0p3. If that works the partition itself should be accessible. If you can't unlock it then you're likely not in the right spot.
Click to expand...

let me give that a go and see what happens.
 
Couldn't it be somehow inferred where it begun from the error that pops up at boot time?
The one that says:

6712
 
Assuming the freebsd-swap was indeed before the encrypted freebsd-zfs partition you could assume the swap was empty (containing all zeros) at least near the end, whereas the encrypted partition would contain all data (looks like random numbers). But I'm not aware of a tool that would let you browse the disk sector by sector. Painful way to scan in any case.
 
SirDice said:
Assuming the freebsd-swap was indeed before the encrypted freebsd-zfs partition you could assume the swap was empty (containing all zeros) at least near the end, whereas the encrypted partition would contain all data (looks like random numbers). But I'm not aware of a tool that would let you browse the disk sector by sector. Painful way to scan in any case.
Click to expand...
It was.
I remember a time while using Linux (before I was introduced to the wonders of BSD) I could have parted start a partition at some sector (or give it a range of sectors to work with).
Does gpart have the same thing?
Do you know of a command that I could run to do that on FreeBSD?
I see this (encircled in red) on the gpart list command:

6716



And I can somehow just "feel", that gut feeling, that it is related to this error that I get when I boot it up:

6717


I think if I could get the command to somehow match those two we just might be good to go!

What do you guys SirDice and vermaden and other more knowledgeable chaps think?
 
You must log in or register to reply here.
Back
Top