graywolf

Members
  • Posts

    675
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Location
    NC

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

graywolf's Achievements

Enthusiast

Enthusiast (6/14)

5

Reputation

  1. I know I am far behind the times with upgrading unRaid. Anything I should be aware of in doing the upgrade? Advice on best method to perform upgrade and what to do in order to perform backout if it goes wrong? How long would an upgrade take? Is the GO file still valid for setting up aliases and creating a tmp file to update crontab to run scripts (i.e. crontab /tmp/file) Have array stopped before upgrading? Any other tips to help it go smoothly?
  2. So even with the 128 Read errors on disk20 the rebuilt disk11 should be good? What should I do about the 1 Current Pending Sector on disk20? I'll have to get another 12TB drive for dual parity, I'll work getting another one What would be best approach in future prior to replacing parity or data drives? Ensure dockers don't stop Ensure nothing writes to disks (downloads, etc) What else?
  3. Disk rebuild just finished 18hrs 35mins 35secs 128 errors Disk11 returned to normal operation Current diagnostics attached Disk20 showing 1 Current Pending Sector tower-diagnostics-20211201-1346.zip
  4. Disk11 showed error on Dashboard with 48 reallocated sectors and a bunch of raw read errors. Since I wanted to replace a 6TB with an 8TB drive I picked that one. Disk6 has 1 reallocated sector. Disk20 showed as Healthy on the Dashboard before the disk11 rebuild. I have the original disk11, but there have been writes to the array.
  5. Diagnostics attached. So is the rebuild messed up and I need to try again? Replaced a 6TB drive with an 8TB drive, currently 3.40 TB into the rebuild tower-diagnostics-20211201-0125.zip
  6. I think I probably need to replace the SeaGate (Disk11) drive but unsure about the HGST (Disk6) drive. Advice would be appreciated. tower-smart-20211126-1608.zip tower-smart-20211126-1610.zip
  7. Another question. If I stop the ddrescue Scraping Failed Blocks then mount the destination disk. If I do the ddrescue fill command to find out what is corrupted, would I be able to unmount the destination disk and restart the ddrescue Scraping Failed Blocks if there are any files I still want it to try recovery? Asking because it looks like it might be days still for the 2nd pass
  8. Once I'm done with ddrescue, it talks about being a good idea to run a file system check on the destination drive. How do I do that for a XFS disk? Do I mount it before the file system check or leave it unmounted? About how long should a file system check run on a 6TB drive (if size of disk matters)?
  9. Could I stop the ddrescue scraping failed blocks, then mount the destination drive to check on a couple files (and maybe copy them to another drive), then stop array, unmount the drive, and then restart ddrescue again?
  10. What should I do now at this point? ddrescue: Input file disappeared: No such file or directory looks like the source disk went offline?
  11. "ddrescue -f --fill=- ~/fill.txt /dev/sdY /boot/ddrescue.log" What if a bad sector did not have any file(s)? does it create a file and fill it with the text?
  12. I read that after ddrescue completes it's thing that "After the clone is complete you can mount the destination disk manually" What would be the command to do that? I don't have UD plugin installed And would mounting the disk be the same as adding it to the array? (no parity currently)
  13. Interesting. Just to clarify, if a video file did play, the visible corruption would be because of the bad blocks anyways and not the addition of the text from the ddrescue fill cmd? Otherwise, is there another method other than adding the text with the ddrescue --fill to correlate the bad blocks with the files?
  14. so "ddrescue -f --fill=- ~/fill.txt /dev/sdY /boot/ddrescue.log" will add the text inside the file that has bad blocks but if I understand correctly, that shouldn't matter for any type of file (txt, pdf, jpg, mkv, etc) since that file is corrupted anyways and would not open/play correctly. Is that correct?
  15. I set it up last month, prior to Nov 6th Parity Check which ran without issue. Never saw anything for Disk18 until the Parity-Resync when I tried to replace the Parity drive with a larger drive. Unfortunately stuff had written to the array during that process so the old parity drive wouldn't be usable.