Skip to content
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

import on boot failed (internal error, value too large) 13.4 #121

Open
Kerrnel opened this issue Jun 27, 2023 · 1 comment
Open

import on boot failed (internal error, value too large) 13.4 #121

Kerrnel opened this issue Jun 27, 2023 · 1 comment

Comments

@Kerrnel
Copy link

Kerrnel commented Jun 27, 2023

System information

Type Version/Name
Distribution Name Ventura
Distribution Version 13.4
Linux Kernel Darwin Kernel Version 22.5.0
Architecture x86_64
ZFS Version zfs-macOS-2.1.6-1
SPL Version zfs-kmod-2.1.6-1

Describe the problem you're observing

zpool not present after reboot

Describe how to reproduce the problem

created zpool with -compatible openzfs-2.1-linux
set up 6 file systems on it with mountpoints in /Users/...
rebooted - not present
zpool import works in terminal to get it back with no errors

$ zpool status
 pool: JAW
state: ONLINE
config:

       NAME                                STATE     READ WRITE CKSUM
       JAW                                 ONLINE       0     0     0
         PCI0@0-SATA@17-PRT0@0-PMP@0-@0:0  ONLINE       0     0     0

errors: No known data errors

What does not work is what the LaunchDaemon does:

$ sudo zpool import -a -d /var/run/disk/by-id
internal error: cannot import 'JAW': Value too large to be stored in data type
Abort trap: 6

$ ls /var/run/disk/by-id
media-01939D5C-101E-4D53-A585-D1F7AF56753B  media-8E92C158-4750-4D0E-A505-B8EDB2459818   volume-239304AA-1025-4481-B72B-4B6B8A843344
media-173B9F63-C24E-4BE7-B1B2-6D4FCA415412  media-A117C0A1-3AE4-4CBF-863D-9DDBF8A8E6FC   volume-37B5C1B7-3A21-49CC-836A-50927E695C5C
media-1A3B019D-2A8E-43BE-8FE3-F0CCAEBFD48A  media-B9808952-4E9B-44D2-8409-44E10A871D5F   volume-46DBF7D8-ABA4-4665-B351-5F786B43CBD9
media-239304AA-1025-4481-B72B-4B6B8A843344  media-BAE09DC1-2BC7-4648-902E-08DD96111B51   volume-66B2847D-198F-4482-99EE-33F7D3A49FCF
media-26395A9D-3563-4440-A0D0-EB32D9EDA26A  media-DDECA0C2-7681-4259-A738-E7625C23F14F   volume-7C6435CA-25ED-4905-A4E3-8192668344AE
media-37B5C1B7-3A21-49CC-836A-50927E695C5C  media-E999A124-A08B-4981-8A68-E3078AF639D3   volume-8E92C158-4750-4D0E-A505-B8EDB2459818
media-432D5DFD-A667-4637-AA86-EAF3A5CD0DB6  media-EDAC254A-EFB4-4CFF-AD7B-5922241DBA2A   volume-A117C0A1-3AE4-4CBF-863D-9DDBF8A8E6FC
media-46DBF7D8-ABA4-4665-B351-5F786B43CBD9  media-F3787DE4-2693-E740-BA65-D14684C5141B   volume-B9808952-4E9B-44D2-8409-44E10A871D5F
media-52AFC783-7340-478C-BD1D-A5842BF88F5C  media-FAB69040-B53C-4DC7-9F9D-B72A1CE598B4   volume-BAE09DC1-2BC7-4648-902E-08DD96111B51
media-66B2847D-198F-4482-99EE-33F7D3A49FCF  volume-01939D5C-101E-4D53-A585-D1F7AF56753B  volume-E999A124-A08B-4981-8A68-E3078AF639D3
media-6DC3AAFA-A249-4223-BBFB-F36967B7C802  volume-0E239BC6-F960-3107-89CF-1C97F78BB46B
media-7A75994E-2295-4CF2-A829-54FB0A043EAA  volume-1A3B019D-2A8E-43BE-8FE3-F0CCAEBFD48A

Include any warning/errors/backtraces from the system logs

 $ tail -n 20 /var/log/org.openzfsonosx.zpool-import-all.log 
Tue Jun 27 14:11:30 EDT 2023
Status: 0
Touching the file /var/run/org.openzfsonosx.zpool-import-all.didRun
Tue Jun 27 14:11:30 EDT 2023
-zpool-import-all.sh
internal error: cannot import 'JAW': Value too large to be stored in data type
+zpool-import-all.sh
Tue Jun 27 14:52:40 EDT 2023
Waiting up to 60 seconds for the InvariantDisks idle file /var/run/disk/invariant.idle to exist
Found /var/run/disk/invariant.idle after 0 iterations of sleeping 0.1 seconds
Tue Jun 27 14:52:50 EDT 2023
Tue Jun 27 14:52:50 EDT 2023
-zpool-import-all.sh
Loading and starting org.openzfsonosx.zpool-import
Tue Jun 27 14:53:00 EDT 2023
Status: 0
Touching the file /var/run/org.openzfsonosx.zpool-import-all.didRun
Tue Jun 27 14:53:00 EDT 2023
-zpool-import-all.sh
internal error: cannot import 'JAW': Value too large to be stored in data type
@Kerrnel
Copy link
Author

Kerrnel commented Jun 27, 2023

I think... the prior drive was an HD - it has a log & cache partition on nvme; perhaps when scanning them via /var/run it craps out. I will try to flush them with /dev/zero and/or re-type the partitions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant