Phase 7 - verify and correct link mkdir mount /dev/disk/by-id/ata-ST33000651NS_Z292V792-part1 /mnt/test -o find /mnt/test -type f -exec grep -binary -quiet 'UnRaid 6 with ddrescue ' \ -print moving disconnected inodes to lost+found. resetting contents of realtime bitmap and summary inodes check for inodes claiming duplicate blocks. process known inodes and perform inode discovery. scan filesystem freespace and inode maps. Remain size: 0 B, remain areas: 0, average rate: 0 B/sĬurrent pos: 143929 MB, run time: xfs_repair /dev/disk/by-id/ata-ST33000651NS_Z292V792-part1 Remaining size: 6385 kB, remaining areas: 1016įilled size: 6385 kB, filled areas: 1016, current rate: 0 B/s Given the amount of time that unraid V6 has been released, I don't understand why I am the first person to run into this, but I am grateful to the community for their generous support in getting it echo -n 'UnRaid 6 with ddrescue ' ddrescue -force -fill=- ~/fill.txt /dev/disk/by-id/ata-ST33000651NS_Z292V792-part1 /boot/WCAZA5082257.ddrescue There is no way I could recover this data without a ddrescue or a similar tool. It appears that only 13 files were affected out of 705. So, do people fire up some virtual machine solution that runs ddrescue? Do they boot another flash drive that runs ddrescue? Is there a different utility that efficiently reads and handles errors like ddrescue does? Some other solution that I am missing? Nobody is denying that this happens, right?
#Use ddrescue gui plus
I must be missing something, because I know that people do have the combination of "broken array" plus "drive with errors" happen.
So my concise question is, with a broken array, and a data drive with errors, what do people do to recover data? Up to this point, I thought ddrescue was the only option, yet ddrescue is missing from unraid V6, something that I view as a basic tool for maintaining storage subsystems when other measures fail. The 4th way to confirm it is the smart report that I attached, below. I've already done the hardware troubleshooting and confirmed that 3 different ways. So I have a known data drive with issues and an invalid parity drive. I may start a new thread to address that. How did it become invalid? The question is not relevant for this thread. What do I mean by broken? The parity drive is not valid.