Datrox

Apologies for the delayed response. Had some additional issues with the flash drive that I was finally able to get resolved. Looks like I got lucky this time! Setup a new config, assigned parity/array drives and pools, and successfully restarted the array. Data on all drives seems to have been retained. Running a parity check with corrections now. Will be executing more regular backups. Thanks for your help!

Hello. I'm looking for some guidance on dealing with an accidental deletion of my primary Unraid server's root directory. Summary: While trying to delete some content from one of my pool devices, I executed "rm -rf /*" via the terminal from within the DVR directory of that pool device. When I realized more than that was being deleted (~10 sec) I immediately cut the power to the server. The Unraid flash drive was empty, so I re-installed a (fairly) recent backup and was able to boot back into the server. I did NOT restart the array, as I noticed all of the unassigned devices were showing a size of 0B for the respective partitions. My assumption is that the content of all of the array devices, and all of the pool devices, were deleted as well. Questions: 1. Is it safe to start the array to check if the contents of all of the attached devices were deleted? 2. Assuming that the array and pool devices were wiped, is there any way to undo this from within Unraid? 3. Assuming that Unraid is unable to recover the deleted content, is it viable to attempt data recovery via a 3rd party tool on each device (5 8TB HDDs, 3 SSDs, and 2 NVMes)? Note that I have a "backup" Unraid server where I have previously backed up (via rsync) my user shares, however, the last backup was ~4 months ago and there is a delta of ~5TB between the primary and backup servers. If at all possible, I'm trying to avoid having to re-rip the hundreds of movies/tv since the last backup, never mind having to re-establish the entire primary Unraid server (plug-ins, apps, networking, etc). Any guidance would be most appreciated. Thanks!

Hello, Just wanted to start off by saying I've been running a pair of Unraid servers for a couple of years now. This forum, and SI1's videos, have been extremely helpful with regards to setup and troubleshooting! Kudos to this community! I picked up a few factory new 14TB disks recently and wanted to upgrade my parity drive from 8TB to 14TB, so I can add the other 14TB drives to the array. I leveraged chatGPT to generate a procedure for upgrading the parity drive, as well as adding the old parity drive to the array. After several prompts, the following procedure was provided. Looking to see if this procedure is accurate before I proceed. Any and all feedback is appreciated! ---chatGPT response--- 1. Backup Data: Before making any changes, it's crucial to back up your important data. While the process should be safe, there's always a risk when dealing with storage configurations. 2. Preclear the New 14TB Drive: Connect the new 14TB drive to another computer and perform a preclear using the Unraid Preclear plugin. This process involves writing zeroes to the entire disk, followed by a read verification pass. This helps identify any potential issues with the drive before it is put into active use. 3. Power Down: Once the preclear is complete and you've verified that the new 14TB drive is in good condition, shut down your Unraid server properly. 4. Replace Parity Drive: Physically remove the old 8TB parity drive and install the new 14TB drive in its place. 5. Boot Up: Power on the server. 6. Access Web Interface: Access the Unraid web interface from a computer on the same network. 7. Assign New Parity Drive: Go to the 'Main' tab in the web interface. You should see the new 14TB drive listed as an "Unassigned Device". Click on it and assign it as the new parity drive. 8. Start Parity-Sync: After assigning the new drive as the parity drive, Unraid will automatically start a parity-sync operation. This will take some time, during which the data on the new drive will be synchronized with the data on the other drives. 9. Verify Parity-Sync Completion: Wait for the parity-sync process to complete. You can monitor the progress in the Unraid web interface. 10. Add Old Parity Drive to Array: Once the parity-sync is complete and you've verified that the new parity drive is working correctly, you can add the old 8TB drive back to the machine. - Physically install the old 8TB drive back into the server. - Go to the 'Main' tab in the web interface. - You should see the old 8TB drive listed as an "Unassigned Device". Click on it and assign it as a data drive (not as parity). 1. Start Array: After adding the old drive to the array, click the 'Start' button to start the array. 2. Data Rebuild: Unraid will now start a data rebuild process, where it will redistribute the data across all the drives, including the newly added 8TB drive. 3. Verify Array Operation: Once the data rebuild process is complete, verify that all your data is accessible and that the array is functioning as expected.

Just wanted to say that I'm experiencing a similar issue to KrypticKahos. I recently ripped the same file (3.2 GB) from the same DVD disc using the same optical drive on two different computers with extremely different results: Windows 10 PC - MakeMKV v1.16.3 - Optical drive connected to a SATA III port on motherboard - Output file saved to SSD connected to SATA III port on motherboard - Read rate: unsure of average rate, but kept increasing during the course of the rip to a max of 14.3x by the end of the rip - Elapsed time: 4:13 Unraid server: - MakeMKV v1.16.3 (Djoss MakeMKV docker) - Optical drive connected to a SATA I port on PCI add-on card - Output file saved to SSD (cache-only) connected to SATA III port on motherboard - Read rate: Reached a max rate of 2.5x, but averaged ~1.8x throughout most of the rip - Elapsed time: 38:39 (~9 times longer to rip than on the Windows 10 PC) * All other dockers were stopped for this test and no other data transfers were occurring on that server I initially suspected that the optical drive being connected to the SATA I port was the issue. However, SATA I has a "theoretical" max transfer rate of ~150 MB/s. The rip on the Unraid machine was averaging ~ 2.4MB/s, which should have had a lot more headroom. Any idea if the SATA I connection is the cause for the significant delta? Or if there's an obvious (not to me) alternative explanation for that extreme difference? Thanks! Paul

I'm experiencing the same issue. I have two servers, one on 6.8.3 (no issue) and the other on 6.9.2 (issue). 6.8.3 server 6.9.2 server