TekWarfare

Started the array and the files are still not showing, unfortunately. Like I said, the folders and files are visible when viewing in Unraid. In fact, I've just downloaded a file via the webui and it works perfectly fine. It's just that they've disappeared in file explorer. Do you reckon it's a permission issue? Owner and permission are quite different to other folders on the same disk Did some further logic checking and it seems that any sub-folder with the owner of nobody doesn't show, whilst the owner of admin does. See this in the second screenshot. So I'm thinking batch change the owner and permission, but this comment here suggests just using the new permissions tool within unraid:

Hi JorgeB! Thank you for replying. I want to mention that my TV and Movie shares were symbolically linked under my Media share using: ln -s /mnt/user/Movies Movies ln -s /mnt/user/TV TV I'm not sure if that has anything to do with it. I did try deleting and recreating the symbolic link to no effect. I also tried mapping the TV share directly but the files are still not there. Anyway, I ran the check as you asked, and here is the output: 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 and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - 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 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done I have then downloaded the diagnostics and attached them here. As the drive was xfs I started in maintenance mode. Should I stop the array, start it in normal (non-maintenance mode) and see if the files are there? Thanks for your help fatal1ty3-diagnostics-20240206-1855.zip

We just had a power outage so the server shutdown immediately. After bringing it back online I'm starting the array with a parity check. Strangely, many of the TV shows stored on Disk 1 are not showing under file explorer in Windows (and plex won't play them or other files that are visible). The shows and files do appear under the disk explorer in Unraid though. Shown this in the attached screenshot. Are there certain steps I should take to fix this? Appreciate any advice :) fatal1ty3-diagnostics-20240205-2038.zip

Rebuild finished successfully. I was confused as to why I couldn't connect to mapped network drives afterwards, but soon realized it was because I started the array in maintenance mode. Thank you for the help, JorgeB. 🙂 Is it fine to remove the offending disk from Historical Devices? Same with the cache drive in the attached picture. There's no point keeping either any more is there?

Replaced the SATA cable to PARITY now. Ran SMART short self-test on all disks, but had to reboot due to "Array Stopped Stale Configuration" bug in Firefox. Rebooted and used Edge. Diagnostics after starting array attached. BIGBOX-diagnostics-20230317-1917.zip

Thank you for the guidance, JorgeB. I left the array started overnight - not performed any of the rebuilding steps yet - and now Parity disk has increased UDMA CRC errors from 6 (before shutdown in OP) to 10 (now). It's the exact same cable as the one used by DISK 1 so looks like they've both gone funny at the same time, or I've accidentally knocked PARITY's SATA cable when re-doing DISK 1's. I'm going to shutdown the server and give PARITY a new cable too. Then I'll perform a SMART shot self-test and post the results I guess.

Attached diagnostics after array start - bought the licence BIGBOX-diagnostics-20230316-2100.zip

Ran a SMART short self-test and attached the SMART report. Also included new diagnostics file after reboot, but not array start BIGBOX-diagnostics-20230316-2049.zip BIGBOX-smart-20230316-2047.zip

Just received the following two e-mail notifications: Event: Unraid Disk 1 error Subject: Alert [BIGBOX] - Disk 1 in error state (disk dsbl) Description: WDC_WD120EDAZ-11F3RA0_5PG85VEF (sdd) Importance: alert Event: Unraid array errors Subject: Warning [BIGBOX] - array has errors Description: Array has 1 disk with read errors Importance: warning Disk 1 - WDC_WD120EDAZ-11F3RA0_5PG85VEF (sdd) (errors 9) I've re-named my server to BIGBOX in the e-mails so I'm not publicly declaring my server name. My understanding is that this is likely (and hopefully) a power or SATA cable issue. As such, I've attached the diagnostics file now before doing anything. Question 1: Am I correct in doing the following?: A. Shutdown server B. Replace SATA and/or Power cable - even reseating SATA cable in different SATA port C. Power on server D. Follow the instructions here: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself Question 2: Following the rebuild steps, the preamble states "There can be cases where it is determined that the reason a disk was disabled is due to an external factor and the disk drive appears to be fine." How do I determine the disk is "fine"? That it shows up under Main after a reboot? Question 3: I'm running an expired trial, and I believe Unraid won't allow me to start the array after a reboot. Is there any way around this for the time being? DISK 1 primarily stores TV shows. I've checked nearly 10 shows at random at various seasons and episodes and they all playback perfectly. Question 4: Is this data being inferred on-the-fly by the difference between the remaining Parity and Data disks? Question 5: Accordingly, am I fine to copy a few important files and folders over SMB? (I am aware of having backup plans) I greatly appreciate any help in the matter. BIGBOX-diagnostics-20230316-1448.zip

So I made an attempt to do this before I followed your advice and it resulted with all my files being placed in a "lost+found" folder on the 'replacement' drive. I did have to run a file system repair with -l, -n and no switch as before that it was complaining of no file system. As this rebuild was meant to write on a per-sector level I assumed it would have restored data in its original form - how it was back when I did the parity sync. This hasn't been the case. I'm at a loss as to what it has actually been doing for the past day then. Is there a way to rebuild the array again so my files are in the correct location?

Followed your advice and it's started the rebuild process. Easier than I thought it would be. Could I wipe the disk (in a Windows system) once I've unassigned it? The idea being that I'm 100% sure the data is gone and can fully evaluate the recovery process. Or, is this superfluous; does the rebuild process write at a sector level? Thank you very much for your help, itimpi 🙂

I've got three WD 12TB disks: 2 data and 1 parity. I would like to stage a hard drive failure to test both the rebuild process and how well the information is restored. Is it possible to lose a parity disk and rebuild that? As far as I'm aware it would be one of the data disks I would have to wipe If anyone could guide me through the process of emulating a HDD failure I would be extremity grateful. Thanks in advance