trurl
Moderators
-
Joined
-
Last visited
Everything posted by trurl
-
We were missing this important info Didn't want you to rebuild an unmountable filesystem.
-
https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself
-
Can you get diagnostics from command line? Also
-
Attach Diagnostics ZIP to your NEXT post in this thread.
-
What is the actual command you used? No reason to not post it with the correct identifier.
-
Attach Diagnostics ZIP to your NEXT post in this thread.
-
What do you get from command line with this? df -h /
-
You can go directly to the correct support thread for any of your plugins by clicking its Support link on the Plugins page of your Unraid webUI.You can go directly to the correct support thread for this docker by clicking its icon and selecting SupportDo you have an attached monitor and keyboard?Post a screenshot of your CA Settings page.What were you actually using to do the copy?contact supportI don't see any disks that you might assign to any pools outside the array. Did you have any before?If you used that flash drive before then your trial expired. Have you tried another flash drive?I didn't check SMART for any disk, since you have so many. Do any disks show SMART (👎) warning on the DASHBOARD page? All disks are mounted, including the disabled/emulated disks, but you don't have any user shares. There seems to be something trying to access user shares before they have been created. Disable Docker and VM Manager in Settings until you get all of this fixed. Reboot in SAFE mode and post new diagnostics.I especially don't recommend it when you have so many drives. In order to rebuild a disk, Unraid must be able to reliably read all other disks. So, even though each disk is an independent filesystem that can be read all by itself on any Linux, any unreliable disk in the array can make it difficult to reliably rebuild a different disk. Since you have dual parity, that risk is reduced somewhat, since you would need 2 unreliable disks to cause problems for rebuilding another disk. But you do seem to have 2 unreliable disks. Why do you have so many small disks anyway? Each additional disk is an additional point of failure. If I were you, I would forget about those USB disks, except as Unassigned Devices, reset the array (New Config) without them, rebuild parity, and copy whatever is on those as Unassigned Devices to other disks in the array. When you eventually need more capacity, upsize disks, don't try to add more.USB not recommended for assigned disks for many reasonsThe appdata and system shares still have files on disk1. Mover won't overwrite files, so they will be duplicates that you will have to clean up yourself. Since you don't have redundant cache those shares will be unprotected. You can backup appdata with a plugin. Did you actually have any VMs?Nothing can move open files. Disable Docker and VM Manager in Settings, run Mover, wait for it to complete, then Attach Diagnostics ZIP to your NEXT post in this thread.Post new diagnosticsAttach Diagnostics ZIP to your NEXT post in this thread.Post a screenshot of MAIN - Unassigned DevicesAttach Diagnostics ZIP to your NEXT post in this thread.
