Cyberalien

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by Cyberalien

  1. I followed your method and now everything is back to normal. Thank you.
  2. hello all ; The server has been running stably for 5 years, and we've never encountered such an issue before. Last year, we installed a caching hard drive, model = Crucial1t CT1000MX500SSD1. Occasionally during operation, there were errors reported indicating some value errors, but they would quickly return to normal afterward. Recently, we found that Docker couldn't be updated , with the error message - --》 "Error: failed to register layer: Failed to create btrfs snapshot: input/output error". My Docker is hosted on the SSD caching hard drive, and even restarting the server couldn't resolve the issue. after that error, I also found error on log : Apr 15 14:52:15 Tower kernel: loop: Write error at byte offset 1317928960, length 4096. Apr 15 14:52:15 Tower kernel: I/O error, dev loop2, sector 2574080 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Apr 15 14:52:15 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Apr 15 14:52:15 Tower kernel: loop: Write error at byte offset 1317994496, length 4096. Apr 15 14:52:15 Tower kernel: I/O error, dev loop2, sector 2574208 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Apr 15 14:52:15 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Apr 15 14:52:15 Tower kernel: loop: Write error at byte offset 1318027264, length 4096. Apr 15 14:52:15 Tower kernel: I/O error, dev loop2, sector 2574272 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Apr 15 14:52:15 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Apr 15 14:52:15 Tower kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction) Apr 15 14:52:15 Tower kernel: BTRFS info (device loop2: state E): forced readonly Apr 15 14:52:15 Tower kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction. Apr 15 14:52:15 Tower kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1992: errno=-5 IO failure the docker also can't start . after the reboot the malfunction persisted.。 what can I do now ?
  3. The latest update: After a power outage restart, all files reappeared, but the same error messages continue to pop up. Could you please advise on what the issue might be?
  4. Hello everyone, Today, after discovering that all the data I downloaded within the past two months (including the movie I was watching the night before) was gone, I found the following log information on my server. Can anyone tell me what happened? Did my SSD fail, or was it a case of intrusion? The main storage for the downloaded movies is an SSD, while the secondary storage is an array, and the data movement direction is from SSD to the array. Why would the data disappear? Even some VM ISO files are reported as unreadable. Please help take a look, thank you. Mar 8 15:05:40 Tower nginx: 2024/03/08 15:05:40 [error] 19046#19046: *2958663 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.12, server: , request: "POST /plugins/dynamix.my.servers/include/unraid-api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.5", referrer: "https://192.168.1.5/Dashboard" Mar 8 15:05:40 Tower nginx: 2024/03/08 15:05:40 [error] 19046#19046: *2958663 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.12, server: , request: "POST /plugins/dynamix.my.servers/include/unraid-api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.5", referrer: "https://192.168.15/Dashboard" Mar 8 15:05:46 Tower nginx: 2024/03/08 15:05:46 [error] 19046#19046: *2958663 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.12, server: , request: "POST /plugins/dynamix.my.servers/include/unraid-api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.5", referrer: "https://192.168.1.5/Dashboard"
  5. hello I run clamav it shows 2019-10-03T08:39:17+0000 ClamAV scanning started Updating ClamAV scan DB Hint: The database directory must be writable for UID 100 or GID 101 ERROR: Can't create temporary directory /var/lib/clamav/clamav-435ac426ce5c25f4c347d7759f496c54.tmp An error occurred (freshclam returned with exit code '57') It works fine a few months ago and I dont know what happend , I check the unraid and have't found the user id is 100 , what should I do with it ? thank u
  6. After read your reply , I upgrade system to 6.7 and reconfig the network.cfg in the /config folder in usb stick then I reboot the system . the system can access the internet now . Thank you all .
  7. same question. Server cannot access the internet. I ping the local network is fine ,but cannot ping the ip address outside like 8.8.8.8, it says system error. the dock and vm network is fine . so now I roll it back to 6.6.7 how I can fix this ? check the diagnostics.zip ?