JuacOHI Posted May 27 Posted May 27 Hello, i'm having an issue that i can't really find a solution. The error happened last night out of the blue, from one second to another, no errors reported or anything weird, and the pc server never restarted nor shut down during this problem. Im currently running this Unraid+Plex for months, i haven't installed anything new nor done any different than i haven't previously done hundreds or thousands of times. Â I've a share named Movies, and it isn't showing the files that are in this share. Last night i finished moving a file from my computer (Windows 10) to this server/share with no issues and when i went to update the Plex library it refreshed and showed that all my Movies were unavailable, and ofc didn't update/added the new ones that i just moved with no issues. The tricky part is that i've other shares in same hard drives and they're showing with no problem. Besides that, if i go and check the files on the disks it shows them in the respective folder (share) Movies. I can see the files and also download them. Â Here are some pics: -Dives: https://imgur.com/a/U1Gsx8P -Share Settings: https://imgur.com/a/AzKG0nP -Share Settings after around 30 seconds: https://imgur.com/a/l5I8ZPq *It changes the Share status -Share Files: https://imgur.com/a/pVWgcA8 -Windows: https://imgur.com/a/8e8vxmC -Movies on disk 1: https://imgur.com/a/J6VxNmw -Movies files: https://imgur.com/a/q0xMddG -Last file moved to server: https://imgur.com/a/bEbJgKq -Permissions of the file on windows: https://imgur.com/a/asc5JZj -Server specs: https://imgur.com/a/vqTEnWX Â I checked running on Maintenance Mode and checking the hard drives with -n and it didn't show any error, i also repaired them with -v and it didn't do anything. The permissions and Export option its exactly the same as always as same as other shares that have no issue at the moment. I updated the permissions of the share on "Tools -> New Permissions". Nothing happened. I tried with 2 other computers (windows) and also can't see the files. Â This share has around 6000 movies, with subtitles, poster iamge, etc. It must contain easily more than 20.000 files. Â Unraid version: 6.12.9 Quote
trurl Posted May 27 Posted May 27 Sorry for the delayed response. Â Can't tell anything about your filesystems until they are mounted. Â Start the array in normal (not maintenance) mode and post new diagnostics Quote
JuacOHI Posted May 27 Author Posted May 27 Im so sorry, im kinda noob on this. Â New diagnostic file. Hope this time i did it right. plex-diagnostics-20240527-1905.zip Quote
trurl Posted May 28 Posted May 28 Emulated disk4 is mounted and is nearly full, but physical disk4 is missing. Â What can you tell us about disk4? Quote
trurl Posted May 28 Posted May 28 Also, the Movies share has data spread across many disks, including emulated disk4. Â On 5/26/2024 at 10:23 PM, JuacOHI said: Share Settings after around 30 seconds Post new diagnostics after Movies share "disappears". Â Quote
JuacOHI Posted May 31 Author Posted May 31 On 5/28/2024 at 8:23 AM, trurl said: Emulated disk4 is mounted and is nearly full, but physical disk4 is missing. Â What can you tell us about disk4? Sorry for the delay on my answers, i was out of town. Â About the disk4, I had a problem with a sata cable, that's why disk4 failed and it was showing as emulated. Â I've news about this issue (no solution). Disk 5 is showing read errors ~1 minute that i start the Array. Without me doing any action, always 20 read errors. I can see the files, folders, download the files, everything, but it shows error. Here its the xfs_repair -n status: Â Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... xfs_repair: read failed: Input/output error btree block 7/73939118 is suspect, error -117 bad magic # 0 in inobt block 7/73939118 xfs_repair: read failed: Input/output error btree block 7/73939119 is suspect, error -117 bad magic # 0 in finobt block 7/73939119 agi_count 576, counted 0 in ag 7 agi_freecount 47, counted 0 in ag 7 agi_freecount 47, counted 0 in ag 7 finobt xfs_repair: read failed: Input/output error btree block 1/70636777 is suspect, error -117 bad magic # 0 in inobt block 1/70636777 inode chunk claims untracked block, finobt block - agno 1, bno 16, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 17, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 18, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 19, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 20, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 21, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 22, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 23, inopb 8 undiscovered finobt record, ino 2147483776 (1/128) undiscovered finobt record, ino 2499363776 (1/351880128) undiscovered finobt record, ino 2625250816 (1/477767168) undiscovered finobt record, ino 2698601152 (1/551117504) undiscovered finobt record, ino 2795108224 (1/647624576) undiscovered finobt record, ino 2795118784 (1/647635136) undiscovered finobt record, ino 2795127104 (1/647643456) undiscovered finobt record, ino 2795135552 (1/647651904) undiscovered finobt record, ino 2795143104 (1/647659456) undiscovered finobt record, ino 2830971200 (1/683487552) undiscovered finobt record, ino 2830978880 (1/683495232) undiscovered finobt record, ino 3032147328 (1/884663680) undiscovered finobt record, ino 3128968704 (1/981485056) agi_count 1408, counted 0 in ag 1 agi_freecount 409, counted 0 in ag 1 sb_icount 11328, counted 9344 sb_ifree 3015, counted 2559 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... found inodes not in the inode allocation tree found inodes not in the inode allocation tree - process known inodes and perform inode discovery... - agno = 0 1483278cd680: Badness in key lookup (length) bp=(bno 0x80000078, len 4096 bytes) key=(bno 0x80000078, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0x80000098, len 4096 bytes) key=(bno 0x80000098, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0x94f943b8, len 4096 bytes) key=(bno 0x94f943b8, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0x94f943d8, len 4096 bytes) key=(bno 0x94f943d8, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0x9c7a25f8, len 4096 bytes) key=(bno 0x9c7a25f8, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0x9c7a2618, len 4096 bytes) key=(bno 0x9c7a2618, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa0d962b8, len 4096 bytes) key=(bno 0xa0d962b8, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa0d962d8, len 4096 bytes) key=(bno 0xa0d962d8, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa699f778, len 4096 bytes) key=(bno 0xa699f778, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa699f798, len 4096 bytes) key=(bno 0xa699f798, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa69a20b8, len 4096 bytes) key=(bno 0xa69a20b8, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa69a20d8, len 4096 bytes) key=(bno 0xa69a20d8, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa69a4138, len 4096 bytes) key=(bno 0xa69a4138, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa69a4158, len 4096 bytes) key=(bno 0xa69a4158, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa69a6238, len 4096 bytes) key=(bno 0xa69a6238, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa69a6258, len 4096 bytes) key=(bno 0xa69a6258, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa69a7fb8, len 4096 bytes) key=(bno 0xa69a7fb8, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa69a7fd8, len 4096 bytes) key=(bno 0xa69a7fd8, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa8bd3138, len 4096 bytes) key=(bno 0xa8bd3138, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa8bd3158, len 4096 bytes) key=(bno 0xa8bd3158, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa8bd4f38, len 4096 bytes) key=(bno 0xa8bd4f38, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xa8bd4f58, len 4096 bytes) key=(bno 0xa8bd4f58, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xb4bae578, len 4096 bytes) key=(bno 0xb4bae578, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xb4bae598, len 4096 bytes) key=(bno 0xb4bae598, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xba8045f8, len 4096 bytes) key=(bno 0xba8045f8, len 16384 bytes) 1483278cd680: Badness in key lookup (length) bp=(bno 0xba804618, len 4096 bytes) key=(bno 0xba804618, len 16384 bytes) - agno = 1 imap claims in-use inode 2147483777 is free, would correct imap imap claims in-use inode 2147483778 is free, would correct imap imap claims in-use inode 2147483779 is free, would correct imap imap claims in-use inode 2147483780 is free, would correct imap imap claims in-use inode 2147483781 is free, would correct imap imap claims in-use inode 2147483782 is free, would correct imap imap claims in-use inode 2147483783 is free, would correct imap imap claims in-use inode 2147483784 is free, would correct imap imap claims in-use inode 2147483785 is free, would correct imap imap claims in-use inode 2147483786 is free, would correct imap imap claims in-use inode 2147483787 is free, would correct imap imap claims in-use inode 2147483788 is free, would correct imap imap claims in-use inode 2147483789 is free, would correct imap imap claims in-use inode 2147483790 is free, would correct imap imap claims in-use inode 2147483791 is free, would correct imap imap claims in-use inode 2147483792 is free, would correct imap imap claims in-use inode 2147483793 is free, would correct imap imap claims in-use inode 2147483794 is free, would correct imap imap claims in-use inode 2147483795 is free, would correct imap imap claims in-use inode 2147483796 is free, would correct imap imap claims in-use inode 2147483797 is free, would correct imap imap claims in-use inode 2147483798 is free, would correct imap imap claims in-use inode 2147483799 is free, would correct imap imap claims in-use inode 2147483800 is free, would correct imap imap claims in-use inode 2147483801 is free, would correct imap imap claims in-use inode 2147483802 is free, would correct imap imap claims in-use inode 2147483803 is free, would correct imap imap claims in-use inode 2147483804 is free, would correct imap imap claims in-use inode 2147483805 is free, would correct imap imap claims in-use inode 2147483806 is free, would correct imap imap claims in-use inode 2147483807 is free, would correct imap imap claims in-use inode 2147483808 is free, would correct imap imap claims in-use inode 2147483809 is free, would correct imap imap claims in-use inode 2147483810 is free, would correct imap imap claims in-use inode 2147483811 is free, would correct imap imap claims in-use inode 2147483812 is free, would correct imap imap claims in-use inode 2147483813 is free, would correct imap imap claims in-use inode 2147483814 is free, would correct imap imap claims in-use inode 2147483815 is free, would correct imap imap claims in-use inode 2147483816 is free, would correct imap imap claims in-use inode 2147483817 is free, would correct imap imap claims in-use inode 2147483818 is free, would correct imap imap claims in-use inode 2147483819 is free, would correct imap imap claims in-use inode 2147483820 is free, would correct imap imap claims in-use inode 2147483821 is free, would correct imap imap claims in-use inode 2147483822 is free, would correct imap imap claims in-use inode 2147483824 is free, would correct imap imap claims in-use inode 2147483825 is free, would correct imap imap claims in-use inode 2147483826 is free, would correct imap imap claims in-use inode 2147483827 is free, would correct imap imap claims in-use inode 2147483828 is free, would correct imap imap claims in-use inode 2147483829 is free, would correct imap imap claims in-use inode 2147483830 is free, would correct imap imap claims in-use inode 2147483831 is free, would correct imap imap claims in-use inode 2147483832 is free, would correct imap imap claims in-use inode 2147483833 is free, would correct imap imap claims in-use inode 2147483834 is free, would correct imap imap claims in-use inode 2147483835 is free, would correct imap imap claims in-use inode 2147483836 is free, would correct imap imap claims in-use inode 2147483837 is free, would correct imap imap claims in-use inode 2147483838 is free, would correct imap imap claims in-use inode 2147483839 is free, would correct imap imap claims in-use inode 2499363777 is free, would correct imap imap claims in-use inode 2499363778 is free, would correct imap imap claims in-use inode 2499363779 is free, would correct imap imap claims in-use inode 2499363780 is free, would correct imap imap claims in-use inode 2625250817 is free, would correct imap imap claims in-use inode 2625250818 is free, would correct imap imap claims in-use inode 2625250819 is free, would correct imap imap claims in-use inode 2625250820 is free, would correct imap imap claims in-use inode 2625250821 is free, would correct imap imap claims in-use inode 2625250822 is free, would correct imap imap claims in-use inode 2625250823 is free, would correct imap imap claims in-use inode 2625250824 is free, would correct imap imap claims in-use inode 2625250825 is free, would correct imap imap claims in-use inode 2625250826 is free, would correct imap imap claims in-use inode 2625250827 is free, would correct imap imap claims in-use inode 2625250828 is free, would correct imap imap claims in-use inode 2625250829 is free, would correct imap imap claims in-use inode 2625250830 is free, would correct imap imap claims in-use inode 2625250831 is free, would correct imap imap claims in-use inode 2625250832 is free, would correct imap imap claims in-use inode 2625250833 is free, would correct imap imap claims in-use inode 2625250834 is free, would correct imap imap claims in-use inode 2625250835 is free, would correct imap imap claims in-use inode 2625250836 is free, would correct imap imap claims in-use inode 2625250837 is free, would correct imap imap claims in-use inode 2625250838 is free, would correct imap imap claims in-use inode 2625250839 is free, would correct imap imap claims in-use inode 2625250840 is free, would correct imap imap claims in-use inode 2625250841 is free, would correct imap imap claims in-use inode 2625250842 is free, would correct imap imap claims in-use inode 2625250843 is free, would correct imap imap claims in-use inode 2625250844 is free, would correct imap imap claims in-use inode 2625250845 is free, would correct imap imap claims in-use inode 2625250846 is free, would correct imap imap claims in-use inode 2625250847 is free, would correct imap imap claims in-use inode 2625250848 is free, would correct imap imap claims in-use inode 2625250849 is free, would correct imap imap claims in-use inode 2625250850 is free, would correct imap imap claims in-use inode 2625250852 is free, would correct imap imap claims in-use inode 2625250853 is free, would correct imap imap claims in-use inode 2625250854 is free, would correct imap imap claims in-use inode 2625250855 is free, would correct imap imap claims in-use inode 2625250856 is free, would correct imap imap claims in-use inode 2625250857 is free, would correct imap imap claims in-use inode 2625250858 is free, would correct imap imap claims in-use inode 2625250859 is free, would correct imap imap claims in-use inode 2625250860 is free, would correct imap imap claims in-use inode 2625250861 is free, would correct imap imap claims in-use inode 2625250862 is free, would correct imap imap claims in-use inode 2625250863 is free, would correct imap imap claims in-use inode 2625250864 is free, would correct imap imap claims in-use inode 2625250865 is free, would correct imap imap claims in-use inode 2625250866 is free, would correct imap imap claims in-use inode 2625250867 is free, would correct imap imap claims in-use inode 2625250868 is free, would correct imap imap claims in-use inode 2625250869 is free, would correct imap imap claims in-use inode 2625250870 is free, would correct imap imap claims in-use inode 2625250871 is free, would correct imap imap claims in-use inode 2625250873 is free, would correct imap imap claims in-use inode 2625250874 is free, would correct imap imap claims in-use inode 2625250875 is free, would correct imap imap claims in-use inode 2625250876 is free, would correct imap imap claims in-use inode 2625250877 is free, would correct imap imap claims in-use inode 2625250878 is free, would correct imap imap claims in-use inode 2625250879 is free, would correct imap imap claims in-use inode 2698601153 is free, would correct imap imap claims in-use inode 2698601154 is free, would correct imap imap claims in-use inode 2698601159 is free, would correct imap imap claims in-use inode 2698601163 is free, would correct imap imap claims in-use inode 2698601168 is free, would correct imap imap claims in-use inode 2698601172 is free, would correct imap imap claims in-use inode 2698601175 is free, would correct imap imap claims in-use inode 2698601179 is free, would correct imap imap claims in-use inode 2698601184 is free, would correct imap imap claims in-use inode 2698601192 is free, would correct imap imap claims in-use inode 2698601194 is free, would correct imap imap claims in-use inode 2698601198 is free, would correct imap imap claims in-use inode 2698601201 is free, would correct imap imap claims in-use inode 2698601202 is free, would correct imap imap claims in-use inode 2698601203 is free, would correct imap imap claims in-use inode 2698601204 is free, would correct imap imap claims in-use inode 2698601205 is free, would correct imap imap claims in-use inode 2698601206 is free, would correct imap imap claims in-use inode 2698601207 is free, would correct imap imap claims in-use inode 2698601208 is free, would correct imap imap claims in-use inode 2698601209 is free, would correct imap imap claims in-use inode 2698601210 is free, would correct imap imap claims in-use inode 2698601211 is free, would correct imap imap claims in-use inode 2698601212 is free, would correct imap imap claims in-use inode 2698601214 is free, would correct imap imap claims in-use inode 2698601215 is free, would correct imap imap claims in-use inode 2795108225 is free, would correct imap imap claims in-use inode 2795108226 is free, would correct imap imap claims in-use inode 2795108227 is free, would correct imap imap claims in-use inode 2795108228 is free, would correct imap imap claims in-use inode 2795108229 is free, would correct imap imap claims in-use inode 2795108230 is free, would correct imap imap claims in-use inode 2795108231 is free, would correct imap imap claims in-use inode 2795108232 is free, would correct imap imap claims in-use inode 2795108233 is free, would correct imap imap claims in-use inode 2795108234 is free, would correct imap imap claims in-use inode 2795108240 is free, would correct imap imap claims in-use inode 2795108241 is free, would correct imap imap claims in-use inode 2795108246 is free, would correct imap imap claims in-use inode 2795108248 is free, would correct imap imap claims in-use inode 2795108249 is free, would correct imap imap claims in-use inode 2795108250 is free, would correct imap imap claims in-use inode 2795108253 is free, would correct imap imap claims in-use inode 2795108257 is free, would correct imap imap claims in-use inode 2795108266 is free, would correct imap imap claims in-use inode 2795108268 is free, would correct imap imap claims in-use inode 2795108273 is free, would correct imap imap claims in-use inode 2795108280 is free, would correct imap imap claims in-use inode 2795108281 is free, would correct imap imap claims in-use inode 2795108284 is free, would correct imap imap claims a free inode 2795118784 is in use, would correct imap and clear inode imap claims in-use inode 2795118787 is free, would correct imap imap claims in-use inode 2795118791 is free, would correct imap imap claims in-use inode 2795118796 is free, would correct imap imap claims in-use inode 2795118800 is free, would correct imap imap claims in-use inode 2795118806 is free, would correct imap imap claims in-use inode 2795118811 is free, would correct imap imap claims in-use inode 2795118814 is free, would correct imap imap claims in-use inode 2795118817 is free, would correct imap imap claims in-use inode 2795118820 is free, would correct imap imap claims in-use inode 2795118825 is free, would correct imap imap claims in-use inode 2795118829 is free, would correct imap imap claims in-use inode 2795118833 is free, would correct imap imap claims in-use inode 2795118838 is free, would correct imap imap claims in-use inode 2795118842 is free, would correct imap imap claims in-use inode 2795118846 is free, would correct imap imap claims a free inode 2795127104 is in use, would correct imap and clear inode imap claims in-use inode 2795127105 is free, would correct imap imap claims in-use inode 2795127109 is free, would correct imap imap claims in-use inode 2795127114 is free, would correct imap imap claims in-use inode 2795127117 is free, would correct imap imap claims in-use inode 2795127121 is free, would correct imap imap claims in-use inode 2795127122 is free, would correct imap imap claims in-use inode 2795127124 is free, would correct imap imap claims in-use inode 2795127129 is free, would correct imap imap claims in-use inode 2795127134 is free, would correct imap imap claims in-use inode 2795127138 is free, would correct imap imap claims in-use inode 2795127141 is free, would correct imap imap claims in-use inode 2795127145 is free, would correct imap imap claims in-use inode 2795127147 is free, would correct imap imap claims in-use inode 2795127152 is free, would correct imap imap claims in-use inode 2795127159 is free, would correct imap imap claims in-use inode 2795127161 is free, would correct imap imap claims in-use inode 2795127166 is free, would correct imap imap claims a free inode 2795135552 is in use, would correct imap and clear inode imap claims in-use inode 2795135553 is free, would correct imap imap claims in-use inode 2795135557 is free, would correct imap imap claims in-use inode 2795135561 is free, would correct imap imap claims in-use inode 2795135565 is free, would correct imap imap claims in-use inode 2795135570 is free, would correct imap imap claims in-use inode 2795135577 is free, would correct imap imap claims in-use inode 2795135581 is free, would correct imap imap claims in-use inode 2795135586 is free, would correct imap imap claims in-use inode 2795135591 is free, would correct imap imap claims in-use inode 2795135592 is free, would correct imap imap claims in-use inode 2795135594 is free, would correct imap imap claims in-use inode 2795135597 is free, would correct imap imap claims in-use inode 2795135601 is free, would correct imap imap claims in-use inode 2795135603 is free, would correct imap imap claims in-use inode 2795135613 is free, would correct imap imap claims a free inode 2795143104 is in use, would correct imap and clear inode imap claims in-use inode 2795143105 is free, would correct imap imap claims in-use inode 2795143108 is free, would correct imap imap claims in-use inode 2795143113 is free, would correct imap imap claims in-use inode 2795143117 is free, would correct imap imap claims in-use inode 2795143122 is free, would correct imap imap claims in-use inode 2795143127 is free, would correct imap imap claims in-use inode 2795143129 is free, would correct imap imap claims in-use inode 2795143131 is free, would correct imap imap claims in-use inode 2795143134 is free, would correct imap imap claims in-use inode 2795143142 is free, would correct imap imap claims in-use inode 2795143146 is free, would correct imap imap claims in-use inode 2795143150 is free, would correct imap imap claims in-use inode 2795143155 is free, would correct imap imap claims in-use inode 2795143156 is free, would correct imap imap claims in-use inode 2795143158 is free, would correct imap imap claims in-use inode 2795143163 is free, would correct imap imap claims in-use inode 2830971202 is free, would correct imap imap claims in-use inode 2830971204 is free, would correct imap imap claims in-use inode 2830971207 is free, would correct imap imap claims in-use inode 2830971208 is free, would correct imap imap claims in-use inode 2830971210 is free, would correct imap imap claims in-use inode 2830971213 is free, would correct imap imap claims in-use inode 2830971214 is free, would correct imap imap claims in-use inode 2830971216 is free, would correct imap imap claims in-use inode 2830971226 is free, would correct imap imap claims in-use inode 2830971229 is free, would correct imap imap claims in-use inode 2830971235 is free, would correct imap imap claims in-use inode 2830971237 is free, would correct imap imap claims in-use inode 2830971244 is free, would correct imap imap claims in-use inode 2830971248 is free, would correct imap imap claims in-use inode 2830971251 is free, would correct imap imap claims in-use inode 2830971255 is free, would correct imap imap claims in-use inode 2830971260 is free, would correct imap imap claims in-use inode 2830978882 is free, would correct imap imap claims in-use inode 2830978883 is free, would correct imap imap claims in-use inode 2830978886 is free, would correct imap imap claims in-use inode 2830978889 is free, would correct imap imap claims in-use inode 2830978891 is free, would correct imap imap claims in-use inode 2830978894 is free, would correct imap imap claims in-use inode 2830978899 is free, would correct imap imap claims in-use inode 2830978900 is free, would correct imap imap claims in-use inode 2830978901 is free, would correct imap imap claims in-use inode 2830978906 is free, would correct imap imap claims in-use inode 2830978910 is free, would correct imap imap claims in-use inode 2830978913 is free, would correct imap imap claims in-use inode 2830978917 is free, would correct imap imap claims in-use inode 2830978921 is free, would correct imap imap claims in-use inode 2830978922 is free, would correct imap imap claims in-use inode 2830978923 is free, would correct imap imap claims in-use inode 2830978924 is free, would correct imap imap claims in-use inode 2830978925 is free, would correct imap imap claims in-use inode 2830978926 is free, would correct imap imap claims in-use inode 2830978927 is free, would correct imap imap claims in-use inode 2830978928 is free, would correct imap imap claims in-use inode 2830978929 is free, would correct imap imap claims in-use inode 2830978930 is free, would correct imap imap claims in-use inode 2830978931 is free, would correct imap imap claims in-use inode 2830978932 is free, would correct imap imap claims in-use inode 2830978933 is free, would correct imap imap claims in-use inode 2830978934 is free, would correct imap imap claims in-use inode 2830978935 is free, would correct imap imap claims in-use inode 2830978937 is free, would correct imap imap claims in-use inode 2830978938 is free, would correct imap imap claims in-use inode 2830978940 is free, would correct imap imap claims in-use inode 2830978941 is free, would correct imap imap claims in-use inode 2830978942 is free, would correct imap imap claims in-use inode 3032147329 is free, would correct imap imap claims in-use inode 3032147330 is free, would correct imap imap claims in-use inode 3032147331 is free, would correct imap imap claims in-use inode 3032147332 is free, would correct imap imap claims in-use inode 3032147333 is free, would correct imap imap claims in-use inode 3032147334 is free, would correct imap imap claims in-use inode 3032147335 is free, would correct imap imap claims in-use inode 3032147336 is free, would correct imap imap claims in-use inode 3032147337 is free, would correct imap imap claims in-use inode 3032147338 is free, would correct imap imap claims in-use inode 3032147339 is free, would correct imap imap claims in-use inode 3032147340 is free, would correct imap imap claims in-use inode 3032147341 is free, would correct imap imap claims in-use inode 3032147342 is free, would correct imap imap claims in-use inode 3032147343 is free, would correct imap imap claims in-use inode 3032147344 is free, would correct imap imap claims in-use inode 3032147345 is free, would correct imap imap claims in-use inode 3032147346 is free, would correct imap imap claims in-use inode 3032147347 is free, would correct imap imap claims in-use inode 3032147348 is free, would correct imap imap claims in-use inode 3032147349 is free, would correct imap imap claims in-use inode 3032147350 is free, would correct imap imap claims in-use inode 3032147351 is free, would correct imap imap claims in-use inode 3032147352 is free, would correct imap imap claims in-use inode 3032147353 is free, would correct imap imap claims in-use inode 3032147354 is free, would correct imap imap claims in-use inode 3032147355 is free, would correct imap imap claims in-use inode 3032147356 is free, would correct imap imap claims in-use inode 3032147357 is free, would correct imap imap claims in-use inode 3032147358 is free, would correct imap imap claims in-use inode 3032147359 is free, would correct imap imap claims in-use inode 3032147360 is free, would correct imap imap claims in-use inode 3032147361 is free, would correct imap imap claims in-use inode 3032147362 is free, would correct imap imap claims in-use inode 3032147363 is free, would correct imap imap claims in-use inode 3032147364 is free, would correct imap imap claims in-use inode 3032147365 is free, would correct imap imap claims in-use inode 3032147366 is free, would correct imap imap claims in-use inode 3032147367 is free, would correct imap imap claims in-use inode 3032147368 is free, would correct imap imap claims in-use inode 3032147369 is free, would correct imap imap claims in-use inode 3032147371 is free, would correct imap imap claims in-use inode 3032147372 is free, would correct imap imap claims in-use inode 3032147373 is free, would correct imap imap claims in-use inode 3032147374 is free, would correct imap imap claims in-use inode 3032147375 is free, would correct imap imap claims in-use inode 3032147376 is free, would correct imap imap claims in-use inode 3032147377 is free, would correct imap imap claims in-use inode 3032147378 is free, would correct imap imap claims in-use inode 3032147379 is free, would correct imap imap claims in-use inode 3032147380 is free, would correct imap imap claims in-use inode 3032147381 is free, would correct imap imap claims in-use inode 3032147382 is free, would correct imap imap claims in-use inode 3032147383 is free, would correct imap imap claims in-use inode 3032147384 is free, would correct imap imap claims in-use inode 3032147385 is free, would correct imap imap claims in-use inode 3032147386 is free, would correct imap imap claims in-use inode 3032147387 is free, would correct imap imap claims in-use inode 3032147388 is free, would correct imap imap claims in-use inode 3032147389 is free, would correct imap imap claims in-use inode 3032147390 is free, would correct imap imap claims in-use inode 3032147391 is free, would correct imap imap claims in-use inode 3128968705 is free, would correct imap imap claims in-use inode 3128968706 is free, would correct imap imap claims in-use inode 3128968707 is free, would correct imap imap claims in-use inode 3128968708 is free, would correct imap imap claims in-use inode 3128968709 is free, would correct imap imap claims in-use inode 3128968710 is free, would correct imap imap claims in-use inode 3128968711 is free, would correct imap imap claims in-use inode 3128968712 is free, would correct imap imap claims in-use inode 3128968713 is free, would correct imap imap claims in-use inode 3128968714 is free, would correct imap imap claims in-use inode 3128968715 is free, would correct imap imap claims in-use inode 3128968716 is free, would correct imap imap claims in-use inode 3128968717 is free, would correct imap imap claims in-use inode 3128968718 is free, would correct imap imap claims in-use inode 3128968719 is free, would correct imap imap claims in-use inode 3128968720 is free, would correct imap imap claims in-use inode 3128968721 is free, would correct imap imap claims in-use inode 3128968722 is free, would correct imap imap claims in-use inode 3128968723 is free, would correct imap imap claims in-use inode 3128968724 is free, would correct imap imap claims in-use inode 3128968725 is free, would correct imap imap claims in-use inode 3128968726 is free, would correct imap imap claims in-use inode 3128968727 is free, would correct imap imap claims in-use inode 3128968728 is free, would correct imap imap claims in-use inode 3128968729 is free, would correct imap imap claims in-use inode 3128968730 is free, would correct imap imap claims in-use inode 3128968731 is free, would correct imap imap claims in-use inode 3128968732 is free, would correct imap imap claims in-use inode 3128968733 is free, would correct imap imap claims in-use inode 3128968734 is free, would correct imap imap claims in-use inode 3128968735 is free, would correct imap imap claims in-use inode 3128968736 is free, would correct imap imap claims in-use inode 3128968737 is free, would correct imap imap claims in-use inode 3128968738 is free, would correct imap imap claims in-use inode 3128968740 is free, would correct imap imap claims in-use inode 3128968741 is free, would correct imap imap claims in-use inode 3128968742 is free, would correct imap imap claims in-use inode 3128968743 is free, would correct imap imap claims in-use inode 3128968744 is free, would correct imap imap claims in-use inode 3128968745 is free, would correct imap imap claims in-use inode 3128968746 is free, would correct imap imap claims in-use inode 3128968747 is free, would correct imap imap claims in-use inode 3128968748 is free, would correct imap imap claims in-use inode 3128968749 is free, would correct imap imap claims in-use inode 3128968750 is free, would correct imap imap claims in-use inode 3128968751 is free, would correct imap imap claims in-use inode 3128968752 is free, would correct imap imap claims in-use inode 3128968753 is free, would correct imap imap claims in-use inode 3128968754 is free, would correct imap imap claims in-use inode 3128968755 is free, would correct imap imap claims in-use inode 3128968756 is free, would correct imap imap claims in-use inode 3128968757 is free, would correct imap imap claims in-use inode 3128968758 is free, would correct imap imap claims in-use inode 3128968759 is free, would correct imap imap claims in-use inode 3128968760 is free, would correct imap imap claims in-use inode 3128968761 is free, would correct imap imap claims in-use inode 3128968762 is free, would correct imap imap claims in-use inode 3128968763 is free, would correct imap imap claims in-use inode 3128968764 is free, would correct imap imap claims in-use inode 3128968765 is free, would correct imap imap claims in-use inode 3128968766 is free, would correct imap imap claims in-use inode 3128968767 is free, would correct imap - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 xfs_repair: read failed: Input/output error cannot read inode 13377452416, disk block 13377452368, cnt 32 Â I attached new diagnostic and also pics of disk5. Â Can this be related to my issue?. Like i said, i haven't done anything different, and sometimes i would get some read error in any a different disk, would restart or change sata and i would stop getting any problem. Never had a share disappear plex-diagnostics-20240531-1928.zip Quote
JorgeB Posted June 1 Posted June 1 Disk5 appears to be failing, run an extended SMART test to confirm. Quote
JuacOHI Posted June 1 Author Posted June 1 I 6 hours ago, JorgeB said: Disk5 appears to be failing, run an extended SMART test to confirm. If i do a short or extended test it says: Completed: read failure  ATA Error Count: 320 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 320 occurred at disk power-on lifetime: 2758 hours (114 days + 22 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 20 ff ff ff 4f 00 14:54:34.508 READ FPDMA QUEUED b0 d1 01 01 4f c2 00 00 14:54:14.162 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 00 14:54:14.159 SMART READ DATA ec 00 01 00 00 00 00 00 14:54:14.151 IDENTIFY DEVICE ec 00 01 00 00 00 00 00 14:54:14.151 IDENTIFY DEVICE Error 319 occurred at disk power-on lifetime: 2758 hours (114 days + 22 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 20 ff ff ff 4f 00 14:18:46.821 READ FPDMA QUEUED 60 00 30 ff ff ff 4f 00 14:18:45.727 READ FPDMA QUEUED 60 00 18 ff ff ff 4f 00 14:18:45.709 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 14:18:45.708 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 14:18:45.707 READ FPDMA QUEUED Error 318 occurred at disk power-on lifetime: 2757 hours (114 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 20 ff ff ff 4f 00 14:12:54.160 READ FPDMA QUEUED b0 d1 01 01 4f c2 00 00 14:12:46.406 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 00 14:12:46.402 SMART READ DATA ec 00 01 00 00 00 00 00 14:12:46.394 IDENTIFY DEVICE ec 00 01 00 00 00 00 00 14:12:46.393 IDENTIFY DEVICE Error 317 occurred at disk power-on lifetime: 2757 hours (114 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 20 ff ff ff 4f 00 14:09:18.563 READ FPDMA QUEUED 60 00 30 ff ff ff 4f 00 14:09:18.093 READ FPDMA QUEUED 60 00 18 ff ff ff 4f 00 14:09:18.091 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 14:09:18.091 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 14:09:18.090 READ FPDMA QUEUED Error 316 occurred at disk power-on lifetime: 2757 hours (114 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 20 ff ff ff 4f 00 14:06:20.637 READ FPDMA QUEUED b0 d1 01 01 4f c2 00 00 14:06:03.973 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 00 14:06:03.970 SMART READ DATA ec 00 01 00 00 00 00 00 14:06:03.960 IDENTIFY DEVICE ec 00 01 00 00 00 00 00 14:06:03.959 IDENTIFY DEVICE  plex-smart-20240601-1016.zip Quote
JuacOHI Posted June 1 Author Posted June 1 Btw, i never got errors on disk5 before the problem happened, not sure if disk5 failing caused the share to disappear or the other way around, if the share disappearing for some random reason its making the disk5 have the read errors because isn't showing properly Quote
itimpi Posted June 1 Posted June 1 That drive looks as if it is on its last legs as it appears to have a large (and increasing) number of reallocated sectors so should be replaced ASAP.  It is most likely that problems with that drive is what caused the share to disappear if the share in question had any of its content on that drive. Quote
JuacOHI Posted June 1 Author Posted June 1 1 hour ago, itimpi said: That drive looks as if it is on its last legs as it appears to have a large (and increasing) number of reallocated sectors so should be replaced ASAP.  It is most likely that problems with that drive is what caused the share to disappear if the share in question had any of its content on that drive. Its a "new" hard drive, literally couple months only, and i actually replaced an old one with this one.  My fear is if i replace the disk5 that is giving me red errors, i might fuck up even more the share movies or it won't fix the actual problem that the fiels disappeared of the share Quote
JorgeB Posted June 2 Posted June 2 Disk5 need to be replaced since it failed the SMART test, problem is that you already have a disabled disk and only one parity, you can try rebuilding disk4 first, but there may be rebuilt with some corruptions because of the disk5 read errors during the rebuild, but not many other options, and once that's done you nee to replace disk5. Quote
JuacOHI Posted June 2 Author Posted June 2 7 hours ago, JorgeB said: Disk5 need to be replaced since it failed the SMART test, problem is that you already have a disabled disk and only one parity, you can try rebuilding disk4 first, but there may be rebuilt with some corruptions because of the disk5 read errors during the rebuild, but not many other options, and once that's done you nee to replace disk5. I understand and i will take the lose if is needed. Â What if this still doesn't fix the issue of the share ? is there a command or something that would move the files of the share to another share ? Quote
JorgeB Posted June 3 Posted June 3 First you need to resolve the disk issues, since they can be causing the filesystem problem, since the emulated disk cannot be 100% emulated. Quote
JuacOHI Posted June 29 Author Posted June 29 Hello. Sorry for not answering before, but i had to buy new hard drives and i also replaced all my cables for a better brand (cable matters) Â After changing cables, i rebuilt my array assigning the disk 4 that was missing (for cable errors). After it was done the share Movies its showing again. Like i said in my previous posts, i was running this Plex Server without the disk 4 for some time (a month or so), so this wasn't the particular problem, and like i said a couple times, the issue happened from one second to another while i was using the server and it was up and running with no issues. Â Now, clearly the disk 5 has problems so now i will replace that disk. I just wanted to give an update for my problem. plex-diagnostics-20240629-1243.zip Quote
JorgeB Posted June 30 Posted June 30 16 hours ago, JuacOHI said: Now, clearly the disk 5 has problems so now i will replace that disk. Yep, has mentioned that disk is failing the SMART test, so it need to be replaced. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.