mikesp18

Members
  • Content Count

    83
  • Joined

  • Last visited

Community Reputation

6 Neutral

About mikesp18

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks, Jorge. I had another crash while I was at work. I'll upload it in the morning. I had enabled a system log but had it writing to a local file and backing it up every 10 minutes. I was worried that backing it up to the flash drive would write too much data. Is that really an issue? Do I need to take the file off of the flash drive before I restart unRAID? If I restart the system will it overwrite the existing log file? Just curious about the order that I should do things.
  2. I am starting to get frequent problems with Unraid. It always seems to happen in the middle of the night, or when I'm at work. It's frustrating when the wife and kids complain when I get out of work and I have to try to trouble shoot. So, help me with my marriage. I'm attaching dianostics, and syslog. The system was up and running around 03:00am local, and was problematic when I notices around 14:00 local. The screen GUI was up on the local box but unresponsive. SSH was not working. WebGui was not working. I did have a drive problem yesterday that was so
  3. Phase 1 - find and verify superblock... - block cache size set to 3012408 entries Phase 2 - using internal log - zero log... zero_log: head block 578753 tail block 574745 ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... invalid start block 2690876492 in record 46 of bno btree block 4/44382387 agi unlinked bucket 4 is 386238468 in ag 4 (inode=8976173060) sb_icount 299168, counted 290912 sb_ifree 8198, counted 14220 sb_fdblocks 598797622, counted 631121483
  4. Phase 1 - find and verify superblock... - block cache size set to 3012408 entries Phase 2 - using internal log - zero log... zero_log: head block 578753 tail block 574745 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. This is the ou
  5. Phase 1 - find and verify superblock... - block cache size set to 3012408 entries Phase 2 - using internal log - zero log... zero_log: head block 578753 tail block 574745 ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... invalid start block 2690876492 in record 46 of bno btree block 4/44382387 agi unlinked bucket 4 is 386238468 in ag 4 (inode=8976173060)
  6. I removed a share and then tried to add a new one. My system log started throwing many errors such as I stopped the array and restarted it. Now under the Array Operations on the Main tab, I see It is giving me the option to format that drive as it is unmountable. This drive was working fine a few seconds prior. Any ideas? I have seen some UDMA_CRC errors on this drive before, but it is a relatively new drive (I seem to frequently get UDMA_CRC errors despite checking and replacing SATA cables). Before I do something stupid like resetting the server, could you guys look a
  7. One more question. In the past, I've used the Minecraft Server console via putty with the following command as per the documentation faqs. However, now I get an error message. It was making it difficult to work out a previous problem. How can I correct this? The result:
  8. That worked. Thank you, sir. For reference if others are looking, here is the successful log line.
  9. Sorry to pester I have the JAVA_VERSION: variable set to 16 However, when I start up the docker after the most recent update, I notice this in supervisord.log JAVA_VERSION not defined,(via -e JAVA_VERSION), defaulting to '8' I'm currently getting a connection refused message in the minecraft app. I wonder if this is why.
  10. Thank you for the hard work on this. I just wanted to confirm what you have been saying. In the latest release of UD, we should be able to leave cache enabled or hard links enable on the remote share as long as the mount is SMB. However, NFS shares cannot have cache enabled. Can cache be left enabled under NFS if hard links are disabled? I believe that I tried this scenario and still had problems.
  11. Any new ideas on the UD SMB and NFS shares dropping to OB still. My Sonarr docker is unusable. Very frustrating since it worked for a year just fine. Attached is doagnostics right after the drop out. As soon as a start a transfer, the event happens. grond-diagnostics-20210501-1246.zip
  12. I've been getting repeat crashes on a Unraid installation that had been stable to over a year. What's best way to download diagnostics if the system has already crashed. I could not SSH into it. The web interface gave no response. Lights were on, but nobody home. After the reset, the diagnostics are new.
  13. Well, it got to the point of crashing Unraid. I had to hard reset Unraid. Uninstall UD. I did try to reinstall it today, and remount the NFS shares. Same thing, dropping mount down to 0, and tons of errors in the log, same as before fileid_changed. grond-diagnostics-20210420-2339.zip I deleted the NFS mounts, and tried out SMB UD mounts. No errors so far.
  14. Well, I'm assuming that the update is related to this. My log just went to 90%. I'll attach the log. I have a lot of these errors: "Apr 18 23:52:10 Grond kernel: NFS: server 192.168.86.113 error: fileid changed" grond-diagnostics-20210419-1414.zip