Suddenly my array will not start.   I have already tried setting the Docker netowrk type to ipvlan.

 

Feb 19 20:33:05 Prime kernel: CPU: 7 PID: 181 Comm: kworker/u64:6 Tainted: P           O       6.1.64-Unraid #1
Feb 19 20:33:05 Prime kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI/X570 AORUS PRO WIFI, BIOS F11 12/06/2019
Feb 19 20:33:05 Prime kernel: Workqueue: btrfs-cache btrfs_work_helper
Feb 19 20:33:05 Prime kernel: RIP: 0010:_compound_head+0x0/0x36
Feb 19 20:33:05 Prime kernel: Code: 75 1d 48 8b 07 0f ba e0 10 73 14 48 8b 47 48 48 89 c2 83 e2 01 74 08 48 ff c8 48 39 c7 75 03 8b 57 5c 48 89 d0 e9 c9 f7 8a 00 <48> 8b 57 08 48 89 f8 f6 c2 01 75 21 66 90 e9 b6 f7 8a 00 f7 c7 ff
Feb 19 20:33:05 Prime kernel: RSP: 0018:ffffc90000a67c58 EFLAGS: 00010212
Feb 19 20:33:05 Prime kernel: RAX: 0000000000000004 RBX: 0000000000000000 RCX: 0000000000001000
Feb 19 20:33:05 Prime kernel: RDX: 0000000000006800 RSI: 0000000000000000 RDI: 0000000000000000
Feb 19 20:33:05 Prime kernel: RBP: 0000000000000000 R08: 0000000000001000 R09: 00000000000001a2
Feb 19 20:33:05 Prime kernel: R10: ffff888000000000 R11: 0000000000032140 R12: 0000000000006800
Feb 19 20:33:05 Prime kernel: R13: ffff888173938000 R14: 000000054bd00000 R15: ffff888105c86fc0
Feb 19 20:33:05 Prime kernel: FS:  0000000000000000(0000) GS:ffff8887fe9c0000(0000) knlGS:0000000000000000
Feb 19 20:33:05 Prime kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 19 20:33:05 Prime kernel: CR2: 0000000000000008 CR3: 0000000107d52000 CR4: 0000000000350ee0
Feb 19 20:33:05 Prime kernel: Call Trace:
Feb 19 20:33:05 Prime kernel: <TASK>
Feb 19 20:33:05 Prime kernel: ? __die_body+0x1a/0x5c
Feb 19 20:33:05 Prime kernel: ? page_fault_oops+0x329/0x376
Feb 19 20:33:05 Prime kernel: ? do_user_addr_fault+0x12e/0x48d
Feb 19 20:33:05 Prime kernel: ? exc_page_fault+0xfb/0x11d
Feb 19 20:33:05 Prime kernel: ? asm_exc_page_fault+0x22/0x30
Feb 19 20:33:05 Prime kernel: ? compound_nr+0x42/0x42
Feb 19 20:33:05 Prime kernel: ? find_first_extent_bit_state+0x11/0x34
Feb 19 20:33:05 Prime kernel: PageUptodate+0x5/0x18
Feb 19 20:33:05 Prime kernel: assert_eb_page_uptodate+0x59/0x7b
Feb 19 20:33:05 Prime kernel: extent_buffer_test_bit+0x3c/0x74
Feb 19 20:33:05 Prime kernel: free_space_test_bit+0x75/0xa3
Feb 19 20:33:05 Prime kernel: load_free_space_tree+0x133/0x2f4
Feb 19 20:33:05 Prime kernel: caching_thread+0xe9/0x438
Feb 19 20:33:05 Prime kernel: btrfs_work_helper+0x114/0x2a5
Feb 19 20:33:05 Prime kernel: process_one_work+0x1ab/0x295
Feb 19 20:33:05 Prime kernel: worker_thread+0x18b/0x244
Feb 19 20:33:05 Prime kernel: ? rescuer_thread+0x281/0x281
Feb 19 20:33:05 Prime kernel: kthread+0xe7/0xef
Feb 19 20:33:05 Prime kernel: ? kthread_complete_and_exit+0x1b/0x1b
Feb 19 20:33:05 Prime kernel: ret_from_fork+0x22/0x30
Feb 19 20:33:05 Prime kernel: </TASK>

 

Attached are diagnostics.  Pleas help!

prime-diagnostics-20240219-2034.zip

If the log tree is the only issue this may help, type:

btrfs rescue zero-log /dev/nvme0n1p1

Then restart the array

JorgeB, that worked to start the array, but then when the Docker service started I got this error:

 

