Jump to content

Randommuch2010

Members
  • Content Count

    43
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Randommuch2010

  • Rank
    Advanced Member
  • Birthday 03/07/1996

Converted

  • Gender
    Male
  • Location
    Perth, Australia
  • Personal Text
    Overkill is underrated.

Recent Profile Visitors

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

  1. Started the array normally and most of the lost data is now back, barring a few odd files here and there. Diagnostics attached. tower-diagnostics-20190517-1251.zip
  2. Last few lines of the xfs_repair; "resetting inode 817376329 nlinks from 5 to 3 resetting inode 817376333 nlinks from 4 to 3 Maximum metadata LSN (7:785632) is ahead of log (1:2). Format log to cycle 10. cache_purge: shake on cache 0x5231e0 left 5 nodes!? cache_purge: shake on cache 0x5231e0 left 5 nodes!? cache_zero_check: refcount is 1, not zero (node=0x15319c092410) cache_zero_check: refcount is 1, not zero (node=0x153184091410) cache_zero_check: refcount is 1, not zero (node=0x153184089060) cache_zero_check: refcount is 1, not zero (node=0x15318408ee10) cache_zero_check: refcount is 1, not zero (node=0x15319c00b210) done" Unsure if it usually runs through in only a couple of minutes, disk4 is still showing as unmountable.
  3. Last phase appears to have failed; Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... entry ".." in directory inode 100 points to non-existent inode 538430905 bad hash table for directory inode 100 (no data entry): rebuilding rebuilding directory inode 100 bad hash table for directory inode 140 (no data entry): rebuilding rebuilding directory inode 140 entry ".." in directory inode 141 points to non-existent inode 4050559755 bad hash table for directory inode 141 (no data entry): rebuilding rebuilding directory inode 141 entry ".." in directory inode 16935984 points to non-existent inode 552014935 bad hash table for directory inode 16935984 (no data entry): rebuilding rebuilding directory inode 16935984 bad hash table for directory inode 67099682 (no data entry): rebuilding rebuilding directory inode 67099682 xfs_repair: phase6.c:1376: longform_dir2_rebuild: Assertion `done' failed. Aborted
  4. Phase 1 - find and verify superblock... - block cache size set to 326760 entries Phase 2 - using internal log - zero log... zero_log: head block 271366 tail block 271362 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. Got this back when I attempted to run that command
  5. Attached new diags. tower-diagnostics-20190517-1832.zip
  6. Rebuild has been marked as complete, Disk4 is still showing as "No filesystem" and as a result, I can't run a filesystem check. Only option it's giving me currently is the option to format it. Any ideas?
  7. Whoops, sorry about that! Just hit proceed and it's cracking along with the Parity sync/rebuild as of about two minutes ago. Shares are all immediatly reachable and the data doesn't seem to have disappeared. I'll let it continue running throughout the night and check back in tomorrow. I can't thank you enough for you help!
  8. Including the parity overwrite warning? If so, presumably I'm good to hit "Proceed".
  9. I've entered that into the CLI, and it hasn't spat out any sort of conformation for me, I'm unsure if that's normal or not. It's also still saying "Parity disk(s) content will be overwritten" when I try to start the array. Do I proceed anyway or is there something I'm missing?
  10. The drive I'm trying to replace is an older SeaGate 2TB (ST2000DM001-9YN164_S2F01HQB), and I'm replacing it with the new 3TB Western Digital in the disk4 slot (WDC_WD30EFRX-68EUZN0_WD-WCC4N5DRV984). The problem drive was the SeaGate 2TB, it simply dropped from the array and hasn't recovered. It's not found by the SATA controller on the motherboard, tried swapping power+SATA cables to a known good pair and no joy.
  11. The above diagnostics are from today, I also have a copy of the diagnostics from the 12th of May.
  12. I've got a copy of the diagnostics from three days ago, so I'm not sure if I can somehow use that to recover from my mistakes. It's been a long day and I had a brain fart I've not done anything more since hitting "New Config", as I'm too concerned to risk any more errors on my part. Regarding the backup, there is no backup of the at-risk data, but it is only Movies and TV shows, so it's not the end of the world if it gets lost. I've attached the diagnostics as requested. tower-diagnostics-20190515-1746.zip
  13. Hey everyone, I'm quite inexperienced with Unraid, and seemingly have myself in a bit of a jam. I've had two drives marked as faulty, contents emulated. One of said drives has stopped working entirely and I've swapped the failed 2TB drive for a new 3TB. When trying to start the array to begin a rebuild, I kept getting "Too many wrong disks" error. I've attempted to create a new config but am unsure about data loss and how to recover the files on the drives. Any idea how to undo the new config so I can work on repairing the old setup? TIA
  14. Evening All, I've been having some drama with getting my UnRAID server to allow me to set up VMs. No matter what I do, the VM tab never appears in the GUI. The CPU supports virtualization and everything that needs to be has been enabled in BIOS. Any suggestions? I've attached diagnostics if it's any help. tower-diagnostics-20160903-1720.zip
  15. Don't seem to be having a whole lotta luck. Still pretty new to this sort of thing. Is there any simple way to configure it just to shut down at 10%?