ArthurL

Hi bumping this up.. what would be my best move next here? Thanks.

Thank. Disk boots up now but welp.. it looks like everything was moved to "lost+found" .. Is there anyway to potentially fix this?

This is the following output of running xfs_repair /dev/md4: Attaching my diagnostics report. Stopped the array, and restarted it again in Maintenance Mode to see if there's any changes.. looks like Disk4 still displays "Unmountable: No file system". @JorgeB - any idea how to proceed here? tower-diagnostics-20240102-1819.zip

Hi @JorgeB - followed your instructions. See attached for the new diagnostics report. For some reason Disk4 is showing "Unmountable: No file system" - I've stopped the array, started it in Maintenance Mode and ran: xfs_repair -nv /dev/md4 These are the results: Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. tower-diagnostics-20240102-1038.zip

Thanks @JorgeB - can you share what would invalidate a parity? I noticed after I had started the array with the new 16TB drives in both Disk1 and Disk4.. my mover started to run shortly after. Not sure if that may have invalidated my parity drive..

Thanke @JorgeB - let me run memtest and see. I recently installed new RAM a few weeks back.. no issues so far. I went from 96GB of RAM to 184GB of RAM.. I didn't get a chance to install the last RAM module because my CPU cooler was blocking the DIMM slot. I had recently tried to rebuild Disk 4 with the new 16GB HDD, with Disk 1 in the current state that it's in. Not sure if that had messed with my parity. I noticed during the rebuild it was reading from Disk 1, while unmountable. Once it was done rebuilding.. it only had 250GB of data on it. Previously it had about 4-5TB on it. I still have my original Disk 4 intact. If you can help share the instructions- would greatly appreciate this. I've just added the original Disk 4 to an external enclosure to try to recover any data that is on it using UFS Explorer. Planning to also do the same for the newly built Disk 1 (16TB). But of what you're saying is true.. then I might be be wrong. Maybe it was confusion on my end. When I was in the process of assigning Disk 4 to the new HDD.. there was only two options.. the original WD disk, and a Seagate 16TB disk. I didn't check serials but I assume the Seagate listed was the newly precleared disk that just finished.

@JorgeB - see attached, thanks. EDIT: Thinking about it.. not sure if this diagnostic file could help since I rebooted the machine a few times and this mishap happened a few days ago.. tower-diagnostics-20231231-2205.zip

Hi all.. I did something really stupid the other night. I was rushing to add 2 new additional drives my array before heading on vacation, but ended up making a noob mistake. Some background, I bought and precleared two new 16TB drives.. we can call them the following: - ZR50KEZD - ZR50THFZ I removed an existing 8TB drive (Disk 1) and replaced it with ZR50THFZ, which was then succesfully rebuilt. I then removed another 8TB drive (Disk 4) and selected what I thought was ZR50KEZD.. but had selected ZR50THFZ instead. For some odd reason, Unraid assigned Disk 1 to ZR50KEZD. This is what I am assuming what happened. I then started the array.. about 20 mins into the rebuild of Disk 4, I noticed Disk 1, which was now ZR50KEZD, gave an error: "UNMOUNTABLE: UNSUPPORTED PARTITION LAYOUT DISK". Now I have essentially 2 disks that are done with 1 parity drive. The original 8TB (Disk 1) drive was wiped.. however my other WD 8TB (Disk 4) drive is still intact. I tried to re-assign Drive 4 to the original disk but it now recognizes it as a new disk. Is there a way to re-assign the original Disk 4 drive, so that I can rebuild Disk 1? Not sure what my options are here. Any help would be greatly appreciated.

This would be great!

Does anyone know why I can't encode the the following files with this tag: H264,MJPEG,MJPEG,MJPEG,MJPEG They're all failing for me. Regular H264 gets encoded just fine.

@SpaceInvaderOne, do you have plans on releasing a guide for Catalina?

Think this might be my first post here.. but I want to say thank you for building this docker. I've been running it the last couple of days and it works just fine. Is there any way you can build notifications into this in the future? A handful of my apps have webhooks into Slack where I get all my notifications. I wouldn't mind getting notifications on when a video file is finished, and how much % of space was saved.