zfs-windows-2.2.6-rc6 "zpool create" saved zfs partitions on other disks

[leonik3]

I installed "zfs-windows-2.2.6-rc6" version. Unfortunately it destroyed my partitions on two other drives.

I launched:
zpool create -o autoexpand=on -o autotrim=on -O dedup=on -O casesensitivity=insensitive -O compression=on -O atime=off -o ashift=12 zzz raidz PHYSICALDRIVE4 PHYSICALDRIVE9 PHYSICALDRIVE10

Windows got a blue screen.

Windows didn't start anymore.

On another computer I saw that zfs partitions were saved on two completely different disks. The first was the Windows system disk on which I was running the command. The second was a disk with some Ubuntu. I have other disks, but they are as connected dynamic disks in Windows - they were not destroyed.

I recovered the Windows partition and Windows system using the following methods:
a) Testdisk-7.3-WIP and "testdisk_win.exe" - all partitions was recovered
b) Windows installation disk and repair mode in cmd and chkdsk /f
c) Windows installation disk and repair mode in cmd and:
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
d) old version of https://sourceforge.net/projects/boot-repair-cd/
e) Once more Windows installation disk and repair mode in cmd and:
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

[lundman]

Woah that is serious. The output of the command is probably lost, but it is hard to picture what goes wrong since it opens PHYSICALDRIVE10 directly (as opposed to mapping it or something like that).

I'll attach 10 disks to my VM and see if I can replicate

[lundman]

OK yeah, so whatever you put in, like PHYSICALDRIVE10 - it opens that literally, and passes it around.

$ wmic diskdrive list brief
Caption                                    DeviceID             Model                                      Partitions  Size
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE1   VMware, VMware Virtual S SCSI Disk Device  0           10733990400
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE0   VMware, VMware Virtual S SCSI Disk Device  3           134211893760
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE2   VMware, VMware Virtual S SCSI Disk Device  0           1069286400
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE3   VMware, VMware Virtual S SCSI Disk Device  0           1069286400
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE4   VMware, VMware Virtual S SCSI Disk Device  0           1069286400
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE5   VMware, VMware Virtual S SCSI Disk Device  0           1069286400
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE6   VMware, VMware Virtual S SCSI Disk Device  0           1069286400
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE7   VMware, VMware Virtual S SCSI Disk Device  0           1069286400
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE8   VMware, VMware Virtual S SCSI Disk Device  0           1069286400
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE9   VMware, VMware Virtual S SCSI Disk Device  0           1069286400
VMware, VMware Virtual S SCSI Disk Device  \\.\PHYSICALDRIVE10  VMware, VMware Virtual S SCSI Disk Device  0           1069286400

$ zpool create -o autoexpand=on -o autotrim=on -O dedup=on -O casesensitivity=insensitive -O compression=on -O atime=off -o ashift=12 zzz raidz PHYSICALDRIVE4 PHYSICALDRIVE9 PHYSICALDRIVE10
working on dev '#1048576#1063256064#\\?\PHYSICALDRIVE4'
setting path here '/dev/physicaldrive4'
setting physpath here '#1048576#1063256064#\\?\PHYSICALDRIVE4'
working on dev '#1048576#1063256064#\\?\PHYSICALDRIVE9'
setting path here '/dev/physicaldrive9'
setting physpath here '#1048576#1063256064#\\?\PHYSICALDRIVE9'
working on dev '#1048576#1063256064#\\?\PHYSICALDRIVE10'
setting path here '/dev/physicaldrive10'
setting physpath here '#1048576#1063256064#\\?\PHYSICALDRIVE10'

Expanded path to '\\?\PHYSICALDRIVE4'
Expanded path to '\\?\PHYSICALDRIVE9'
Expanded path to '\\?\PHYSICALDRIVE10'


# ls -l '/e/Virtual Machines/disk*.vmdk'
-rw-r--r-- 1 lundm 197609      196608 Oct  5 12:43 '/e/Virtual Machines/disk2-000001.vmdk'
-rw-r--r-- 1 lundm 197609      196608 Oct  5 12:43 '/e/Virtual Machines/disk3-000001.vmdk'
-rw-r--r-- 1 lundm 197609     2228224 Oct  5 13:03 '/e/Virtual Machines/disk4-000001.vmdk'
-rw-r--r-- 1 lundm 197609      196608 Oct  5 12:43 '/e/Virtual Machines/disk5-000001.vmdk'
-rw-r--r-- 1 lundm 197609      196608 Oct  5 12:43 '/e/Virtual Machines/disk6-000001.vmdk'
-rw-r--r-- 1 lundm 197609      196608 Oct  5 12:43 '/e/Virtual Machines/disk7-000001.vmdk'
-rw-r--r-- 1 lundm 197609      196608 Oct  5 12:43 '/e/Virtual Machines/disk8-000001.vmdk'
-rw-r--r-- 1 lundm 197609     2228224 Oct  5 13:03 '/e/Virtual Machines/disk9-000001.vmdk'
-rw-r--r-- 1 lundm 197609     2097152 Oct  5 13:03 '/e/Virtual Machines/disk10-000001.vmdk'

