// "[o.o]"

After a long shower, im thinking again. Was not far away from turning all FreeBSD machines to Gentoo Linux machines, to avoid these stupid zfs errors i have gotten in my virtual machines. All of a sudden it sort of freezes and spews litterarly thousands errors like:
vtbd0: hard error cmd=write

Even though it would have taken a long long time, and would be a headache deluxe.

With linux you could just mount a disc image, copy shit out of it then start over.
no no, zfs (the filesystem that freebsd defaults) that is such a good thing, everyone keeps saying. (feels abit like a sect)
Not that easy.

First you need to do something like:
$ mdconfig -a -t vnode -f disk0 -u 1

Then it will create /dev/md1p1, /dev/md1p2, /dev/md1p3 files (boot, swap, root)

After that you Should be able to:
$ zpool import

For it to show something like:
....
zroot
md1p3

now you should be able to import that to a new zfs pool.
$ zfs mount zroot # this results in something like saying zroot already exist.
Ok ok you think, just use a new name
$ zfs mount zroot zroot2 # mount as zroot2, no fuck that, you get some other error then that it is in use somehow...
...
What the actual F?

Will my NAS shit iself any day now, beoynd repair?!

ext3 and 4(linux file systems) i never ran into an issue like this for decades...

will have to look into ufs and if openbsd has a filesystem with less issues... (summer vacation saved? :'( )

aside, neighbours not showing respect, don't be a fuckin douch like that.