-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot create a zpool. Somethig wrong with a full path to disks #423
Comments
I've tried to hide all the special paths to make things easier, so does it say the same thing if you say |
Wow! It worked out! A lot of thanks! I would appreciate if you prompt what should be appropriate extended settings to create the pool. |
zpool destroy data_pool goes to the blue screen. All actions were taken under the Windows Test Mode. Does it matter? |
destroy BSOD? Ok, I will look into it. As for create, you probably was casesensitivity=insensitive for Windows. |
I would prefer to keep ZFS defaults in most cases, beside some important settings or those that can only be set at creation time like casesensitivity (set to Windows alike insensitive), normalisation (FormD) or ashift (set all vdevs in a pool to same ex 12) or utf8only (yes) Set other values per filesystem as needed. If you preset on pool-level, it is the default when creating ZFS filesystems but most properties can be modified later. Important for Windows btw
see https://openzfs.github.io/openzfs-docs/man/master/8/zpool-create.8.html |
Import you use either the GUID "8353579647598997825" or the name "usb", unless you are renaming? Can't say I have ever tried the import deleted pool, but should you use -D then as well? |
ok, works! zpool import -fD destroyed_GUID poolname btw |
needed when you destroy the pool, otherwise not. |
I'am gonna use an unallocated partition of SDD for L2ARC cashing. One more question: how to import zpool after windows rebooting automatically? |
ZFS needs independent blockdevices. What you can do for example: btw |
Are we saying |
After many tries I have create a zpool DATA and a dataset BEFREE. This config has been used: L2ARC (SSD 250 GB): Created a dataset: The task planner imports the zpool at the start of system. It worked out for the beginning.
zpool list, zpool import -a do reveal nothing. The second try to reestablish a zpool. The same result. May be something wrong with my zpool config? |
I would start with defaults to compare
list all importable nondestroyed pools
list all importable destroyed pools
|
I still keep the initial config. The pool stays imported. It seems working, but copying of 1,4Tb stored on HDD files causes file managers to freeze. the system failed to transfer data from storage to pool. File managers (Total Commander, WinMerge) do not respond, are not killed by the task manager, only a hard reset copes. got out of the situation by synchronizing the storage and pool using ubuntu-live. I wander how reasonable is it to use zfs on Window at this stage? I adore zfs, use it on my private servers and even laptops with linux. It looked as a good idea to try it on my Windows workstation upd: copying to pool hangs ubuntu dead as well |
Your last comment makes me think I do not need to stress about it right away. But yes, obviously Windows version might not be production ready today, but we are working hard toward that goal, and each bug you guys report gets us closer. |
There is possible nothing wrong with zfs. I have discovered that the glitch happened to the saved Users folder from the original Windows system. Something goes wrong with user privileges or something else. Users, $recycle bin are under suspicion. Now the system is stable, so I will take my risks using zfs on Windows. Thank you guys again for making this world better! |
If a copy hangs on Windows, this can be a configuration problem but if the pool hangs on Ubuntu as well after a move, this looks more like a hardware problem, related to RAM, cabling, temp or disks especially when it happens after some time. Also compatibility problems can be the reason like we had with Crystal Diskmark or the Aomei backup driver. To find and fix it is important that many are testing ZFS on different hard or software environments and report remaining problems. |
Is there a way to use GUID of drive instead of physicaldriveX creating a zpool in Windows? |
I have discovered, that those hangs occur during coping 'system's files' from any of Users, System files or Recycle Bin. Coudld be something wrong with file's attributes. After excluding these folders from "list to copy", all 1,5 Tb was placed on zfs pool at last. Unfortunately after several computer's reboots the pool disappeared at all for no obvious reason. Nor windows, neither Ubuntu zfs didn't discovered that pool at all. Now I have change my platform to AMD Ryzen 7 8700F + ASUS TUF GAMING B650M-E + 3 HDDs + system SSD. Will see how zfs works on it. I am going to keep my old Core i5 11600 as a platform for testing. |
System information
Windows 11 Pro | 24H2 build 26100.2605
motherboard | gigabyte b550m ds3h v2
processor | Core i5 11600
HDD | SATA III WD Red Plus WD40EFPX, 4T
HDD | SATA III Seagate Ironwolf ST4000VN006, 4T
HDD | SATA III Seagate Ironwolf ST4000VN006, 4T
Distribution Name |
Distribution Version |
Kernel Version |
Architecture | AMD64
OpenZFS Version | zfswin-2.2.6rc11
zfs | zfs-kmod-zfswin-2.2.6rc11
Describe the problem you're observing
can't create a zpool
zpool create data_pool \.\PHYSICALDRIVE0
working on dev '#1048576#4000776716288#\.\PHYSICALDRIVE0'
setting path here '/dev/physicaldrive0'
setting physpath here '#1048576#4000776716288#\.\PHYSICALDRIVE0'
cannot create 'data_pool': invalid argument for this pool operation
can't create a zpool raidz
create data_pool raidz \.\PHYSICALDRIVE0 \.\PHYSICALDRIVE1 \.\PHYSICALDRIVE2
working on dev '#1048576#4000776716288#\.\PHYSICALDRIVE0'
setting path here '/dev/physicaldrive0'
setting physpath here '#1048576#4000776716288#\.\PHYSICALDRIVE0'
working on dev '#1048576#4000776716288#\.\PHYSICALDRIVE1'
setting path here '/dev/physicaldrive1'
setting physpath here '#1048576#4000776716288#\.\PHYSICALDRIVE1'
working on dev '#1048576#4000776716288#\.\PHYSICALDRIVE2'
setting path here '/dev/physicaldrive2'
setting physpath here '#1048576#4000776716288#\.\PHYSICALDRIVE2'
cannot create 'data_pool': invalid argument for this pool operation
Describe how to reproduce the problem
happens every time during zpool creation
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: