October 26, 20214 yr Got a messgage in "Fix Common Problems" saying "Unable to write to disk2". Disk on main shows green. I've attached the smart report but I have no idea what I'm looking at or for to resolve the issue. These two files are of the same HD just at different times. I also attached the server diagnostics ST4000DM004-2CV104_WFN07L1M-20211026-1427.txt ST4000DM004-2CV104_WFN07L1M-20211026-1641.txt tower-diagnostics-20211026-1649.zip
October 27, 20214 yr Author Running the xfs_repair, I get the following message Quote Phase 1 - find and verify superblock... - block cache size set to 720848 entries Phase 2 - using internal log - zero log... zero_log: head block 2411715 tail block 2411503 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. I'm not sure how to proceed
October 28, 20214 yr Author 17 hours ago, trurl said: both, be sure to capture the output so you can post it I didn't capture the output. Is it contain in a log somewhere?
December 21, 20214 yr Author After fixing my HD issues, well I think I did, I got another read error from FCP. Please see attached extended SMART report and diagnostics. If I need to replace the dive I have another available an my parity is valid. Is it possible I have a bad cable? tower-smart-20211221-1709.zip tower-diagnostics-20211221-1739.zip
December 22, 20214 yr 8 hours ago, sgt_spike said: I got another read error from FCP Not sure what the issue with FCP is, you log is spammed by : Dec 19 07:22:13 Tower emhttpd: error: get_fs_sizes, 5903: Input/output error (5): statfs: /mnt/user/KEEP Dec 19 07:22:13 Tower emhttpd: error: get_fs_sizes, 5903: Input/output error (5): statfs: /mnt/user/Users Storage and to a lesser extent by : Dec 21 17:37:47 Tower smbd[1109]: [2021/12/21 17:37:47.996296, 0] ../../source3/smbd/service.c:841(make_connection_snum) Dec 21 17:37:47 Tower smbd[1109]: make_connection_snum: '/mnt/user/HTML' does not exist or permission denied when connecting to [HTML] Error was Input/output error I'd say reboot, manually run FCP and grab new diagnostics.
December 22, 20214 yr Author 5 hours ago, ChatNoir said: Not sure what the issue with FCP is, you log is spammed by : Dec 19 07:22:13 Tower emhttpd: error: get_fs_sizes, 5903: Input/output error (5): statfs: /mnt/user/KEEP Dec 19 07:22:13 Tower emhttpd: error: get_fs_sizes, 5903: Input/output error (5): statfs: /mnt/user/Users Storage and to a lesser extent by : Dec 21 17:37:47 Tower smbd[1109]: [2021/12/21 17:37:47.996296, 0] ../../source3/smbd/service.c:841(make_connection_snum) Dec 21 17:37:47 Tower smbd[1109]: make_connection_snum: '/mnt/user/HTML' does not exist or permission denied when connecting to [HTML] Error was Input/output error I'd say reboot, manually run FCP and grab new diagnostics. I'm not sure what you mean by spammed. I ran an extended test in FCP and got what you see in the attached jpg. Now the HD is disabled and contents emulated (I understand what that means). The syslog does show those same errors you mentioned along with "Dec 22 07:15:01 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO". I'm not sure what that means either. How can I convert a drive to SG_IO? Reading through the wiki on replacing HDs now. tower-syslog-20211222-0720.zip
December 29, 20214 yr Author I had t o replace my drive as it finally failed. I was able to rebuild from parity but I seem to have a couple of issues. 1. FCP is reporting /var/log is getting full (currently 100 % used) - Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem, but ideally you should seek assistance in the forums and post your. 2. The disk is showing the files but one particular share isn't showing the files in a specific folder. It only show "No listing: Too many files". But again those files show up on the disk in that specific folder. How does the share have different views? Could both issues be related? I post attached my Diagnostics as mention in the FCP issue tower-diagnostics-20211229-1238.zip
December 29, 20214 yr Author 1 minute ago, JorgeB said: Check filesystem on disk2. This should solve my issues?
December 29, 20214 yr Author Attached is the results for the check disk. I don't see any recommendations in the report. If files are to be moved to lost+found, do I move them back? I'm not sure what to do at this point ChectDisk2Report.txt
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.