-
[Typo] Unraid preclear
The bottom of preclear status report has a typo of genereated rather then generated #################################################################################################### # Unraid Server Preclear of disk ZXA12345 # # Cycle 1 of 1, partition start on sector 64. # # # .... # # # # #################################################################################################### # Report genereated on: July 15, 2025 at 13:52:42 # ####################################################################################################
-
[PLUGIN] Unraid Open Files Plugin (Fork)
Actually for me on 7.1.4 it does NOT specify there is a replacement plugin available: Deprecated plugin file.activity.plg This plugin has been deprecated and should no longer be used due to the following reason(s): This plugin is unknown to Community Applications. It is highly advised to uninstall this and reinstall the replacement file.activity plugin available within Apps While this plugin should still be functional, it is not recommended to continue to use it. Deprecated plugin open.files.plg This plugin has been deprecated and should no longer be used due to the following reason(s): This plugin is unknown to Community Applications. It is highly advised to uninstall this and reinstall the replacement open files plugin available within Apps While this plugin should still be functional, it is not recommended to continue to use it
-
[Plugin] Appdata.Backup
What cmd would you like me to run on it?
-
[Plugin] Appdata.Backup
Ive reported the padding with zeroes error before for Chrome, Im now getting it for PhotoPrism also. Woudl be great if this can be looked at as it appears in this forum for a while already. tar creation failed! Tar said: tar: /mnt/user/appdata/ferdium/.config/Ferdium/Partitions/service-1954dbfc-c6e4-49e9-8564-8e96ad85444f/Cache/Cache_Data/012cb887f079a2f9_0: File shrank by 520 bytes; padding with zeros tar creation failed! Tar said: tar: /mnt/user/appdata/ferdium/.config/Ferdium/Partitions/service-1954dbfc-c6e4-49e9-8564-8e96ad85444f/Cache/Cache_Data/012cb887f079a2f9_0: File shrank by 520 bytes; padding with zeros tar creation failed! Tar said: tar: /mnt/user/appdata/ferdium/.config/Ferdium/Partitions/service-1954dbfc-c6e4-49e9-8564-8e96ad85444f/Cache/Cache_Data/012cb887f079a2f9_0: File shrank by 520 bytes; padding with zeros Its worth noting Ferdium and Chrome are not even running in the first place...
-
[Plugin] FolderView2
Can you give example what u have? Just doesnt work for... /appdata/icons/ground7_unraid-animated-svgs/Always%20Animate/downloads.svg
-
[Plugin] FolderView2
Is there a way to reference a local icon instead of internet URL? Is it possible to have multiple rows without full expanding?? i.e. If my folder has 6+ things in it, only 5 or 6 show making it not obvious what's in there. would love to have a second 'minimized' row.
-
[Plugin] Appdata.Backup
I'm also getting padding with zeros error. This container is not even started, and the mapped path is not in use for any other docker container [05.04.2025 12:44:44][ℹ️][ferdium] No stopping needed for ferdium: Not started! [05.04.2025 12:44:44][debug][ferdium] Not executing script: Not set! [05.04.2025 12:44:44][debug][ferdium] Backup ferdium - Container Volumeinfo: Array ( [0] => /mnt/user/appdata/ferdium:/config:rw ) [05.04.2025 12:44:44][debug][ferdium] usorted volumes: Array ( [0] => /mnt/user/appdata/ferdium ) [05.04.2025 12:44:44][ℹ️][ferdium] Should NOT backup external volumes, sanitizing them... [05.04.2025 12:44:44][debug][ferdium] Volume '/mnt/user/appdata/ferdium' IS within AppdataPath '/mnt/user/appdata'! [05.04.2025 12:44:44][ℹ️][ferdium] Calculated volumes to back up: /mnt/user/appdata/ferdium [05.04.2025 12:44:44][debug][ferdium] Target archive: /mnt/user/appdata-disks/CommunityApplicationsAppdataBackup/ab_20250405_110002/ferdium.tar [05.04.2025 12:44:44][debug][ferdium] Generated tar command: -c -P -f '/mnt/user/appdata-disks/CommunityApplicationsAppdataBackup/ab_20250405_110002/ferdium.tar' '/mnt/user/appdata/ferdium' [05.04.2025 12:44:44][ℹ️][ferdium] Backing up ferdium... [05.04.2025 12:45:12][debug][ferdium] Tar out: tar: /mnt/user/appdata/ferdium/.config/Ferdium/Partitions/service-1954dbfc-c6e4-49e9-8564-8e96ad85444f/Cache/Cache_Data/012cb887f079a2f9_0: File shrank by 520 bytes; padding with zeros [05.04.2025 12:45:12][❌][ferdium] tar creation failed! Tar said: tar: /mnt/user/appdata/ferdium/.config/Ferdium/Partitions/service-1954dbfc-c6e4-49e9-8564-8e96ad85444f/Cache/Cache_Data/012cb887f079a2f9_0: File shrank by 520 bytes; padding with zeros [05.04.2025 12:45:29][debug][ferdium] lsof(/mnt/user/appdata/ferdium) Array ( ) [05.04.2025 12:45:29][debug][ferdium] Not executing script: Not set! [05.04.2025 12:45:29][ℹ️][ferdium] Installing planned update for ferdium... [05.04.2025 12:45:40][ℹ️][ferdium] Starting ferdium is being ignored, because it was not started before (or should not be started).
-
How to remove 2 drives from raid1 cache?
It doesn't appear so, I get quite a nice red warning All existing data on this device will be OVERWRITTEN when array is Started bridge-diagnostics-20231023-1030.zip
-
How to remove 2 drives from raid1 cache?
Thank you they were removed, However now the NVMes are listed as Cache 3 and Cache 4. How can I move them up to 0 and 1?
-
How to remove 2 drives from raid1 cache?
I've upgraded my system from 2 sata ssds to 2 nvme ssds. When I started up the array I added the 2 nvmes to the same pool as the existing 2 satas. i.e. there are now 4 drives in the pool. As far as I can tell they are raid 1. Clicking cache says: Data, RAID1: total=206.00GiB, used=204.18GiB System, RAID1: total=32.00MiB, used=48.00KiB Metadata, RAID1: total=2.00GiB, used=1.14GiB GlobalReserve, single: total=341.97MiB, used=0.00B No balance found on '/mnt/cache' Current usage ratio: 99.1 % --- No Balance required I want to remove the 2 satas. I thought I could just stop array and says pool has 2 disks but I can't lower it. So what's the procedure to simply remove the drives and let it 'rebalance' (I think) to just the 2 nvmes? bridge-diagnostics-20231022-1536.zip
-
Help recovering from several disk disables/failures
Yes I did maintenance just to keep it offline for now. I'm saying the message sent though implies the rebuild started.
-
Help recovering from several disk disables/failures
Also, bug report (maybe just bad wording?): I started in maintenance mode and did the unassign/assign and the notifications tell me its being reconstructed even though I didnt hit sync yet. Event: Unraid Disk 3 message Subject: Notice [BRIDGE] - Disk 3, is being reconstructed and is available for normal operation Description: WDC_WD100EMAZ-00WJTA0_JEGW40YN (sdd) Importance: normal Event: Unraid Disk 5 message Subject: Notice [BRIDGE] - Disk 5, is being reconstructed and is available for normal operation Description: WDC_WD100EMAZ-00WJTA0_JEGW1ADN (sde) Importance: normal bridge-diagnostics-20231018-1311.zip
-
Help recovering from several disk disables/failures
1) This is xfs_repair below, just wanted to make sure seems ok to you. 2) Parity main bottleneck is drives right? I plan on upgrading the CPU on this (3rd gen i7 3770k to 12th gen i5-12600K 6p4e), just wanted to know if I should bother doing the upgrade first. Phase 1 - find and verify superblock... - block cache size set to 1419048 entries Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) failed to find log head zero_log: cannot find log head/tail (xlog_find_tail=5) - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 4 - agno = 0 - agno = 3 - agno = 5 - agno = 6 - agno = 7 - agno = 2 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (6:207268) is ahead of log (1:2). Format log to cycle 9. XFS_REPAIR Summary Wed Oct 18 12:23:00 2023 Phase Start End Duration Phase 1: 10/18 12:18:08 10/18 12:18:08 Phase 2: 10/18 12:18:08 10/18 12:19:10 1 minute, 2 seconds Phase 3: 10/18 12:19:10 10/18 12:19:18 8 seconds Phase 4: 10/18 12:19:18 10/18 12:19:18 Phase 5: 10/18 12:19:18 10/18 12:19:19 1 second Phase 6: 10/18 12:19:19 10/18 12:19:26 7 seconds Phase 7: 10/18 12:19:26 10/18 12:19:26 Total run time: 1 minute, 18 seconds done bridge-diagnostics-20231018-1302.zip
-
Help recovering from several disk disables/failures
Completed with no errors! (Guess the old power supply is garbage) UI hasn't changed, I still have: Disk 1 Unmountable DIsk 3 disabled Disk 5 disabled And my option by rebuilt parity is still just Read-Check. bridge-diagnostics-20231018-1147.zip
-
Help recovering from several disk disables/failures
So Read-Check is about to finish, 0 errors so far. Assuming that completes without errors, what's the next step?
128bytes
Members
-
Joined
-
Last visited