jolma

Found the solution: 1. Stop the qbittorrent docker 2. go to mnt/user/app data, rename the qbittorrent (as a backup, name it whatever you like). 3 start the qbittorrent docker (this will like a new bittorrent, set a new user detail (login/password)) 4. stop the qbittorrent docker again (create path download exactly as before if you installed a new qbitorrent) 5. copy BT_Backup, categories.json & qbittorrent.conf from backup to new qbittorrent. 6. start qbittorent docker, it will be the same but new client.

This also happens to me, I cant log in, says connection refused too. Please help.

Tools - about - downgrade OS

from my experience when you get ip of "169.254.141.64" it means your server didn't get IP from DHCP server on your router... so you can check or restart your router.. hope it helps...

Trying to summarize 1. After upgrading 2 of my drives unmountable Check using fdisk -l /dev/sdb and fdisk -l /dev/sde, both drives detected 2 TB, real capacity is 10TB and 4TB so next step. Using command from this post Check again with step number 2, if didn't work try this post If the problem still persist then try this step if the drives already detected with the real capacity, then do this Then all is good :D Thank you hope it helps for someone that have the same problem with me

All Good, Thank you very much @JorgeB

Here is the new output reboot then unmount?

Here is the result I restarted and using command -g also didn't work.. the disk 3 is still unmountable.. here is the new diagnostics tower-diagnostics-20250522-2017.zip

here is the output, Thanks

started the array, Disk 3 still unmountable, diagnostics attached tower-diagnostics-20250522-1827.zip

How to fix backup header for sde?

This is result of the command, is it okay? to restart?

Here is the output root@Tower:~# fdisk -l /dev/sdb Disk /dev/sdb: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: TOSHIBA MG06ACA1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdb1 64 3907029167 3907029104 1.8T 83 Linux root@Tower:~# fdisk -l /dev/sde Disk /dev/sde: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: ST4000VN006-3CW1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sde1 64 3907029167 3907029104 1.8T 83 Linux" "

Hello, I just upgrade my unraid twice, first from 7.0.0 to 7.10, reboot and success but I set my array to not automatically start but all the disks is recognizeable, so I continue to updated it to 7.12 version, after I reboot , 2 of my disks read wrong disks, I cannot start the array, So I setup new config, with all the same drive and start the array, Then 2 drives unmountable. As can be seen in the pictures both drives are the same as before. The diagnostics attached, Thanks tower-diagnostics-20250522-1500.zip

Sorry, for the late post rebuilding complete so the main problem is 2 harddrive are broken, that is why it is not recognized, so the step are: 1. Clone/rescue each drive using ddrescue. 2. set up new config, following this guide 3. Wait for parity to rebuild, Thanks