Jump to content
LAST CALL on the Unraid Summer Sale! 😎 ⌛ ×

ChatNoir

Moderators
  • Posts

    3,807
  • Joined

  • Last visited

  • Days Won

    9

ChatNoir last won the day on December 2 2023

ChatNoir had the most liked content!

2 Followers

About ChatNoir

  • Birthday January 8

Retained

  • Member Title
    Not so Advanced Member

Converted

  • Location
    France

Recent Profile Visitors

10,694 profile views

ChatNoir's Achievements

Experienced

Experienced (11/14)

762

Reputation

91

Community Answers

  1. I do not follow many threads, but I do receive notification from subforums and new users posts (moderators thing I guess). You probably already checked your spam folder on yahoo ? It still works fine with hotmail.com (barely more hyped provider )
  2. @meiee if it happens often, and you need support to fix that, you should create a new thread in general support with details and your diagnostics. https://forums.unraid.net/forum/55-general-support/
  3. Not available in the archive https://docs.unraid.net/unraid-os/download_list/ But why not 6.12.13 ?
  4. Don't know about this specific model, but there are advices here :
  5. I did change the location of my music a few months back, not really to save power but to have it more responsive when starting a new playlist. In my case I just put it on my general SSD pool that does: appdata caching transcode tempdir music now It was simpler for me and large enough (4x 500GB in RAID10). The Pool is the best solution in my opinion. Now it would depend on your specific server details to decide if it is a separate pool or something more generic.
  6. There are BTRFS errors : Aug 19 14:06:31 Tower kernel: btrfs_validate_extent_buffer: 1850 callbacks suppressed Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 1 wanted 0xc1a226c5 found 0x6bade2d5 level 0 Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 2 wanted 0xc1a226c5 found 0xee1c9cd7 level 0 Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 1 wanted 0xc1a226c5 found 0x6bade2d5 level 0 Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 2 wanted 0xc1a226c5 found 0xee1c9cd7 level 0 Aug 19 14:06:31 Tower kernel: I/O error, dev loop2, sector 20264160 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Aug 19 14:06:31 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 86, rd 90, flush 0, corrupt 0, gen 0 Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 1 wanted 0xc1a226c5 found 0x6bade2d5 level 0 Aug 19 14:06:31 Tower kernel: BTRFS warning (device nvme1n1p1): checksum verify failed on logical 966566641664 mirror 2 wanted 0xc1a226c5 found 0xee1c9cd7 level 0 Aug 19 14:06:31 Tower kernel: loop: Write error at byte offset 10375249920, length 4096. Aug 19 14:06:31 Tower kernel: I/O error, dev loop2, sector 20264160 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Aug 19 14:06:31 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 87, rd 90, flush 0, corrupt 0, gen 0 Probably to your docker image. You should delete and recreate it. If it continues, you should do a memcheck.
  7. It would be much easier with the diagnostics. But the I/O and BTRFS errors might suggest an issue with a pool.
  8. I think he meant a support thread on the forum. If your thread received no answers, you can bring it back on the first page after a day or two. I would guess that during summer, fewer people are on the forums. So the chances of another user seeing it and being able to help you would be lower. If it is about a docker container, you should probably ask on the container support thread.
  9. I do not click on shorten URL exactly for this reason. And I think that many people act this way.
  10. Could it be a Power Supply issue ?
  11. @Bovin is this solved for you ? If so, what was the issue ?
  12. Also, this should probably have been addressed in General Support rather than in Bug Reports.
  13. This is probably something that should be addressed in the General Support subforum until it is demonstrated that it is indeed a bug.
×
×
  • Create New...