HAMANY

Members
  • Posts

    61
  • Joined

  • Last visited

Everything posted by HAMANY

  1. I'm not familiar with sonarr and radarr, but this should work: - Edit the docker - "Add another Path, Port, Variable, Label or Device" - The SMB share will be under this path "/mnt/remotes/<SMB Share Name>/" Then the docker will have access to the SMB share similar to the array
  2. Are your apps installed as dockers in UnRaid? Add the paths of the SMB shares and UD moints to the dockers, then add them as a new source.
  3. Not sure if Symlink / soft links will work, but why you don't just map multiple drives in your main PC? You can add different sources to your Plex (Array, SMB shares, unassigned drives, etc.)
  4. Have you tried plugins like "File Activity" or "Open Files" to see what files/processes are currently being active?
  5. As far as I know, SMB and NFS shares cannot be added to the array, as they are not viewed as a "Drive" to other unRaid server.
  6. You're right, this was the issue. Reduced it to 100GB and everything works fine now. Thanks a lot @trurl and @JorgeB
  7. Hi all, When switching the Share "Primary storage" from "Cache" to "Array", dockers like rtorrent and FileZilla can't write new files, even in SMB shares. Switching back to "Cache" then everything works fine. I've seen the below thread, but I don't understand why the using (/mnt/user/) path doesn't work with the "Array"? I remember it was working fine in older updates. Appreciate your help. Thanks. tower-diagnostics-20240227-1735.zip
  8. I've restored the backup in a new USB stick. Every thing looks stable now. Thank you @trurl
  9. Yes I do. Should I do full data restore? Or just for the corrupted files? Thanks
  10. Thank you! The array is back online again, however, there are some issues. - Some dockers and plugins got corrupted. The Community App tab disappeared. - Loading the docker icons in the dashboard page is very slow. The server is overall slower than before. - Many disks have UDMA CRC error. Although recently, I've changed the power and Sata cables - Every time I restart the server, the Cache drive goes to unassigned. Appreciate your suggestion tower-diagnostics-20230217-1030.zip
  11. Attached. Disk 6 is rebuilding now. tower-diagnostics-20230209-0746.zip
  12. Disk 6 the drive that got disabled Cache (nvme0n1) the cache ssd that is shown as unassigned Is there any risk of losing the pool data (cache)? It has all the dockers, I've a backup for it.
  13. Hi all, Few days ago, one of my drives had read errors and got disabled (Disk 6). I stopped the array, remove the disk from the array, started the array again, saw the disk in unassigned but I wasn't able to select it in the array (No disk). So I shutdown the server, changed the disabled disk cables, started the server again, then the surprise. The cache (NVME) was shown under the unassigned devices, when I add it to the pool, it says it's a new device. Also there were many disks with UDMA CRC errors. I've attached the diags before the first restart and after the restart. Appreciate your help. Thank you. tower-diagnostics-20230209-0626 (After Restart).zip tower-diagnostics-20230206-2321 (Before Restart).zip
  14. Thanks. True, I misunderstood the when I saw the options under "Preserve current assignments". I thought if I select "all", the emulated data + disk data will both be restored to my drives. Anyways, I've done what @JorgeB mentioned and everything worked as expected, the parity sync is in progress. Thank you all @JorgeB, @trurl, @itimpi. I will mark this issue as resolved. Lessons learned: - Avoid SATA power splitters - Avoid motherboard SATA ports and get SAS HBA
  15. So in the New Config I've to select "Array Slot", correct? If I selected "All" and I don't have enough space in the drives, what will happen? Anything else I should consider before applying? Thank you.
  16. How can I choose between rebuilding the disks or parity? Rebuilding the parity is more suitable for me.
  17. Almost done copying my files. As for assigning the 2 disks back to the array again and start rebuilding, should I add both disks together? or one by one (Finish rebuilding one then add the second)? Thanks
  18. One of them is mounting fine (sdm) and I can see my data in the same structure. The other one is not mounting (sde), I get the below output when I click on the "file system check" Diags attached. There is a button called "Run with correct flag", should I try it? FS: xfs Executing file system check: /sbin/xfs_repair -n /dev/sde1 2>&1 Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. File system corruption detected! tower-diagnostics-20221016-1555.zip
  19. Thanks. Should I copy my data before doing these steps?
  20. I posted the latest diags in the previous reply after starting the array in normal mode. The Lost+Found folder contains folders and files with random numbers. The folders contain my files with the original naming with the correct file extension ✔️. The files are just renamed to numbers with no extension ❌. I don't have 1:1 backup for all the files, as most of them are available online. I've backups for some personal folders. I will do the follow, and please let me know what do you think. - I will copy the entire Lost+Found folder to an external drive, it's around (11.5TB) - Will rebuild parity after your confirmation - If there any corrupted/missing files, I will restore them from the backups or re-download them. Appreciate your advise.
  21. Thank you for your cooperation. Done for both desks with no errors. The last 2 lines are Format log to cycle 4. done I stopped the array then started it in normal mode as stated in the documentation. The 2 drives still have red x sign near the disk name and the status is "disabled". The entire drives contents were moved to the "lost+found" share. What should I do next? tower-diagnostics-20221016-1244.zip
  22. I'm running the GUI. Removed the -n and got the below outputs. Should I proceed with the "-L" ? Disk 7 Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. Disk 9 Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.
  23. What parameters should I use for the "xfs_repair"? I checked both disks using "-n" and received the below output Kindly note that, one of the disks was rebuilding before is gets disabled again and become unmountable. Would have this corrupt my files? Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. tower-diagnostics-20221016-0042.zip
  24. I replaced all the splitter cables, check all the connections and restarted the server. I removed all Sata splitters, only use 2 molex to 2x Sata. Disks 7 and 9 looks they are disabled and shown as "Unmountable disks". Is there any way to rebuild them using the parity? Do you think it's wise to mount the drives on Windows and copy all the files from these 2 disks before doing the rebuilding? Appreciate your advise. Thank you. tower-diagnostics-20221015-2337.zip