(I assume writes to disk10 is smaller due to being parity)

Can you confirm that wmic diskdrive list brief matches the disks you are expecting? Windows likes to re-order disks after all.

[leonik3]

Before issuing the command, I restarted Windows so that the disk numbers would be permanently set and would not change, and I checked the numbering of each disk in two programs.

I remembered that I had two blue screens. The first time, Windows did not crash (no zfs partition was written to it). I repeated the procedure then and it crashed.

[leonik3]

[leonik3]

Just to clarify. I connected 3 additional disks to this system and they were numbered: 4, 9 and 10

[lundman]

They aren't in your wmic diskdrive list brief output at all though?

[leonik3]

No, they are not on this list.
After adding these three additional disks to this system, they (these added disks) then got numbers 4, 9, 10. The above images do not show this state with these three added disks.

[leonik3]

My problems must have been due to a bad installation, from the fact that I had some old version openzfsonwindows installed a long time ago. I installed a new version (zfswin-2.2.6rc9) now and had windows restarts and blue screens. After multiple attempts to install and uninstall, after disabling several applications, openzfsonwindows installed OK, without restarting Windows, then I uninstalled it and reinstalled it without error. I think I have a correct, clean installation now.

However, I have a new problem. It does not depend on whether the disks have a GPT partition or were wiped to an uninitialized state using diskpart (clean):

"cannot label 'PHYSICALDRIVE0': try using parted(8) and then provide a specific slice: -2"

[lundman]

OK so you used diskpart clean, then could not label disk and got that error? Will check

[leonik3]

Yes, after diskpart clean was these errors too.

[leonik3]

Now I installed the latest version of Ubuntu in VirtualBox, then compiled and installed the latest version of ZFS (zfs-2.3.0-rc2), then connected these 3 disks to VirtualBox and Ubuntu like this:

VBoxManage.exe createmedium -filename c:\VM\VB_HD_LINKS\6T.1.vmdk --variant RawDisk --format=VMDK --property RawDrive=\.\PhysicalDrive1
VBoxManage.exe createmedium -filename c:\VM\VB_HD_LINKS\6T.2.vmdk --variant RawDisk --format=VMDK --property RawDrive=\.\PhysicalDrive2
VBoxManage.exe createmedium -filename c:\VM\VB_HD_LINKS\6T.3.vmdk --variant RawDisk --format=VMDK --property RawDrive=\.\PhysicalDrive3

then in Ubuntu I created the pool:
zpool create -o autoexpand=on -o autotrim=on -O dedup=on -O casesensitivity=insensitive -O compression=on -O atime=off -o ashift=12 wz /dev/sdb /dev/sdc /dev/sdd

and then on Windows I have imported the pool and upgrade it:

[leonik3]

Pool works very fine, but Task Manager don't show load of disks from the pool:

[lundman]

Great - I will still look at the diskpart issue.

As for the disk IO, no idea how that works, yet. Feel free to research it, but I'll eventually get to it. If I am lucky, chatgpt already knows the answer.

[lundman]

Hmm no amount of diskpart clean makes it break for me, I guess because the disks were once used. But even dd had no issues

$ dd if=/dev/zero of='/dev/sdb' bs=512 count=2000
2000+0 records in
2000+0 records out
1024000 bytes (1.0 MB, 1000 KiB) copied, 0.185304 s, 5.5 MB/s

WDKRemoteUser@WinDev2407Eval MINGW64 /c/src/openzfs (development)
$ out/build/x64-Debug/cmd/zpool/zpool.exe create BOOM PHYSICALDRIVE1
invalid vdev specification
use '-f' to override the following errors:
\\?\PHYSICALDRIVE1 contains a corrupt primary EFI label.
Expanded path to '\\?\PHYSICALDRIVE1'

WDKRemoteUser@WinDev2407Eval MINGW64 /c/src/openzfs (development)
$ out/build/x64-Debug/cmd/zpool/zpool.exe create -f BOOM PHYSICALDRIVE1
working on dev '#1048576#10726932480#\\?\PHYSICALDRIVE1'
setting path here '/dev/physicaldrive1'
setting physpath here '#1048576#10726932480#\\?\PHYSICALDRIVE1'
sending mountpoint: '\??\?:'
Expanded path to '\\?\PHYSICALDRIVE1'