The following system core files were found: zpool.core
Description
Problem/Justification
Impact
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
均誠 王 July 9, 2021 at 4:29 PM
Thanks for the update, I'll check and see if my ram is just going bad, since it has been the for years already. This might be the reason for me to go for hardware that supports ecc ram, thanks!
Alexander Motin July 9, 2021 at 2:10 PM
The zpool command crash is probably a consequence of your pool corruption. This is what I see in the core:
Core was generated by `zpool import -f Media_Vault'.
Program terminated with signal SIGABRT, Aborted.
#0 thr_kill () at thr_kill.S:3
3 thr_kill.S: No such file or directory.
(gdb) bt
#0 thr_kill () at thr_kill.S:3
#1 0x0000000800877394 in __raise (s=6) at /truenas-releng/freenas/_BE/os/lib/libc/gen/raise.c:52
#2 0x00000008007ed589 in abort () at /truenas-releng/freenas/_BE/os/lib/libc/stdlib/abort.c:67
#3 0x00000008002c3281 in zfs_verror (hdl=0x800b72000, error=2090, fmt=<optimized out>, ap=0x7fffffffbaf0) at libzfs_util.c:336
#4 zpool_standard_error_fmt (hdl=0x800b72000, error=<optimized out>, fmt=<optimized out>) at libzfs_util.c:738
#5 0x00000008002c2b65 in zpool_standard_error (hdl=0x1895a, error=6, msg=0x800878f5a <thr_self+10> "\017\202\264G")
at libzfs_util.c:610
#6 0x00000008002b0def in zpool_import_props (hdl=0x800b72000, config=0x80310c088, newname=0x0, props=<optimized out>, flags=2)
at libzfs_pool.c:2031
#7 0x0000000000224378 in do_import (config=0x80310c088, newname=0x0, mntopts=0x0, props=0x0, flags=2) at zpool_main.c:3044
#8 0x0000000000219c60 in zpool_do_import (argc=<optimized out>, argv=0x800b34098) at zpool_main.c:3638
#9 0x0000000000213116 in main (argc=<optimized out>, argv=0x7fffffffeb48) at zpool_main.c:10392What I see is a bit confusing, but it probably matches this quota from forum port:
freenas# zpool import -f Media_Vaultinternal error: cannot import 'Media_Vault': Integrity check failed
Abort trap (core dumped)In the debug provided I see your system crashed 5 times on April 20, and in each of the cases the cause was different. It makes me think that you have experienced some serious random memory corruption. Considering you are using desktop-class hardware with non-ECC RAM it can be a hardware issue. I'd recommend you to check cooling and everything you can, run good long memory test and then you'll have to recreate the pool. I don't see what we can do here unfortunately.
均誠 王 June 1, 2021 at 3:54 PM
Sure thing @iX-Tony, I have uploaded the debug into the private upload. Please feel free to ask for more information, and my pool was killed(suspected related to this issue), and I would like to quickly move on so I can have my nas back up.
Many thanks!
iX-Tony June 1, 2021 at 12:38 PM
Thank you for the report @均誠 王. Can you please provide a debug (navigate to System > Advanced and click SAVE DEBUG), the core files if possible, and upload the files to the Attachments: Private area in this ticket?
Private Attachments are only accessible to the developers.
Details
Details
Assignee
Reporter
Labels
Time remaining
Fix versions
Affects versions
Priority
LowKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Hi team, my TrueNAS system gave me this error recently:
```
The following system core files were found: zpool.core. Please create a ticket at https://jira.ixsystems.com/ and attach the relevant core files along with a system debug. Once the core files have been archived and attached to the ticket, they may be removed by running the following command in shell: 'rm /var/db/system/cores/*'.
2021-05-27 09:49:32 (America/Los_Angeles)
```
Therefore uploading this file for the team
I am suspecting this has something to do with my recently failure in my pool, attaching the post I posted on the forume for reference if you guys are interested.
https://www.truenas.com/community/threads/disconnecting-broken-drives-from-pool-not-able-to-restore.93477/