Feb 20 05:11:57 Prime kernel: BTRFS error (device nvme0n1p1): incorrect extent count for 20423114752; counted 18189, expected 18188
Feb 20 05:11:58 Prime kernel: BUG: kernel NULL pointer dereference, address: 0000000000000008
Feb 20 05:11:58 Prime kernel: #PF: supervisor read access in kernel mode
Feb 20 05:11:58 Prime kernel: #PF: error_code(0x0000) - not-present page
Feb 20 05:11:58 Prime kernel: PGD 1c26a9067 P4D 1c26a9067 PUD 17e423067 PMD 0 
Feb 20 05:11:58 Prime kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Feb 20 05:11:58 Prime kernel: CPU: 4 PID: 4602 Comm: kworker/u64:5 Tainted: P           O       6.1.64-Unraid #1
Feb 20 05:11:58 Prime kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI/X570 AORUS PRO WIFI, BIOS F11 12/06/2019
Feb 20 05:11:58 Prime kernel: Workqueue: btrfs-cache btrfs_work_helper
Feb 20 05:11:58 Prime kernel: RIP: 0010:_compound_head+0x0/0x36
Feb 20 05:11:58 Prime kernel: Code: 75 1d 48 8b 07 0f ba e0 10 73 14 48 8b 47 48 48 89 c2 83 e2 01 74 08 48 ff c8 48 39 c7 75 03 8b 57 5c 48 89 d0 e9 c9 f7 8a 00 <48> 8b 57 08 48 89 f8 f6 c2 01 75 21 66 90 e9 b6 f7 8a 00 f7 c7 ff
Feb 20 05:11:58 Prime kernel: RSP: 0018:ffffc900020cfc58 EFLAGS: 00010212
Feb 20 05:11:58 Prime kernel: RAX: 0000000000000004 RBX: 0000000000000000 RCX: 0000000000001000
Feb 20 05:11:58 Prime kernel: RDX: 0000000000006800 RSI: 0000000000000000 RDI: 0000000000000000
Feb 20 05:11:58 Prime kernel: RBP: 0000000000000000 R08: 0000000000001000 R09: 00000000000001a2
Feb 20 05:11:58 Prime kernel: R10: ffff888000000000 R11: 0000000000032140 R12: 0000000000006800
Feb 20 05:11:58 Prime kernel: R13: ffff888107689000 R14: 000000054bd00000 R15: ffff888139af8300
Feb 20 05:11:58 Prime kernel: FS:  0000000000000000(0000) GS:ffff8887fe900000(0000) knlGS:0000000000000000
Feb 20 05:11:58 Prime kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 20 05:11:58 Prime kernel: CR2: 0000000000000008 CR3: 00000001a0c3e000 CR4: 0000000000350ee0
Feb 20 05:11:58 Prime kernel: Call Trace:
Feb 20 05:11:58 Prime kernel: <TASK>
Feb 20 05:11:58 Prime kernel: ? __die_body+0x1a/0x5c
Feb 20 05:11:58 Prime kernel: ? page_fault_oops+0x329/0x376
Feb 20 05:11:58 Prime kernel: ? do_user_addr_fault+0x12e/0x48d
Feb 20 05:11:58 Prime kernel: ? exc_page_fault+0xfb/0x11d
Feb 20 05:11:58 Prime kernel: ? asm_exc_page_fault+0x22/0x30
Feb 20 05:11:58 Prime kernel: ? compound_nr+0x42/0x42
Feb 20 05:11:58 Prime kernel: ? find_first_extent_bit_state+0x11/0x34
Feb 20 05:11:58 Prime kernel: PageUptodate+0x5/0x18
Feb 20 05:11:58 Prime kernel: assert_eb_page_uptodate+0x59/0x7b
Feb 20 05:11:58 Prime kernel: extent_buffer_test_bit+0x3c/0x74
Feb 20 05:11:58 Prime kernel: free_space_test_bit+0x75/0xa3
Feb 20 05:11:58 Prime kernel: load_free_space_tree+0x133/0x2f4
Feb 20 05:11:58 Prime kernel: caching_thread+0xe9/0x438
Feb 20 05:11:58 Prime kernel: ? move_linked_works+0x2f/0x6a
Feb 20 05:11:58 Prime kernel: ? pwq_adjust_max_active+0x88/0xa7
Feb 20 05:11:58 Prime kernel: btrfs_work_helper+0x114/0x2a5
Feb 20 05:11:58 Prime kernel: process_one_work+0x1ab/0x295
Feb 20 05:11:58 Prime kernel: worker_thread+0x18b/0x244
Feb 20 05:11:58 Prime kernel: ? rescuer_thread+0x281/0x281
Feb 20 05:11:58 Prime kernel: kthread+0xe7/0xef
Feb 20 05:11:58 Prime kernel: ? kthread_complete_and_exit+0x1b/0x1b
Feb 20 05:11:58 Prime kernel: ret_from_fork+0x22/0x30
Feb 20 05:11:58 Prime kernel: </TASK>

prime-diagnostics-20240220-0518.zip

Array started regularly with dockers disabled. 

 

With dockers disabled, array start ok in maintenance mode.

 

I get the above errors when fully starting the array with Dockers enabled    

Edited February 20, 20242 yr by andrew82

Docker image is corrupt, recreate:

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

Thanks.  Can I use my backups to restore the settings for the docker image?  I didn't see that in the instructions.  

You can restore them from CA previous apps, that is in the instructions.

Rebuilt image and did a scrub of the cache drive.  Here were the results:

 

UUID: 7102a52f-c454-4272-a805-415ef0a050ba

Scrub started: Wed Feb 21 20:42:27 2024

Status: finished Duration: 0:00:59

Total to scrub: 166.04GiB

Rate: 2.81GiB/s

Error summary: csum=216

Corrected: 0

Uncorrectable: 216

Unverified: 0

If that really is a new docker image and already has corruption, there's likely and underlying hardware issue, I would start by running memtest