Rafael

Then I will check this, but for now, my problem was solved and the data recovered! Thank you so much for your help again saved my life.

After destroy log, this is result: And run de Check Again: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.After this, I started the array on normal mode, my disk back to life with all the space used, I believe my media is back, I'm just waiting for the program to check if anything is missing. But I'm looking to this error on my logs: Jul 5 10:19:03 NASHOME kernel: ata5.00: exception Emask 0x50 SAct 0x6 SErr 0x4090800 action 0xe frozen Jul 5 10:19:03 NASHOME kernel: ata5.00: irq_stat 0x00400040, connection status changed Jul 5 10:19:03 NASHOME kernel: ata5: SError: { HostInt PHYRdyChg 10B8B DevExch } Jul 5 10:19:03 NASHOME kernel: ata5.00: failed command: READ FPDMA QUEUED Jul 5 10:19:03 NASHOME kernel: ata5.00: cmd 60/00:08:18:4b:12/01:00:85:00:00/40 tag 1 ncq dma 131072 in Jul 5 10:19:03 NASHOME kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) Jul 5 10:19:03 NASHOME kernel: ata5.00: status: { DRDY } Jul 5 10:19:03 NASHOME kernel: ata5.00: failed command: READ FPDMA QUEUED Jul 5 10:19:03 NASHOME kernel: ata5.00: cmd 60/00:10:d8:ce:f1/01:00:80:00:00/40 tag 2 ncq dma 131072 in Jul 5 10:19:03 NASHOME kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) Jul 5 10:19:03 NASHOME kernel: ata5.00: status: { DRDY } Jul 5 10:19:03 NASHOME kernel: ata5: hard resetting link ata5 is the same HDD with issues before. Do you know what could be happening? And thank you very much for all the help you are giving me, you are saving my life. 😅 nashome-diagnostics-20250705-1115.zip

I try to click on "FIX" and receive this message:

The Check filesystem result: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... 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... sb_ifree 701, counted 700 sb_fdblocks 15208003, counted 22022919 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 2 - agno = 1 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. About the memory, I'm getting a new one, but I've been using it for a few years, with this failure, something annoying, however, it hasn't caused any major problems so far, just minor problems! 🤣

I recently moved to a region with somewhat unstable electrical power. I've been experiencing full blackouts as well as voltage drops below expected levels. About 3 days ago, there was a power outage, and I simply turned the server back on afterward without paying much attention to its state. However, I noticed a constant spin-down and spin-up noise from one of the HDDs, happening every 10–20 seconds. Unfortunately, I didn’t have time to investigate at that moment. Yesterday, I finally checked, and one of the HDDs is showing the error: "Unmountable: wrong or no file system". Coincidentally, this is the same drive that previously had a faulty SATA cable. I replaced the cable, but the error persists. Another issue I noticed is with ErsatzTV, which I use to create IPTV channels. It reports when media files become unavailable, and it’s now showing around 4,000 media files as missing from my total of over 10,000. I checked some of these files manually, and they are indeed gone. I believe they were on the HDD that’s now unmountable. However, shouldn’t Unraid emulate the data in such cases? I’d like to know how to proceed in this situation, and whether it's possible to recover the drive and the missing data. Off-topic: Any recommendations on what kind of UPS I should get to avoid this kind of issue in the future? Does it have to be a pure sine wave model, or can a more basic one do the job? Thank you all for your help. nashome-diagnostics-20250704-1218.zip

What's the best way to get this information? 🤔

Thanks for the reply! So, I've had this memory problem for many years. I believe the Chinese Xeon KIT I bought in December 2022 came with problematic memories, but since it didn't cause me any issues, I simply ignored it until a better time to buy new ones. However, in June 2024, I bought the P2000, and when I did the first installation, I was able to access the drive settings without any issues. At the end of 2024, I couldn't anymore, but I left it aside, since everything was working, and I could have transcoding functionality in docker. I recently took it to better understand the issue, because I wanted to see if I can reduce the energy consumption... So, finally, I decided to send the message here in the thread, because I don't know what else to do. Could it still be related to my memories or motherboard?

Could someone help me with a problem? When I try to access http://[IP]/Settings/nvidia-driver the unraid WebUI freezes for a few minutes, and I can't access the nvidia configuration page, because it keeps loading infinitely. Accessing other pages also becomes impossible after trying to access the settings, because it keeps loading for a certain amount of time, and only after a few minutes the WebUI unfreezes if I have the Nvidia configuration page closed. I don't know what it could be, I've already removed the driver completely, restarted the server, then reinstalled the driver via Community Apps and the issue remains. I can use the GPU normally in my Dockers, but configuring it, choosing a driver, or anything like that requires the driver configuration page. I have two GPUs on the server, a P2000 for transcoding and a simple GT to just be able to plug in a maintenance screen. nashome-diagnostics-20250212-1319.zip

This bug still happens, I'm using q35-2.6 and working.