As the title suggests, I added a disk(after a normal stopping of it) to the arrey due to it being 100% full. I started the array as normal and it was taking a long time. I checked the disks and 1-5 listed "Unmountable wrong or no file system"

OK...

So my thoughts are... that due to the power loss which forced the check and while it was in the middle of it I added the new disk...

I had 0 parity errors up to this point so I thought everything was fine and adding a new disk would go without issue...

Once I noticed that Star command was taking too long and noting the errors, I decided to restart the array, remove the disk, let parity finish and try again. The system isnt rebooting. Seemingly its working? through starting the disks before it tries to restart.

Not wanting to upset the system further I have paused all further actions and will let it continue tonight. I hope to wake up tomorrow with the system ready for me to start the array.

Question is. should I

1. force it off and continue adding the new disk, thinking this was a hung/stuck process

2. Let it continue rebooting normally, remove the new disk, and let the array complete the parity check before adding the disk normally

3. start a new config(I assume this would be the quickest way, hoping that the final disk(the only one with new data is good)

Worst case is that I have one file on disk 19 being bad(it was late at night) and once that we naturally find a bad video, we delete it and find a new copy, but will the system act the same way later?

Never been here before... Currently the system is stuck on disk 9 trying to mount(all others failed) after 1.5h.

Ill attach Diags when ready... process has been running for the past 10mins...

Edited September 12Sep 12 by mathomas3

I was able to do a full backup of the USB if that's the only thing we have to go on

Attached are the systems current running logs... Of note... these are repeating.... with no change... Hard restart needed? What would be the following steps... Is this a bug?

Sep 11 18:04:21 Tower kernel: CPU: 4 UID: 0 PID: 133393 Comm: lsblk Tainted: P D O 6.12.54-Unraid #1

Sep 11 18:04:21 Tower kernel: Tainted: [P]=PROPRIETARY_MODULE, [D]=DIE, [O]=OOT_MODULE

Sep 11 18:04:21 Tower kernel: Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.8.0 05/23/2018

Sep 11 18:04:21 Tower kernel: RIP: 0010:block_devnode+0x10/0x30

Sep 11 18:04:21 Tower kernel: Code: cc cc cc 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 48 8b bf 48 ff ff ff 48 8b 47 48 <48> 8b 40 68 48 85 c0 74 05 e9 52 2d 5b 00 31 c0 c3 cc cc cc cc 66

Sep 11 18:04:21 Tower kernel: RSP: 0018:ffffc900080ffd28 EFLAGS: 00010282

Sep 11 18:04:21 Tower kernel: RAX: ffffffffa6b9c3e0 RBX: ffff888107b864c8 RCX: ffffc900080ffd64

Sep 11 18:04:21 Tower kernel: RDX: ffffc900080ffd60 RSI: ffffc900080ffd5e RDI: ffff888109217400

Sep 11 18:04:21 Tower kernel: RBP: ffff888107b864c8 R08: ffffc900080ffd68 R09: 0000000000000000

Sep 11 18:04:21 Tower kernel: R10: 0000000000000009 R11: 0000000000000000 R12: ffffc900080ffd68

Sep 11 18:04:21 Tower kernel: R13: ffffc900080ffd5e R14: ffff8881094a03c0 R15: 0000000000001000

Sep 11 18:04:21 Tower kernel: FS: 0000146a7c919780(0000) GS:ffff888667880000(0000) knlGS:0000000000000000

Sep 11 18:04:21 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Sep 11 18:04:21 Tower kernel: CR2: ffffffffa6b9c448 CR3: 0000000151972003 CR4: 00000000003706f0

Sep 11 18:04:21 Tower kernel: Call Trace:

Sep 11 18:04:21 Tower kernel: <TASK>

Sep 11 18:04:21 Tower kernel: device_get_devnode+0x30/0xc0

Sep 11 18:04:21 Tower kernel: dev_uevent+0x89/0x230

Sep 11 18:04:21 Tower kernel: uevent_show+0x8d/0xe0

Sep 11 18:04:21 Tower kernel: dev_attr_show+0x1f/0x50

Sep 11 18:04:21 Tower kernel: sysfs_kf_seq_show+0x84/0xc0

Sep 11 18:04:21 Tower kernel: seq_read_iter+0x15e/0x350

Sep 11 18:04:21 Tower kernel: vfs_read+0x131/0x1c0

Sep 11 18:04:21 Tower kernel: ksys_read+0x71/0xc0

Sep 11 18:04:21 Tower kernel: do_syscall_64+0x68/0xe0

Sep 11 18:04:21 Tower kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e

Sep 11 18:04:21 Tower kernel: RIP: 0033:0x146a7c9b6c02

Sep 11 18:04:21 Tower kernel: Code: 00 00 00 48 8b 05 e6 71 16 00 64 89 10 48 c7 c2 ff ff ff ff 48 83 c4 18 48 89 d0 c3 0f 1f 40 00 49 89 ca 48 8b 44 24 20 0f 05 <48> 89 c2 48 3d 00 f0 ff ff 77 0b 48 89 d0 48 83 c4 18 c3 0f 1f 00

Sep 11 18:04:21 Tower kernel: RSP: 002b:00007ffea778c0b0 EFLAGS: 00000202 ORIG_RAX: 0000000000000000

Sep 11 18:04:21 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000442ff0 RCX: 0000146a7c9b6c02

Sep 11 18:04:21 Tower kernel: RDX: 0000000000001000 RSI: 000000000049e0c0 RDI: 0000000000000009

Sep 11 18:04:21 Tower kernel: RBP: 0000146a7cb1d210 R08: 0000000000000000 R09: 0000000000000000

Sep 11 18:04:21 Tower kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000146a7cb1d0c0

Sep 11 18:04:21 Tower kernel: R13: 0000000000000000 R14: 0000000000442ff0 R15: 0000000000003fff

Sep 11 18:04:21 Tower kernel: </TASK>

Sep 11 18:04:21 Tower kernel: Modules linked in: md_mod nvidia_uvm(PO) xt_CHECKSUM ipt_REJECT nf_reject_ipv4 vhost_iotlb br_netfilter veth nf_conntrack_netlink xt_nat xfrm_user xfrm_algo xt_addrtype nfsd auth_rpcgss lockd grace sunrpc zfs(PO) spl(O) xt_connmark xt_conntrack ip6table_mangle iptable_mangle xt_MASQUERADE xt_tcpudp xt_mark tun nf_tables nfnetlink ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ntfs3 tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls tg3 ses enclosure intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 drm_ttm_helper mgag200 sha1_ssse3 ttm drm_shmem_helper aesni_intel video i2c_algo_bit crypto_simd cryptd drm_kms_helper ipmi_ssif rapl intel_cstate drm mei_me agpgart backlight intel_uncore mpt3sas mxm_wmi sr_mod input_leds megaraid_sas cdrom raid_class joydev

Sep 11 18:04:21 Tower kernel: mei i2c_core led_class scsi_transport_sas ipmi_si acpi_power_meter wmi acpi_ipmi button [last unloaded: kvm]

Sep 11 18:04:21 Tower kernel: CR2: ffffffffa6b9c448

Sep 11 18:04:21 Tower kernel: ---[ end trace 0000000000000000 ]---

Sep 11 18:04:21 Tower kernel: RIP: 0010:block_devnode+0x10/0x30

Sep 11 18:04:21 Tower kernel: Code: cc cc cc 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 48 8b bf 48 ff ff ff 48 8b 47 48 <48> 8b 40 68 48 85 c0 74 05 e9 52 2d 5b 00 31 c0 c3 cc cc cc cc 66

Sep 11 18:04:21 Tower kernel: RSP: 0018:ffffc90023933d28 EFLAGS: 00010282

Sep 11 18:04:21 Tower kernel: RAX: ffffffffa6b9c3e0 RBX: ffff888107b864c8 RCX: ffffc90023933d64

Sep 11 18:04:21 Tower kernel: RDX: ffffc90023933d60 RSI: ffffc90023933d5e RDI: ffff888109217400

Sep 11 18:04:21 Tower kernel: RBP: ffff888107b864c8 R08: ffffc90023933d68 R09: 0000000000000000

Sep 11 18:04:21 Tower kernel: R10: 0000000000000009 R11: 0000000000000000 R12: ffffc90023933d68

Sep 11 18:04:21 Tower kernel: R13: ffffc90023933d5e R14: ffff88868771e5a0 R15: 0000000000001000

Sep 11 18:04:21 Tower kernel: FS: 0000146a7c919780(0000) GS:ffff888667880000(0000) knlGS:0000000000000000

Sep 11 18:04:21 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Sep 11 18:04:21 Tower kernel: CR2: ffffffffa6b9c448 CR3: 0000000151972003 CR4: 00000000003706f0

Sep 11 18:04:21 Tower kernel: note: lsblk[133393] exited with irqs disabled

Sep 11 18:04:22 Tower kernel: BUG: unable to handle page fault for address: ffffffffa6b9c448

Sep 11 18:04:22 Tower kernel: #PF: supervisor read access in kernel mode

Sep 11 18:04:22 Tower kernel: #PF: error_code(0x0000) - not-present page

Sep 11 18:04:22 Tower kernel: PGD 561a067 P4D 561a067 PUD 561b063 PMD 7294fa067 PTE 0

Sep 11 18:04:22 Tower kernel: Oops: Oops: 0000 [#2198] PREEMPT SMP PTI

server logs

On the Diags... im stuck at

/sbin/btrfs filesystem usage -T /mnt/cache 2>/dev/null|todos >>'/tower-diagnostics-20260911-1945/system/btrfs-usage.txt'
/sbin/btrfs filesystem show /dev/sdcp1 2>/dev/null|todos >>'/tower-diagnostics-20260911-1945/system/btrfs-usage.txt'

Think I found the error based off of that last error I found... The issue is with tailscale...

Without uninstalling in the next few reboots worked for me... I will keep this in mind should this happen again... I was able to start the array in Maintance mode with the fewer disk and start again with the larger ammount. Then I did a full start with that and it started formatting the disk. All seems good... the solution was for the (thought to be original issue) is...

I dont know... For me what it seemed to involve was starting the array in Maintance mode with fewer disks. Started the array like that and after it started with dockers starting. I powered it off to add the new disk. After the new disk was added, I once again started in Maintance mode. It seemed happy after stopping the array. Once again, I started the array with the new disk still added, I fully came up and started formatting the new disk.

It worked for me, but the info below still might be another issue for me. Dont know. I dont start/stop my array often. If possible, it only gets powered off for hardware issues or adding/removing a disk.

"

ChaoticSoundMembers

February 3, 2025

• Author

• Solution

Hey, so i had some time this weekend and i figured out what was happening (spoiler: i was dumb 😅).

So, before upgrading to v7, i was using Tailscale on a docker container.

After upgrading i started using the Tailscale plugin and stopped the container (just stopped, didn't remove it).

Everything was working fine, but i forgot an important detail.

The old Tailscale container had autostart turned on.

When unRAID rebooted due to the power outage the container started again, and i ended with two Tailscale instances running (plugin and container).

That was the cause of everything.

Removing the container made the issue of nginx restarting go away.

 

Thanks for the help 😅

"

Edited September 12Sep 12 by mathomas3