This is a new build, just trying to load it with data for the first time and keep having issues during copy or import.
Initially, I was trying to do a Disk Import via an attached USB SSD enclosure. It would get about 30% then crash. This happened about 4 times and I gave up. I assumed it was the USB enclosure, etc and after researching, most suggested just to copy over the network.
So then tried using Robocopy to copy from my old NAS to this new True NAS build. Again, it would copy for 3 - 5 minute, then crash.
From what I researched, I found the data/crash directory and extracted this from the textdump.tar.0.gz (the latest):
Also saw that info.0 had the same modified time...here it is:
Not sure if there are other logs to examine?
I'm not a unix guy (windows developer, so somewhat technical, but not on hardware or linux) so any help appreciated in a manner I hope understand.
Thanks in advance!
Initially, I was trying to do a Disk Import via an attached USB SSD enclosure. It would get about 30% then crash. This happened about 4 times and I gave up. I assumed it was the USB enclosure, etc and after researching, most suggested just to copy over the network.
So then tried using Robocopy to copy from my old NAS to this new True NAS build. Again, it would copy for 3 - 5 minute, then crash.
From what I researched, I found the data/crash directory and extracted this from the textdump.tar.0.gz (the latest):
Code:
Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xffffffff80af4b3e stack pointer = 0x28:0xfffffe01415f69c0 frame pointer = 0x28:0xfffffe01415f6a40 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (z_wr_iss_h_2) trap number = 9 panic: general protection fault cpuid = 0 time = 1673415926 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe01415f67e0 vpanic() at vpanic+0x17f/frame 0xfffffe01415f6830 panic() at panic+0x43/frame 0xfffffe01415f6890 trap_fatal() at trap_fatal+0x385/frame 0xfffffe01415f68f0 calltrap() at calltrap+0x8/frame 0xfffffe01415f68f0 --- trap 0x9, rip = 0xffffffff80af4b3e, rsp = 0xfffffe01415f69c0, rbp = 0xfffffe01415f6a40 --- __mtx_lock_sleep() at __mtx_lock_sleep+0xce/frame 0xfffffe01415f6a40 vm_reserv_alloc_page() at vm_reserv_alloc_page+0x5c5/frame 0xfffffe01415f6aa0 vm_page_alloc_domain_after() at vm_page_alloc_domain_after+0xb5/frame 0xfffffe01415f6b20 kmem_back_domain() at kmem_back_domain+0x10a/frame 0xfffffe01415f6b90 kmem_malloc_domainset() at kmem_malloc_domainset+0xaf/frame 0xfffffe01415f6c00 keg_alloc_slab() at keg_alloc_slab+0xb0/frame 0xfffffe01415f6c50 zone_import() at zone_import+0xf0/frame 0xfffffe01415f6ce0 cache_alloc() at cache_alloc+0x326/frame 0xfffffe01415f6d50 cache_alloc_retry() at cache_alloc_retry+0x25/frame 0xfffffe01415f6d90 zio_write_compress() at zio_write_compress+0x1a6/frame 0xfffffe01415f6e00 zio_execute() at zio_execute+0x9f/frame 0xfffffe01415f6e40 taskqueue_run_locked() at taskqueue_run_locked+0x181/frame 0xfffffe01415f6ec0 taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame 0xfffffe01415f6ef0 fork_exit() at fork_exit+0x7e/frame 0xfffffe01415f6f30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe01415f6f30 --- trap 0x246, rip = 0xbc7f0d20, rsp = 0, rbp = 0 --- KDB: enter: panic panic.txt0600003014357446366 7153 ustarrootwheelgeneral protection faultversion.txt0600006414357446366 7555 ustarrootwheelFreeBSD 13.1-RELEASE-p2 n245412-484f039b1d0 TRUENAS
Also saw that info.0 had the same modified time...here it is:
Code:
root@truenas[/data/crash]# vim info.0 Dump header from device: /dev/ada2p1 Architecture: amd64 Architecture Version: 4 Dump Length: 598016 Blocksize: 512 Compression: none Dumptime: 2023-01-10 22:45:26 -0700 Hostname: truenas.local Magic: FreeBSD Text Dump Version String: FreeBSD 13.1-RELEASE-p2 n245412-484f039b1d0 TRUENAS Panic String: general protection fault Dump Parity: 3525357351 Bounds: 0 Dump Status: good
Not sure if there are other logs to examine?
I'm not a unix guy (windows developer, so somewhat technical, but not on hardware or linux) so any help appreciated in a manner I hope understand.
Thanks in advance!